Hi committers,
as you probably noticed, i started to rummage around in
Bugzilla, searching for bugs still in existence and learning
more about current and persistent problems.

Apart from the keep-* problem there are the following issues:
- Other unimplemented or incompletely implemented elements
  and attributes. In particular:
   o fo:table-and-caption because DocBook uses this
   o fo:inline-container
   o common properties of fo:inline
   o whitespace handling attributes
   o a few shorthands
- Height/BPD of block elements other than table.
- Padding for fo:block (and perhaps other block elements)
- Margins for tables, if that's a bug (see recent posts)
- Better error reporting, in particular:
   o Report structure violations properly (for example don't
     drop fo:table-rows which are not children of
     fo:table-(body|header|footer) silently)
   o Notify about attributes which shouldn't be there or
     are not implemented. Currently, this is horribly
     inconsistently handled.
   o A few more sensible messages for attributes that are
     missing. I think, if a master-reference is missing,
     claiming it has no proper value is misleading.
- Link hotspots. I think i have some unique bug reports
  to contribute in addition to the respectable set already
  in place :-)
- Text loss near fo:inline and -horror!- character references!
- Image scaling.
Not yet in Bugzilla, i think:
- Problems with properties of hypenated words (many
  are only applied to the last part).
- conditional-page-master last
- Clipping (overflow="hide" or something)
Probably further down the ToDo list:
- Better handling of forward ref page-number-citations
   (reformat line or something). Hopefully solvable locally.
- Sensible algorithm to handle leader-length.maximum="100%",
   perhaps combined with point above. Should be localised
   to a line, therefore only moderatly hard. This is definitely
   a "must have".
- PDF extensions, like encrypting. Perhaps integration with some
   other project.

I think i'll leave Bugzilla alone until the next bug summary
next weekend.

Questions:
Will there be another maintenance release before something comes
out of the redesign?
If so, when? Roadmap?
If so, which should be the problems solved? Pick from above or
add whatever you think should be added.

Further question: Is the duplicate id bug fixed in all its
incarnations?

Oops: The FAQ goes along slowly, as usual. Converted to the
FAQ-with-sections DTD referenced recently on the forrest-dev
list.

Thanks
J.Pietschmann


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to