Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.
Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > .NET .resources localized files do not import correctly

 Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
.NET .resources localized files do not import correctly - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Sun Apr 11th, 2010 11:31 pm
PM Private Upload Quote Reply
Massoud
Member
 

Joined: Sun Apr 11th, 2010
Location:  
Posts: 7
Status: 
Offline
 I have a base file called Base.resources, and 2 localized files called Base.es.resources and Base.es-ES.resources

When I add the Base.resources file to a project, Sisulizer automatically recognizes the 2 other localized files in the Project Wizard, but it does not actually import the localizations.

If I however, convert all 3 files to .resx files, then the import of Base.resx works fine and the other 2 localized files are loaded correctly.

Another interesting thing is that all 3 .resources files appear in the Project Wizard - Select File page, whereas in the case of .resx, only the Base.resx appears.

Any ideas? (Converting all .resources file to .resx is not an option as a workaround)
Back To Top PM Private Upload Quote Reply

 Posted: Sun Apr 11th, 2010 11:38 pm
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
 We haven't tested importing from .resources but from .resx or compiled assembly files (.exe, .dll).

I will chech this. Can you zip your .resources files (original and localized) into a ZIP file and upload it to me. Use the Private Upload button.

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Mon Apr 12th, 2010 12:38 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
 Thank you for the files. I fixed both bugs. The next Sisulizer build (303) correctly imports data from localized .resources files. Also it does not show the localized .resources file in Project Wizard.

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Mon Apr 12th, 2010 01:44 am
PM Private Upload Quote Reply
Massoud
Member
 

Joined: Sun Apr 11th, 2010
Location:  
Posts: 7
Status: 
Offline
 Thank you Jaakko.

This is the fastest ever resolution of an issue from a vendor in my 20 years in the IT business. Great work. Thanks.

Massoud
Back To Top PM Private Upload Quote Reply

 Posted: Mon Apr 19th, 2010 09:48 am
PM Private Upload Quote Reply
noam
Member
 

Joined: Mon Apr 19th, 2010
Location:  
Posts: 4
Status: 
Offline
 Jaakko.Salmenius wrote: We haven't tested importing from .resources but from .resx or compiled assembly files (.exe, .dll).

Are you sure it's tested for binaries? I have the same problem when importing an .EXE that already has two satelite .DLLs.
Back To Top PM Private Upload Quote Reply

 Posted: Mon Apr 19th, 2010 09:54 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
 It has been tested on EXE. Can you send me your original assembly and the satellite assembly files. Zip them into a zip file and click Private Upload.

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Mon Apr 19th, 2010 11:11 am
PM Private Upload Quote Reply
noam
Member
 

Joined: Mon Apr 19th, 2010
Location:  
Posts: 4
Status: 
Offline
 Another question (I'm new here, I hope it's the right place):
I tried to create a new sisu project from my Visual Studio 2005 solution (.sln), which contains many C++ .NET projects in subfolders (.vcproj). Sisu scanned all the solution tree, but reported "Project does not contain any resources to be localized" - for all of them. What's wrong?
Back To Top PM Private Upload Quote Reply

 Posted: Mon Apr 19th, 2010 11:37 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2115
Status: 
Offline
 Hi,

I guess with C++ .NET you mean managed C++. Have you set the localizable flags of your .NET forms? This is needed to move the strings in your forms to resources.

Hope this helps

Markus




____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Tue Apr 20th, 2010 03:50 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
 noam wrote: Are you sure it's tested for binaries? I have the same problem when importing an .EXE that already has two satelite .DLLs.

Thank you for the files. There was a bug in Sisulizer and I fixed it. Now it can correctly import your satellite assembly files.

New build (303) will coime out in few days.

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Tue Apr 20th, 2010 03:55 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
 noam wrote: Another question (I'm new here, I hope it's the right place):
I tried to create a new sisu project from my Visual Studio 2005 solution (.sln), which contains many C++ .NET projects in subfolders (.vcproj). Sisu scanned all the solution tree, but reported "Project does not contain any resources to be localized" - for all of them. What's wrong?
Sisulizer can not localize managed C++ projects (.vcproj). It can localize C# and VB.NET projects and also unmanged C++ EXE/DLL/OCX files.

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Thu Apr 22nd, 2010 08:29 am
PM Private Upload Quote Reply
noam
Member
 

Joined: Mon Apr 19th, 2010
Location:  
Posts: 4
Status: 
Offline
 Jaakko.Salmenius wrote: Sisulizer can not localize managed C++ projects (.vcproj). It can localize C# and VB.NET projects and also unmanged C++ EXE/DLL/OCX files.

Jaakko
  • But it can localize managed C++ binaries (EXE / DLL), like the ones I've sent you, right?
  • Do you have plans to support managed C++ projects? Most of our projects are like this, so it will be a consideration when buying a localization tool.
Back To Top PM Private Upload Quote Reply

 Posted: Thu Apr 22nd, 2010 09:06 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
 noam wrote: But it can localize managed C++ binaries (EXE / DLL), like the ones I've sent you, right?
Yes. You can localize managed C++ binaries

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Thu Apr 22nd, 2010 09:10 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
 noam wrote: Do you have plans to support managed C++ projects? Most of our projects are like this, so it will be a consideration when buying a localization tool.

No plans. The reason is that .vsproj file format is very different from .csproj and .vsbproj. Our current scanner can only read C#/VB kind of project files.

We recommend C++ users using binary localization.

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Thu Apr 22nd, 2010 09:20 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
 noam wrote: Do you have plans to support managed C++ projects? Most of our projects are like this, so it will be a consideration when buying a localization tool.

What Visual Studio version do you use?

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Thu Apr 22nd, 2010 09:43 am
PM Private Upload Quote Reply
noam
Member
 

Joined: Mon Apr 19th, 2010
Location:  
Posts: 4
Status: 
Offline
 Microsoft Visual Studio 2005
Version 8.0.50727.762 (SP.050727-7600)
Back To Top PM Private Upload Quote Reply

 Posted: Thu Apr 22nd, 2010 10:02 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
 Visual Studio 2005 and even 2008 used very different project file format for managed C++ compared to C#. This is why we do not support managed C++ project.

In Visual Studio 2010 managed C+ project file format is similar to C# and we can add support for that.

Right now binary localization is the only way for you if you use Sisulizer.

Jaakko



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

Current time is 05:19 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > .NET .resources localized files do not import correctly



WowUltra modified by Sisulizer Copyright © 2007-09 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize