|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Translation engine can't handle culture specific translations
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Translation engine can't handle culture specific translations
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Translation engine can't handle culture specific translations - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
ahawksworth Member
|
I have just begun to set up the sisulizer translation memory on a sql server database and after saving the translations to the translation memory I see that the tables in the database have been populated with data. However neither the language or target translation tables store the country/culture information for translated items, they just store the language code. This becomes a problem when you have a project targeting multiple languages and multiple countries/cultures for some of those languages, in my case: - Spanish (Chilie), es_CL - Spanish (Spain, International Sort), es_ES After saving the es_CL translations (which were done by a human translator) to the database, and using the "translate using translation engine" option, sisulizer automatically translates values in the es_ES target locale! Is there any way to make Sisulizer: a) Store the complete locale information along with each value b) Only use values in the Translation Memory where the complete locale information matches I would appreciate any help you could give.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, "File" menu -> "Save to Translation Memory" and "Column" menu -> "Save to Translation Memory" features don't use country extensions, but Sisulizer allows also on saving translations with country extensions to translation memory. Below is short description: Open Sisulizer and go to "Tools" -> "Translation Engines". Here select your translation memory and go to "Documents" tab. Next click on "+" button (it opens Import Wizard) and select Sisulizer project received from your Spanish translator. Attachment: screen.png (Downloaded 41 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Import Wizard detects translation languages included to selected project and ask you about imported languages (you can select multiple items with CTRL key). Attachment: screen1.png (Downloaded 41 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
In next step of Import Wizard you should uncheck "Ignore country part in the language codes" option. Attachment: screen3.png (Downloaded 41 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
After import translation memory contains different items for "Spanish (Chile)" and "Spanish (Spain, International Sort)", and of course, Sisulizer for "Spanish (Spain, International Sort)" column use only items saved to translation memory with this extension after using "Translate Using Translate Engine" -> your translation memory. Best regards, Janusz Attachment: screen4.png (Downloaded 41 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
ahawksworth Member
|
Thanks for the quick reply, I have cleared the translation memory database and imported all of the files received from translators as you suggested. I can see that the translations now stored in the database now have both language and country codes. However, when attempting an import from translation memory (Project>Translate Using Translation Engine>SQL Database..), Sisulizer is still filling in translations for es-ES even though the translations in the database are clearly marked as es-CL. Is there a way to enforce country-code checking when importing via the sisulizer sql server translation engine??
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hmm... I tested this trick with my translation memory based on MySQL database and it works correctly for es-ES and es-CL on my PC. Unfortunately, I don't use MS SQL Server, but I'll ask other team members about checking it with this database type. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
ahawksworth wrote: Is there any way to make Sisulizer: Sisulizer has an option that controls if the country part of the language code is stored or not. Unfortunately the default value is to remove the country part and it is there is no easy way to change. The only way is the method Janusz told you. To make this easire I added Import strings sheet to the Translation Engines sheet. See the screenshot. Starting from next build (301) this sheet is available and you can change the value. Also I change the default value not to cut the country part. I also tested different Spanish version on SQL Server and it worked. So you better wait of build 301 that will come out next week. Jaakko Attachment: Untitled.png (Downloaded 31 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
ahawksworth Member
|
OK I will give this a try when the new build comes out and let you know it this works. Thank you both for your help in this matter.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
ahawksworth Member
|
The "Import Settings" panel that has been added to the Translation Engines dialog has helped make it easier to store the country code when saving translations from Sisulizer to the SQL Server Translation Memory. So thanks for that, however I'm still having trouble with the translate using translation engine feature. I've attached some screen shots to show this process. 1) es-CL translations imported into Sisulizer from translators. 2) Translations saved to SQL Server database 3) es-CL translations appear in database with language/country code. 4) Run a "Translate using translation engine>SQL Server" command in Sisulizer. 5) Sisulizer has used the es-CL translations in the database to translate the es-ES values. The "Ignore the country code" option is not set on the "Import Settings" panel, so why does Sisulizer ignore the country code when making use of the translation engine? Any help greatly appreciated, Thanks. Attachment: Steps.jpg (Downloaded 18 times)
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
ahawksworth wrote: The "Ignore the country code" option is not set on the "Import Settings" panel, so why does Sisulizer ignore the country code when making use of the translation engine? The current implementation is following. First Sisulizer tried to find exact match (e.g. both language and country codes matched). If not found it tried language only match and uses it if found. This is why the current build ignores country code. Starting in the next build (303) it is possible to control what translations are used. The following sheet lets you specify if to accept country codes, different country codes or neutral values (e.g. no country codes). Here is online help for the sheet. Translate settings Use this sheet to specify how to select translations when using translation memory to translate projects. Language match Specifies how exact language match must be when finding translations. Possible options are: Option Description Use country neutral translations when translating a sub language If checked Sisulizer uses also country neutral translations in the case there is no country specific translation. For example if this is checked and you are translating a German (Switzerland) column and there is no translation having de-CH language code but there is a translation having de language code then Sisulizer will use it. Use country specific translations when translating the main language If checked Sisulizer uses also country specific translations in the case there is no country neutral translations. For example if this is checked and you are translating a German column and there is not translation having de language code but there is a translation having German (Switzerland) language code then Sisulizer will use it. Use translations of the same language but different country If checked Sisulizer uses also translations of the same language but different country in the case there is no country specific translations. For example if this is checked and you are translating a German (Austria) column and there is not translation having de-AT language code but there is a translation having German (Switzerland) language code then Sisulizer will use it. Attachment: Untitled.png (Downloaded 15 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
ahawksworth Member
|
That sounds great, when should we be expecting the next build (303) to be released? Thanks again for your help.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
303 will come out in two weeks. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 06:21 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Translation engine can't handle culture specific translations | |
Sisulizer software localization tool - Three simple steps to localize
