|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Why Sisulizer change the context!?
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Why Sisulizer change the context!?
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Why Sisulizer change the context!? - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
sborisgmxat Member
|
hello! We are using the Version 1.6.22. We want to update to the Version 1.6.28 but we saw that the contexts are changed! We tried to use the version (2.0.296) but the contexts were changed again! V. 1.6.22 -->CmsLib.Text.resx.Strings.CmsLib.Text.strFallback V. 1.6.28 -->CmsLib.Text.resx.Strings.CmsLib..CmsLib.Text.strFallback V. 2.0.296 -->CmsLib.Text.resx.strFallback That's crazy because we have to change our programm when we want to upgrade to a newer Sisulizer version! best regards Boris
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Boris, If the context changes Sisulizer always offers also the possibility to re-use translations by value. So no translation gets lost. I'm not sure why the context changes in your case, but it should not have a negative effect of your work in any way. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
sborisgmxat Member
|
Hi Markus, The function „re-use translation by value“ doesn’t solve our problem because we have several different translations for one value. For example “Auto” is translated either as “Vehicle” or as “Auto” (Abbreviation for Automatic). Using “Re-use translation by value” would set all occurences of “Auto” to “Not translated”. If all Sisulizer versions would generate the same context for a translation there would be no problem. The best solution would be to convert the contexts of old versions to contexts in the new version.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, Have you checked out that the context is really lost. It might just be that the newer version display the context in a different way. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
sborisgmxat Member
|
Hello Markus! Please have a look at the attached screenshot. Here are the steps to get this result: 1.) Scan resx in Sisulizer 1.6.22 save slp 2.) Open slp in 2.0.296 3.) Scan for changes (using exactly the same resx). 4.) Done! The first line with the old context is shown as "unused" (blue dot in first column) The second line has a different context. Attachment: Context.jpg (Downloaded 55 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, Can you please zip the .resx and the .slp and upload it. Please use the "Private Upload" button right above this post. It helps us to keep track of uploads and forums posts. We will take a look Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Our developers still improve Sisuslizer, to Sisulizer 2008 were added many features related to .NET and it is probably result of changing of context assigning method for .NET platform. However, originals are identical so Sisulizer should automatically translate new items (new contexts). Could you tell me if output files created by Sisulizer 2008 are still correct (work with your application)? Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
sborisgmxat Member
|
Hi! As mentioned in my earlier post (Posted: 01-02-2010 17:02) we cannot use the automatic translation (by value) of new contexts because it only works if there is only one translation for a specific string.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, Can you please zip the .resx and the .slp and upload it. Please use the "Private Upload" button right above this post. It helps us to keep track of uploads and forums posts. We will take a look Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Markus.Kreisel wrote: Hi, Hi Boris, We already have your sample resx file, but we need more information about "real" project (number of resx files etc.). Maybe it allows find any workaround for you. Could you send to us your original project with resx files (directory)? Working with real project/sources can enhance possibilities for good workaround for you. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Thank you for files. We try find solution for similar cases, however, it can take some time. I found some workaround for you. Maybe this is imperfect solution, but it can help you fix it in your project with current build. Your project contains original duplicates translated in different way and this is main issue related your project, so first you should find these items (before scan with build 296). Go to (still in build 1.6) "View" menu -> "Sheet Filter" -> "Other" tab and select "Duplicate rows which has been translated in different ways". It give you only 118 rows to checking, while your project contains above 18000 items. Go to "Column" menu -> "Select column" (or use column’s context menu). Next, mark all items via icon on sheet toolbar or via "Row" menu -> "Marked", then reset filters and save project. Now you can scan your Sisulizer 1.6 project with build 296 (don’t remove unused items!). After scan you get lot of new and unused, but now you need check only 118 marked items. For your convenience you can use "Sheet Filters" -> "Edit" -> "Other" tab and select "All duplicate rows". When you find marked unused item, you can use Select Node in sheet context menu, because new, appropriated item should be in this same node. Next you should compare, new and unused items and optionally change translations. I know this is very imperfect solution, but it can limit time for correction to 1 – 3 hours (instead week). BTW: Let me know if you already haven't build 1.6. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 08:57 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Why Sisulizer change the context!? | |
Sisulizer software localization tool - Three simple steps to localize
