URL:
  <https://savannah.gnu.org/bugs/?66496>

                 Summary: [ru.tmac] Let groff use respelled string
translations
                   Group: GNU roff
               Submitter: barx
               Submitted: Fri 29 Nov 2024 02:31:23 PM CST
                Category: Macro package - others/general
                Severity: 1 - Wish
              Item Group: Build/Installation
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Fri 29 Nov 2024 02:31:23 PM CST By: Dave <barx>
(I suggested this on the email list
(http://lists.gnu.org/r/groff/2024-11/msg00057.html); the thread has one
refuted objection and no other discussion.)

The log entry for
[http://git.savannah.gnu.org/cgit/groff.git/commit/?id=f486938c5 commit
f486938c5] says:

> Spell string translations using groff special character escape
> sequences instead of Latin-1 or Latin-9 code points; this way they
> work with a document that uses them no matter what its own encoding.
> 
> I didn't do "ru.tmac"; that one's more of a pickle.  The goal identified
> above could be achieved by sifting the string translations through
> preconv(1) and committing that, but that would come at the cost of
> rendering them unintelligible to humans (and therefore prone to error).

Spitballing an idea: leave ru.tmac as-is in git.  Make the build run it
through preconv and prepend a header identifying it as so modified, and
pointing users to the original file.  The processed file would be installed as
ru.tmac, so that groff gets the benefit of its encoding-agnosticism, while the
original would be installed as, say, ru.tmac.orig, so humans get the benefit
of being able to read it.

This would mildly clutter a system's tmac directory, which would be offset by
improved usability.







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?66496>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to