This issue exists to collect and keep track of locales to be supported
that have no LANGID defined in OOo. Note that only the presence of a
defined value (and it's mapping to ISO names) is important here, not
whether there are locale data defined for specific locales. To request
an additional ID value, please first take a look at the lang.hxx URL
mentioned below, and only if there's no entry that matches your request
add your request to the issue, stating language and country and their
assigned ISO names, if possible.

I'd like to keep this issue ongoing and not set it to fixed, or
verified, or closing it, in order to direct all requests to one single
place. Therefore it's target is currently not determined, but changes
should go in to every next 1.0.x and 1.1.x build to enable further
localization. If we'd need an issue's status to keep track of
implementation we should create a sub-issue then.

Some may already know that OOo doesn't support locales that weren't
predefined by MS for the reason that core document locale attribute
features use the MS-LANGID values. Changing the core representation
currently is not feasible. Note that this is mainly not about UI
localization (e.g. the telephone country code restriction of resources
is not related to this topic, though the resource compiler may benefit
from new values too) but hinders the use of new locale data not fitting
into the MS view of the world. 

So far we didn't want to risk compatibility issues with documents that
were created using a user defined LANGID value, which to use currently
is the only proper way to support more locales. But there is definitely
a need for locales not supported by MS so we'll add values defined in
the LANGID user space to our repertoire. This means

1. Documents that will be created with OOo using such a value, when
   exported to MS or any other binary format using LANGIDs will most
   likely lose locale attribution when imported by any other application
   than OOo/SO.

2. Documents created with another application using user space values
   that incidentally match values defined by OOo will display OOo's
   locale specific attribution when imported, instead of an en_US
   fallback.

3. Future support of OOo locales in binary file formats might make it
   necessary to remap values if MS came up with new Windows reserved
   values that map to identical locales.


For technical information about MS-LANGIDs and a list of values
currently defined please see (long line wraps)

http://www.openoffice.org/unbranded-source/browse/~checkout~/util/tools/inc/lang.hxx?rev=1.5.12.1&content-type=text/plain

respectively the latest revision available.
[seems that file could need a :%retab with ts=4 and expandtab on]


Once a new value is to be supported the following places need to be
updated:

tools/inc/lang.hxx
        Define a LANGUAGE_... value conforming to MS-LANGID rules of the
        user space. Be sure it doesn't conflict with already existing
        entries or primary languages or their combinations with
        sublanguages.

tools/source/intntl/isolang.cxx
        Create a unique back and forth mapping between the LANGID and
        it's ISO names. Without this, the corresponding locale will not
        be offered at various places.

svx/source/dialog/langtab.src
        Add an UI visible entry to the string list arrays of available
        locales. This is subject to localization, currently at least
        English_US and German entries have to be provided in order to
        trigger automatic extraction for localization tools.


The following is only needed if localization is not accomplished using
the EXTERN 99 language of the L10N framework, but the new language is
intended to be part of the core resource system instead:

rsc/inc/rsclang.c
        Add the name of the lang.hxx LANGUAGE_... define without the
        LANGUAGE_ part to the list of known languages.

tools/source/rc/resmgr.cxx
        Implement a mapping from LANGUAGE_... to telephone country code
        in method ResMgr::GetLang().

solenv/inc/postset.mk
        Add a RES_... section similar to the existing ones.