On 08/12/2015 14:23, Greater Worcester Land Trust wrote: > I read in the FAQ that you post here to request a new language effort. > I am looking to start work on a Nipmuck localization.
Let's start at the very beginning. How well does LibO _currently_ support Nipmuck?: * Is Locale data for Nipmuck correct? * Is the language currently selectable at >Options >Language Settings >Languages >Default Language >Western"? * How accurate is the spell checker? * How accurate is the hyphenation tool? * How accurate is the grammar checker? * Are all the glyphs found in the writing system used by the language correctly represented in LibO? * Are templates appropriate to the language, and its inherent culture, available? * Are templates appropriate to the language, and its inherent culture, accurate? Once all that is done, then start creating basic documentation. My recommendation is that for at least the first round, translate existing documentation. With the second round of documentation, start using local examples, usages, etc. within the documentation. After creating complete documentation for four or five releases of LibO, most of the glossary related issues will have been solved, which simplifies the translation by several orders of magnitude. I'd also recommend starting with the built-in help file, rather than the initial screens, when translating the UI. Sidenote: In talking with professors who specialize in minority language, and language recovery, the uniform response is that it is much more important that the office suite produce accurate documents in the target language, than the UI be in the target language. Rephrasing: -- To unsubscribe e-mail to: [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
