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
Placing translated files to different folder - 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: Tue Dec 5th, 2017 04:01 pm
PM Private Upload Quote Reply
mikakoistinen
Member
 

Joined: Tue Sep 26th, 2017
Location:  
Posts: 2
Status: 
Offline
Hi,
Is it possible to place translated files (app.FI, app.EN) to different subfolder.
Our app distribution system in customers internal network assumes that only .exe, .bpl and .dll exists in application directory.
If not we can live with that, but if it's possible it would help us a lot.

Back To Top PM Private Upload Quote Reply

 Posted: Tue Dec 5th, 2017 05:29 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


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

Check out Project - Edit Source - <your source>. There you find an output section. This should do the trick.

If not you still can use SLMake.exe in a batch and move the files if needed by move commands.

Markus



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

 Posted: Tue Dec 5th, 2017 05:53 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1981
Status: 
Offline
Hi,

Right click the Delphi source on project tree and choose properties. Select the File sheet and enter the output directory into Output directory files.

This directory is also used in SlMake. However when using SlMake you can override the output directory by using the -output option. For example

SlMake create -output:"C:\Output" Sample.slp

The above will direct output to C:\Output no matter that is the value defined in the source's properties.

Ilkka

Attachment: Untitled.png (Downloaded 7 times)



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

 Posted: Tue Dec 5th, 2017 06:10 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3781
Status: 
Offline
Here is detailed info about output settings: https://www.the-localization-tool.com/where-i-can-set-up-output-file-names-and-paths/

Best regards,
Janusz



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

 Posted: Thu Dec 7th, 2017 07:59 am
PM Private Upload Quote Reply
mikakoistinen
Member
 

Joined: Tue Sep 26th, 2017
Location:  
Posts: 2
Status: 
Offline
Thanks to all for replies.
But how to tell in Delphi application that it should look translated resources from languages\ subfolder?

Back To Top PM Private Upload Quote Reply

 Posted: Thu Dec 7th, 2017 11:28 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3030
Status: 
Offline
The resource files are loaded by VCL automatically. It looks for them in the same path the main binary is located.

But you can embed the dlls into your binary. This way your customer will not have the dlls in the program dir. Anyway the VCL will create these files at runtime of your program to the path your exe is located. At program end these files become deleted.

Here you find background info about resource dlls and how to change language at runtime. It does not fit 100% the topic but is a good start to understand VCL and resources:

https://www.sisulizer.com/online-help/RuntimeLanguageChangeVcl.shtml

Perhaps our R&D has some hint how to overcome this VCL limitation.

Markus



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

Current time is 06:34 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 > Placing translated files to different folder



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