|
|||
|
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Importing translations from localized files
|
|
|||
|
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Importing translations from localized files
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Importing translations from localized files - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... | ||||||||||||||
| Author | Post | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
khuber Member
|
I am trying to import .PO files for several languages. So far I figured out that the following works best: - Import .pot files using the Import wizard - Use the command "import translations from localized files" => the program automatically detects the translated strings from the PO files (if they are in the same directory) and associates them with the right source string My questions are: - is there a better/faster way to import PO files for several languages? - is there a way how I can avoid having to give the .pot file since all my .PO files already contain the native language anyways? - since I have to give the .POT file for each translation together with the .PO files I cannot mark several files at once for import since the program cannot associate multiple .POT files then. Is there a way around this? - is there a way to change the postfix character => I would need <.> instead of <_>? e.g. myfile.de.po and not myfile-de.po - can I change the directory where I am looking for the translated files since otherwise I have to copy all into one directory? - how can I avoid that in the context column the path of the source file will be attached? Last edited on Thu Jul 31st, 2008 03:38 pm by khuber |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi, you will find the settings you are looking for if you use Project - Edit Source. There you can change paths and seperators. The context column needs to be unique. This is only possible if there is a path. Else two .po files in different dirs would have the same context. If you send your .po / .pot files plus your .slp in a .zip to support (at) sisulizer.fi we will check if there is a better way to localize them with Sisulizer. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
khuber Member
|
Thanks for the swift reply: - the method you describe works but I have to set the postfix for each PO file. Since I have dozens of them this is rather tedious. Could you consider to rather move this to a more central place since I guess the postfix character will be the same for all files anyway? Alternative: - I could merge all .PO files but this also means that I have to merge all .POT files and present them to Sisulizer again. Do you see any other way than that for now? - is there a way how I can merge .PO files with Sisulizer itself?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, the place for such global settings would be Tools -> Platforms. But in the moment there are no global settings for .po but I can move this thread to the Sisulizer wish list for future versions. For the moment you could try to add all files to one project, change one file to your needs and then edit the other entries in Sisulizer project .slp with some text or XML editor. This should speed up things. While you have to do this only once it should be a not top bad solution for now. Nevertheless we can move this thread to the wish list. If you send me your files we can also try here if we find some better way for them. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
khuber Member
|
Hi, Would have been a great idea. I did what you said and edited the .slp file with a text editor. Now the program should find the files but it tells me that it cannot find them even though it writes the correct extension now in the error message... Seems that the message now is correct but that the program cannot digest any other postfixes than <_> or at least no file extension with more than one <.>? BTW: when I use the "copy" command in the log view it always copies all the strings and not only the one that is marked... is this as it is intended? Thanks.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, yes, you always get the whole log in the clipboard. If you send me your files I will take a look. If something is odd I will forward it to R&D for repair. Without the files I can only guess what happened and where a possible missunderstanding is. Please send it to support (at) sisulizer.fi. The files are held confidential. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
khuber Member
|
Hi, No problem, I will rename the file extensions. Maybe you could have your developers check if files with several <.> can be imported. Thanks
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, if you send me the files I can look into it. If there is an issue I will forward to R&D. Without a reproducable problem I can not put it to the R&D queue. I really would love to take a look to see if we can make something better or where the problem is. If you do not want to share the files I can understand, but then I can not llok deeper into it. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
khuber Member
|
Hi, Thanks for the offer. Unfortunately I cannot send you the files. Solution: Replacing file extensions did the job, seems to be a problem with more than one <.> in the file name as assumed. Thanks
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
One thing regarding the merging. A collegue gave me some background info I did not had. I don't think you will need to merge po files if you use Sisulizer. Simply create a new version of your .po and place it at the same place (same name and path). Then use Project - Scan for Changes. Sisulizer finds the changed and new strings. Existing translaions are re-used. You do not need to create a new Sisulizer project if you made a new version of your product. That's why I said you have to do the changes to the .slp only once for your product. Take a look at the movie showing this Sisulizer feature: http://www.sisulizer.com/swf/sisulizer-scanforchanges.shtml Hope this help Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator
|
We played a little bit around here and we think we find some reproducable issue with the two dots we can report to R&D. Thanks for your report Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
khuber Member
|
Hi, Thanks for your very dedicated support !!!
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator
|
Sorry for insisting so much on the files. But with them we can see problems even faster (the experience of many cases). But of course we understand if the are confidential... Thanks again fo you feedback Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 03:50 am | |
| Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Importing translations from localized files | |
Sisulizer software localization tool - Three simple steps to localize
