|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Pre-populate target XLIFF elements
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Pre-populate target XLIFF elements
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Pre-populate target XLIFF elements - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
YamagataEurope Member
|
It would be nice to have an option during the XLIFF export wizard to pre-populate the target elements with the source content (+ overwrite if there is already content in target). This would avoid extra processing to be able to translate the XLIFF files in other translation environments like SDL Trados.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
I am not sure if I undestod correctly what you ment. When Sisulizer exports data into XLIFF it writes the original value into the source element and the translation into the target element. If there is not translation then target element is left empty. Here is a sample that show an item where there is no translation. <trans-unit id="Name"> <source>Car</source> <target></target> </trans-unit> Same item in the situation when there is a translation <trans-unit id="Name"> <source>Car</source> <target>Auto</target> </trans-unit> Can you explain little bit more what is the feature you need? Jaakko
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Nieminen Administrator
|
I looked the files that you sent I noticed what went wrong. There two reason. 1) Many of your rows have been marked "Do not translated". By default Sisulizer does not export those rows. See the screenshot to see how to make Sisulizer to export even "Do not translate" rows. Jaakko Attachment: Untitled1.png (Downloaded 9 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
2) Make sure that you have checked this check box. By default it is checked but if it is not checked then Sisulizer does not write target element if there is no translation given in the Sisulizer project. Jaakko Attachment: Untitled.png (Downloaded 9 times)
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
YamagataEurope Member
|
Hi, If we need to translate XLIFF files in another translation environment like SDL TagEditor, we need to have the translation entered in the <target> element. We now have to copy the content from the <source> elements to the <target> elements for units without translation to be able to translate correctly (because of the way TagEditor works). A screenshot from TagEditor might clarify it better. Attachment: XLIFF-target.png (Downloaded 8 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
So what you need is an option that makes Sisulizer to populate the original value in the target element if there is no translation. Is this right? Jaakko
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
YamagataEurope Member
|
Yes :-D And also an option to overwrite the already present translations with the source for if we needed to re-translate already translated strings.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
YamagataEurope wrote: Yes :-D OK. I start working. And also an option to overwrite the already present translations with the source for if we needed to re-translate already translated strings. To make sure. This option (if checked) will make Sisulizer to write the original string in the target element even if there is a current translation for that language. Right? Jaakko
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
YamagataEurope Member
|
That's correct!
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
OK. I will implement this too. Both will be in the next build (316). Jaakko
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
YamagataEurope Member
|
Impressive support! Thanks a bunch.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
This feature is now ready. It will come with the next build (316) that will be released later this month. See the screenshot. It contains Translation value combo where you can select how and what translation value is written. Jaakko Here is a part from the online help. Translation value Specifies how translation value is written. Possible values are: Value Description Ignore if no value If there is no translation value the translation is not written. Write empty if no value If there is no translation value an empty string is written. Write original if no value If there is no translation value the original value is written. Write always empty An empty string is always written even if there is a translation value. Write always original The original value is always written even if there is a translation value. Attachment: Untitled.png (Downloaded 3 times)
|
||||||||||||||||
| |||||||||||||||||
| Current time is 06:33 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Pre-populate target XLIFF elements | |
Sisulizer software localization tool - Three simple steps to localize
