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
Building of language files with language-specific codes - 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: Thu Aug 6th, 2020 01:40 pm
PM Private Upload Quote Reply
LeenaHaapoja
Member
 

Joined: Thu Aug 6th, 2020
Location: Espoo, Finland
Posts: 4
Status: 
Offline
I have been using Sisulizer for some time now, and built source files in all available languages for several times now. The original source files are in English (en-US), and I'm creating the translations in Finnish (fi-FI) and Swedish (sv-SE). Every time when building the files, all files are named according to the original language, for example, "filename_en-US.xml". I then must rename all the FI and SV files manually, and that feels a bit stupid.

Are there any options or preferences where I can define the output files to have the correct language code in their names.

Previously I have been using SDL Passolo localization tool, and there it was possible to make these definitions.

Back To Top PM Private Upload Quote Reply

 Posted: Mon Aug 10th, 2020 07:17 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3877
Status: 
Offline
Hello,
You can change it. Go to Project menu -> Edit source -> select your source, or right click on source node in the Project Tree and select Properties item, Next, in the Properties dialog window go to File tab. Here you set output folder, type specified output file name or use output pattern name (this is very useful, if you fave multiple languages in a project). Here is additional info about this: https://www.sisulizer.com/online-help/SourceCodeSourceDialogFileSheet.shtml
Janusz

Attachment: output.png (Downloaded 8 times)



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

 Posted: Mon Aug 10th, 2020 09:18 am
PM Private Upload Quote Reply
LeenaHaapoja
Member
 

Joined: Thu Aug 6th, 2020
Location: Espoo, Finland
Posts: 4
Status: 
Offline
Thanks, I will check that.

Back To Top PM Private Upload Quote Reply

 Posted: Mon Aug 10th, 2020 10:02 am
PM Private Upload Quote Reply
LeenaHaapoja
Member
 

Joined: Thu Aug 6th, 2020
Location: Espoo, Finland
Posts: 4
Status: 
Offline
I checked the project properties, and since all the original files have the language code "en", I cannot get rid of it?

I, however, was testing with the following parameters:

<sl><body>_<sl>.<ext>

which then generates files with both 'en' and the 'language code' files, e.g.:

Application.AccountGroup_en_sv.xml

In this case I would any way have to remove the 'en' code manually from the file names? So there is no possibility to replace the 'en' code during building of the files?

So I guess the only solution here is to remove the 'en' language code from the source files, and then the correct file naming would work ok?

Attachment: Sisulizer_File.png (Downloaded 7 times)

Last edited on Mon Aug 10th, 2020 10:15 am by LeenaHaapoja

Back To Top PM Private Upload Quote Reply

 Posted: Mon Aug 10th, 2020 11:19 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3877
Status: 
Offline
If you plan localize your application only into one language, you can simple type full name for output file, e.g. Application.AccountGroup_en_sv.xml. But you can't use this solution, if you would like localize it to multiple languages. Optionally you can change name of source file(s) or output files outside Sisulizer. I suggest do it with source files, because you have only one language source files, so you needn't change names of output files built in many languages. You need only replace (and change name) source files in this workflow after updating of sources, while with changing of output filenames you need do it not only after updating of sources, but also after every building output files by Sisulizer. Note, if you changes source filename, you need add it as new source to your SLP project, but this is only onetime operation. If you need change names for lot of files I recommend using of third party software with batch mode for this. There are lot of tools with batch name replacing support. I use freeware Advanced Renamer for many years.
Janusz



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

 Posted: Mon Aug 10th, 2020 01:05 pm
PM Private Upload Quote Reply
LeenaHaapoja
Member
 

Joined: Thu Aug 6th, 2020
Location: Espoo, Finland
Posts: 4
Status: 
Offline
Thanks, Janusz for your replies!

I will discuss possible renaming of the source files with our SW development teams, but in the meantime, I will use a batch renaming software - so thanks for giving a hint about that, too.

Back To Top PM Private Upload Quote Reply

Current time is 01:20 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 > Building of language files with language-specific codes



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