[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] best practice: should extraction process create target elements?
You did a really nice job showing the different ways of looking at this. I really liked thinking about this.
But I don't think this topic is one that lends itself to a best practice. I think the answer to "should the extraction process create target elements" is "it depends."
My extraction process for my translation provider is a good example.
Factors include whether it is a new translation, or an update to a previous translation; whether the translation includes "boilerplate" material; etc.
Here's a mythical sample of an update to a previous translation:
<warranty state="boilerplate>Some warranty here</warranty>
<chapter state="new">This is my first chapter</chapter>
<chapter state="updated">In July we said hello. Now in November we say goodbye.</chapter>
We extract into this XLIFF:
<source>Some warranty here</source>
<!-- notice, no target. The translation provider needs the source, let's say for context,
but is locked out of the boilerplate -->
<source>This is my first chapter</source>
<target>This is my first chapter</target>
<!-- notice there is a target here.
The translation provider finds it most efficient to type the translation directly into the target.
We find it best if they only enter text, not tags-->
<source>In July we said hello. Now in November we say goodbye.</source>
<target>Es julio. Decimos hola.</target>
<!-- our translation provider finds it useful to see the previous translation,
even thought the text has changed. They type over the previous translation
with the new translation. It seemed odd to me at first. But they insisted this
helps them -->
The practice of when to generate target elements was driven more by our translation providers (each of whom are represented in the TC), than by me as a developer.
Don't think there is a best practice when contemplating generating target elements as part of the extraction, any more than I think there's a best practice when contemplating whether or not to use a skeleton file. The answer to each, as I see it, seems to be, "it depends."
Thanks for this thought provoking topic,