Re: [tlug] Re: Piping stderr?

["Stephen J. Turnbull" <stephen@example.com>]

>>>>> "Jiro" == Jiro SEKIBA <jir@example.com> writes:

    Jiro> For example, russian characters have 2 width in EUC-JP, but
    Jiro> in Unicode it's 1.  If programs knows, original encoding, it
    Jiro> can correct that information.

So much for CSI.  :-)

Do you have an URL which standardizes this CSI API?  All Google turned
up was a bunch of flamewars, with the Sun people saying "but we've
already implemented CSI, and gotten it certified by the Chinese, so
we'd have to have multiple binaries," and Markus Kuhn and Bruno Haible
saying, "yeah, well, why shouldn't the rest of us take the opportunity
to standardize on a single sane coded character set, and add the
necessary properties to that standard"?

It seems CSI is basically about sucking up to the Chinese and other
nationalists, providing standard heuristics for Japanese TTYs
(wcwidth), and fighting off the Microsoft dragon, while pretending to
be "more general".

How about the users, who want to use characters, not code points?  And
the programmers, who would like to be able to stop worrying about the
damage that characters they don't know about can do to their file
system (for example)?

-- 
Institute of Policy and Planning Sciences     http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
 My nostalgia for Icon makes me forget about any of the bad things.  I don't
have much nostalgia for Perl, so its faults I remember.  Scott Gilbert c.l.py