|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Charset for importing po-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 | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
carval Member
|
Hello, I have imported a spanish po-file, which has utf-8 charset. What I get are strange, cryptic chars if a string contains chars like "á" in "Datos básicos". In sizulizer help I found something about po localization, so I changed the charset of my po-files to "text/plain; charset=CHARSET" and imported them again. This didn't work either. What is the secret to import and display such strings? Can you help us?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi, Can you please zip your po and slp-file and upload it. Please use the new "Private Upload" button right above this post. It helps us to keep track of uploads and forums posts. We take a look Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, Your project is for .NET (Visual Studio project) platform. This platform use UTF-8 with BOM (Byte Order Mark) encoding, while imported PO files generated by POEdit have also UTF-8 format but without BOM, and for this reason Sisulizer can't correctly import some characters. Import from PO files is rather dedicated for Sisulizer projects based on PO files where both source and imported file have this same encoding, that is UTF-8 w/o BOM and it work perfectly - I performed also test with your files, and Sisulizer imported correctly all accented Spanish characters. I'll ask our developers about adding support for similar cases (import from UTF-8 w/o BOM resources to project based on source files use UTF-8 with BOM) to import feature. Workaround: Open Spanish PO file in any advanced text editor (e.g. RJ Texted, PSPad, Ultraedit etc.) and save it as UTF with BOM file. Next import this converted file to your Sisulizer project. You can also use to conversion your file, very good and freeware tool named Kaboom written by Markus. You can find more information and download this tool here: http://www.sisulizer.com/kaboom/index.shtml Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
carval Member
|
Hi, thanks a lot for the quick help and information. Now everything works fine. 
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
I fixed this in 292. Now Sisulizer can correctly detect the encdoing of PO files even they do not use BOM. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 08:30 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 > Charset for importing po-files | |
Sisulizer software localization tool - Three simple steps to localize
