Re: RFC: Changing of /doc/manuals/ implementation (summary)
On Sun, Sep 15, 2002 at 07:36:18AM -0700, Rildo Taveira de Oliveira wrote:
> For Brazilian Portuguese use pt_BR, see PO files.
Yes, I know that and I know how you feel. That is why my question was
posted not to get any future complain :)
I think I was unclear about my question.
"How do we address possible file name extention inconsistency for pt_BR
locale?"
> --- Osamu Aoki <debian@aokiconsulting.com> wrote:
> > After all the discussion, most convincing proposal
> > to me was by Martin
> > Schulze <joey@infodrom.org>.
> >
> > Message-ID:
> > <[🔎] 20020910081811.GI30868@finlandia.infodrom.north.de>
If we follow this while maintaining pt_BR as pt_BR :-)
/doc/manual/<doc-name>/<doc-name>.pt_BR.txt (Good so far)
/doc/manual/<doc-name>/<doc-name>.pt_BR.html (It does not work with
apache but most consistent)
/doc/manual/<doc-name>/<doc-name>.pt-br.html (This is needed for apach
but ugly inconsistency.)
We do not have issues with other locales since practically no other
locales insist to use separate locale for country.
Best solution is to fix apache but ..... too much trouble.
Let me also elaborate more on this "language specifying" middle
extention. UTF-8 or EUC vs. S-JIS type of encoding in Japanese can be
a part of this locale part like:
If document is
/doc/manual/<doc-name>/<doc-name>.en_US.ISO-8859-1.txt
We abbreviate as
/doc/manual/<doc-name>/<doc-name>.en.txt
But in future it coud be
/doc/manual/<doc-name>/<doc-name>.en_US.UTF-8.txt
This is real issue for CJK(Oriental 16 bit code) language locales.
/doc/manual/<doc-name>/<doc-name>.??.UTF-8.txt
ja_JP.eucjp (We want UNIX style now)
ja_JP.ujis
ja_JP.utf8 (UNICODE is future)
japanese
japanese.euc
japanese.sjis (some wants MSDOS/Windows95 style)
--
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Osamu Aoki <debian@aokiconsulting.com> @ Cupertino, CA USA +
Reply to: