Follow-up Comment #17, bug #66392 (group groff): [comment #15 comment #15:] > It wouldn't--he said without looking at the code--be hard > to make `.hla` interpolate "undefined".
If the register .hla always exists, I don't really have an issue with it
returning an empty string: it's just as easy to compare against as the string
"undefined", and as long as "" is documented as meaning the hyphenation
language is undefined, this is consistent with groff's historically minimalist
interface.
In fact, conceptually we ought to be able to distinguish an undefined value
from one defined as the string "undefined":
$ printf '.hla undefined\n.tm \\n[.hla]\n' | groff
undefined
I also just verified that groff has historically returned an empty string for
\n[.hla] if, for instance, the troffrc file is skipped, so changing it to
"undefined" here would technically break compatibility.
I guess I've talked myself out of wanting any change around this.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66392>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
