On Sun, Apr 14, 2002 at 08:09:23AM -0400, [EMAIL PROTECTED] wrote:
> On Sun, 14 Apr 2002, Dan Kogai wrote:
> 
> > On Sunday, April 14, 2002, at 05:38 , Sean M. Burke wrote:
> > > At 23:30 2002-04-13 +0300, Jarkko Hietaniemi wrote:
> > >> (You know what?  Since of the files will be named README.xx and
> > >> written in pod, the build machinery will automatically create
> > >> the pod pages "perljp", "perltw", "perlcn", and "perlkr"...)
> > >
> > > BTW, you all know those are country codes and not language tags, right?
> > 
> > Right.  But sometimes we have to bend the rule to keep legacy systems 
> > happy.  So be it .(cn|jp|kr|tw) instead of .(zh_cn|ja|ko|zh_tw) ;)
> 
>   I'm just wondering what legacy system we have to/can make happy
> by using (cn|jp|kr|tw) in place of (zh_cn|ja|ko|zh_tw).  My North Korean

The 8.3 crowd.  zh_ and zh_ look pretty similar.

(Before somebody asks why do we care any more about 8.3, I'll answer
 that that's the way it has been done.)

> brethren may not like it much if I use 'kr' instead of 'ko' (ko_kr) :-)

In theory we could go for (zhcn|jajp|kokr|zhtw)?  But that doesn't
look ring any bells to me at all.

>   BTW, I'm sorry to make things more complicated when we seem to
> have enough headache with perldoc's handling of 8bit characters.  However,
> I can't help thinking it'd be better to make README.xx in UTF-8 and let
> Encode convert to legacy encodings depending on the present locale setting
> (LC_CTYPE -> nl_codeset()) than the other way around. Am I missing
> something here?

That would work only if we had a header in *English* explaning how to
convert the rest of the file to the legacy encoding-- since, at least
as of now, the likelyhoods of a CJK users having
(1) a legacy encoding capable software
(2) a UTF-8 capable software
are not even comparable.
Which would kind of make void the whole idea of these CJK-friendly files.

I therefore suggest we forget the whole idea.

>   Jungshik 

-- 
$jhi++; # http://www.iki.fi/jhi/
        # There is this special biologist word we use for 'stable'.
        # It is 'dead'. -- Jack Cohen

Reply via email to