Re: hyphenating non-english characters

2024-08-01 Thread Werner LEMBERG

> Unfortunately, I got stuck at this point, as the hyphenation file
> that I used is encoded in latin1.  Sorry for not including it, this
> is the place I got the file from:
> https://ctan.org/tex-archive/language/hungarian/hyphenation

These patterns are very outdated.  The current version of the patterns
(which is a file larger than a whopping 500kByte) is part of the
'tex-hyphen' bundle and can be found, among other places, in the
TeXLive git repository at

  
https://git.texlive.info/texlive/tree/Master/texmf-dist/tex/generic/hyph-utf8/patterns/tex/hyph-hu.tex

> Another weird thing is, while it does contain the á,é,í,ó,ö and ü
> characters, it omits the ő and ű characters entirely.

The abovementioned file is encoded in UTF-8, which you have to convert
to Latin2 by doing, for example,

```
iconv -f utf8 -t latin2 < hyph-hu.tex > hyph-hu.latin2.tex
```


Werner


Knuth Plass

2024-08-01 Thread Douglas McIlroy
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 sets type inside a circle given as a
prcomputed list of line lengths. The way one would specify a circle in
groff would be as a self-perpetuating lined trap that runs an incremental
circle generator, How do you deal with this inextricable admixture of
format-specification and line-breaking?

Circle-filling is rare, but it is just an extreme case of wrapping around a
figure inserted at a trap location, which is not unusual.

A second concern is about K-P and unjustfied text, which I have come to
prefer. K-P typesetting then gives every paragraph a different apparent
width. In my experience this is typically more objectionable than results
from plain old greedy line filling. (Of course I expect the latter to still
be available.)

Doug