Hi Alexis, At 2025-12-05T21:45:58+0100, Alexis (surryhill) wrote: > I've been intrigued by the mm macros and while exploring their > capabilities I wondered why some of the strings, e.g. for the > table of contents or on on cover pages were still in English even > though I passed -mden to groff when preparing the document. > > That sparked my interest and I dug deeper only to find hard coded > strings and alias oddities--where, for example, Licon is an alias > of Captc and Captc is translated in de.tmac and mapped in trans.tmac, > but Licon still contains the initially set Captc value CONTENTS.
Whoops. This was probably my error when swinging my renaming hammer against the anvil of groff mm back in August (and before).[1] Thanks for catching this before we released 1.24! I would have claimed that when renaming things, I typically do a "git grep -n whatever >|Q" and then "vi -q Q" to make sure I inspect all cases, but clearly I must not have done so here. > Wanting to use mm and produce documents for German readers, > I set out to see what changes were necessary in order to fully > support localisation in mm documents. Turns out only a few: > > - Replace uses of groff <1.23 compatibility aliases, e.g. Licon, > Lifg, etc. with the their Cap counterpart, e.g. Captc, Capfg. Yes, this is something I should have done myself. I'll take care of this mess since I made it. Expect it in my next push. > - Introduce strings for hard-coded text, namely subject, date, from, > Work Project No., File Case, and memorandum titles in cover pages > > - Add aliases to trans.tmac for newly introduced strings, namely > Authors, Date, Subject > > - Add German translations for newly introduced strings to de.tmac Please file a Savannah ticket for these changes and annotate it "[PATCH] [mm]". (You could also tag it with "[l10n:de]" if you feel inspired by Debian Project practices.) I expect it was never done before because (I surmise) AT&T corporate memoranda were never issued in any language but English. [...] > To the best of my knowledge I've made the changes backwards > compatible, and would greatly appreciate if groff and mm users would > offer their insight, advice, and feedback. I'd like to hear from mm users too, since I seem to have taken on the mantle of its maintainership without at any point consciously deciding to. (I started hacking on it at first just to kill bugs and to learn "the hard parts" of troff via full-service macro package development, and later more aggressively in service of my "London/Reiser Unix VAX port paper reconstruction" project.[2]) Regards, Branden [1] commit 2c9a5154e57b1df5c4f45d569c2047a5e05c348b Author: G. Branden Robinson <[email protected]> Date: Wed Aug 27 18:36:40 2025 -0500 [mm]: Rename `Capcon` to `Captc`. ... commit 6297362eac589c693130e9dc8e0f2ba9bf7b3662 Author: G. Branden Robinson <[email protected]> Date: Thu Aug 14 12:16:29 2025 -0500 [mm]: Rename `Tcst` string to `Tcstatus`. ... commit 10d60b1b620c5d8e8ff3a4d77edf24c1759f2744 Author: G. Branden Robinson <[email protected]> Date: Mon Nov 4 03:08:00 2024 -0600 [mm]: Rename `Li*` strings to `Cap*`. And yes, those items are "NEWS"ed.[3] [2] https://lists.gnu.org/archive/html/groff/2024-10/msg00096.html [3] https://cgit.git.savannah.gnu.org/cgit/groff.git/tree/NEWS?id=54e2b45a1c302e00ce1ec98da4a0bfa76f6d8730#n573
signature.asc
Description: PGP signature
