|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > import existing translations from a tree directory structure
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > import existing translations from a tree directory structure
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| import existing translations from a tree directory structure - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Ninke Member
|
Hello Sisulizer team, I'm evaluating Sisulizer (standard and professional) and I wonder if it is possible to import existing translations from a directory structure. In the documentation I read: 'if you have selected MyFile.properties file and there exists MyFile_de.properties file, Project Wizard will add German to the project and imports translations from MyFile_de.properties' This is really useful functionality, but it seems not to work with the Project Wizard option 'Localize all similar files in a directory'. Our Java software consists of a large directory structure, with many folders. In a lot of folders are .properties files. Where translations already exist, there are files like the following in one folder: screen_en.properties, screen_nl.properties, screen_de.properties. We like to import all these directories at once, where Sisulizer recognizes the existing translations. Is this possible? Best regards, Ninke
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, If you would like you use"Import Translations from Localized Files" your directory structure and filenames of localized files should be matched with Output directory and Output files settings in "File" tab in source properties dialog. Source properties dialog is available via "Project" menu -> "Edit source" or via context menu of your directory node in Project Tree (I think you use "Localize all similar files in a directory" method) . Here is article about output files settings: http://www.the-localization-tool.com/?p=30 . Example: You can build your empty (not translated) Sisulizer project and next compare output directory structure with your localized directory. Then, you can change file output settings in Sisuliuzer or simply copy localized files to output directory generated by Sisulizer. Next you can perform Import Translations from Localized Files. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Ninke Member
|
Hello Janusz, Thank you for your explanation. I start to understand things in Sisulizer. We had some other 'problems' as well. Our source-files had the language code '_en' added (screen_en.properties, instead of screen.properties) and our Danish translations had _dk instead of _da. Now we changed this, it works perfectly. Thank you. Best regards, Ninke
|
||||||||||||||||
| |||||||||||||||||
| Current time is 05:42 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 > import existing translations from a tree directory structure | |
Sisulizer software localization tool - Three simple steps to localize
