|
|||
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > exporting a bilingual translation memory in xls format
|
Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius |
|
exporting a bilingual translation memory in xls format - 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 | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
Luckyshamrock365 Member
![]() |
Hi, I would like to know how to do the above in Sisulizer..I'm new to this tool, I would also like to know if Sisulizer pretranslates strings through memory like other CAT tools or not as currently I never got suggested translations. Thanks a lot Paola
|
||||||||||||||||
|
| |||||||||||||||||
Markus.Kreisel Administrator ![]()
![]() |
This might help: https://www.the-localization-tool.com/i-want-to-re-use-translations-from-my-other-sisulizer-projects-is-this-possible/ Sisulizer also can export tranbslation to TMX and import from TMX. You find these unter Tools - Translation Engines. Most common is the import transaltions from other .slp files. Think of a SLP files as of a translation memory file. In contrast to regular TMs the SLP does store a context. While in document localization standard TMs without context work well. But in software localization we speak often about single words where a context is really needed. Hope this helps Markus P.S. Perhaps you can include the details of your questions in the posts and not in the title. Thanks
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
|
|
|||||||||||||||||
Luckyshamrock365 Member
![]() |
Sorry but my question was if I can export an xls file thank you
|
||||||||||||||||
|
| |||||||||||||||||
Markus.Kreisel Administrator ![]()
![]() |
You can export language pairs for translation to XLS if you use File - Export. It will export all strings in the SLP. You can send that file to your translator and later re-import it The translation memory database content can only be exported to TMX which is the standard for TM exchange between localization tools. It is not recommended to export the TM to have it translated and import it back later. The recommended way is to export the strings in the SLP and send it to your translator. You can either send it in Sisulizer format and the translator can use the free edition to edit the translation package. Then he has WYSIWYG and context information. This is the best way to do it. Or you skip WYSIWYG and context and send a XLS file. Better use XLIFF what is the standard for exchanging translations between transaltion tools. The translator can use traditional TMs like Trados etc to translate. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
|
Current time is 07:42 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 > exporting a bilingual translation memory in xls format |
Sisulizer software localization tool - Three simple steps to localize