|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| support .bundle extension - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
jlsymantec Member
|
Using PHP codes, all localizable strings are externalized to .bundle format. a .bundle text string format is exactly the same as java resource only .properties file for example: Context=English_string there is an exception. Java has to indicate the filename by insert <lang_code>, for example: French - sample_fr_FR.properties where sample_<lang_code>.properties. However, in .bundle, there is no such rule. Once you build the resource .bundle, no need to have language_code on the filename. English - sample.bundle japanese - sample.bundle So to come around, language specific subfolder will keep the .bundle file Wish list: /en/sample.bundle /ja/sample.bundle /fr/sample.bundle ... .. can you add a supported .bundle extension?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, You could use following pattern <sl>sample.bundle in “Output files” field and as result you will get: /en/sample.bundle /ja/sample.bundle /fr/sample.bundle However I think better solution is usage following pattern: <sl><body>.bundle, because it is more flexible solution. For example when you use “Localize all similar files in a directory” and you have in this directory more files e.g. sample.php and second_sample.php you will get for <sl>sample.bundle only one output file, that is, sample.bundle (as in your example above), while for <sl><body>.bundle Ssisulizer will create following output files structure: /en/sample.bundle /en/second_sample.bundle /ja/sample.bundle /ja/second_sample.bundle /fr/sample.bundle /fr/second_sample.bundle You could to set up output pattern via right click on source node in Project tree and select Properties item from context menu: Attachment: screen.png (Downloaded 42 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Sisulizer allows on very flexible output pathname management. You could use wildcards in pathnames and real pathname parts mixed with special Sisulizer pathname patterns. Sisulizer use two types of pathname patterns: 1. File parameters: <file> Variable is replaced with the original file name with extension. <relativefile> Variable is replaced with the relative file to the source file. <body> Variable is replaced with the original file name without extension. <ext> Variable is replaced with the original file extension without period. 2. Language parameters: <sl> Sisulizer's locale code is used. <iso> ISO locale code is used. It is combination of language and country. <net> NET culture code is used. It is combination of language and country. <win> Windows locale code is used. It contains two or three upper case characters. For example "EN" is for English, "ENU" is for English (United Stated), and "CHT" is for Traditional Chinese. <mfc> MFC locale code is used. It contains three upper case characters. For example "ENE" is for English, "ENG" is for English (United Kingdom), and "CHT" is for Traditional Chinese. <nls> Windows locale id is used. It is a integer number containing the primary and sub language ids. <hex> As above but four digit hex value is used instead decimal value. Below you could to see to different examples of pattern usage: For example if the original file is C:MyFilesSample.xml and the pattern is <body>_<iso>.<ext> the German (Austria) file will be C:MyFilesSample_de_AT.xml. For example if the original file is C:MyFilesSample.xml and the pattern is <sl><file> the Chinese (Taiwan) file will be C:MyFileszh.traSample.xml. More information you could to find here: http://www.sisulizer.com/online-help/DelphiSourceDialogFileSheet.htm Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
jlsymantec Member
|
Wonderful, let me give it a try!!
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
jlsymantec Member
|
sweet, it works, thanks a lot!
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
jlsymantec Member
|
sweet, it works, thanks a lot!
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:02 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > support .bundle extension | |
Sisulizer software localization tool - Three simple steps to localize
