Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
When I generate the xliff translation file only the source value is included. The target element/field/value is not written. Is this by design?
What's the workflow for re-translating a value which has already been translated at an earlier point of time? Wouldn't it be helpful to include the already translated value if for instance it needs to be edited for typos or quality improvements?
Yes, its by design; after a lot of work with different translation companies/services. We have been told they prefer to work where the target values are not populated.
Most translators are using some form of Translation Memory software that will populate values they have already translated into their system when the files are loaded up, as such, they don't need/want the target values as apparently its easier in their workflows to work this way.
It is however on our own internal list to make this optional (so you can choose to add target values) - but at the moment it's not in the product.
Ok, thanks for the clarification. I'm in the process of preparing the translation files and was just wondering this. No immediate need, but I would think an option for including target value could be helpful.
Having the option of including the existing target values in the xlf export would be very useful in our implementation.
Have this option be implemented? or is it still on your internal list.
Thanks in advance for your help.
It's on our list, but its closer.
we are in the process of re-engineering the xliff 2 stuff to make it easier to support xliff 2.1 and in that we are building the include target value functionality.
early next year is our likely release date.
Thank you Kevin for your quick reply.
Sounds very promising! Will be keeping an eye out for it!
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted