|
|||
|
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) > Usage - Three simple steps to localize > Different rootnamespace in vb.net project
|
|
|||
|
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) > Usage - Three simple steps to localize > Different rootnamespace in vb.net project
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Different rootnamespace in vb.net project - Usage - Three simple steps to localize - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
kaderli Member
|
Hi We are testing/evaluating sisulizer for localize our application, now we got the following problem. We have a vb.net project. This project has a root namespace set, named "Foo". A class within this project has another Namespace, named "Bar". Now the localisation with sisulizer doesn't work. Is there a workaround to set a "pre" namespace to a project/class in sisulizer? If needed, i may send you a test project. thanks manuel
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Please send a test project to support (at) sisulizer.fi Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
kaderli Member
|
Hi This problem only occur if you use the source for translation. If you use the binary, it works. Since i don't have time for analyse and proper description, and since the binary translation is enough for us, i wont be able to prepare/send a test project. cheers manuel
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
Can you send the exe file please. It would helo me to figure out the problem in source scanning. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
kaderli Member
|
Hi I've sent to documentation to you. cheers manuel
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
kaderli Member
|
Hi Do you have news about this topic? cheers
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
Sorry about this delay. I thought that binary localization is working and this is why I did not look the case right away. I am now working on it. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
I fixed this in 1.6.23. The reason for the bug was that C# and VB handle namespaces in different name. Both has the default namespace of the project. However if a form in C# contains different namespace as the default one then forms namespace is used. If VB contains that the actual namespace is default_namspace.custom_namespace. Our code assumed that VB uses the same method as C#. This is why it failed. There is not workaround. The new version will come out next week. Thank you for the bug report. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 04:07 am | |
| 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) > Usage - Three simple steps to localize > Different rootnamespace in vb.net project | |
Sisulizer software localization tool - Three simple steps to localize
