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 l
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:
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 preference wo
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 "t
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 th
Luca Furini a écrit :
> Vincent wrote:
>
>>> The LineLM tries, in the first instance, to avoid using hyphenation
>>> points, so the penalty is not taken into account. But this has the side
>>> effect of using the first glue element as a feasible break (if the
>>> penalty were a feasible break too,
Vincent wrote:
The LineLM tries, in the first instance, to avoid using hyphenation
points, so the penalty is not taken into account. But this has the side
effect of using the first glue element as a feasible break (if the
penalty were a feasible break too, it would surely be a better one, such
a
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.
I agree with you that it would be good to have them configurab
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 combin
Hi Luca,
Luca Furini a écrit :
> 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
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.
J.P
On Tue, Dec 05, 2006 at 01:23:45PM +0100, Luca Furini wrote:
> 3) At the moment, the LineLM can call findBreakingPoints() up to three
> times, the last one with a maximum adjusting ratio equal to 20. I came to
> the conclusion that this is really TOO much. I tried stopping after the
> second cal
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 th
12 matches
Mail list logo
