Re: Extensions for hyphenation

Hi!

Sorry for cutting this a bit off, but I'd like to suggest the
following steps:

1. Concentrate on the next release, with hyphenation support. Which
issues are open? I recall these: (a) How to deal with the pattern
files, and (b) tables. Did I forget something? Are there some pages
not rendering which were rendering before?

For dealing with tables, see below, step 2 (after step 3).

3. Floats: will not be part of the next release, but I'd like to
finish this rather soon; this has been delayed already long enugh.
(There has been some progress, BTW, see
<http://flpsed.org/hgweb/dillo_floats_geerken>.)

2. How to deal with tables?

a) I've pushed my changes regarding extremes calculation to
<http://flpsed.org/hgweb/dillo_hyphen>, but I'd like to push it into
the main repository as soon as possible. The current state has some
bugs, but I hope it should be stable soon.

This is, BTW, generally some cleanup and so useful independent of this
special purpose. (Might be even somewhat faster than the old
implementation.)

b) I'd like to use it for my approach: not using hyphenation for
calculation the extremes, but of course, using hyphenation when
breaking lines (also in table cells). This gives us:

(i) full advantages of hyphenation;

(ii) no risk regarding table rendering: table columns will be the same
as before, and similar to other browsers (without hyphenation), so the
problems Jorge mentioned will not occure;

(iii) finally, this would make one bug obsolete:

| **Incorrect calculation of extremes:** The minimal width of a text
| block (as part of the width extremes, which are mainly used for
| tables) is defined by everything between two possible breaks. A
| possible break may also be a hyphenation point; however, hyphenation
| points are calculated in a lazy way, when the lines are broken, and
| not when extremes are calculated. So, it is a matter of chance whether
| the calculation of the minimal width will take the two parts "dil-"
| and "lo" into account (when "dillo" has already been hyphenated), or
| only one part, "dillo" (when "dillo" has not yet been hyphenated),
| resulting possibly in a different value for the minimal width.

(See "dw-line-breaking.doc" for more. This would leave only "low
priority" issues.)

After the release, other approaches could be discussed.

Comments and thoughts?

Regards
Sebastian