svn commit: r836815 - in /websites/staging/openofficeorg/trunk/content: ./ openofficeorg/translate.html

[bu...@apache.org]

Author: buildbot
Date: Wed Oct 31 23:17:02 2012
New Revision: 836815

Log:
Staging update by buildbot for openofficeorg

Modified:
    websites/staging/openofficeorg/trunk/content/   (props changed)
    websites/staging/openofficeorg/trunk/content/openofficeorg/translate.html

Propchange: websites/staging/openofficeorg/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Oct 31 23:17:02 2012
@@ -1 +1 @@
-1404412
+1404414

Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/translate.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/translate.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/translate.html Wed Oct 31 23:17:02 2012
@@ -192,6 +192,12 @@ translated string should be a copy of th
 "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