<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span> changed
<a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - [CJK Issue, Enhancement] Distinguishing both Korean and Japanese font from all CJK[Chinese-Japanese-Korean] fonts such as Noto CJK font series and Source Han Sans series, etc."
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134742">bug 134742</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Blocks</td>
<td>
</td>
<td>113638
</td>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>vstuart.foote@utsa.edu
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - [CJK Issue, Enhancement] Distinguishing both Korean and Japanese font from all CJK[Chinese-Japanese-Korean] fonts such as Noto CJK font series and Source Han Sans series, etc."
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134742#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - [CJK Issue, Enhancement] Distinguishing both Korean and Japanese font from all CJK[Chinese-Japanese-Korean] fonts such as Noto CJK font series and Source Han Sans series, etc."
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134742">bug 134742</a>
from <span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span></b>
<pre>(In reply to DaeHyun Sung from <a href="show_bug.cgi?id=134742#c0">comment #0</a>)
<span class="quote">>...
> So, In my opinion, It seems necessary to discuss the display implementation
> of the font selection box on LibreOffice with developers from CJK Users and
> Developers such as, Korea, China, Taiwan, Hong Kong, Macau and Japan.
>
>...</span >
Well sure, but realistically the current logic for composing the "sample text"
strings for the font name list box--makeShortRepresentativeTextForScript()--is
kind of limited and responds only to the fonts reported Unicode coverage (or as
it is hardcoded against its font name).
With your prototype handling of Noto you've taken its reported CJK script
support, and then parsed the font's name for a string ("KR", "JP", "SC", "TC",
"HK") indicating its target script to assign the sample text shown in the font
listings.
But as you've found there are some weaknesses to this approach. First that you
are dependent on what the font reports for its script coverage. But also you
are dependent on what the font designer actually named the font/font family!
The mechanism is fragile--font names change, reported script coverage is too
broad or is misreported. Import filters pass through questionable font names.
For CJK alone there would need to be a lot of fontname "strings" that would
have to be maintained.
So parsing the fontname for language script does not go far enough. In addition
to responding to reported script support the fontlist and combobox selection
should respond to the CJK locale--of the user's UI, or of the target paragraph.
On the other hand the combobox holding the font list performs multiple roles,
general font selection and display of formatting/style but also handling of
Graphite/OTF smart font features.
IIUC in addition to simply displaying the localized font labeling of the
"ShortRepresentativeText" for the Unified CJK font families, the listbox
strings will need a refactoring: 1) respond to user's locale selection, 2)
respond to language as set for the paragraph with text cursor focus, 3)
indicate usage of GSUB locl, or the CJK focused tags [1][2].
Kind of see localized labeling of the font name, in parallel to <a class="bz_bug_link
bz_status_NEW "
title="NEW - Handling of fonts with more than 4 styles (R/B/I/BI) is suboptimal"
href="show_bug.cgi?id=35538">bug 35538</a> for
rendering styles. It all would need a major refactoring. Requires dev
work--maybe a good GSOC project?
=-ref-=
[1]
<a href="https://en.wikipedia.org/wiki/List_of_typographic_features#Features_primarily_intended_for_or_exclusively_required_by_East-Asian_tetragrams_(Chinese,_Japanese,_Korean">https://en.wikipedia.org/wiki/List_of_typographic_features#Features_primarily_intended_for_or_exclusively_required_by_East-Asian_tetragrams_(Chinese,_Japanese,_Korean</a>)
[2]
<a href="https://wiki.documentfoundation.org/Smart_font_optional_features_for_Graphite_and_OpenType_fonts#List_of_optional_smart_font_features_and_their_ID">https://wiki.documentfoundation.org/Smart_font_optional_features_for_Graphite_and_OpenType_fonts#List_of_optional_smart_font_features_and_their_ID</a></pre>
</div>
</p>
<div id="referenced">
<hr style="border: 1px dashed #969696">
<b>Referenced Bugs:</b>
<ul>
<li>
[<a class="bz_bug_link
bz_status_NEW "
title="NEW - [META] Fonts listed in LibreOffice"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=113638">Bug 113638</a>] [META] Fonts listed in LibreOffice
</li>
</ul>
</div>
<br>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>