|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Importing translated RC 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
renatonow Member 
|
Hi: So far our translation approach was to localize individual .RC files manually. Now that we have Sisulizer I wonder if there is any way to import the already translated .RC files to save us some time avoiding the translation of everything again. Cheers, Renato
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Renato, you can inport .rc using File- Import - but only to existing .rc resources of the same kind. So you might want to make a new project from the original .rc, import the other languages in .rcs to it and the export everything to e.g. a text file with the Export Wizard. Now you can import the language pairs to any project. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
renatonow Member
|
Works very nice, thanks a lot!
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
jhung Member
|
I tried the above method: created a new project from the original nvDispS.rc, imported the other language in zht\nvDispS.rc to it, no string was imported. Any steps I missed? Thanks for helping. Jenny Last edited on Wed Sep 19th, 2007 10:16 pm by jhung |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Can you send nvDispS.rc and zht\nvDispS.rc to me support (at) sisulizer.fi Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
jhung Member
|
Sure, I'll send them as attached. Thanks, Jenny Hi Jaakko, since you got the files, for confidential reasons I am going to remove Sample.zip from the posting. Let me know if you need it later. Thanks for looking at those files. Jenny Last edited on Thu Sep 20th, 2007 06:14 pm by jhung |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
Hi Jenny, The attached zip file contains only the Chinese RC. Can you also send the original (English?) RC. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
Sorry. Forget my previous email. I got all files. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
Hi Jenny, The Traditonal Chinese RC file your sent is in Unicode (UTF-16) but it contains the following line: #pragma code_page(950) This tells that the file uses code page encoding and uses code page 950. Now there is conflict: the file is in Unicode but it tells that it does not use Unicode. This made scanning of the file to fail. I converted your Chinese file from Unicode to code page file (attached) and Sisulizer could import that. I also found one bug. When you create a new project for your RC Project Wizard shows a message: Thre are existing translations: - Original (...) Do you want to import them? If you click Yes Sisulizer add and invalid language (Original) to the project and imports nothing. If you click No everything works OK. I fixed the bug in 1.6.9 1.6.9 will come out very soon. I will inform you when it is ready. I will change RC scanning such way that if the file is in Unicode then Sisulizer ignores the #pragma code_page(xxx) line. Thank you for your bug report and files. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
jhung Member
|
Hi Jaakko, It works! You are wonderful. Thank you for the quick fix. Jenny For confidential reason I would appreciate if you can remove the attachment you posted. The dream tool for software localization is coming for real now - Thanks to Sisulizer! Last edited on Thu Sep 20th, 2007 10:28 pm by jhung |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
tscherf Member
|
Hi Jaakko, Funny, I am actually following up on Jenny's work. She is a coworker of mine. I tried to import translations from localized .RC files that had the pragma tag indicating an ANSI code page, yet the encoding is UTF-16. That still does not work. It worked once I saved the files back to their correct ANSI encoding as specified in the pragma line. One issue I have is that I get all translations from my previously translated .RC files, expecpt for one. It only picks up part of the translation and leaves me with about 3000 non-translated words. If I send you my files, can you check what the reason for this is? Also, is the fix for the pragma issue going to be in the next build? Thanks. Toby
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
tscherf Member
|
Hi Jaakko, Another thing. I've created a project with 28 languages, for which I need translations imported from 8 .rc files each. Is there a way to bulk import? The source consists of 8 .rc files for which I have corresponding localized .rc files. I believe I tried a bulk import but it wouldn't take the translations. Thanks for your help.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
Hi Toby, Yes please send the files to support (at) sisulizer.fi Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
tscherf wrote: Another thing. I've created a project with 28 languages, for which I need translations imported from 8 .rc files each. Is there a way to bulk import? The source consists of 8 .rc files for which I have corresponding localized .rc files. I believe I tried a bulk import but it wouldn't take the translations. Thanks for your help. The bulk import existing when you create new project but unfortunately it does not work on RC file. I will implement this. I can implement a feature where you scan select multiple import fiels at the same time. However this only helps you if the files are on the same directory. I start thinking a multifile import feature for Import Wizard when you first select all files you want to import and then step throgu rest of the wizard. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
No need to send the file. I still have Jenny's files.
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
tscherf Member
|
I have another issue relating to translation imports. I simulated the exchange with Translators / Editors and found when I took the file back from Translation changes to implementation in the project it did not pull in all of my translations. The project file that I imported was an .slp file. Upon further investigation I noticed that the translation was infact identical to the source, so this happens on strings where source and translation strings match. Is this a setting I am missing? Those strings were marked as complete on the Translator side of things.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Renate.Reinartz Administrator 
|
Hi Toby, Please take a look at attached screen shot. If you import a Sisulizer project (.slp) you have more options. Regarding your question: Please check if option Import also those items where the translated value equals to the original value is checked. Check which Overwrite method fits best to your needs. May be you want to change it to If the import status is higher than the current status. The saviest way is to check Confirm overwrite, but it can be quite annoying if there are a lot of strings to overwrite. The default settings of this dialog fit for most cases. Anyway be careful with your settings in this dialog. Make sure you set all options like you need them. Better consult the corresponding online help page, too. This importing is very flexible, but the right settings e.g. for Translation status import depend on your workflow. In example: Will the translator deliver all translations with status set to complete, or will he/she provide with his translation status more information? How is the translation status currently? These are questions you have to solve, but for every case you will find the right option in this dialog. Just set the corresponding option in Import translation status. Hope this helps Renate Attachment: sl-import-wizard-slp.jpg (Downloaded 8 times)
____________________ http://www.sisulizer.de - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 04:02 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 translated RC files | |
Sisulizer software localization tool - Three simple steps to localize
