|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > SLmake skips some strings by xlf-import
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > SLmake skips some strings by xlf-import
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| SLmake skips some strings by xlf-import - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
ka_developer Member
|
Dear developers, as we recently noticed SlMake skips some strings by xlf-import. Everything is correct if we do the same import manually in sisulizer studio. I've created a test to reproduce the problem. Could you please have a look on it? I will then make a private upload with the data.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi, I tried the test1.bat and it does not show the effect on your shot. Do you have the latest Sisulizer build 306? Before I got to test2.bat I need to make sure we have the same basis in step 1. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
ka_developer Member
|
Yes, I have the version 306. Sisulizer.exe has the version 2.1.306.0 and is from 04.06.2010. SLMake.exe has no version inside but is also from 04.06.2010. The SLMake directory was still "Sisulizer 2008" because I allways installed in the same directory. Now I have deinstalled it and installed again the version 306. The directory is now called "Sisulizer 2010" so I've adjusted the test1.bat and test2.bat accordingly. Still I have the same effect. Tests are on drive D in D:\sisulizer test directory on my machine (XP Professional, SP3)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hmmm, Since SLMake uses some settings from your sisulizer.slo file this might be the difference. Can you please upload your .slo file that we can test with your settings. Perhaps you search your hard disk to make sure you only have one sisulizer.slo on your machine. Please use the "Private Upload" button right above this post. It helps us to keep track of uploads and forums posts. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, I found that your French and English resources in your dlls are all marked as German. So your three dlls are all imported into the German column. The last one in the batch wins the race (if overwriting while importing in your settings is allowed). Now you might wonder how the other columns are filled. This is already done by the add parameter. It finds the sub dirs and import the resources of the dlls - except German. German is also the original language and therefore it is not imported automatically. Btw: It does not matter if the -lang parameter is given or not in the import. I ask our R&D to look into that. In my opinion it should overrule the settings in the resource dlls like the GUI setting does. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
ka_developer Member
|
Hallo, thank you very much for this info. I'll tell the developer about it. Still we have another issue as reproduced by the test2. When you start test1, the strings in french are read into the project and exported in xlt file. These string also are properly seen in the french column. But if you do test2 after it, these string are not imported from xlf into the other project in the directory test2. But some other french strings are imported. Could you please have a look on that?
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, I found that the problem occurs in lines with a line feed in it. These are written in a different way using SLMake than using the GUI. While XLIFF is imported by value the original values differ and the rows are not imported. I forwarded that to our R&D Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
ka_developer Member
|
Hallo, In test1, I've excpicitly marked the resources in the en and fr directories as english and french (Now I see them like this if I open the dlls with resource editor of VS 2010). But still the french texts go to the german column as mentioned before I also added test3. Here I have an slp Project and xlf-exported german translation and it is not possible to import it into this projekt in both sisulizer studio and SLMake (cmp. test3.jpg). I private upload the files now, could you please have a look?
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, I think the error reports I send to our R&D will do the trick. I found two issues causing the differences between GUI and SLMake behaviour. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
I fixed this in 307. The problem was that when SlMake exported XLIFF in incorrectly encoded string using C/C++ encoding (e.g. \n, \r). When importing Sisulizer expects unencoded strings. This is why importing of multiline strings failed. Use 307, export XLIFF again and now importing works correctly. 307 will be released on Friday. Jaakko
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Nieminen Administrator
|
I also fixed the importing issues in Test1 where French was given as language but DLL contained German language resource. This fix is also in 307. Jaakko
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:51 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > SLmake skips some strings by xlf-import | |
Sisulizer software localization tool - Three simple steps to localize
