|
|||
|
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) > Bugs and Quirks in Sisulizer > Warning missing, when the selected import column changes
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Warning missing, when the selected import column changes - Bugs and Quirks in Sisulizer - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
MSchrenker Member
|
Hello, I have a Sisulizer project with the languages German (original) and Japanese and Japanese(MY). I defined Japanese (MY) as a sublanguage of Japanese. Both Japanese translations are the same at this time. The translator got the translation file with both Japanese columns and got the task to translate the current Japanese version to Japanese (MY). Because there is already a translation in it, he only has to change the relevant strings for the sublanguage. He did it the other way around by mistake and made the changes into the Japanese column instead of the Japanese (MY) column. This shouldn't be that big problem. The problem occurres, when I try to import his translation into my main sisulizer project file. Because of the mistake, I can't use the normal way to Receive the translation into the correct column Japanese(MY), That's why I use "Right-Click On the Column Japanese(MY)-> Import ..." . The wizard asks then, which column to import from, but it doesnt matter whether I choose Japanese or Japanese (MY), the translation is always imported into my Japanese column! I expected at least a warning, that the Japanese column will be changed and not the column from which I started the import function. My work around was to copy the translation into the correct column in the translation file itself and import it then normally. A fix or a warning would be nice Thank you in advance, Marko Last edited on Wed Nov 15th, 2006 11:30 am by MSchrenker |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
Hi Marko, I am working on this case. A new version will fix this. It will also have more flexible way to define custom language/countries/variants. Currently there is not workaround. I don't know when I get this done my most likely early next week. Best regards, Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
In the means time can you send me <sldir>Sisulizer.slo to support (at) sisulizer.fi I take a look at it and try to figure out if there is a workaround. If not I can ake sure that importing really works with new build. Jaakko Last edited on Tue Mar 27th, 2007 04:41 am by Jaakko.Salmenius ____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
MSchrenker Member
|
Hi Jaakko, I send you the file. Marko
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
I fixed this in 1.1.9. Now Sisulizer correctly imports data to the active column. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
MSchrenker Member
|
I can confirm that now. Thank you very much Marko
|
|||||||||||||
| ||||||||||||||
| Current time is 04:46 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) > Bugs and Quirks in Sisulizer > Warning missing, when the selected import column changes | |
Sisulizer software localization tool - Three simple steps to localize