|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Exchanging project with translators using other tools
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Exchanging project with translators using other tools
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Exchanging project with translators using other tools - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Frede Member
|
We're about to translate our software to a number of other languages. The translators usually use other software like Trados, Wordfast or Transit. I know I can export files in TMX, XLIFF and other standard formats that these tools can use. My question is what I am missing by doing this instead of having the translators installing and using the free edition of Sisulizer. What happend to translation statuses, invalidated items, comments etc. when I exchange the project using XLIFF or TMX? Thanks Frede
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Frede, I would recommend the XLIFF format since it is the translation exchange format while TMX is a translation memory exchange format. With both formats you can include or exclude comments and statuses in Sisulizer. See screenshot. Please make sure that your third party tools support the import/export/maintenance of the attributes as well. Hope this helps Markus Attachment: 0003.jpg (Downloaded 36 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Sisulizer saves comments, statuses etc. information to TMX or XLIFF files, but I fear not all external tools can't use these items saved to exported files. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Frede Member
|
I have no experience in these other Tools (trados etc.) but I need the exchange process to be as smooth as possible. If that means requiring that the translators use Sisulizer I would not hesitate to require that if they were to take on the job of translating. On the other hand, IF it's possible to get the same functions etc. that Sisulizer offers from another tool that would not be a problem of course. Envalidated items for example. How would that be handled if imported from XLIFF? Currently the invalidated flag could be cleared for 2 reasons. Either the translation has changed or the translator cleared the invalidated flag since the translation was still correct after the original string was changed. How would this be handled if we were to exchange XLIFF files? Frede
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Sisulizer doesn't save Invalidated status to XLIFF file (supported items are visible on Markus' screenshot), but you can use Invalidated filter in Export Wizard for filtering these items. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Frede Member
|
Yes, of course I want the invalidated items to be in the file i exchange since they might need an update. When it reads the strings back it should of course only clear the invalidated flag in my main project IF the translator cleared the flag OR changed the translation. Since other tools does not likely have an invalidated flag I cannot see how this could work. /Frede
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Frede, Importing and Exporting always has some drawbacks. If other tools lack some features there is nothing we could do from our side. We can only export and import all possible attributes. If the other tool does not support attributes it should not touch them while localizing the XLIFF. E.g. Sisulizer works in a way, that it uses original files as a sort of a template to build the localized "copies". If other tools work in a similar way the would keep the extra information alive while building the localized version of the XLIFF. But that is something you have to ask the other tool vendor. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hi Frede, Jaakko implemented import and export of Invalidated status for TMX and XLIFF files. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Frede Member
|
But as I understand this, this will only be usable if any other tool alsop use these flags? /Frede
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Yes. XLIFF and TMX does not contain invalidated flag. This is why we had to add a custom tag (invalidated in TMX and sl:invalidted in XLIFF). If you tool can edit custom tags then it can be edited and imported back tgo Sisulizer. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
TMX: <tu> <prop type="context">sample.ini.Countries.Finland</prop> <prop type="rowstatus">rsInUse</prop> <tuv xml:lang="en"> <seg>Finland</seg> </tuv> <tuv xml:lang="fi"> <prop type="status">tsComplete</prop> <prop type="invalidated">1</prop> <seg>Suomi</seg> </tuv> </tu> XLIFF: <trans-unit id="All.sample.ini.Countries.Finland"> <source>Finland</source> <target state="final">Suomi</target> <context-group> <context context-type="element">Countries.Finland</context> </context-group> <sl:rowstatus>rsInUse</sl:rowstatus> <sl:invalidated>1</sl:invalidated> </trans-unit>
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Frede Member
|
I see, when's the new build released?
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:54 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Exchanging project with translators using other tools | |
Sisulizer software localization tool - Three simple steps to localize
