Date: Tue, 17 Oct 1995 05:27:12 +0300 (MSK) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) <ache@astral.msk.su> To: Terry Lambert <terry@lambert.org> Cc: hackers@freefall.freebsd.org, joerg_wunsch@uriah.heep.sax.de, kaleb@x.org Subject: Re: A couple problems in FreeBSD 2.1.0-950922-SNAP Message-ID: <el0InWmq04@ache.dialup.demos.ru> In-Reply-To: <199510170200.TAA26131@phaeton.artisoft.com>; from Terry Lambert at Mon, 16 Oct 1995 19:00:48 -0700 (MST) References: <199510170200.TAA26131@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199510170200.TAA26131@phaeton.artisoft.com> Terry Lambert
writes:
>> >For one, my "hack" meets the definition of the ISO ratification of X3J11
>> >and at the same time conforms to ISO 8859-x character set rules.
>>
>> >It works for all ISO8859-x users, not just ISO8859-1.
>>
>> >The difference is wherein the character code points are set based on
>> >columnar location. This was, in fact, one of the stated design goals
>> >of the 8859-x standards.
>>
>> Well, lets consider D7 char from 8859-1 exactly: is it
>> ispunct() too f.e, in 8859-5?
>> Lets consider DF char exactly, is it islower() too f.e. in 8859-5?
>8859-5 is broken. You admit this by using KOI-8 instead, yet you want
>to use it as an example?
The only reason that I reference to 8859-5 is that I remember it well :-)
If you want, I can dig out another 8859 incompatible font, it simple
takes longer time.
>> >If you need to make code that isn't internationalized and you want a hack,
>> >call the setlocale(,"") in main() if the desired program.
>>
>> It will be broken for locales wich char width > 8bits.
>> Proper thing is to call non-standard startup_setlocale() which
>> check char size not exceeds 8bit.
>Or to specify XPG/3 instead of XPG/4. XPG/4 marked the introduction of
>the heinously bogus runic encoding methods and thus wide character process
>encoding. If you specify XPG/3, then you will be fine.
Well, I plan to go and fix all current ctype-aware FreeBSD sources
to call setlocale() first. I can remove my hack only after
this step will be done. So, I need to know exactly, what XPG we
plan to support. If we don't plan to support runic encoding,
we can reduce current bloat much more by removing runic. In early days
I plan to see strict 8bit locale into FreeBSD but Garrett was who
introduce runic locale. I prefer not use runic, of course.
>If you are worried about CJK and other "large glyph set" character sets
>(ie: won't fit in 0x00-0xff), they have ISO-2022 locales and aren't
>very interested in XPG/4 and/or Unicode/ISO10646 anyway because of the
>inability to build multinationalized applications for multilingual
>processing in the unified character sets. That doesn't mean the Win95
>and WinNT won't cause Unicode to take over the world whether anyone
>likes it or not. It will take over the world. In the end, the end
>user, not the programmers make the decisions. All the end user cares
>about is that it works, not about the amount of effort programmers
>have to expend to make it work. Arguing with large glyph set
>internationalization using XPG/4 mechanisms as an example to the
>contrary is non-productive.
--
Andrey A. Chernov : And I rest so composedly, /Now, in my bed,
ache@astral.msk.su : That any beholder /Might fancy me dead -
FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead.
RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?el0InWmq04>