libcroco wishes #1

I'd be looking to use the SAC API, so that's the primary focus of
my thoughts here.

* Robust parsing - should be capable of recovering - or trying to recover -
  after fatal error.
  The simplest regime for this would be on a fatal error to emit an
  error message, find the next "}", emit a message "skipping to line/char"
  and try to resume parsing after it.  But maybe we can do better.

* Messages should identify where they come from (file/line/col).
  This applies both to normal events and errors.

* Robust recovery from lesser errors
  e.g. if a value field is malformed, remaining rules in the ruleset
  should still be parsed.

* fragment parsing - e.g. for inlined styles

and one that could be implemented at a higher level:

* Parsing of property values to an O-O representation
  e.g. a box has position, size and colour attributes.
  colour has RGB, hex and (sometimes) tokenised representations.



-- 
Nick Kew

Received on Tuesday, 2 March 2004 11:31:55 UTC