Op Do, 2010-06-24 om 10:50 +0200 skryf Goran Rakic:
> У чет, 24. 06 2010. у 08:13 +0200, André Schnabel пише:
> > 
> > Did anybody try to build a tmx from old translations using po2tmx and 
> > then pretranslate?
> 
> If I clear all duplicates in my compendium I have 100% fuzzy match with
> PO too. Fuzzy match is not the same as moving the exact translation
> string. Moving translation string does not require any review. 

I completely agree that matching strings by identifier is more valuable
than a 100% string match.


> > > = Contexts everywhere =
> > 
> > oo2xliff gives you the full context ;)
> 
> This is a missing feature in oo2po. Context is passed and visible in a
> comment, not in a gettext msgctxt field where other tools expects it.

The msgctxt field was always meant to be used to disambiguate otherwise
identical messages.  It isn't meant to be an identifier for the string,
because the source text (msgid) is the unique identifier (when combined
with the optional msgctxt).

When we added support for msgctxt in the converters, the support for it
in many PO software was very minimal, so we obviously wanted to only use
it where it was necessary (and we continued to give alternatives, such
as KDE comments, merging, etc.)  Recent releases of the toolkit (since
version 1.3.0) only support "merge" and "msgctxt", however.


Maybe we should add an option to always add msgctxt based on the
identifier, similar to the old "msgid_comment_all" style we used to
have:
http://translate.sourceforge.net/wiki/toolkit/duplicates_duplicatestyle


> > using tmx gives you what you want. Iv you use xliff as format for 
> > translation files, you could even correctly mark how the segment was 
> > translated and decide later hwo to deal with such segments 
> > (auto-approve, review ...)
> 
> I can do the same with PO file. Maybe the semantics is not standardized
> like in xliff but xliff is overcomplicated. I want to be able to grep
> and sed my translations, I can not do that with xliff.

Just in case some people weren't aware:  pogrep from the Translate
Toolkit can search in XLIFF, PO and TMX files (and even .mo files as
well :-)
http://translate.sourceforge.net/wiki/toolkit/pogrep

Keep well
Friedel

--
Recently on my blog:
http://translate.org.za/blogs/friedel/en/content/emotions-and-localisation


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

Reply via email to