openoffice-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robw...@apache.org
Subject svn commit: r1351121 - /incubator/ooo/site/trunk/content/openofficeorg/translate.mdtext
Date Sun, 17 Jun 2012 16:19:58 GMT
Author: robweir
Date: Sun Jun 17 16:19:58 2012
New Revision: 1351121

URL: http://svn.apache.org/viewvc?rev=1351121&view=rev
Log:
initial checkin of draft

Added:
    incubator/ooo/site/trunk/content/openofficeorg/translate.mdtext   (with props)

Added: incubator/ooo/site/trunk/content/openofficeorg/translate.mdtext
URL: http://svn.apache.org/viewvc/incubator/ooo/site/trunk/content/openofficeorg/translate.mdtext?rev=1351121&view=auto
==============================================================================
--- incubator/ooo/site/trunk/content/openofficeorg/translate.mdtext (added)
+++ incubator/ooo/site/trunk/content/openofficeorg/translate.mdtext Sun Jun 17 16:19:58 2012
@@ -0,0 +1,85 @@
+Title:     How to Help Translate Apache OpenOffice
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+##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/).
+
+###How to Help
+
+First, register your interest.   We track a list of volunteers
+interested in helping with each language on our wiki here: XXXX
+
+You should add your name to that list, and send an email to
+ooo-l10n@incubator.apache.org to introduce yourself and your interest
+in helping with that language.
+
+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-l10n list requesting the PO file for that language.  This
file can be
+loaded into a translation management tool (some popular ones are listed 
+[here](http://wiki.services.openoffice.org/wiki/Pootle_User_Guide#Translating_off-line) 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.
+
+ 1. 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.
+
+ 1. Whichever method you use, when you have completed the initial
+translation, send a note to the ooo-l10n list.  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-l10n list if you want that help.
\ No newline at end of file

Propchange: incubator/ooo/site/trunk/content/openofficeorg/translate.mdtext
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message