<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-2">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">As stated previously, Unicode makes no guarantee of supporting source separation / round-trip compatibility with HP264x. A proposal for encoding a distinction would need to provide a different line of argumentation for a need to encode.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Unicode <unicode-bounces@corp.unicode.org>
<b>On Behalf Of </b>piotrunio-2004@wp.pl via Unicode<br>
<b>Sent:</b> Friday, January 31, 2025 2:28 PM<br>
<b>To:</b> James Kass <jameskass@code2001.com>; unicode <unicode@corp.unicode.org><br>
<b>Subject:</b> Re: Odp: RE: Re: Re: Unicode fundamental character identity<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p>Dnia 31 stycznia 2025 22:08 James Kass via Unicode <<a href="mailto:unicode@corp.unicode.org">unicode@corp.unicode.org</a>> napisał(a):<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #999999 1.5pt;padding:0in 0in 0in 6.0pt;margin-left:0in;margin-right:0in">
<div id="gwpc000f635">
<div>
<p class="MsoNormal">On 2025-01-31 5:42 PM, <a href="mailto:piotrunio-2004@wp.pl">
piotrunio-2004@wp.pl</a> via Unicode wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">I'm not saying that it is, but if I'm relying on arguments relevant to<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">the actual usage of the characters, and the dominant opposing side<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">does not provide all that much coherent of a reasoning in return, then<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I'm getting suspicious.<o:p></o:p></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Doug and Peter have provided some good advice with respect to such<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">suspicions. My apologies to Peter Constable for my failure to<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">understand exactly what was being dismissed earlier in this thread.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Quoting from <a href="https://www.unicode.org/L2/L2025/25010-script-wg-report.pdf" target="_blank">
https://www.unicode.org/L2/L2025/25010-script-wg-report.pdf</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">"We deem the differences demonstrated in the proposal to not constitute<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">differences in plain text. No evidence of a document that would make a<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">distinction between the corresponding characters in the different code<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">pages was provided."<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">That seems coherent enough. If a simple and concise exhibit can be made<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">showing the desired distinction making a difference in plain text, then<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">that would be a logical next step. Evidence illustrating data loss in<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">round-tripping would also be helpful. Input from the user community<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">supporting retaining distinctions in Unicode should help the effort.<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The proposal L2/25-037 already shows a difference in plain text of the HP 264x characters, where 0x12 (2) connects below vertical or perpendicular diagonal, whereas 0x18 (8) connects below diagonal of same direction. Those are different
types of connections which is a plain text distinction of box drawings.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Data loss in round-tripping is implicitly evident from the information provided in the proposal: if an HP 264x Large Character set mode document has the characters 0x12 0x18, it converts to Unicode as U+1CE2B U+1CE2B, which converted back
to HP 264x Large Character set mode is 0x12 0x12, which loses the distinction between the two characters and will appear slightly differently than the original document on HP 264x platform.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>