Dear All,
I just tried to reply following the Savannah link below, but was
apparently not successful. I'll keep trying!
Before my answer gets lost at /dev/nul, here it is:
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.
===============
I wish you a all a good, healthy and peaceful year 2024!
Oliver.
On 29/12/2023 20:50, Dave wrote:
Follow-up Comment #11, bug#62830 (group groff):
[comment #9 comment #9:]
It would be helpful to me if Messrs. Tanaka and Corff could
reach a consensus on a schema for naming CJK font families. :)
To assist in that, I'm adding Oliver to this bug's cc. Oliver, do you have
any response to comment #10 here? (You can post a comment to the bug report
without having to create a savannah account.)
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62830>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
--
Dr. Oliver Corff
Mail:oliver.co...@email.de
