Re: Pd: Odp: RE: What to do if a legacy compatibility character is defective?

Asmus Freytag via Unicode <[email protected]> Fri, 24 Oct 2025 15:34:20 -0700
Newsgroups gmane.text.unicode.general
Message-ID <[email protected]>
On 10/24/2025 2:54 PM, Nitai Sasson via Unicode wrote:
> f you use a font that makes those Unicode characters look like they 
> did on their original platform, there is no issue. But a given font 
> can only emulate one platform at a time. You're not going to get a C64 
> and PET/VIC-20 frankenstein of a document. Take your pick: do you want 
> it to look like C64, or do you want it to look like PET/VIC-20? Choose 
> your font accordingly.

Round tripping plain text to a mix of devices is not a goal, just as 
round tripping plain text Han characters to a mix of regional variants 
is not a goal.

You (Piotr) need to demonstrate that for a single display, on a single 
device or emulator for a single device, you cannot get the correct 
appearance by systematically using a device appropriate font.

If a device supports "shifted" modes, then a device appropriate font may 
change based on the shift status.

Only when that accommodation fails to produce the correct appearance is 
there a case for further disunification.

The diagonal connector issue satisfies this requirement, but as far as I 
have been able to understand, the block characters do not.

A./