Re: [Scrollkeeper-devel] Clarification about language tag

[Dan M. <mu...@al...>]

On Sun, 12 May 2002, Christian Marillat wrote:

> >> "CM" == Christian Marillat <mar...@fr...> writes:
> 
> > Hi,
> > Quoting the scrollkeeper documentation :
> 
> > ,----
> > | The standard OMF specifies the "language" element as optional and as
> > | having no attributes. For ScrollKeeper to relate documents with the
> > | locale of the user, the locale of the documents must be specified. This
> > | is done by using a new attribute, "code", of the "language" element. The
> > | language code should be a standard locale.
> > ----
> 
> > But unfortunately, if the language tag is set to "en", scrollkeeper is
> > unable to install that document.
> 
> Somebody can explain why the 'en' language tag doesn't work ?
> 
> Christian

On a technical level, it doesn't work because (a) we technically didn't
translate the categories into 'en', and (b) we don't list 'en' as one of
the supported locales. (We list the supported locales in
cl/templates/Makefile.am.)  So, supporting 'en' is about as hard as
writing the po file for it.

I always assumed the standard was to use the fallback locale, C, for
documents in English, and that there wasn't much point in setting one's
locale to 'en' or setting the locale in an OMF file to 'en'.  Of course
English is my first language and I'm no expert on locales, so I may be
missing something.  Is there a reason why we should install English 
documents under both the C locale and en locale?  Or do some distributions 
not put english documents in the C locale and instead put them under the 
en locale?

-Dan