Hi Walter, At 2023-09-11T19:45:30+0200, Walter Alejandro Iglesias wrote: > On Mon, Sep 11, 2023 at 07:18:59PM +0200, Walter Alejandro Iglesias wrote: > > I normally use OpenBSD in my desktop, which still comes with groff > > 1.22.4. Today I booted an old laptop with Debian testing (Devuan to > > be more precise) and, after updating it, I could finally test groff > > 1.23. > > > > Lately, as I mentioned in this same list months ago, instead of the > > conventional hyphenation method (my documents are in UTF-8 Spanish),
This suggests to me that preconv(1) _must_ be run before you try to process your documents with this technique. > > I've been using an application I wrote myself to generate a file > > with entries like this: > > > > .hw a-ba-co > > .hw ár-bol > > .hw ca-ba-ña > > [...] > > > > Also UTF-8 encoded. > > > > I save those entries to a file called "hyphen.tr" and I source it > > from my groff document: > > > > .mso hyphen.tr > > > > 1.23 output (under Debian) seems to be identical to 1.22 (under > > OpenBSD), I see no issue in the PDF, both have the same words broken > > in the same syllables, that's why I don't understand why 1.23 throws > > me hundreds of lines of error like the following: > > > > troff:/home/morlock/Documents/Roquesor/Groff/tmac/hyphen.tr:8777: > > error: expected ordinary or special character, got an escaped '%' > > > > I took a look to the hyphen.tr file and didn't find no '%' > > character. > > > > Someone have any idea what happens here? > > If instead of sourcing hyphen.tr from my macros with .mso I source it > directly from the roff document with .so those error messages desapear. Please share input file(s) that reproduce the problem, and a command line that produces the diagnostic message you quoted above. Regards, Branden
signature.asc
Description: PGP signature
