You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by bu...@apache.org on 2013/10/12 18:04:19 UTC
svn commit: r882308 - in /websites/staging/openoffice/trunk/content: ./
translate.html
Author: buildbot
Date: Sat Oct 12 16:04:18 2013
New Revision: 882308
Log:
Staging update by buildbot for openoffice
Modified:
websites/staging/openoffice/trunk/content/ (props changed)
websites/staging/openoffice/trunk/content/translate.html
Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Oct 12 16:04:18 2013
@@ -1 +1 @@
-1530424
+1531553
Modified: websites/staging/openoffice/trunk/content/translate.html
==============================================================================
--- websites/staging/openoffice/trunk/content/translate.html (original)
+++ websites/staging/openoffice/trunk/content/translate.html Sat Oct 12 16:04:18 2013
@@ -109,19 +109,19 @@ updated, to add translations for terms a
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.</p>
-<p>A list of translations available in the most recent release of Apache
-OpenOffice can be found <a href="http://www.openoffice.org/download/other.html">here</a></p>
-<p>A larger list of languages, including ones that have incomplete
-translations are listed <a href="https://translate.apache.org/projects/aoo40/">here</a>.</p>
+<p>A list of complete, released, translations
+available in the most recent release of Apache
+OpenOffice can be found <a href="http://www.openoffice.org/download/other.html">here</a>.</p>
+<p>A larger list of languages, including ones where translation work is
+still ongoing, can be found <a href="https://translate.apache.org/projects/aoo40/">here</a>,
+while the full list of available translations,
+including incomplete and dormant ones, is available
+<a href="http://svn.apache.org/viewvc/openoffice/trunk/extras/l10n/source/">here</a>.</p>
<h2 id="how-to-help">How to Help</h2>
-<p>First, register your interest. We track a list of volunteers
-interested in helping with each language on our wiki <a href="https://cwiki.apache.org/confluence/display/OOOUSERS/Localization+Volunteers">here</a>.</p>
-<p>You should add your name to that list, and subscribe to our localization
+<p>First, subscribe to our localization ("L10N")
mailing list by sending an email to
<a href="mailto:L10N-subscribe@openoffice.apache.org">L10N-subscribe@openoffice.apache.org</a>;
-you will receive a confirmation request, just reply to it to be subscribed. Then you should
-<a href="mailto:L10N@openoffice.apache.org">send a note</a> to the list and introduce
-yourself and your interest in helping with that language.</p>
+you will receive a confirmation request, just reply to it to be subscribed.</p>
<p>If an OpenOffice build is <a href="http://www.openoffice.org/download/other.html">already available</a>
in your language, you should download and
install it. If you find errors in the translation, you can report them
@@ -129,41 +129,18 @@ via bug reports in <a href="https://issu
or enter a suggested fix into Pootle (more on Pootle below).</p>
<p>If an OpenOffice build is not yet available for your language, then that typically
means that the translation is not yet complete. You can help finish
-the translation in several ways:</p>
-<ol>
-<li>
-<p>You can send a note to the <a href="http://openoffice.apache.org/mailing-lists.html#localization-mailing-list">L10n list</a>
-requesting the PO files for that language. These files can be
-loaded into a translation management tool (some tools are listed
-<a href="http://wiki.openoffice.org/wiki/Pootle_User_Guide#Translating_off-line">here</a>,
-with <a href="http://www.poedit.net/">POEdit</a> being a popular choice) where you can edit the
-translation. When done, or when you've made progress that you want to
-verify, you can submit the new PO files as an attachment in Bugzilla.
-This approach works well if you are the only person working on a
-translation.</p>
-</li>
-<li>
-<p>You can suggest translations on our
-<a href="https://translate.apache.org/projects/aoo40/">Pootle server</a> <br />
-The project "Committers" (those volunteers who have
-demonstrated sustained contributions to the project and have been
-voted in as committers) already have a password. If you are not a committer,
-you can request a personal password for Pootle by sending an e-mail to our
-<a href="http://openoffice.apache.org/mailing-lists.html#localization-mailing-list-public">L10n list</a>
-and then you can start providing suggestions in Pootle. Suggestions will need to
-be reviewed by a Committer, but translators who have made substantial
-contributions via their efforts are regularly given Committer rights.</p>
-</li>
-<li>
-<p>Whichever method you use, when you have completed the initial
+the translation by obtaining an account in
+<a href="https://translate.apache.org/projects/aoo40/">Pootle</a>,
+our online translation system.
+A comprehensive guide on using Pootle and requesting access is available at
+http://wiki.openoffice.org/wiki/Pootle_User_Guide</p>
+<p>When you have completed the initial
translation, send a note to the
<a href="http://openoffice.apache.org/mailing-lists.html#localization-mailing-list">L10n list</a>.
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.</p>
-</li>
-</ol>
<p>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,
@@ -173,52 +150,6 @@ OpenOffice project might be able to help
users, so let us know, via a note to the
<a href="http://openoffice.apache.org/mailing-lists.html#localization-mailing-list-public">L10n list</a>
if you want that help.</p>
-<h2 id="tips-for-translators">Tips for translators</h2>
-<p>If you are a new translator, you can find the following tips helpful.
-Please ask on the
-<a href="http://openoffice.apache.org/mailing-lists.html#localization-mailing-list-public">L10n list</a>
-if you have any questions.</p>
-<ol>
-<li>
-<p>Do not translate the file <tt>basic/source/app.po</tt>; these strings belong
-to an outdated tool (TestTool) no longer distributed with OpenOffice. Ignore that
-file and return it exactly as you received it.</p>
-</li>
-<li>
-<p>When you save a file in POEdit, you may receive the error "Header Field
-Project-Id-Version still has the initial default value". That error is not problematic
-in itself, since that field is not used in the current localization process. However,
-it may shadow other errors, so it's better that you edit your PO file settings (in POEdit:
-Catalog - Settings) and replace "PACKAGE_VERSION" with something like "aoo40" and
-"LANGUAGE" with the English name of your language (e.g., "German", "Italian", "Spanish"...).</p>
-</li>
-<li>
-<p>Some strings contain a "~", like "All ~Pages"; these are meant for keyboard
-accelerators; you should ignore the "~" in newly translated strings: OpenOffice
-will automatically assign an accelerator to commands.</p>
-</li>
-<li>
-<p>Some strings, especially those in the <tt>helpcontent2</tt> directory, contain markup,
-e.g. <pre>You see the <link href=\"text/schart/main0202.xhp\">Formatting Bar</link> here.</pre>
-In that case, do not touch anything between "<" and ">". So your
-translated string should be a copy of the original, where you only translate
-"You see the", "Formatting Bar", and "here".</p>
-</li>
-<li>
-<p>When a PO file contains both translated and untranslated strings, PoEdit will
-show untranslated (or partially translated by automatic matching, so-called
-"fuzzy") strings first. You can scroll down the file to see already translated strings
-if you want to be consistent with the terminology in use.</p>
-</li>
-<li>
-<p>If you are a team, or you plan to have someone else review your changes,
-please note that PO files do not have a way to mark a translation as "to be
-reviewed". Most teams who want to review translated file before submitting them
-agree to mark new and modified translations as "Fuzzy" in Pootle, so that
-reviewers can immediately see what has changed and "unfuzzy" those strings
-after verifying that the translation is correct.</p>
-</li>
-</ol>
</div>
<div id="footera">