Re: Some more po files for some languages (Greek, Swedish, Asturian, Turkish, Uighur, Portugese, Kazakh)

[Andrea Pescetti <pe...@apache.org>]

On 31/10/2012 Andrea Pescetti wrote:
> Jürgen Schmidt wrote:
>> I have prepared some more sets of po files for languages where I noticed
>> volunteers here on the list or where got concrete requests.
> To all: do not translate basic/source/app.po

To complete my previous message, here are some tips I've just added to 
http://incubator.apache.org/openofficeorg/translate.html (Rob, feel free 
to move somewhere else if appropriate). They cover the most common 
questions asked here by new translators, including those asked in this 
thread.

Tips for translators

If you are a new translator, you can find the following tips helpful. 
Please ask on the ooo-L10n list if you have any questions.

    1.  Do not translate the file basic/source/app.po; these strings 
belong to an outdated tool (TestTool) no longer distributed with 
OpenOffice. Ignore that file and return it exactly as you received it.

    2.  When you save a file in POEdit, you may receive the error 
"Header Field Project-Id-Version still has the initial default value"; 
you can safely ignore it; that field is not used in the current 
localization process.

    3.  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.

    4.  Some strings, especially those in the helpcontent2 directory, 
contain markup, e.g.

       You see the <link href=\"text/schart/main0202.xhp\">Formatting 
Bar</link> here.

       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".

    5.  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.

    6.  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.

Regards,
   Andrea.

Re: Some more po files for some languages (Greek, Swedish, Asturian, Turkish, Uighur, Portugese, Kazakh)

[Jürgen Schmidt <jo...@gmail.com>]

On 11/1/12 12:22 AM, Andrea Pescetti wrote:
> On 31/10/2012 Andrea Pescetti wrote:
>> Jürgen Schmidt wrote:
>>> I have prepared some more sets of po files for languages where I noticed
>>> volunteers here on the list or where got concrete requests.
>> To all: do not translate basic/source/app.po
> 
> To complete my previous message, here are some tips I've just added to
> http://incubator.apache.org/openofficeorg/translate.html (Rob, feel free
> to move somewhere else if appropriate). They cover the most common
> questions asked here by new translators, including those asked in this
> thread.
> 
> Tips for translators
> 
> If you are a new translator, you can find the following tips helpful.
> Please ask on the ooo-L10n list if you have any questions.
> 
>    1.  Do not translate the file basic/source/app.po; these strings
> belong to an outdated tool (TestTool) no longer distributed with
> OpenOffice. Ignore that file and return it exactly as you received it.
> 
>    2.  When you save a file in POEdit, you may receive the error "Header
> Field Project-Id-Version still has the initial default value"; you can
> safely ignore it; that field is not used in the current localization
> process.
> 
>    3.  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.
> 
>    4.  Some strings, especially those in the helpcontent2 directory,
> contain markup, e.g.
> 
>       You see the <link href=\"text/schart/main0202.xhp\">Formatting
> Bar</link> here.
> 
>       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".
> 
>    5.  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.
> 
>    6.  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.
> 

Thanks Andrea for this further instructions and help. I am not sure but
is this information already documented somewhere? If not it's probably
worth to put it in the wiki.

I am working on the removal of basic/source/app.po but I have to do some
cleanup and tests here before. Please ignore it as Andrea has already
suggested.

Juergen