<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>On 2024-02-02 14:33, William_J_G Overington via Unicode wrote:</p>
<blockquote type="cite"
cite="mid:78ea0e0b.225a.18d6bf4f134.Webtop.92@btinternet.com">Regarding
the issue raised in the thread
<br>
<br>
<a class="moz-txt-link-freetext" href="https://forum.affinity.serif.com/index.php?/topic/197938-private-characters-created-with-microsoft-eudceditexe">https://forum.affinity.serif.com/index.php?/topic/197938-private-characters-created-with-microsoft-eudceditexe</a>
<br>
</blockquote>
The issue appears to be (copying text from that thread to this): <br>
<blockquote type="cite">
<div data-role="commentContent"
class="ipsType_normal ipsType_richText ipsPadding_bottom ipsContained"
data-controller="core.front.core.lightboxedImages">I have
created two "private" characters using the Windows built-in
eudcedit utility. The first one I have saved to a specific font
and the second one I have saved to all fonts.
<p> I can locate and copy both characters in Character Map and
paste them successfully into Notepad and into my CAD programs,
but not Affinity Publisher (v.1) Is there a special procedure
in Publisher that will overcome this, or is the programe not
yet equipped to deal with private characters?
</p>
</div>
</blockquote>
<br>
<p>On 2024-02-02 14:33, William_J_G Overington via Unicode wrote:</p>
<blockquote type="cite"
cite="mid:78ea0e0b.225a.18d6bf4f134.Webtop.92@btinternet.com">can
anyone explain what is happening please?
<br>
</blockquote>
<p>I can perhaps shed some light, if not explain definitively. <br>
</p>
<p>Anyone using EUDCedit would be well advised to learn what Windows
has to say about what EUDC is and how it works in Windows. A web
search finds:</p>
<p><b>End-User-Defined and Private Use Area Characters</b> (2021)
<a class="moz-txt-link-rfc2396E" href="https://learn.microsoft.com/en-us/windows/win32/intl/end-user-defined-characters"><https://learn.microsoft.com/en-us/windows/win32/intl/end-user-defined-characters></a></p>
<p>
<blockquote type="cite">
<p>End-user-defined characters (EUDC) in <a
href="https://learn.microsoft.com/en-us/windows/win32/intl/double-byte-character-sets"
data-linktype="relative-path">double-byte character sets</a>
(DBCSs) and private use area (PUA) characters in <a
href="https://learn.microsoft.com/en-us/windows/win32/intl/unicode"
data-linktype="relative-path">Unicode</a> are custom
characters. They can be defined and implemented either by an
end user or by another party…. Their use enables users to form
names and other words using characters that are not available
in standard screen and printer fonts.</p>
<p>The EUDC and PUA characters can be assigned differently, or
not assigned at all, on different computers. Some code pages
have extensions that reuse the EUDC range, … a manufacturer
might provide a custom set of characters in one of these
ranges, … user groups can attempt to provide additional
characters in the PUA. Different combinations of these cases
can cause conflict. When creating applications that rely on
EUDC or PUA characters, you should keep in mind the
conflicting interpretations of an individual code point.…</p>
</blockquote>
<br>
</p>
<p><b>Character Sets and Fonts</b> (2021)
<a class="moz-txt-link-rfc2396E" href="https://learn.microsoft.com/en-us/windows/win32/intl/character-sets-and-fonts"><https://learn.microsoft.com/en-us/windows/win32/intl/character-sets-and-fonts></a></p>
<p>
<blockquote type="cite">To create an EUDC or PUA character, the
user chooses a character value that is within the specified
range and adds the <a
href="https://learn.microsoft.com/en-us/windows/win32/intl/uniscribe-glossary"
data-linktype="relative-path">glyph</a> to the font in the
entry that corresponds to that character value. The user creates
the glyph using an EUDC editor or using a font package purchased
from a font vendor. Any DBCS font can contain EUDCs, and any
Unicode font can contain PUA characters. The font is called a
"separate" EUDC/PUA font if it contains only EUDCs. The font is
an "integrated" EUDC/PUA font if it contains standard characters
as well as EUDCs.…<br>
TrueType fonts can be installed either as .ttf files or as .tte
files. Since the operating system hides .tte files, applications
cannot enumerate or otherwise examine the installed fonts using
GDI API functions. On many operating systems, the system default
EUDC/PUA font and separate EUDC/PUA fonts are installed as .tte
files. Applications such as EUDC editors and the Control Panel
must use registry entries to add, modify, and delete such
fonts.…<br>
</blockquote>
</p>
<p><br>
</p>
<p>The backstory is that end-user defined character handling is a
text requirement originating from ideographic scripts, especially
Japan, and an era when the glyph complement of Japanese fonts was
small (c 5,000 glyphs) compared to the range of ideographic
characters listed in dictionaries and fair game to use in text (c
70,000 characters). Authors wanting to use such "outside
characters" (known as "gaiji" in Japanese) in their publications
had to resort to special measures like EUDCs. OS and application
vendors who wanted to sell to serious publishers in the Japanese
market need to provide EUDC tools. <br>
</p>
<p>The need for special measures like EUDC has receded greatly with
the arrival of ideographic script fonts with very large glyph
repertoires. Use of EUDC tools in ideographic script documents is
likely now a niche. Use of EUDC outside of ideographic script
context is even more of a niche. <br>
</p>
<p>The original question was, "I can [not] locate and copy [my EUDC]
characters in… Affinity Publisher (v.1) Is … the programe not yet
equipped to deal with private characters?"</p>
<p>It seems pretty likely to me that the program is not equipped to
deal with EUDC characters. The feature list for Affinity Publisher
<a class="moz-txt-link-rfc2396E" href="https://affinity.serif.com/en-us/publisher/full-feature-list/"><https://affinity.serif.com/en-us/publisher/full-feature-list/></a>
does not mention Japanese or Chinese typography support. If they
do not have ideographic typography as a major feature, they are
even more unlikely to have Windows-specific EUDC support.</p>
<pre class="moz-signature" cols="72">--
. --Jim DeLaHunt, <a class="moz-txt-link-abbreviated" href="mailto:jdlh@jdlh.com">jdlh@jdlh.com</a> <a class="moz-txt-link-freetext" href="http://blog.jdlh.com/">http://blog.jdlh.com/</a> (<a class="moz-txt-link-freetext" href="http://jdlh.com/">http://jdlh.com/</a>)
multilingual websites consultant, Vancouver, B.C., Canada</pre>
</body>
</html>