|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Sizulizer and Across, export/import of translations
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Sizulizer and Across, export/import of translations
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Sizulizer and Across, export/import of translations - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Christine Member
|
Dear all, as fuzzy matches are not supported, I am in the moment evaluating using another TMS together with Sizulizer, Across in this case. What I did was the following: Export only the source language of the project as TMX. => Import into Across. => Translate into German. => Export as TMX. => find and replace "en to "de" <tuv xml:lang="de">=> Import into Sizulizer. The strange thing was: The only string I really translated was not imported. (For all other strings, I kept the (English) source text. They were imported.) Other questions: * How is the imported file aligned with the project strings? I observed that the exported TMX file contains only the language strings, without any ID or tag. * Is there a DST file available for the XML code of the TMX generated by Sizulizer? Best regards, Christine
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
I tried again, and it seems, that only those "translated" strings are imported that are identical to the source language. This does not make too much sense for me. Any thoughts?
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Christine, can you please send me the TMX and the SLP you try to import it into to support_(at)_sisulizer.com and I give it a try. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
I tried again and exported the file together with the Context tags. Now reimporting worked as expected. It seems that Sizulizer aligns the terms on basis of the Context tags. Do I understand correctly that Sizulizer sets up a unique context tag for each string when loading the source files and uses this tag for alignment? I am sorry for all those questions, but I could not find the information in the Help. Best regards, Christine
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Christine, as I understood do you only have one language column in your TMX. It was EN and you translated it into DE. Sisulizer can either assign "by context" or "by value". While you only have one column "by value" can not work but "by context" does for sure because it is stored with the value in the TMX. You should always use "by context" whenever possible. If you export from Sisulizer it makes sure that each row has a unique context. I would recommend that you export the TMX with more than one language column. Create the target language column in Sisulizer, e.g. German and export it to the TMX. Before translating your TMX it should look like this (I left out headers etc.): (...) <tu> <prop type="context">Converter.properties.About</prop> <prop type="rowstatus">rsInUse</prop> <tuv xml:lang="en"> <seg>About...</seg> </tuv> <tuv xml:lang="de"> <prop type="status">rsInUse</prop> <seg></seg> </tuv> </tu> (...) After translating your TMX it should look like this: (...) <tu> <prop type="context">Converter.properties.About</prop> <prop type="rowstatus">rsInUse</prop> <tuv xml:lang="en"> <seg>About...</seg> </tuv> <tuv xml:lang="de"> <prop type="status">rsInUse</prop> <seg>Über...</seg> </tuv> </tu> (...) Now you can import Über... by value (About...) or by context (Converter.properties.About). Off course by context is still the recommended way - but you do not need to edit <tuv xml:lang="en"> into <tuv xml:lang="de">. But I'm not sure if Across supports direct localization of TMX (like Sisulizer does) or if it can only use it for import and export to its TM (Sisulizer can do both). If the later is the case, you should try Excel format instead. This should be localizable by Across and it should be able to build localized XLS files (and not export as TMX) with the right languages codes. We have customers sucessfully using the the Excel import and export of Sisulizer in combination with third party editors. Excel import and export was a customer request for this special situation. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
Thank you very much for your suggestions. I imported the TMX file as XML into Across. The trouble is that I need to translate the English string in Across. This means, if I would import both the English and German columns into Across, the German column would be empty. But I cannot translate an empty string. I hope it is clear what I mean. I will try the Excel format, though I guess the main problem will be the same. Best regards, Christine
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Christine, please let us know how it worked. If you import back the XLS into Sisulizer please do not forget to add a context column with the "Add other" button and move it to the top of the columns list like in the screenshot. While exporting Sisulizer creates the context in the first column but at import it is not automatically detected. Best Markus Attachment: import.jpg (Downloaded 46 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
I made another test with the TMX ex- and import, exporting the source language and reimporting the source as English translation (without modifying the file). I would have expected to "translate" 100 % this way. It worked nicely BUT it seems that existing translations in English (most were untranslated before the import) were not overwritten, even I selected Always and Confirm Overwrite as Overwrite Method. Why is that? Best regards, Christine
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Christine, can you please mail us the slp and the TMX to support_(at)_sisulizer.com so we can take a look what might happen there. Please also name us one row that should be overwritten but isn't so we can focus on that. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
I understood now the behaviour - I was confused because I set up the import to import also identical strings and change the status of imported strings. I would have expected that all strings would be set to the new status, but only strings that were actually different and were changed during the import were changed. I tried now again and changed one of the strings - it was overwritten and status was changed too. So that's fine. I guess you could argue that it does not make sense to change the state of unchanged strings. On the other hand, if I translate and verify strings in a separate program, I would like to set the status of all strings automatically during import, even if they were not changed. But that is only a minor issue.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Christine Member
|
I tried out the Excel ex- and import and it also worked fine with Across. It seems that it does not make much difference whether I use TMX or Excel. In both cases, I need to change the language tag from "source language" to "target language". In TMX, a Find and Replace "en" will do. In Excel, I change the column header. Thank you very much again, Christine
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Christine, great. This way you can use Sisulizer for scaning and building plus Across for translating until we add the promised TM features from our road map to Sisulizer :-) Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 07:39 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Sizulizer and Across, export/import of translations | |
Sisulizer software localization tool - Three simple steps to localize
