search

computerline1z / okapi

Automatically exported from code.google.com/p/okapi
0 stars 0 forks source link

Tikal should only import approved text-unit's from xliff docs #444

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by Uli.Laeg...@gmail.com on 20 Feb 2015 at 2:30

GoogleCodeExporter commented 9 years ago 
Hi Uli,

Can you provide more information about what you're trying to do?  From the 
title, I'm guessing that you want to use the '-m' option, but restrict it to 
only merging targets from the XLIFF that have an approved status.  Is that 
correct?

Original comment by tingley on 21 Feb 2015 at 11:57

GoogleCodeExporter commented 9 years ago 
Sorry, i missed to write details. 
Your guess is correct.
I created xliff files via a rainbow pipeline.
Known text units are filled from an pentm database.
The untranslated units i filles with the source text for the comfort of the 
translators.
Now i want to import the translated xliff into my pentm with Tikal (-imp).
Tikal import's now all the targets. Here it should only import the text units 
which are marked as "approved" in the xliff.

Original comment by Uli.Laeg...@gmail.com on 23 Feb 2015 at 6:57

GoogleCodeExporter commented 9 years ago 
FYI: That Tikal -imp command uses the Format Conversion step, which is also 
available from Rainbow. And it has the option to output only approved entries. 
That option is simply not exposed (yet) through the Tikal parameters.
So as a temporary workaround you should be able to use Rainbow instead of Tikal.
I'll try to find some time to add the parameter in Tikal.

Original comment by yves.sav...@gmail.com on 23 Feb 2015 at 11:46

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision 923b678ce509.

Original comment by yves.sav...@gmail.com on 23 Feb 2015 at 12:33

GoogleCodeExporter commented 9 years ago 
The fix will be in the next snapshot.

Original comment by yves.sav...@gmail.com on 23 Feb 2015 at 12:38

GoogleCodeExporter commented 9 years ago 
Ah, i looked at the FormatConversionStep but didn't realized that's
the same as import in Tikal.
I tried it out and it worked except the replacement of the ${trgLang} variable.
Maybe the issue 429 is still open in the FormatConversion Step?

Original comment by Uli.Laeg...@gmail.com on 23 Feb 2015 at 3:30