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
setting the folders (for source and target files) - 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 Apr 11th, 2017 10:59 am
PM Private Upload Quote Reply
MLoehr
Member
 

Joined: Tue Apr 11th, 2017
Location:  
Posts: 11
Status: 
Offline
Hi,

Is there a way to set the folders (for the source and target files) in one go? So far I've only found a way of doing it individually (apart from editing the XML project file).

Kind regards,
Michael

Back To Top PM Private Upload Quote Reply

 Posted: Tue Apr 11th, 2017 11:46 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2903
Status: 
Offline
The recommended way is to localize project files. Sisulizer picks up all needed files from the project. This way you do not need setup each EXE and its DLL individually.

Markus



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

 Posted: Tue Apr 11th, 2017 12:17 pm
PM Private Upload Quote Reply
MLoehr
Member
 

Joined: Tue Apr 11th, 2017
Location:  
Posts: 11
Status: 
Offline
Hi Markus,

Thanks for your reply. So far I've been working as follows (with a different software, I no longer will be using):

- start with German Version A (with around 200 components from one source folder)
- set up a project for the translation -> translate the German version A to English version A (generating all English components into one target folder)
- as soon as the translation process is finished, both folders are no longer accessable or marked read-only
- new German Version B arrives -> a new source folder with the new components is created
- the project settings are changed to this new source folder (this is what I'm missing in Sisulizer)
- the software now automatically looks for changes according to the new source folder

The point of this method is that I want to create defined "translation pairs". And I also want to be able to switch back to a certain version (e.g. in case of errors).

Is there a way to do this with Sisulizer? Or are there alternative methods?

Michael

Back To Top PM Private Upload Quote Reply

 Posted: Tue Apr 11th, 2017 12:45 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2903
Status: 
Offline
Sisulizer is organized a little bit different. It generates files into target folder in a way the target platform needs them. E.g. .NET is very strict with that. Files must be at a defined place. Sisulizer orgaizes them in a way that you directly can start your localized project after the build is done. This is only possible if the files are in the right place.

You can change the output path if your platform allows different paths under Project - Edit Source -<your source>. But it is not recommended to change it for every build run.  For some platforms there are limitations described above.

But there is an elagant way to use it nearly your way.

Simply create your projects using SLMake, our command line utility (an Enterprise feature). Always create to the same output path. In the same batch you add some copy logic that moves Sisulizer`s output files to your target locations.

https://www.the-localization-tool.com/category/how-to/slmake/

Hope you like this work-around.

Markus



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

 Posted: Tue Apr 11th, 2017 01:01 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3702
Status: 
Offline
I think Markus idea is best for you, but if you do not like this solution, optionally you can also use following solutions:
  • Add updated source folder as new source (required is different source path). Sisulizer should automatically re-translate it (based on matched original values or original and context values). You can separately manage sources, for example exclude specified source (eg. old), scan, build or export them separately. If you do not need old source, you can later remove it and keep only new in a SLP. Unfortunately, it can significantly increase size of project and using of system resources.
  • You can change source/output paths to folder with updated files and next re-scan SLP. Optionally you can save updated a SLP file with new name. This way you will keep old version. Here is article about Sisulizer path settings: https://www.the-localization-tool.com/where-i-can-set-up-output-file-names-and-paths/
Of course, those solution could be useless for you, but it depend on your workflow and developing platform

Janusz



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

Current time is 09:06 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 > setting the folders (for source and target files)



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