🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.std.internat
Article #649

Re: Data tagging (was: 8-bit representation, plus an X problem)

#649
From: Masataka Ohta
Date: Thu, 07 Jan 1993 09:22
54 lines
2682 bytes
In article <24564@alice.att.com> andrew@alice.att.com (Andrew Hume) writes:

>> >~ Then, how can I create a text file which contains both Chinese
>> >~ and Japanese?

>	the layer handling character transport need not know.

Then, after the transport, the distinction information is lost.

>one would presume the display layer needs to know. as for seeking,
>we can find word boundaries and all sorts of useful things WITHOUT
>knowing higher-level information such as font changes or size changes.

"all sorts of useful things"? Then, how can display the part of the text
after seek? Isn't displaying characters useful?

>	we've come a long way; from a guess of mine as to how
>NT does internationalisation, you've deduced 10646 is utterly hopeless.

No, no. Regardless of NT, 10646 itself is utterly hopeless. I only made
you realize that.

>> >~ Making everything English text is another fatal misdesign of Plan 9
>> >~ as an internationalized OS.

>> >	damned if i know where i said the text was english.

>> How damned Plan9 is. It is much better to be said "Not a tty" than
>> "iwmczal aslkdjf lskjancm aslkio" on inappropriate ioctl.

>	what? you said plan 9 is crap because it uses english. i replied
>that i never said plan 9 had to use english. you reply plan 9 is crap because
>it doesn't use english.

Yes. That the Plan9 with English error status is worse than the current
UNIX with integer error status does not mean you can't make Plan9 even
worse.

>> Internationalization of "errno" interpretation is a simple and
>> already-solved problem.

>	really? i would think so for the cases like posix where there is
>a predefined list of alternatives and implementations such
>as a list of language-dependent strings indexed by error numbers work
>just fine. when the errors are not so constrained, i am unaware
>of any general solution. does anyone know of one? if so, could you
>describe it here or email me please?

Simple.

Let all error classes be known in advance and provide appropriate
messages locally to each class of errors.

						Masataka Ohta
Technical Details
Message-ID: <2641@titccy.cc.titech.ac.jp>
Path: arc1-ca.pugleaf.net!sparky!uunet!olivea!sgigate!sgiblab!nec-gw!nec-tyo!wnoc-tyo-news!cs.titech!titccy.cc.titech!necom830!mohta
References: <24426@alice.att.com| <1gpruaINNhfm@frigate.doc.ic.ac.uk> <2630@titccy.cc.titech.ac.jp> <24564@alice.att.com>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!olivea!sgigate!sgiblab!nec-gw!nec-tyo!wnoc-tyo-news!cs.titech!titccy.cc.titech!necom830!mohta
From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
Newsgroups: comp.std.internat
Subject: Re: Data tagging (was: 8-bit representation, plus an X problem)
Message-ID: <2641@titccy.cc.titech.ac.jp>
Date: 7 Jan 93 09:22:54 GMT
References: <24426@alice.att.com| <1gpruaINNhfm@frigate.doc.ic.ac.uk> <2630@titccy.cc.titech.ac.jp> <24564@alice.att.com>
Sender: news@titccy.cc.titech.ac.jp
Organization: Tokyo Institute of Technology
Lines: 54