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

Issue #444 resolved
Former user created an issue

Original issue 444 created by Uli.Laege... on 2015-02-20T14:30:10.000Z:

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.

Comments (6)

  1. Former user Account Deleted

    Comment 1. originally posted by @ysavourel on 2015-02-21T23:57:13.000Z:

    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?

  2. Former user Account Deleted

    Comment 2. originally posted by Uli.Laege... on 2015-02-23T06:57:16.000Z:

    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.

  3. Former user Account Deleted

    Comment 3. originally posted by @ysavourel on 2015-02-23T11:46:19.000Z:

    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.

  4. Former user Account Deleted

    Comment 5. originally posted by @ysavourel on 2015-02-23T12:38:23.000Z:

    The fix will be in the next snapshot.

  5. Former user Account Deleted

    Comment 6. originally posted by Uli.Laege... on 2015-02-23T15:30:53.000Z:

    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?

  6. Log in to comment