Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index

On 10/12/2010 07:39 PM, Florian Effenberger wrote:

Trying to get some structure in, so any advice welcome.

ISO 639-3 language code, then  These are used for
localization projects.

ISO 3166-2 country code, then .then These are used for
marketing projects. would discuss marketing in New Zealand. would discuss Māori localization issues. would discuss Manx localization issues. would discuss marketing in the Isle of Manx.

I realize that there are some edge cases with this approach.  For example: would discuss Straits Salish localization
issues. would discuss Southern Puget Sound Salish
localization issues. for marketing Straits Salish in the Pacific
Northwest. for discuss marketing Southern Puget Sound
Salish in the Pacific Northwest.
or for marketing Southern Puget Sound Salish for marketing Straits Salish.

Using the assigned ISO numbers, rather than letters would be more
language and country neutral.

Note: I'm using Straits Salish and Southern Puget Sound Salish as
examples. I don't know if there are enough users of either language, to
be able to provide either a UI, or documentation in either language.

No human will see non-list, non-bulk, non-junk email sent to this address.
It all gets forwarded to /dev/null

To unsubscribe, e-mail to
List archives are available at
All messages you send to this list will be publicly archived and cannot be deleted.


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.