|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Untranslated rows autotranslates to (Empty) in language variant
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Untranslated rows autotranslates to (Empty) in language variant
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Untranslated rows autotranslates to (Empty) in language variant - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Frede Member
|
When scanning the project Sisulizer incorrectly auto translates some untranslated strings to (Empty) for language variants. Not all strings are set this way but only some. We have a variant called AMS that is a variant of Swedish. For Swedish 100% of the rows are translated but for the AMS variant only the strings that differ from the Swedish translation is translated. The effect is that when building the AMS variant it will contain all of the Swedish translations and the AMS variant translations will replace the default Swedish. This does not seem to happen with every scan but appears to be random (maybe due to specific changes in the source project files). I have seen this behaviour before so it is not only related to the 1.6.17 release but it is of course very annoying. The project files are changed (small changes) between scans btw. top screenshot is before the scan, bottom is after scan. Notice the (Empty) auto translations for the variant. Please advice as this is urgent Regards Frede Attachment: SL-EmptyVariant.jpg (Downloaded 31 times) Last edited on Fri Jan 11th, 2008 07:31 am by Frede |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator 
|
I will fix this to 1.6.18. It will come out next week.
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Frede Member
|
Ilkka.Salmenius wrote: I will fix this to 1.6.18. It will come out next week. That sounds great. Just out of curiosity, how is it that only some words are affected and it appears more or less random (to me at least). /Fredrik
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Frede Member
|
Ilkka.Salmenius wrote: I will fix this to 1.6.18. It will come out next week. That sounds great. Just out of curiosity, how is it that only some words are affected and it appears more or less random (to me at least). /Fredrik
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Frede Member
|
When is 1.6.18 planned to be released?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Unfortunately we still have one urgent bug to fix and we will do that during the weekend. The new version will come on Monday. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 02:08 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Untranslated rows autotranslates to (Empty) in language variant | |
Sisulizer software localization tool - Three simple steps to localize
