|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Import translations from localized files does not work for .sln files
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Import translations from localized files does not work for .sln files
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Import translations from localized files does not work for .sln files - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Jablonski Member
|
Starting a new Sisulizer (V3.330) project and selecting a solution file to scan, there is the option to read already existing resources. In our case the native language is English and the already existing language in the solution is German. As expected after scan is finished, there is a column for native and German language in Sisulizer. Now the German resource is changed in VS2010 and the solution is rebuild. If I now use ‘Project / Import translations from localized files’ from Sisulizer menu to get the changes – Sisulizer fails. The output window shows ‘Importing data’ but changes are not imported. If a project from the same solution file is added as source in Sisulizer, the ‘Project / Import translations from localized files’ work as expected. The changed items are imported. Is this a bug in ‘solution as source’ or do we misunderstood this functionality?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator 
|
You are right. Sisulizer did not import localized files if you selected Project | Import from localization files and your source was a Visual Studio solution file. We had just forgotter to implement it. I implemented it. Starting from the next build (331) this feature works. In the meantime you have to import each .resx or .xaml file individually. Thank you for reporting this. regards, Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jablonski Member
|
Thanks for your quick reply, we try to use the workaround meanwhile. Regards from Germany, Ralf Jablonski
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Supergg76 Member
|
Hello, I think i have the same bug. For the project we use 2 applications and 1 commons libraries. The two applications are using the commons libraries. We build 3 .net projects. On Sisulizer, i create a new project for the first application and i translate the commons libraries by this way. Save and Build resources On Sizulizer, i create a new project for the second application and i do a "Scan for changes". When i try to see the translated values, sisiluzer display the original value and not the values translated by the first application. I create a simple example on attachment. On the Application1 in English the value of label1 is set to "English version APP1". Save an Build resources Open the Application2 and sisulizer display "English version APP2" after a "scan for changes" ??? not "English version APP1". Can you explain me why and if exist a fixes for this bug
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
If you would like import translations from localized files to existing project you need use "Project" -> "Import Translations from Localized Files".On the Application1 in English the value of label1 is set to "English version APP1". Save an Build resources Your FR resx file contains this value ("English version APP2"), but when I built Application1, Sisulizer saved correct "Version FR" value to output FR resx file. Next, I imported localized resources to Application2 via "Import Translations from Localized Files" and again I got correct result, that is "Version FR" in French column. So it works well. Seems to me that you didn't execute build operation in Application1.slp before import to Application2.slp. BTW: What do you think about adding all your .NET sources (e.g. SLN) to one Sisulizer project? It could simplify your work, for example you needn't import resources between SLP files, because all items are included to one SLP and Sisulizer automatically translate all duplicates, allows on better managing all your localizations, for example you can in easy way check coherence of translations (duplicates), validate and build all or selected sources in one operation, etc. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Supergg76 Member
|
Thanks for your response but a try to do the "Import Translations from Localized Files" and there is an error because it cannot find the common resources dll. This file is well present on the directory (see HDTREE.JPG). I give you on attachment APP1.JPG : Screen shot after building resources APP1Reports.zip : the report of building APP2.JPG : Screen shot after import APP2Reports.zip : th report of import The aboutInf.jpg to give you the information about the version. This is an example i do for you to explain the malfunction i have seen and it is not the real project. The project is less than 20 MO and confidential.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Import to SLN files was improved in build 331. Please update your Sisulizer and try again. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Supergg76 Member
|
thanks for this information. We check for upgrading the version but le build 331 is not compatible with the 2010 version. Only for V 3 A build with this patch is disponible for 2010 version ???
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator 
|
Sorry, but we do not provide updates for Sisulizer V2010 anymore. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Supergg76 Member
|
After I read yours response, I suggest an upgrade for this tools and the Renault DS unit bought the new version of sisulizer 335. Today, I try this and the test is not OK. I do the same procedure with the example and I can retrieve the new value for the common components from the second application. I do a "scan for changing" and the system show no modification. When I do an import from resource, the system import the value without warning. This fact confirms I do the modification from the first application. But is not a solution because the operation erase the current value without warning. Please can you explain me why the "scan for changes" didn't show the modification on translated values realise from an other solution by sisulizer.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello,When I do an import from resource, the system import the value without warning. This fact confirms I do the modification from the first application. But is not a solution because the operation erase the current value without warning. "Project" -> "Import Translations from Localized Files" overwrite existing translations, but before operation is displayed confirmation message with info about this. "Import Translations from Localized Files" feature is rather dedicated for new projects (with already localized files translated e.g. by third party tools) for quick import. For this reason, you can't set any import options. If you would like import translations without overwriting existing translations in SLP, use "File" -> "Import". Import Wizard is fully customizable, so you can adjust import to your needs, but Import setup take more time. For example, when you would like import translations to your SLP based on SLN, select in Import Wizard form1.fr.resx file and in Options step set "Overwrite method" as "Never". Please can you explain me why the "scan for changes" didn't show the modification on translated values realise from an other solution by sisulizer. Sisulizer ignore localized files (files with added .NET culture ID e.g. Form1.fr.resx) during source scan, because otherwise it could generate dangerous loopback - for example after build (during scan) SIsulizer will find new source files, that is e.g. Form1.fr.resx, add it as source, with French translations as originals. During next build, Sisulizer will generate form1.fr.fr.resx file in output for this file, etc. So it create terrible chaos. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 08:10 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Import translations from localized files does not work for .sln files | |
Sisulizer software localization tool - Three simple steps to localize
