|
|||
|
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 incomplete translations from language DLLs
|
|
|||
|
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 incomplete translations from language DLLs
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Importing incomplete translations from language DLLs - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
lagucw Member
|
Hi there (sorry for the length of this but....), I am currently evaluating Sisulizer to replace our existing tool which doesn't handle C# translations or Html Help. It has an option to export to XLIFF but when I try to use the file in Sisulizer, I only get one DLL (there are 20 in the project) - the problem could be with the existing toll. So, it would seem that the best way to transfer existing projects would be to import the translated DLLs into Sisulizer. However, apart from French, German & Spanish, most of our translations are incomplete for various reasons. This may be because the translations are done by our software distributors in different countries and certain features of the software are not widely used everywhere so they translate as little as possible! Also it may be that they are still translating v5.0.2 and we have released v6.1 so they will want to use what translations they have so far in v5.0.2 and upgrade the Language Pack to v6.1. My problem is this - Using our existing, partially translated DLLs and the "Import translations from localized files" function causes all items to be marked as "Auto translated" - ie it assumes that as they are localised files then they are fully translated. Is it possible to import in a different way and retain the information about the translation status. I presume the only way would be if the import function compared the string in the original file to the string in the import file and if equal, mark the field as "not translated". I realise that certain strings would be incorrectly marked (eg 'Description' would be marked as 'not translated' in French when in fact the translation is the same) but there would be fewer instances of this, in my case at least! (I think this function would need to be an option switch). Is this function currently available? If not, any suggestions on how to sort this out? Thanks & regards, Chris
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello,Using our existing, partially translated DLLs and the "Import translations from localized files" function causes all items to be marked as "Auto translated" - ie it assumes that as they are localised files then they are fully translated.You can change default status of imported strings here: Menu Tools > General > Translation > Change translation status > When imported Attachment: Snap.png (Downloaded 61 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
Above UI item set up default status for all import operation, but if you use: Menu File > Import feature you can to set up status of imported translation only for selected import operation. Below is screenshot for import operation for localized DLL files (Import wizard has different steps and dialog windows for every supported format of imported files). If you during import from localized DLL you uncheck option “Import those items where the translated value equals to the original value” imported will be only really translated strings e.g. French, and all items identical with original language (usually not translated) of your Sisulizer project will be skipped Attachment: Snap1.png (Downloaded 61 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
Any localization tool doesn’t save status information directly to localized DLL. I don’t know your localization tool, and for this reason I don’t know also what import formats supports your tool. If your tool supports TMX (Translation Memory Exchange) format, you probably could to import your translation statutes via TMX file. Let me know via forum post or PM what tool you currently use, maybe I will find other ways to import of your translations to Sisulizer project. Below is screenshot Import Wizard for TMX file import with indicated section of status import. Attachment: Snap2.png (Downloaded 60 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
If you already imported translations from partially localized DLL together with not translated items, you could to filter all these not translated items in the Sisulizer, if you select menu View > Sheet filter > Edit > Text tab > Translated strings compared to originals > Identical. You have also access to Sheet filter via icon of Filter panel toolbar icon. This Filter allows you to see only translated strings identical with original (usually not translated), then you can select translation column and clear all contents of column. If you then click on “Default filter” in main toolbar or in Filter panel, you will see only real translation in sheet (e.g. French strings). Attachment: Snap3.png (Downloaded 60 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
lagucw Member
|
Hi Janusz, Many thanks for your excellent & rapid response. The switch within File/Import to turn off the import of equal items would appear to do what we want, as I can then sort out the untranslated items afterwards. However, our current Language Pack has 20 DLLs in it, and when I select the files to import in the Import Wizard (it lets me highlight all 20 files), only the first one gets imported. So, I used the 'Set Default' option within the wizard, and then used the 'Project/Import Translations From Localized Files' to import all 20 files but it doesn't seem to use the same options as the Wizard. Is there any way to set this switch within the 'Import Translations From Localized Files' option or do I have to use the File/Import wizard and do the files one at a time (which will be quite laborious, having to run the wizard 20 times for each Language Pack). Regards, Chris
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
lagucw Member
|
Sorry - ignore where I say "used the 'Set Default'" - I realised this set things back to default. What I did was change the settings and ensured that the program retained those settings before doing the 'Project/Import Translations From Localized Files' Chris
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hi, Thank you for your opinion and PM. As I mentioned above Sisulizer could import translation from many different formats e.g. Excel, TMX, CSV but unfortunately your previous localization tool is not advanced software, has many limitations, and for this reason you can use only import from targeted, localized DLL files. Is there any way to set this switch within the 'Import Translations From Localized Files' option or do I have to use the File/Import wizard and do the files one at a time (which will be quite laborious, having to run the wizard 20 times for each Language Pack).If you want import only really translated strings, you need use Import Wizard, because feature "Import Translations From Localized Files" is rather dedicated for import from fully localized files, and for such files you don't need set up any options, but I will ask our R&D about possibility implementing option for ignore identical strings in original and translation, because we always interest in improving our software. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
lagucw Member
|
OK, I guess that (if we choose Sisulizer) we would only have to go through the hassle of importing the DLLs when we first convert to the new tool, and after that we would be using the Exchange Wizard. In any case, we don’t do all of our 18 Language Packs at the same time, just when they are requested by our software distributors. Thanks again – you’ve been very helpful. Regards, Chris
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
Instead Export Wizard you could use "Import Translations From Localized Files" feature for import all languages (with not translated strings), next you could use filter feature (look on my above advice about filter) and remove all not translated strings from all language column at once. This solution could be really faster then using Export Wizard. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
lagucw Member
|
I see what you mean – just tried it and it's a much better way to do it (hey, this is good support!) Thanks & regards, Chris
|
|||||||||||||
| ||||||||||||||
| Current time is 02:28 pm | |
| 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 incomplete translations from language DLLs | |
Sisulizer software localization tool - Three simple steps to localize
