[bug #62642] MORE.STUFF: add material about "groff-utf8"

[Bjarni Ingi Gislason]

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

                 Summary: MORE.STUFF: add material about "groff-utf8"
                 Project: GNU troff
               Submitter: bjarniig
               Submitted: Fri 17 Jun 2022 01:35:59 AM UTC
                Category: General
                Severity: 3 - Normal
              Item Group: Documentation
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Fri 17 Jun 2022 01:35:59 AM UTC By: Bjarni Ingi Gislason <bjarniig>
Subject: MORE.STUFF: add material about "groff-utf8"

www.haible.de/bruno/packages-groff-utf8.html (year 2005)

  From "groff-utf8":

# Displays an UTF-8 encoded man page on an UTF-8 text terminal.
# Like "groff", except that it also works for UTF-8 encoded man pages and
# supports a wide range of Unicode characters.
# Prerequisites:
#   - Requires groff-1.18.1 or newer.
# Limitations:
#   - The only supported output devices are "utf8" and "html".
#   - For CJK languages, groff outputs lots of "Can't break line" error
#     messages. This is because groff breaks only at spaces, and Chinese,
#     Japanese, Korean, Thai etc. are written mostly without spaces.
#   - No bidi for Hebrew, Arabic and Farsi is done.
#   - No rendering for Indic languages is done.
# Notes:
#   - For Vietnamese: When using 'less'-381 for viewing, make your terminal
#     window wider than 80 columns. Otherwise 'less' will break lines too
#     early (apparently because it considers many zero-width characters as
#     being of width 1).
#   - For Vietnamese: In xterm, characters with 2 accents are rendered as a
#     hollow box when bold. As a workaround, you can use rxvt, which uses
#     inverse instead of bold.








    _______________________________________________________

Reply to this item at:

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

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