Follow-up Comment #6, bug #66919 (group groff): At 2025-03-18T02:00:43-0400, G. Branden Robinson wrote: > And that's how I fix the bug you're reporting.
Or, rather, how I correct the input document to not assume an
English-language document can spell words using non-English letters and
make assumptions about how they will undergo hyphenation.
I promptly realized I can go one better. Because `\[~o]` is equivalent
to õ under groff's hood, we don't even need to invoke `hcode` with a
special character as the first argument. You get the desired
hyphenation (and groff-tradition) automagically.
$ iconv -f iso-8859-1 ATTIC/66919d.groff
.ll 1n
lanteronial
.pchar \[~o]
lanter\[~o]nial
.\" Now let's pretend we speak Portuguese.
.hcode õ o
.pchar \[~o]
lanter\[~o]nial
$ ./build/test-groff -a -Wbreak ATTIC/66919c.groff
<beginning of page>
lantero<hy>
nial
special character "~o"
is not translated
does not have a macro
special translation: 0
hyphenation code: 0
flags: 0
ASCII code: 0
asciify code: 245
is found
is transparently translatable
is translatable as input
mode: normal
lanter<~o>nial
special character "~o"
is not translated
does not have a macro
special translation: 0
hyphenation code: 111
flags: 0
ASCII code: 0
asciify code: 245
is found
is transparently translatable
is translatable as input
mode: normal
lanter<~o><hy>
nial
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66919>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
