Il 27/04/2013 18:44, Jürgen Schmidt ha scritto:
On 4/27/13 9:41 AM, Paolo Pozzan wrote:
Hi Juergen and thanks for your work.
Reply below.

Il 24/04/2013 16:29, Jürgen Schmidt ha scritto:
On 4/22/13 8:54 PM, Jürgen Schmidt wrote:
Hi,

I am currently preparing po files for AOO 4.0 and will focus on the
languages that we have already released. All other langs will follow
immediately.

I have created 2 new projects on the "old" Pootle server to get an
impression of how much work we have to do.

For the UI in "de" will have to check/translate for example 4986
strings, I know we have string moved and translations should be already
available but my knowledge of the language tools and/or translation
memory is too lazy. any kind of help is appreciated ;-)

I am quite comfortable with this kind of tools. What kind of help do you
need? Can you be more specific?

I am not quite sure, I would like to know for example how I can create a
translation memory based on 3.4.1 and to benefit from this with the
moved strings in 4.0

- First of all you need all the po files from 3.4.1. There used to be the possibility to download a zip file of a single project from pootle. This seems not possible anymore but it's essential to have it. - Then with msgcat you can concatenate all the files in one single big po file with all the translations. - By using po2tmx [1] (a tool of the translate toolkit) you convert that big po file in a translation memory with unique segments. - You can use that tmx file in your favourite CAT tool (like Virtaal or Lokalize) which will tell you about the percentage of match. There is surely the possibility to implement this in pootle, but I have never seen the pootle backend. With some tools you can also translate automatically the 100% matches.
Hope this helps. Let me know if you need more informations.

Paolo

[1] http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/po2tmx.html


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to