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: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
32 bit and 64 bit platforms - 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: Fri Nov 13th, 2009 10:38 am
PM Private Upload Quote Reply
GertRijs
Member
 

Joined: Mon May 12th, 2008
Location: Netherlands
Posts: 55
Status: 
Offline
Hi,

Currently I use Sisu for a set of 32 bit binaries (exe + ~ 6 dlls). Soon I will be building them as 64 bit as well.

The 32bit binaries are in E:\cpp\bin\Win32\Release (+ subdirs). The 64bit binaries will be in E:\cpp\bin\x64\Release.

Obviously, the strings/dialogs etc to be translated are exactly the same for both platforms. Also the name of the exe/dll is the same, only their location is different.

I wonder what the easiest/best Sisu setup is for this.

Should I make a copy of the slp file and change it for the new 64 bit  locations? If I do this, I guess I need to import translations to both slp files... A bit messy and error prone, I think.

Or should I add the 64bit binaries to my current slp? That may be confusing to my translators (they see the same dialog twice, once for the 32bit binary, once for the 64bit binary).

Am I missing something?

Gert

Back To Top PM Private Upload Quote Reply

 Posted: Fri Nov 13th, 2009 11:34 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

I would not care to much about your translator. Since Sisulizer automatically translates all duplicates he might not even see the duplicate dialogs. Just tell him that you have 32-Bit and 64-Bit in one project and due to the automatic he only needs to translate once. He will understand.

And then you have everything in one place. No need to sync - clean - easy - convinient. The way it should be.

Markus



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

 Posted: Fri Nov 13th, 2009 11:36 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3266
Status: 
Offline
Btw: Nice to hear that you support 64-bit soon. I went for Windows 7 with 64-bit and are happy with it except that there are not too much 64-bit apps. Hope that will change soon with vendors like you!

Markus



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

 Posted: Fri Nov 13th, 2009 11:42 am
PM Private Upload Quote Reply
GertRijs
Member
 

Joined: Mon May 12th, 2008
Location: Netherlands
Posts: 55
Status: 
Offline
Thanks Markus, I guess I will do that then.

Gert

Back To Top PM Private Upload Quote Reply

 Posted: Fri Nov 13th, 2009 11:50 am
PM Private Upload Quote Reply
GertRijs
Member
 

Joined: Mon May 12th, 2008
Location: Netherlands
Posts: 55
Status: 
Offline
I just had this thought....

Suppose I change the sisu settings so it will use
E:\SisuMe
as the base directory for its source exe/dll files.


When I want to build a new release, a script that
copies "win32" to E:\SisuMe
runs sisu to translate the binaries
.... lots of other processing
cleans E:\SisuMe
copies "x64" to E:\SisuMe
runs sisu to translate the binaries
.... lots of other processing

This should work I think? That way I can have only one sisu slp file without "duplicate" sources.

Back To Top PM Private Upload Quote Reply

 Posted: Fri Nov 13th, 2009 12:04 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

Please give it a try and report. Since the structure of your 32- and 64-bit binaries should be identical it might work.

Hope to hear from you soon

Markus




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

 Posted: Fri Nov 13th, 2009 12:17 pm
PM Private Upload Quote Reply
GertRijs
Member
 

Joined: Mon May 12th, 2008
Location: Netherlands
Posts: 55
Status: 
Offline
Probably somewhere next week.

You are already on our http://www.fileviking.com beta-list (did you receive my email last week?), so you can expect to test the File Viking 64 bit edition soon.

Back To Top PM Private Upload Quote Reply

 Posted: Fri Nov 13th, 2009 04:01 pm
PM Private Upload Quote Reply
GertRijs
Member
 

Joined: Mon May 12th, 2008
Location: Netherlands
Posts: 55
Status: 
Offline
This may go to "feature requests".

I didn't try the script (bat file) option yet, but a much more cleaner way of handling this might be to introduce "global variables" or "defines" to sisu.

So, for slmake or sisu itself I start it like

slmake /define:SUBDIR=win32 ...other options...

and in all settings I use something like
E:\cpp\bin\{SUBDIR}\release\MyProgToTranslate.exe
and sisu replaces it automatically... so it becomes
E:\cpp\bin\win32\release\MyProgToTranslate.exe

Talk to your developers about it, they will love the idea, I'm sure ;-)

Back To Top PM Private Upload Quote Reply

 Posted: Fri Nov 13th, 2009 04:53 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3266
Status: 
Offline
What would you think of envoronment variables? You could set them with SET mypath=c:\xyz in your bat before you call SLMake. So far I could not convince R&D about that idea.

Markus



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

 Posted: Sat Nov 14th, 2009 08:47 am
PM Private Upload Quote Reply
GertRijs
Member
 

Joined: Mon May 12th, 2008
Location: Netherlands
Posts: 55
Status: 
Offline
For me environment variables would work just as well.

However, using command-line parameters is a bit more flexible, I think.

> So far I could not convince R&D about that idea.

When I talked to you earlier this year, you told me they are "hard core developers"... They should love this idea ;-)

Back To Top PM Private Upload Quote Reply

 Posted: Mon Nov 16th, 2009 06:23 am
PM Private Upload Quote Reply
GertRijs
Member
 

Joined: Mon May 12th, 2008
Location: Netherlands
Posts: 55
Status: 
Offline
FYI,

It seems to work fine (the script solution):
copies "win32" to E:\SisuMe
runs sisu to translate the binaries
.... lots of other processing
cleans E:\SisuMe
copies "x64" to E:\SisuMe
runs sisu to translate the binaries
.... lots of other processing

Back To Top PM Private Upload Quote Reply

 Posted: Mon Nov 23rd, 2009 02:45 pm
PM Private Upload Quote Reply
GertRijs
Member
 

Joined: Mon May 12th, 2008
Location: Netherlands
Posts: 55
Status: 
Offline
While the above works (copying the binaries), my current build script works like this:
http://www.delphi-localization-tool.com/?p=28
(Yes, a post on Sisulizer's own blog ;-)
Basically, my build script creates a copy of the slp file where it changes the source directory (where the win32 binaries are) to the x64 source directory. Then runs Sisu with the new slp.

Gert

Back To Top PM Private Upload Quote Reply

 Posted: Mon Nov 23rd, 2009 03:09 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

You should really read Gert's post on our blog.

Markus

P.S.: We swear that Gert was neither bribed nor tortured in the making of his posts :-) He is an ISV and you should take a look at the software he localizes with Sisulizer here: http://www.watchdirectory.net



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

Current time is 07:13 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > 32 bit and 64 bit platforms



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

Impress - Privacy statement

Sisulizer software localization tool - Three simple steps to localize