|
|||
|
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 > Translation import for a subset of files/languages
|
|
|||
|
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 > Translation import for a subset of files/languages
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Translation import for a subset of files/languages - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Olivier_ho Member
|
Hi, Our programmers are requested to write the interface in English, but they are French, and very often, they also design the French interface at the same time (especially when they have an urgent delivery to do...). Therefore, the situation in which I should Scan for changes + get French translations as done by the developer is quite frequent. Now, when I do that, it updates all languages and all files of the project, when I would rather use the Project\Import translations from localized files option only for one file, one language, usually. Is there a way to do that ? Thanks, Olivier.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello Olivier, I afraid my help for you will be useless, because I can't guess how you work with your developers, and either you get from your developer source code and you comile binary files or you get only binary files, but mixed original language e.g. French-English could produce many unexpected problems. If you your developers are native French speakers, maybe better solution is rebuild your project, set French as original and English as alternative original. Usually English is the best choice for original language because it is likely that you can find much more translator from English to your target language as for example from French to your target languages. By setting alternative original language to English than none Sisulizer does not show French original strings in the original column but translated strings in English language. This makes it possible to change the translator language pair suitable for your translator. You could select as alternative original any language from already existing languages in your project. Alternative original setting is available in menu Project > Options… > General. Below is screenshot from General tab of project options. Attachment: screen.png (Downloaded 49 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
Now, when I do that, it updates all languages and all files of the project, when I would rather use the ProjectImport translations from localized files option only for one file, one language, usually. Instead menu Project > Import Translation from Localized Files you could use File > Import… This import method allows you select source file and targeted language column for translations import, because this import option always use "By context" import method, you have certain that translation will be imported only to selected file (node) in your project . Below is link to discussion on forum about differences between these mentioned above import methods: http://forum.sisulizer.com/forum3/1010.html Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
One additional hint: If you use Project - Scan for Changes Sisulizer will Scan for Changes in all files. But if you right click a source in the project tree and click Scan for Changes Sisulizer will only scan the selected source. Might be better than scan all sources in the project. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Olivier_ho Member
|
Thank you for all those hints. What I was looking for was the File\Import method, which indeed does what I want. -> just a question about that function : When I run File\Import, it asks me whether I want to save the project first. If I answer No, it does nothing. Is it on purpose that you cannot import without saving the project? I tried the Alternate source language option. This is nice and will be useful to me, but it raised a question: when you run Scan for changes using that option, it does not scan the alternate language file, does it? Thanks, Olivier.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hi Olivier,When I run FileImport, it asks me whether I want to save the project first. If I answer No, it does nothing. Is it on purpose that you cannot import without saving the project?This message is displayed for all important project operations, if you have not saved changes in project. It allows you avoid unexpected loss of your data, and when you would like perform import operation, you should in this case click 'Yes'. I tried the Alternate source language option. This is nice and will be useful to me, but it raised a question: when you run Scan for changes using that option, it does not scan the alternate language file, does it?You have always one language in your source e.g. binary files, alternative original is "virtual" original included to your project, not to original source, and for this reason Scan for changes concern only real existing language of your source. For your case I suggest you following work method: - Your developers send to you updated resources with French strings - You update (scan for changes) resources in your project. - Your project should to have French as original and English as translation, and you should update English column contents for changed and new French strings. - Next you send project to your translators, but with set up English as alternative original - All your translators will see only English language as original. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Olivier_ho Member
|
Janusz Grzybek wrote:This message is displayed for all important project operations, if you have not saved changes in project. It allows you avoid unexpected loss of your data, and when you would like perform import operation, you should in this case click 'Yes'. My question was : if I click Yes, it saves the project AND then runs the import. There is no way to run the import *without* saving the project. Is it normal?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Yes, you can't run import without saving project, but message is displayed only if you have unsaved changes. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hi Olivier,There is no way to run the import *without* saving the project. Is it normal? It was changed in build 275, and now when you click ‘No’ in confirmation message, import will be performed without saving of project. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 01:37 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 > Translation import for a subset of files/languages | |
Sisulizer software localization tool - Three simple steps to localize
