On 6/4/12 7:08 PM, Rob Weir wrote: > On Mon, Jun 4, 2012 at 12:05 PM, Jürgen Schmidt > <[email protected]> wrote: >> On 6/4/12 5:15 PM, Rob Weir wrote: >>> I'm putting this draft together, not because I have all the answers, >>> but because I think I have most of the questions. Hopefully others >>> can help fill in the details. When complete, this can go onto the >>> website and we can have a blog post to call for more translation >>> volunteers. >> >> you are faster than I ;-) >> > > Or just more free time ;-0 > >> I would create a new wiki page and would like to update the wiki page >> http://wiki.services.openoffice.org/wiki/Pootle_User_Guide >> > > The topic is broader than just Pootle, so I hope we have a new page > that covers the higher-level questions, such as what I have here. > That can then point into the Pootle wiki for details on using that > tool. > > >>> >>> --------------------------------------------------------- >>> >>> =How to Help Translate Apache OpenOffice= >>> >>> >>> ==Introduction== >>> >>> OpenOffice traditionally has had excellent localization support, >>> especially with its support of over 100 languages, including many >>> minority languages that are not commonly supported in commercial >>> products. Our community-led, all-volunteer, open source development >>> model facilitates this. >>> >>> Each new version of OpenOffice requires the translations to be >>> updated, to add translations for terms and phrases that have been >>> added or changed in the product. So maintaining support for any given >>> translation is an ongoing effort, requiring volunteers to help keep >>> the translations current, complete and accurate. >>> >>> A list of translations available in the most-recent release of Apache >>> OpenOffice can be found here: >>> http://www.openoffice.org/download/other.html >>> >>> A larger list of languages, including ones that have incomplete >>> translations are listed here: >>> https://translate.apache.org/projects/OOo_34/ >>> >>> [ Is that the correct URL? There were other AOO-related projects on >>> Pootle as well. ] >> >> the url is correct for the UI, we have a separate project for the help >> >> https://translate.apache.org/projects/OOo_34_help/ >> > > OK. So we should mentioned both. I also see projects for AOO 4.0 in > Pootle. What is that for?
AOO 4.0 is currently a placeholder for future work, it was initially created by Raphael as well as plain OOo (Apache OpenOffice (incubating) I don't have the necessary rights to create or delete projects yet. I have to work on this ;-) > >>> >>> [ Also, is that the entire list of PO files or do we have others? I >>> thought we had more than 71 languages ] >> >> no I think we have more, I have started to integrated all po's we have >> in the repo but have had problems with some of them. This work have to >> be finished... >> > > OK. So maybe on the wiki page where we list volunteers we list all of > the languages. And then we can put a note that says if a volunteer > wants to work on a language that is not yet loaded onto Pootle, they > should send a note to the list. we have 112 sdf files in our repo, means 112 languages. Ok one is a helper only. > > > And if someone wants to work on an entirely new language? How do they > get started there? We should have some info on that. good idea, bit I will try to update pootle with all languages Juergen > >> >>> >>> >>> ==How to Help== >>> >>> First, register your interest. We track a list of volunteers >>> interested in helping with each language on our wiki here: XXXX >>> >>> [ This doesn't exist yet, but I propose adding it ] >> >> yes, but we should create one to track the progress and to know who is >> working on the different languages. Good to know whom to contact ;-) >> >> I will do that ... >> > > Thanks. > >>> >>> You should add your name to that list, and send an email to >>> [email protected] to introduce yourself and your interest >>> in helping with that language. >>> >>> [ I'd love to start a new list, [email protected] to >>> handle this and the following translation coordination issues ] >> >> I would propose [email protected] (otherwise i18n) >> > > OK. > >>> >>> If a build with your language already exists, you should download and >>> install. If you find errors in the translation, you can report it >>> directly as a bug report in Bugzilla >>> (https://issues.apache.org/ooo/enter_bug.cgi?product=native-lang) or >>> enter a suggested fix into Pootle (more on Pootle below). >>> >>> If a build is not yet ready for your language, then that typically >>> means that the translation is not yet complete. You can help finish >>> the translation in several ways: >>> >>> 1) You can send a note to the ooo-dev list [or ooo-i10n list if we >>> make one] requesting the PO file for that language. This file can be >>> loaded into a translation management tool where you can edit the >>> translation. When done, or when you've make progress that you want to >>> verify, you can submit the new PO file as an attachment in Bugzilla. >>> This approach works well if you are the only person working on a >>> translation. >>> >>> [ I need a list of some suggested tools that can be used with PO files ] >> >> see http://wiki.services.openoffice.org/wiki/Pootle_User_Guide >> > > Good. > >> A tool to verify the sdf files >> http://wiki.services.openoffice.org/wiki/Gsicheck >> > > Do translators ever need to touch the SDF files? > >>> >>> 2) You can suggest translations on our Pootle server: >>> https://translate.apache.org/projects/OOo_34/ Logins to Pootle are >>> reserved for project "Committers" (those volunteers who have >>> demonstrated sustained contributions to the project and have been >>> voted in as committers). So initially you will need to work with >>> Pootle via suggestions. But translators who have made substantial >>> contributions via their efforts are regularly give Committer rights. >>> >>> 3) Whichever method you use, when you have completed the initial >>> translation, send a note to ooo-dev [or ooo-i10n list if we make >>> one]. At that point we can make a special test build of Apache >>> OpenOffice for you to review. If more changes are required in the >>> translation, we can iterate on these steps, making changes, making new >>> test builds, etc. >>> >>> Note: This process works best if there is a community of users >>> supporting the effort, and not just a single translator. The >>> additional users, even if they cannot help with the translation >>> directly, they can help review the test build and point out errors in >>> translation, as well as other localization errors. Others on the >>> OpenOffice project might be able to help you find other interested >>> users, so let us know, via a note to the ooo-dev list [or ooo-i10n >>> list if we make one], if you want that help. >>> >>> ------------------------------- >>> >>> [ Anything else we should add? I assume we already have more on the >>> website someplace on the technical details of translation, dealing >>> with formatting strings and other non-translatable content, dealing >>> with substitutions in a string, etc. ] >>> >>> [ A separate topic, and one where we could use an equivalent document, >>> would be How to Help Translate the Website ] >>
