Follow-up Comment #9, bug #68133 (group groff): [comment #8 comment #8:] > But in between--internally to the formatter--ahh, that's a different story. > Every unique _character_, whether ordinary, special, or indexed, an > associated > [https://cgit.git.savannah.gnu.org/cgit/groff.git/tree/src/roff/troff/charinfo.h?h=1.24.1 > charinfo object].
I left out a point here. So given that, in GNU _troff_, everything that is a _character_ has some "charinfo", what does it mean to "translate" something that has charinfo into something that doesn't? And what does it mean go the other way? What does it mean to translate something that lacks charinfo into something that has a chunk of it? Review the linked source file and review all those properties. Someone absolutely could say, "just do a textual substitution, man", and I guess that's pretty close to what you're saying. To which I say, "then why aren't you using **strings**, which already exist? And if those aren't flexible enough, why aren't you macro-parameterizing the input to our macro interpreter?" If you need something that freaking clever, write some m4 that produces *roff input. [https://cgit.git.savannah.gnu.org/cgit/groff.git/tree/tmac/groff_man.7.man.in?h=1.24.1 It's not hard. I've done it.] _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?68133> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
signature.asc
Description: PGP signature
