|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > rows in new project messed up
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > rows in new project messed up
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| rows in new project messed up - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Ninke Member
|
Dear support people, One of our .properties files in a java project is not handled as we would wish. It's a file with special characters, and reading in a Sisulizer project is not correct. Also the output of the translation, changes the characters. Here is the text of the file: key.disp.0=1234567890-\= key.disp.1=QWERTYUIOP[]\ key.disp.2=`ASDFGHJKL;' key.disp.3=ZXCVBNM,./ key.shift.0=\!_(at)_\#$%^&*()_+ key.shift.1=QWERTYUIOP{}| key.shift.2=~ASDFGHJKL\:" key.shift.3=ZXCVBNM<>? In the attachment I add an image where you can see how this looks in Sisulizer. The row key.disp.2 is sticked to key.disp.1. And the backslash characters have dissappeared. In exporting a translation of these strings, the backslash is still disappeared, but we need it in our code. Is this something you can change? Or should we leave these strings out of our translations? Best regards, Ninke Attachment: codeFile.jpg (Downloaded 19 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator 
|
I am working on this. Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Ilkka.Salmenius Administrator
|
Backslash character (\) is used as escape character in .properties file. It means that \= is not \ and = but just =. If you want to have \ character in your string you have to write ti twice \ key.disp.0=1234567890-\= -> 1234567890-= but key.disp.0=1234567890-\\= -> 1234567890-\= Also if the last character of any .properties line is \ then the next line is appended to that line. In your file key.disp.1=QWERTYUIOP[]\ key.disp.2=`ASDFGHJKL;' Becomes key.disp.1=QWERTYUIOP[]key.disp.2=`ASDFGHJKL;' Change it to key.disp.1=QWERTYUIOP[]\\ key.disp.2=`ASDFGHJKL;' You can read more about .properties format from http://en.wikipedia.org/wiki/.properties Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ninke Member
|
Hello Ilkka, Thanks for your answer. Our software developers are aware of the use of escape characters. Actually we need the functionality in the code. But in some languages it might be necessary to change some characters in our string. It would be nice if we could use Sisulizer for this. We cannot change our .properties files, because then the source language will behave different from its translations. If it is not possible to import and export our strings as an exact copy in Sisulizer, we will exclude them from the project and make the changes manually. But if you can provide a better solution, we would be glad to hear. Best regards, Ninke
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Ilkka.Salmenius Administrator
|
Ninke wrote: But if you can provide a better solution, we would be glad to hear. Use text file localization. First you have to map properties extension to text file. Choose Tools | General and see the screen shot. Now when you have mapped the file every time you select a .properties file Sisulizer ask you what parser to use. Select Text. Sisulizer will detect the format incorretly. Remove the second field. See the second screenshot. Ilkka Attachment: Untitled.png (Downloaded 8 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator
|
Wait a moment. There is a problem in this mapping. I will check this. Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Ilkka.Salmenius Administrator
|
Here is screenshot about Project Wizard when you have selected .properties file and choosed Text parser. The problerm with current build is that it does not remember the new map you added and but changes the default mapping of properties to text. I fixed this. The fix will be in the next build (330) that will be released later this week. Ilkka Attachment: Untitled.png (Downloaded 7 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 05:10 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > rows in new project messed up | |
Sisulizer software localization tool - Three simple steps to localize
