Bernard wrote, "My work on the knuth-plass branch is also interesting,"
I'd love to hear how you approach that. All I could think of is really
heavy-duty dynamic programming that replicates almost the full internal
state of groff in every path.
As one example, the K-P paper set
On 7/8/23, Bertrand Garrigues wrote:
> If people are interested I may try to find some time to work on it.
Bertrand,
I'm very interested and excited by the mock-up you have so far. I
know your time is in short supply, but I'd highly appreciate any that
you're able to devote to this.
On 7/8/23
I hate to keep raining on the persistent dream of K-P in groff, but it
fits poorly with troff's basic typesetting model. How will it deal
with line-length changes that pop up in the middle of a paragraph, due
to requests that can come inline or from a macro, perhaps triggered by
a trap? K-P faces
.
[...]
> I'll note that even if K-P can't be done this way, because the algorithm
> requires a view of more than one page at a time
Indeed, I don't think it's possible to implement Knuth-Plass in a macro
package, it's already very difficult to implement it into tre
Hi Deri,
I understand the main problem with type 1 fonts is the 256 glyph
> restriction with pdfs, there is no such restriction in the font itself, I
> have Japanese type 1 fonts with more than 18000 glyphs which can be used in
> pdfs. Type 1 is dumber than more modern formats, but the glyphs them
On Tuesday, 23 May 2023 20:15:33 BST G. Branden Robinson wrote:
> I've tried a couple of times to start reading this, but the font is
> so fantastically ugly that it's making my brain wander off.
>
> Screenshot attached.
>
> Does the PDF not embed the font it's expecting? What is causing the
> i
one this way, because the algorithm
requires a view of more than one page at a time (I, uh, admit I haven't
actually learned how Knuth-Plass works yet), then the foregoing might
still be worth doing for widow and orphan management.
> If you are interested in micro typography there was an
On 5/8/23, Douglas McIlroy wrote:
> K-P would not be a mere add-on to groff. K-P knows in advance the
> shape of the space into which a paragraph must fit, but groff doesn't.
> This means a whole lot of groff state must be carried along with the
> K-P dynamic program.
I don't doubt your analysis
K-P would not be a mere add-on to groff. K-P knows in advance the
shape of the space into which a paragraph must fit, but groff doesn't.
This means a whole lot of groff state must be carried along with the
K-P dynamic program. The latter merely needs to keep a set of
candidate line-break points.
F
On 5/6/23, G. Branden Robinson wrote:
> Myself, I wonder if K-P couldn't be implemented above the formatter
> itself, using a diversion. We could then put the implementation in an
> auxiliary macro package. Since I have plans to attack our facilities
> for diversion re-processing anyway, it migh
latively innocuous. The occasional
> > > pitch on this mailing list for paragraph awareness is far less so.
> >
> > If you're referring here to changing groff's line-by-line processing
> > to paragraph-at-once processing (via Knuth-Plass or similar
> >
ere to changing groff's line-by-line processing
> to paragraph-at-once processing (via Knuth-Plass or similar
> algorithm), that's a central part of groff's 2014 mission statement
> (http://www.gnu.org/software/groff/groff-mission-statement.html, where
> it's billed as an
|
> |I've started to work on Knuth-Plass algorithm last year, I've written
>
> That is pretty cool and good news for GNU roff!
Well, there is a long road before finishing this work, and I hope I can
complete it after the next release, probably next year.
> Congratulations!
Sorry, hit the wrong button!
-- >8 -- >8 -- Forwarded message -- 8< -- 8< --
Date: Thu, 09 Nov 2017 16:33:52 +0100
From: Steffen Nurpmeso
To: Bertrand Garrigues
Cc: Ingo Schwarze
Subject: Re: [Groff] Knuth-Plass Algorithm
Bertrand Garrigues wrote:
..
|Hmm... Bug #40716 &quo
ff's features and plans stated in the mission statement like
>> Knuth-Plass algorithmy for paragraph-based linebreaks, native support
>> for TrueType, Open Type, and other non-Type1 PostScript fonts, and
>> improving Unicode support ?
>
> Nothing. Setting up a missio
15 matches
Mail list logo
