|
|||
|
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Updating and exporting Translation Memory
|
|
|||
|
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Updating and exporting Translation Memory
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Updating and exporting Translation Memory - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... | ||||||||||||||
| Author | Post | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
janneke.h Member
|
I have started working with Sisulizer yesterday and found out a lot but still have some questions. My job is to outsource translations (in this case in about 6 languages) to translators who have no experience with Sisulizer. Also I am not the builder of the software to be translated. Of course I can send the .slp I got from the customer to the translators and they can manually tranlsate every string, maybe use autopropagate duplicates to be quicker, but we would rather that translators use an app like Trados Workbench for this, so that an TM is kept and updated and fuzzy matches are given. I know that Sisulizer also has a TM-function and that's what I'm looking into now. I have used the slp we got from the customer to export a TM, but even though the slp has hundred of already translated strings in it, the exported TMX has 0 translation units. Also when I try File --> Save to TM 0 translations are saved. Can you please give me some feedback on what's going wrong here? I know that the TM could be updated and this could mean similar functions as when working with Workbench, but why can't I export a TM from an existing project? In this case the TM we want is a TMX, and not use a database on a server. We want the translators to be able to keep their personal TM's updated after every job too. Next question: how can I differentiate between different TM's and their language pairs in Sisulizer, and how how can an .slp with multiple languages be exported to TMX's in these respective languages? An far as I know, in Trados you can use only one language pair per TM. How can the language pairs in the project be extracted separately? And then one more question: when a TM is actually used in Sisulizer and a previously translated string is found, how will the translator know? Will it be automatically put in the strings? It's hard for me to test things like this because I have no coding skills to make test-cases. Thanks in advance.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, Sisulizer saves to Translation Memory only strings with statuses equal and higher from status set in Translation Memory settings. You can change default status here: menu Tools > Translation Engines > Common settings (look on attached screenshot). For example, if you have 10 000 strings in project with status "Translated", 100 strings with status "Complete", and in "Add string if the status greater or equal to" TM setting is set to "Complete", Sisulizer save only 100 strings to TM! Attachment: screen.png (Downloaded 31 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
janneke.h Member
|
Thank you, that is very very helpful.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
You could to save translations to TM directly from program e.g. via menu File > Save to Translation Memory, but you could also add to Sisulizer TM external files with translations e.g. other Sisulizer projects, TMX files, CSV files etc. by click Add button (plus symbol) in following dialog window: Tools > Translation Engines > Documents tab (look on screenshot). Attachment: screen1.png (Downloaded 30 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
How can the language pairs in the project be extracted separately?Instead export whole your TM database (it could sometimes contains lot of useless translations from different Sisulizer projects, and many language pairs) I recommend export to TMX contents of selected project. It seems to me that it is faster, simple, and more safe solution, e.g. it allows to avoid many misunderstanding with multiple translations from different projects for this same original string. You could export project contents here: menu File > Export. In second step of Export Wizard you could to select language pairs saved to exported files. You could select one or more languages (look on screenshot). Additional Export Wizard for project is very flexible solution, because you could use lot of different settings e.g. save to TMX file strings from selected node or with selected status. Attachment: screen2.png (Downloaded 30 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
Sisulizer currently doesn't support fuzzy matching feature, but it is on our roadmap and will be implemented soon, in near future will be also implemented to Sisulizer special TM Editor. TM Editor will be advanced tool for edit and management contents of translation memory. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
And then one more question: when a TM is actually used in Sisulizer and a previously translated string is found, how will the translator know?You could to check already saved language pairs and numbers of exist translation in menu Tools > Translation Engines > Information tab. Attachment: screen3.png (Downloaded 27 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
Will it be automatically put in the strings?If you would like use TM to translation not translated strings you could use: 1. menu Column > Translate Using Translation Engine This feature try e.g translate all available empty strings in project for selected language column. 2. Select one or more translation cells in translation sheet and use context menu for translation only selected cells (look on screenshot). Attachment: screen4.png (Downloaded 29 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
janneke.h Member
|
Thank you so much! I have tried everything and it all worked out. All is clear now, thanks for taking the time to clarify everything so thoroughly. Best, Janneke
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
I have still some advices for you. As you probably noticed on screenshots from Translation Engines dialog window, on left side of window is visible list of created Translation Memories. You could create new Translation Memory by clicking "+" icon. New TM could be based on following database engines: - Access - ADO/ODBC compatible - dBase - DBISAM (embedded to Sisulizer) - Firebird - Interbase - MySQL - Oracle - Paradox - SQL Server During creation new TM you should to set up different path to TM directory, then for already exist database, because two TM with this same path could sometimes produce conflicts. Sisulizer allows in flexible way on using selected Translation Memories with your projects, because you could enable or disable specified TM for selected sources in project. You can to choose TM for your sources in "Translation Engines" tab of "Source properties" dialog window: This dialog is available via "Properties" in context menu of source item in "Project tree" or via "Edit source" in menu "Project". Janusz Attachment: screen5.png (Downloaded 23 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 10:32 pm | |
| Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Updating and exporting Translation Memory | |
Sisulizer software localization tool - Three simple steps to localize
