In a conversiation with our (most likely) translation bureau I asked if it would be helpful to provide a description of the translation fields to help the translators understand the context of what they're translating.
The response was somewhat of a "hmm..." and that surprised me.
But since I don't see an option for including doctype property descriptions in the translation file (xliff) maybe no one else has asked for this either?
in theory its something we could add, but when you get into grid elements, and elements within elements (so, for example, leblender controls inside a grid inside vorto.. something we have seen!) there won't always be a description to provide (so there might be at the top level, but not 3-4 items down).
having used some of the translation software (the primary one people use is SDL Trados), I am not sure if they have a place in the UI to show this per field. but the xliff spec does allow it, so again we could look at it.
Ok, I will also see how we progress and hopefully be able to verify a good quality translation. In other words, if the translation is good enough, then we don't need the description :-)
Field descriptions (meta data)
In a conversiation with our (most likely) translation bureau I asked if it would be helpful to provide a description of the translation fields to help the translators understand the context of what they're translating.
The response was somewhat of a "hmm..." and that surprised me.
But since I don't see an option for including doctype property descriptions in the translation file (xliff) maybe no one else has asked for this either?
Any insights here?
-Tor
yep, no one has requested that before,
in theory its something we could add, but when you get into grid elements, and elements within elements (so, for example, leblender controls inside a grid inside vorto.. something we have seen!) there won't always be a description to provide (so there might be at the top level, but not 3-4 items down).
having used some of the translation software (the primary one people use is SDL Trados), I am not sure if they have a place in the UI to show this per field. but the xliff spec does allow it, so again we could look at it.
Kevin
Ok, I will also see how we progress and hopefully be able to verify a good quality translation. In other words, if the translation is good enough, then we don't need the description :-)
-Tor
is working on a reply...