Vincent Hennebert wrote:
I'd have to think more about it, but:
- perhaps the compareNodes method should compare the line/page numbers
for each node rather than the index in the Knuth sequence. Or some
mixing of the two.
The index can tell us which node allows to lay out more content, the
Hi Luca,
Luca Furini a écrit :
snip/
1) TextLM breaks the text even when a / or a - is found, handling
them as hyphenation points with the usual sequence of glue + penalty +
glue elements.
The LineLM tries, in the first instance, to avoid using hyphenation
points, so the penalty is not
Hi guys,
J.Pietschmann a écrit :
Simon Pepping wrote:
Would this be a good moment to make these features of the breaking
algorithm user configurable, like they are in TeX? This allows people
to play with the various possibilities without having to modify the
code.
This can be combined with
On Wed, Dec 06, 2006 at 12:19:01PM +0100, Luca Furini wrote:
Simon Pepping wrote:
Would this be a good moment to make these features of the breaking
algorithm user configurable, like they are in TeX? This allows people
to play with the various possibilities without having to modify the
On Wed, Dec 06, 2006 at 03:46:54PM +0100, Vincent Hennebert wrote:
Luca Furini a écrit :
Vincent wrote:
I don't follow you: IIUC the glue-penalty-glue triplet is generated only
the second time, when the first breaking doesn't give acceptable
results? What do you mean by the penalty is
On Dec 6, 2006, at 20:39, Simon Pepping wrote:
Hi folks,
On Wed, Dec 06, 2006 at 12:19:01PM +0100, Luca Furini wrote:
snip /
I agree with you that it would be good to have them configurable.
Your idea is to put them in the configuration file or in the fo file
itself? At the moment, my
Chuck Bearden wrote:
If in a left-aligned block some typical text words are followed by a string
longer than the line-length and containing no spaces (e.g. a long URL), then the
foregoing text will have premature line breaks, i.e. halfway to two-thirds the
way into the line.
I had a look at
Simon Pepping wrote:
Would this be a good moment to make these features of the breaking
algorithm user configurable, like they are in TeX? This allows people
to play with the various possibilities without having to modify the
code.
Probably, if this can be combined with implementing UAX14.