[bug #62830] [PATCH] [grops] support CJK fonts encoded in UTF16

[G. Branden Robinson]

Follow-up Comment #13, bug#62830 (group groff):

[https://lists.gnu.org/archive/html/bug-groff/2023-12/msg00090.html Oliver
posted the following to the bug-groff list]; apparently the GNU Savannah web
site was not permitting him to comment on this ticket, which is pretty weird.


Hi,

thank you very much for considering my previous comment on the CJK font naming
issue.

It is perfectly fine with me to build the font names by terms of primary
language, i.e. starting with C for Chinese, K for Korean, J for Japanese.

In my humble opinion and according to decades of personal experience in this
area, a majority of documents in these languages will be composed and perused
by users of one language alone, and just by following prior practice, using a
language-based naming scheme will allow the majority of users to navigate in
familiar waters.

The minory of users who --- from the beginning --- compose documents with the
need for equal typeface across several languages will use those fonts which
provide a full coverage of CJK characters, and for them, the first letter
doesn't really matter. They'll pick the font first, then the language, in
contrast to the users mentioned before.

Best regards,
Oliver.




    _______________________________________________________

Reply to this item at:

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

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