Mark wrote:
On Sat, 19 Oct 91 19:33:24 +1000, Bob Smart wrote:
Now the problem at the moment is that there is Japanese software
(and maybe even hardware) to handle 2022, and it doesn't (yet) handle
Mnemonic.
There will never be. The people of East Asia are not going to adopt an
arbitrary system conjured by a bunch of ignorant white folk. A crude way of
putting it, but true.
About arbitraryness: The naming I have chosen is as stated before
very close to official CJK and ISO naming, as expressed in DIS
10646 and even in newer SC2/WG2 documents submitted by JISC.
The ISO 10646 naming is of the form JIS-X0208-1981-17-66
where the two last numbers are row and column in the JIS standard.
I have chosen a shortened form of that, eg j1766 . I do not think
that is showing a lot of ignorance from my side, and even JISC work
is using this naming scheme (the shortened form) in some work.
This is then used in some ISO/IEC JTC1/SC22 work defining
mnemonics - this is where I have got the stuff from (OK - I am
also the main force behind this SC22 work - but is is written
according to SC22 requirements).
Then it may be ignorance to use this work in email.
It gives some functionality, though.
A conversion between mnemonics for CJK and actual CJK 2022
encoding is easy. It can be done by anyone.
I do not want to be an European cultural imperialist
and I would like to hear CJK pepole say what is useable -
The Japanese are then the most voiced on this list.
Mnemonic doesn't have the same advantages for the Japanese that it
has for European languages, but it still has the nice property of
being a 7-bit universal character set which won't drive your terminal
to do funny things if you happen to display the encoded form.
That's what the current ISO-2022 is. The only characters used in JIS are
those occupying the space of the printable US-ASCII glyphs -- 0x21 through
0x7e. The ESC codes to shift in and out of JIS are defined for the purposes
of this shifting and will not make your terminal `do funny things'.
Well, it shows funny characters on my equipment. Maybe this then is broken.
Anyway JIS encoding will be gibberish on unextended hardware.
So we need another presentation of JIS (and other CJK) 2022 encoding.
Keld