|
|||
|
.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
|
|
|||
|
.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 |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Luckyshamrock365 Member
|
What about pre-translations in the target fields? Is it possible to see pre-translations like for ex with Trados? Thank you
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Luckyshamrock365 Member
|
Hi Ok, i send the completed translation to use it as a memory (e lo file is the translation) and i send it together to the new slp, with the new strings to translate...at this point how do i call for pre-translation from the 1st slp? Thank you
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, If you would like import translations to new SLP file from other SLP file, you need use Import Wizard ("File" menu ->"Import..."). This way you can also import also other translation formats e.g. XLIFF or TMX. If you import translations from other SLP file or updated SLP received from your translator, you can import translations by 3 methods: "By context", "By value" and "By context first then by value". Here is detailed description of these 3 methods: https://www.the-localization-tool.com/short-explanation-of-import-methods/ With "By context" method is most precise method, and only items with matched context or partially matched context will be imported. I recommend using of this method if you import translations from SLP updated by your translator. This setting is specially useful, if your project contains duplicates that should be translated in different way in targeted language. If you try import translations from different slp, By context is rather unusable and you should use "By value" and "By context first then by value" methods. This same way works internal Translation Memory or import from other translation resources (e.g. from XLIFF, CSV or TMX). With Sisulizer you can also import translation from already localized files, by Import Wizard or via "Project" menu -> "Import Translations from Localized Files" (if targeted Sisulizer output filename and path are matched with your localized file). Here are details: https://www.the-localization-tool.com/i-would-like-import-translations-from-my-already-localized-files-to-sisulizers-project-is-this-possible/ Here is article about import translations from other formats: https://www.the-localization-tool.com/i-switched-to-sisulizer-can-i-re-use-translations-from-my-old-localization-tool-in-sisulizer/ If you would like send SLP to your translator, I recommend using of our Exchange Wizard ("File" menu -> "Exchange"). Here you can create customized version of your SLP, based on filters (here article about filers in Exchange WIzard: https://www.the-localization-tool.com/filters-in-exchange-and-export-wizards/), included languages, excluded resources/files, use Alternative language feature, etc. You can even include Sisulizer installer (free version) to generated Exchange package. If you update your source file, you needn't create new SLP and re-import translations. Simply, run "Project" menu -> "Scan For Changes..." and Sisulizer updated project and optionally translate new items (if you select this option in General settings). All changed, new and unused items will be marked by special dots (here is article about this: https://www.the-localization-tool.com/what-do-these-red-blue-and-yellow-dots-in-the-flags-column-mean/). You can use filters for preview all those changed items: https://www.the-localization-tool.com/filter-panel-common-filters-for-translation-sheet/. If your changd source contains updated original strings, you can compare it by enabling "Previous Original" column in the Sisulizer sheet. If originals are changed, you maybe need update translations. All those translations will be indicated by Invalidated dot (https://www.the-localization-tool.com/what-means-red-dot-in-right-top-corner-of-translation-cell/). All unused items, after removing from SLP are by default automatically saved to internal Translation Memory, so you ca re-use it later. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 04:35 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 > exporting a bilingual translation memory in xls format | |
Sisulizer software localization tool - Three simple steps to localize
