Hello,

So far I've quite comfortable working with Poedit within its own range of possibilities. What's essentially lacking though is a way of correlating my translations with the actual GUI of OO.

I'm running into many instances when I simply have to know more of the context than a given string can actually provides in order to get not just the concepts right but also the right order of words, declination endings, etc. One way of grappling with this situations is by juxtaposing my translation with those in German, Russian, and Polish (the languages I know besides my native) but it is not satisfactory.

Is there a tool / technique / special OO build or extension that would held me locate the translated strings cur in the GUI of OO?

Regards,

Aivaras


2013.03.14 11:06, Aivaras Stepukonis rašė:
Hello,

I wasn't aware something like a KeyID build existed. It sounds very promising. Based on Serg Bormant's description this is exactly what is needed in the case of declined languages (I'm translating to Lithuanian) which are much more contextual than analytic languages.

Where can I download the latest version of KeyID?

Regards,

Aivaras


2013.03.14 06:58, Serg Bormant rašė:
Hi janl,

kid is very usefull, especially for offline translation and moreover with separate build when adding key IDs to the language of translation. We can
simply grep for key ID on the .po tree to identify the one msgstr from
large set. For ex., in Russian we need to differ verbs with nouns because
they has different translations, so verb Print is "Печатать", but the
same noun in dialog title is "Печать" and so on. With kid we can find the
right target "Print" in list of others.

I thought it was a feature our testers used a lot, so I have prepared
genLang with a "kid switch" so it later can be expanded to generate the
keys.

It's very important to and heavily used by at least Russian team.




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

Reply via email to