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 .libreoffice.org: These are used for localization projects. ISO 3166-2 country code, then .then libreoffice.org: These are used for marketing projects. [email protected] would discuss marketing in New Zealand. [email protected] would discuss Māori localization issues. [email protected] would discuss Manx localization issues. [email protected] would discuss marketing in the Isle of Manx. I realize that there are some edge cases with this approach. For example: [email protected] would discuss Straits Salish localization issues. [email protected] would discuss Southern Puget Sound Salish localization issues. [email protected] for marketing Straits Salish in the Pacific Northwest. [email protected] for discuss marketing Southern Puget Sound Salish in the Pacific Northwest. or [email protected] for marketing Southern Puget Sound Salish [email protected] 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. jonathon -- 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 [email protected] List archives are available at http://www.libreoffice.org/lists/marketing/ All messages you send to this list will be publicly archived and cannot be deleted.
