Well, I think the CJK people are not the people to care for
when we are talking fallback notation. The CJK people will
have 2022 support anyway and thus have the right stuff for their eyes.
The Japanese cannot use 2022 in the headers. That's why the solution
for the headers must also solve the Japanese problem in a reasonable
way.
Then we can discuss what is the best way of presenting CJK
on an avarage dumb US/Danish/Russsian/Greek terminal.
How about something like "Yasushi Nakahara"?
One advantage of the current mnemonic CJK naming is that
you can see that it is CJK, and if you have the CJK tables,
you can look up the right character easily. Mnemonic CJK is
now in the form <character set><row><column> eg j1756 for
some Japanese ideographic character.
Yes, but who wants to look up characters in tables just to read
someone's name? For you it's OK. You can read J&o/rn without looking
at a table. But for the Japanese, it's not OK.
Regards,
EvdP