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 

 Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
SlMake - update .csproj to include reference to alternate language .resx - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Mon Oct 5th, 2009 10:24 pm
PM Private Upload Quote Reply
mb
Member
 

Joined: Fri Oct 2nd, 2009
Location:  
Posts: 11
Status: 
Offline
Is it possible for SlMake to extend the localization process 1 step further and update my .csproj with the reference to the alternate language .resx? 

Back To Top PM Private Upload Quote Reply

 Posted: Tue Oct 6th, 2009 04:00 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
No. Sisulizer never changes the original files. It always creates localized files. If you want to add localized .resx file into your VS project you have to add them manually.

See this

http://www.sisulizer.com/online-help/NetVsCompileSatellite.htm

Jaakko



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

 Posted: Wed Nov 11th, 2009 10:36 pm
PM Private Upload Quote Reply
ngallimore
Member
 

Joined: Wed Nov 11th, 2009
Location: Brisbane, Australia
Posts: 2
Status: 
Offline
Hi,

We also have come up against this issue... in some cases our C# project files include many RESX files, and adding these manually would be painful. We also have an automated build system that runs Sisulizer (build system uses Microsoft Team Build, based on MSBuild) that performs a scan and build so that it can create binary files that contain the latest resources.

The basic premise is this: the nightly build should generate a build with the latest resources in both English (original language) and any languages that we are localising into. Obviously for resources that have not yet been fully translated the result would be a mixture of English and, say, Russian, but the build would be complete in that it would be run properly in either English or Russian and all resources (regardless of translation status) would be present. This allows for earlier testing of the translated version, particularly for issues other than raw translations (e.g. culture settings such as number formats, etc).

If, say, a new form is added to the source code by a developer, the RESX file would be created on the build machine by that night's automated build but not added to the C# project file or checked into source control. Now I'm comfortable writing components to do both those steps, but what is missing is a list of the resource files that Sisulizer creates. Is there some way for Sisulizer to create a log of the files it creates (can include existing files; doesn't have to be just brand-new files)? Or is there some other way that the same result could be achieved? Ultimately full MSBuild integration would be fantastic, as this would also provide a way to pass back outputs that does not rely on log files and override key settings in the SLP file when running Sisulizer. We'd be happy to work with you to get this running, but not sure if this is a feature you would be looking at adding, though. :)

The reason we want to localise the source rather than the binaries is that it fits into the build process better, provides better tracking of history in source control (can compare REX files, can't compare binaries), and means that developers can manually edit the RESX files if they desperately need to for testing purposes (with the understanding that they will be overwritten next time the build process runs).

By the way, very happy with Sisulizer in general; we’ve been using it for several years for a C++ / Win32 program very successfully. This is our first foray into using it for .NET programs, but it already is proving to be very capable in this area as well.

Thanks in advance,

Nick

 

Back To Top PM Private Upload Quote Reply

 Posted: Tue Nov 17th, 2009 10:10 am
PM Private Upload Quote Reply
lyutik
Member
 

Joined: Fri Feb 27th, 2009
Location:  
Posts: 24
Status: 
Offline
To ngallimore:
I'm solving the same problem by having a script, that looks in .csproj file and replaces all the mentions of .resx files with *.resx.
f.e.
<Content Include="ActivationApp_LocalResourcesLinkInvalid.aspx*.resx">

Last edited on Tue Nov 17th, 2009 10:17 am by lyutik

Back To Top PM Private Upload Quote Reply

 Posted: Tue Nov 17th, 2009 10:16 am
PM Private Upload Quote Reply
lyutik
Member
 

Joined: Fri Feb 27th, 2009
Location:  
Posts: 24
Status: 
Offline
To Jaakko:
is there is any approach for translator to fix misprints in original using Sisulizer?
It's of course possible using translation to the same language, but I need a way to fix exactly original files...

Back To Top PM Private Upload Quote Reply

 Posted: Tue Nov 17th, 2009 10:27 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Bedburg, Germany
Posts: 1876
Status: 
Offline
Hi Lyutik,

Our golden rule is to never change the source code of our customers. So if there is a typo in the original strings you have to fix that in the source code.

If you have many typos you could try this. Simply create a new project for your .resx files. Add a target language that is the same as your source language.  Instead of entering translations enter corrections. Let Sisulizer build your corrected .resx. Make sure to use Project - Edit source - <your source> - Options - Items that localized... -> All to get a file with all entries.

I have not tried that with .resx - but it might be worth a try.

Markus



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

 Posted: Tue Nov 17th, 2009 11:07 am
PM Private Upload Quote Reply
lyutik
Member
 

Joined: Fri Feb 27th, 2009
Location:  
Posts: 24
Status: 
Offline
Thank's.
But I need fix exactly in original files

Back To Top PM Private Upload Quote Reply

 Posted: Tue Nov 17th, 2009 11:12 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Bedburg, Germany
Posts: 1876
Status: 
Offline
Hi,

Sorry, but Sisulizer will never change the originals. Your source is always the read-only template for the localized copies Sisulizer creates.

Markus



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

Current time is 11:43 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > SlMake - update .csproj to include reference to alternate language .resx



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