<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Old Hungarian letters and its req. missing"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107496#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Old Hungarian letters and its req. missing"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107496">bug 107496</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 Kovács Viktor from <a href="show_bug.cgi?id=107496#c15">comment #15</a>)
<span class="quote">> cc: Stuart, is there any font acceptation method for UNICODE standard?</span >
No, they are font foundry neutral. You are free to assign any glyph(s) desired
to the established Unicode point/name values U+10C80..U+10CFF. Obviously if you
assign the wrong glyph to a point the users will not appreciate it, just keep
to the Unicode specification. Styling the glyphs are up to the font designer(s)
and whatever internal approval to publish.
For missing codepoints you'd have to use a PUA assignment in the target font to
start with--and users, applications would have to pick it up there.
And when additional glyphs are accepted by users, then petition Unicode to add
glyphs to the U+10C80..U+10CFF reserved range, U+10cB3-BF and U+10CF3-F9. Or
possibly assign an additional block.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>