Follow-up Comment #8, bug #66919 (group groff): [comment #6 comment #6:] > 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.
My test file makes no assumptions. It explicitly sets the hyphenation code it
wants to get the breaking it wants. It was purposely designed to rely on no
Latin-1 hyphenation codes set by any past or present startup files.
> we don't even need to invoke `hcode` with a
> special character as the first argument.
True, in this case we don't need to. However:
* It used to work, and now it doesn't.
* The manual currently says the first .hcode argument can be a special
character.
* We should want to minimize the amount of Latin-1 users are required to
supply in input. At present nothing can be done about the second .hcode
argument, but the first could previously be specified using only ASCII
characters.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66919>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
