|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| modify original resources - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
erik Member
|
Let's say I find a typing error in the original resources. Can I change it with Sisulizer directly? I haven't found a way to do this yet.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Erik, Sisulizer never changes your sources. It only scans them and combines them with your translations to new files. If you find a typo in your sources you have to edit your sources and then use Project - Scan for Changes to update Sisulizer. While Sisulizer uses the context and not the value to indentify your strings there will be no translation lost. After Scan for Changes the row will have a red row status marker. This means that the orginal was changed and your translation might need a review. In the case of an typo you can ignore that status for the changed row. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
erik Member
|
Well, changing the sources would be great feature, it would certainly save time. Perhaps if there was the possibility to "unlock" the source, correct the typo, and then "lock" it again.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Erik, it is a golden rule for Software Localization tools never changes source code. In most projects the translator is not the developer. And the developer would not like the idea that the translator can edit the source in any way. You can do a trick. Simply add the language of your original as a target language. Then you can collect the correction in the virtual target language and you can use Sisulizer to build a corrected original for you. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
brunis Member
|
Your golden rule is a pretty silly argument. Building an item in sisulizer overwrites all my existing .en-us.resx resources. Locking the application to one specific purpose to uphold the golden rule is just as silly. I'd have to second the request to allow editing of the default (original) language. Could be a checkbox option in the languages pane. It could come with a warning like: "for developers only, if you're a tranlator, don't use this". Or something similar. Having this tool as a resource editor instead of visual studio, would be very useful to our developers.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Brunis, >>Building an item in sisulizer overwrites all my existing .en-us.resx resources. Sure, Sisulizer has to write the files. The steps are: a) Scan. Sisulizer scans files. These are by definition not localized and have one language. b) Translate. Now the strings are in the Sisulizer project. c) Build. Sisulizer writes new files. These are now localized and can have more than one language. In .NET there is a naming schema and Sisulizer follows it. Some of you might have already localized outside of Sisulizer and created manually one of the files Sisulizer has to build. To profit from already translated strings imports these languages. The new project wizard finds them - if in .NET naming standard - and imports them automatically by request. For Sisulizer they are not part of the localization source. You can think of these existing translations as a form of translation memory. After the import these translations are safed in the .slp. All information from such container like e.g. .en-us.resx files is extracted and is not needed anymore. Sisulizer now has the authority over these files and they are not meant to be maintained manually anymore. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 07:54 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 > modify original resources | |
Sisulizer software localization tool - Three simple steps to localize
