URL: <https://savannah.gnu.org/bugs/?67830>
Summary: Localisation of mm cover pages and copy type
Group: GNU roff
Submitter: afh
Submitted: Sat 20 Dec 2025 10:59:49 AM UTC
Category: Macro package mm
Severity: 3 - Normal
Item Group: Rendering/Cosmetics
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Unlocked
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Sat 20 Dec 2025 10:59:49 AM UTC By: Alexis <afh>
The following issue was originally
[https://mail.gnu.org/archive/html/groff/2025-12/msg00015.html reported to the
groff mailing list] and this bug report then submitted as
[https://mail.gnu.org/archive/html/groff/2025-12/msg00059.html suggested in
one of the replies]:
Intrigued by the mm macros and the mm cover pages I created a minimal working
example (mwe) to test the cover page capabilities and added `-mden` expecting
to see certain cover page keywords such as `subject` and `date` being
translated to German (`Betreff` and `Datum`) only to find that this isn't the
case currently.
Since I'd like to use mm including the cover pages and produce documents for
German readers, I set out to see what changes were necessary in order to
support localisation in mm documents.
Please find attached a patch that adds support for localising mm cover pages,
the necessary German translations, as well as a minimal working example for
demonstration purposes.
To test run:
groff -Tutf8 -mm -mden -rC1 -dmt=0 mwe-mm-cov-l10n.mm
Note that for easier testing the mwe allows to set the value for `.MT` via the
`mt` register on the command-line e.g. `-dmt=1`.
Although use of copy type, i.e. `-rC1` up to `-rC4` is undocumented according
to `m.tmac` I decided include German translations for the `Pg_type!1` to
`Pg_type!4` strings for completeness.
Not (yet) being intricately familiar with the mm macros it's quite possible
that I've missed hardcoded or untranslated strings and I'd appreciate if folks
more familiar with mm would provide feedback
Although being a native German speaker I'm somewhat uncertain whether my
translations for the copy type, charge case and file case are the most
appropriate.
Regarding the patch itself I'm uncertain whether the approach I've chosen
aligns well with current mm and other groff macro packages best practices.
Therefore I'd very much appreciate feedback from seasoned mm and groff users,
developers, and maintainers.
----
P.S.
The issue and mwe were prepared and tested on macOS Tahoe 26.2 using groff
1.23.0 as well as groff built from the latest changeset; at the time
3b532543264323e4ef49252c0b2573489c77713f from Fri Dec 19 16:48:23 2025 -0600.
Additionally the following environment variables were set:
GROFF_ENCODING=utf-8
GROFF_TYPESETTER=pdf
_______________________________________________________
File Attachments:
Name: mm-l10n.patch Size: 3.3KiB
<https://file.savannah.gnu.org/file/mm-l10n.patch?file_id=57986>
Name: mwe-mm-cov-l10n.mm Size: 425B
<https://file.savannah.gnu.org/file/mwe-mm-cov-l10n.mm?file_id=57987>
AGPL NOTICE
These attachments are served by Savane. You can download the corresponding
source code of Savane at
https://savannah.gnu.org/source/savane-a7ba5c45d6a575f8aa486208476de1878950f160.tar.gz
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67830>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
