Gecko [ lorencats.com ]

Name	Size	Permission
AUTHORS	2.31 KB	-rw-r--r--
Cache.txt.gz	2.35 KB	-rw-r--r--
Cookies.txt	2.35 KB	-rw-r--r--
Dillo.txt	3.51 KB	-rw-r--r--
Dpid.txt.gz	3.83 KB	-rw-r--r--
Dw.txt	217 B	-rw-r--r--
HtmlParser.txt	3.54 KB	-rw-r--r--
IO.txt.gz	7.49 KB	-rw-r--r--
Images.txt.gz	1.79 KB	-rw-r--r--
Imgbuf.txt.gz	2.64 KB	-rw-r--r--
NC_design.txt.gz	1.91 KB	-rw-r--r--
NEWS.Debian.gz	299 B	-rw-r--r--
NEWS.gz	494 B	-rw-r--r--
README	2 KB	-rw-r--r--
README.Debian	351 B	-rw-r--r--
Selection.txt.gz	2.16 KB	-rw-r--r--
changelog.Debian.gz	6.89 KB	-rw-r--r--
changelog.gz	35.04 KB	-rw-r--r--
copyright	2.38 KB	-rw-r--r--
dillorc.gz	5.14 KB	-rw-r--r--
dw-changes.doc	3.95 KB	-rw-r--r--
dw-example-screenshot.png	3.72 KB	-rw-r--r--
dw-images-and-backgrounds.doc....	2.73 KB	-rw-r--r--
dw-layout-views.doc.gz	3.22 KB	-rw-r--r--
dw-layout-widgets.doc.gz	3.24 KB	-rw-r--r--
dw-map.doc	2.19 KB	-rw-r--r--
dw-overview.doc.gz	1.8 KB	-rw-r--r--
dw-size-of-widget.png	2.76 KB	-rw-r--r--
dw-style-box-model.png	5 KB	-rw-r--r--
dw-style-length-absolute.png	756 B	-rw-r--r--
dw-style-length-percentage.png	1.08 KB	-rw-r--r--
dw-style-length-relative.png	1.06 KB	-rw-r--r--
dw-textblock-collapsing-spaces...	641 B	-rw-r--r--
dw-textblock-collapsing-spaces...	521 B	-rw-r--r--
dw-textblock-collapsing-spaces...	802 B	-rw-r--r--
dw-textblock-collapsing-spaces...	586 B	-rw-r--r--
dw-usage.doc.gz	3.79 KB	-rw-r--r--
dw-viewport-with-scrollbar.png	755 B	-rw-r--r--
dw-viewport-without-scrollbar....	542 B	-rw-r--r--
dw-widget-sizes.doc.gz	2.44 KB	-rw-r--r--
fltk-problems.doc.gz	1.75 KB	-rw-r--r--
index.doc	1.37 KB	-rw-r--r--
lout.doc	3.06 KB	-rw-r--r--
rounding-errors.doc	909 B	-rw-r--r--
uml-legend.doc.gz	1.46 KB	-rw-r--r--
user_help.html	13.66 KB	-rw-r--r--

Code Editor : HtmlParser.txt

October 2001, --Jcid
 Last update: Jul 2009

---------------
                        THE HTML PARSER
                        ---------------

Dillo's  parser is more than just a HTML parser, it does XHTML
and  plain  text  also.  It  has  parsing 'modes' that define its
behaviour while working:

typedef enum {
     DILLO_HTML_PARSE_MODE_INIT = 0,
     DILLO_HTML_PARSE_MODE_STASH,
     DILLO_HTML_PARSE_MODE_STASH_AND_BODY,
     DILLO_HTML_PARSE_MODE_BODY,
     DILLO_HTML_PARSE_MODE_VERBATIM,
     DILLO_HTML_PARSE_MODE_PRE
   } DilloHtmlParseMode;

The  parser  works  upon a token-grained basis, i.e., the data
stream is parsed into tokens and the parser is fed with them. The
process  is  simple:  whenever  the  cache  has new data, it is
passed to Html_write, which groups data into tokens and calls the
appropriate functions for the token type (tag, space, or word).

Note:   when  in  DILLO_HTML_PARSE_MODE_VERBATIM,  the  parser
doesn't  try  to  split  the  data stream into tokens anymore; it
simply collects until the closing tag.

------
TOKENS
------

* A chunk of WHITE SPACE     --> Html_process_space

* TAG                        --> Html_process_tag

The tag-start is defined by two adjacent characters:

first : '<'
      second: ALPHA | '/' | '!' | '?'

Note: comments are discarded (  )

The tag's end is not as easy to find, nor to deal with!:

1)  The  HTML  4.01  sec.  3.2.2 states that "Attribute/value
    pairs appear before the final '>' of an element's start tag",
    but it doesn't define how to discriminate the "final" '>'.

2) '<' and '>' should be escaped as '&lt;' and '&gt;' inside
    attribute values.

3)  The XML SPEC for XHTML states:
      AttrValue ::== '"' ([^<&"] | Reference)* '"'   |
                     "'" ([^<&'] | Reference)* "'"

Current  parser  honors  the XML SPEC.

As  it's  a  common  mistake  for human authors to mistype or
    forget  one  of  the  quote  marks of an attribute value; the
    parser   solves  the  problem  with  a  look-ahead  technique
    (otherwise  the  parser  could  skip significant amounts of
    properly-written HTML).

* WORD                       --> Html_process_word

A  word is anything that doesn't start with SPACE, that's
    outside  of  a  tag, up to the first SPACE or tag start.

SPACE = ' ' | \n | \r | \t | \f | \v

-----------------
THE PARSING STACK
-----------------

The parsing state of the document is kept in a stack:

class DilloHtml {
     [...]
     lout::misc::SimpleVector<DilloHtmlState> *stack;
     [...]
  };

struct _DilloHtmlState {
     CssPropertyList *table_cell_props;
     DilloHtmlParseMode parse_mode;
     DilloHtmlTableMode table_mode;
     bool cell_text_align_set;
     DilloHtmlListMode list_type;
     int list_number;

/* TagInfo index for the tag that's being processed */
     int tag_idx;

dw::core::Widget *textblock, *table;

/* This is used to align list items (especially in enumerated lists) */
     dw::core::Widget *ref_list_item;

/* This is used for list items etc; if it is set to TRUE, breaks
        have to be "handed over" (see Html_add_indented and
        Html_eventually_pop_dw). */
     bool hand_over_break;
  };

Basically,  when a TAG is processed, a new state is pushed into
the  'stack'  and  its  'style'  is  set  to  reflect the desired
appearance (details in DwStyle.txt).

That way, when a word is processed later (added to the Dw), all
the information is within the top state.

Closing TAGs just pop the stack.

${this.title}

Code Editor : HtmlParser.txt