Follow-up Comment #22, bug #58930 (project groff): * The expanded Unicode coverage is great! * fallbacks.tmac does seem like a better place for these definitions. * I'm interested in your thoughts on the trade-off presented in comment #11, because it has bearing on some of your other proposed definitions here besides \[u2011]: ** Other characters, such as single quotation marks, tend to be kerned in the font files, and thus would not be when using these aliases. ** The various spaces implemented with \h'' will be nonbreaking. In many cases, that's probably OK or even desired. But in cases where it isn't, might it be better to warn the user that the character is unrecognized, rather than accept it but potentially typeset it in a subpar way?
_______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?58930> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/