<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 4/24/16 3:18 PM, Simon Cozens wrote:<br>
</div>
<blockquote cite="mid:571D4626.6010505@simon-cozens.org" type="cite">
<pre wrap="">On 25/04/2016 08:05, Khaled Hosny wrote:
</pre>
<blockquote type="cite">
<pre wrap="">The problem with merging is which script tag to select for the merged run,
Kana or Hani or “it depends on the font”.
</pre>
</blockquote>
<pre wrap="">
Why does it matter what script tag to apply if there are no opentype
interactions with Japanese?</pre>
</blockquote>
<br>
<br>
As for Unicode: the accepted definition of <i>script</i> is a set
of characters that form a complete system for writing sounds. Of
course, any definition of that word needs interpretation, but
katakana and hirigana are both complete, i.e. one could possibly
write Japanese entirely in katakana, or in hiragana. Unicode uses
the separate notion of <i>writing system</i> to speak about the use
of characters to write a language; most of the time, a writing
system uses a single script, but Japanese is the notable exception.
The Korean writing system is another example (hangul + han).<br>
<br>
It's also noteworthy that ISO 15924 provides a tags for combination
of scripts:<br>
<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
Hanb 503 Han with Bopomofo (alias for Han + Bopomofo)<br>
Hrkt 412 Japanese syllabaries (alias for Hiragana +
Katakana)<br>
Jpan 413 Japanese (alias for Han + Hiragana + Katakana)<br>
Kore 287 Korean (alias for Hangul + Han)<br>
<br>
and that the likely subtags
(<a class="moz-txt-link-freetext" href="http://www.unicode.org/cldr/charts/latest/supplemental/likely_subtags.html">http://www.unicode.org/cldr/charts/latest/supplemental/likely_subtags.html</a>)
reflect that:<br>
<br>
ja -> ja_Jpan_JP<br>
<br>
<br>
Even if there are no typographic interaction between kanji, katakana
and hiragana glyphs, there is a need to apply OT features. It's hard
to imagine that having ~5 character runs can be as efficient as
applying them to whole paragraphs. On that basis, I have asked for a
long time for an OT equivalent of Jpan (which does not preclude the
presence of hani and kana).<br>
<br>
Eric.<br>
<br>
<br>
<br>
<br>
<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<blockquote type="cite">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
Jpan 413 Japanese (alias for Han + Hiragana + Katakana)</blockquote>
<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<table border="1" cellpadding="1" cellspacing="2">
<tbody>
<tr>
<td>Hanb</td>
<td>503</td>
<td>Han with Bopomofo (alias for Han + Bopomofo)</td>
</tr>
</tbody>
</table>
<br>
<br>
<br>
<br>
<br>
(although, because that notion is not critical for Unicode, it's <br>
<br>
<blockquote cite="mid:571D4626.6010505@simon-cozens.org" type="cite">
<pre wrap="">
On the other hand, I have just remembered one interaction: a pan-CJK
font such as Source Han Sans / Noto Sans CJK will have variant forms of
the kanji for Chinese, Japanese and Korean. But even then the selection
should be done on language, not on script - I haven't checked how it works.
So if pushed I would say Kana, just in case. But it really shouldn't matter.
_______________________________________________
HarfBuzz mailing list
<a class="moz-txt-link-abbreviated" href="mailto:HarfBuzz@lists.freedesktop.org">HarfBuzz@lists.freedesktop.org</a>
<a class="moz-txt-link-freetext" href="https://lists.freedesktop.org/mailman/listinfo/harfbuzz">https://lists.freedesktop.org/mailman/listinfo/harfbuzz</a>
</pre>
</blockquote>
<br>
</body>
</html>