Unicode fundamental character identity

[James Kass]

On 2025-02-01 12:01 AM, piotrunio-2004 at wp.pl via Unicode wrote:
> That still cannot possibly work on isolated instances of the 
> characters. In fact, if you have two different Large Character set 
> strings that only differ by the use of 0x12 or 0x18 character, then 
> the HP 264x will display them distinct in Unicode 16.0 mapping they 
> will result in the exact same string and no amount of contextual glyph 
> substitution will work. And as I said, complex features such as 
> contextual glyph substitution are fundamentally completely out of 
> scope for characters that originated from semigraphical text, no 
> matter how modern the system displaying it is.
Sorry, I didn't understand the problem.  Contextual substitution won't 
work without context, so isolated characters can't work.  It also won't 
work if the character to which it is supposed to be joined is on the 
line of text above or below.