|
|||
|
|||
| Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius | Page:   1 2 |
|
|||||||||||||||
| Not importing some resources - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Sisusupport Administrator
|
IanMcCarthy wrote: Things like OK and dB and OSHA appear gray in the translated column but don't get written to the resx files during the build (I checked the basic resx code in a text editor). Gray means it is the same as original value. By default SL does not write them to localized .resx file. You have to have the above settinsg at least Translated to make SL to write them there. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
IanMcCarthy Member
|
Thought I was missing something... Thanks for the swift response. Ian
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
IanMcCarthy Member
|
OK, I still have a problem with the way this is working: I create a new Sisulizer project based upon my .NET solution file, I opt to import any currently existing German (for example) resources. OK I change the 'Items that localized resource files contain' option to 'All' and then select 'Build item'. The resultant resx files now contain the translated text (even where it's the same as the original English). OK I don't keep the Sisulizer project because if I make changes to the .NET solution, I want to rebuild a new Sisulizer project afresh from the current resx files in the .NET solution. OK However, when I create a new Sisulizer project from the .NET solution file (as I did before, importing existing German) the German text strings get omitted if they match the original English. Not OK I now don't know which strings are new and need translation and which don't just because they happen to be the same in German and English. Not OK I can't give an accurate estimate of the amount of translation required as I now have many more un-translated strings than I should. Not OK Is there a way to make Sisulizer keep the translated strings (when they match the original) during the 'new project - import phase'? Many thanks for your assistance, Ian
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Sisusupport Administrator
|
IanMcCarthy wrote: I don't keep the Sisulizer project because if I make changes to the .NET solution, I want to rebuild a new Sisulizer project afresh from the current resx files in the .NET solution. OK If you open SL project and choose Project | Scan for Changes, SL will rescan your project and will update the SL project matching the new (changed) .NET project. There is no need to create a new SL project every time your .NET project changes. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Sisusupport Administrator
|
IanMcCarthy wrote: Is there a way to make Sisulizer keep the translated strings (when they match the original) during the 'new project - import phase'? Not at the moment but I start seeing that our current implementation that import only those strings that differs from the original is wrong. I will change the logic that it will import all items from the localized resource files even those that equal the original ones. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Sisusupport Administrator
|
1.5.13 has a new logic when importing existing translatons. If the localized resource contains an item it is imported even if it equals to the original string. 1.5.13 will come out tomorrow. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
IanMcCarthy Member
|
Hi, me again... I'm not sure the "Items that localized resource files contain" option is working properly. 1. I import existing translations (German) from NET solution. 2. I translate items where the German is the same as the English (OK, Format, etc). 3. I select "Translated" for the above option and build the project. 4. Same text items are not included in the resx files. If I select "All", then for non-translated items the English gets saved in the German resx file and if I now re-create the project from the NET solution everything gets marked as translated (when it's not). If the "Translated" option saved just translated items (irrespective of them being the same in both languages) I'd be home free. Can you verify the operation of this option? Thanks Ian
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Sisusupport Administrator
|
Hi Ian, I checking this and it work just OK at my computer. Tak a look at this picture. It contains a project where original language is English and target language Finnish. I have translated One to One (that is incorrent Finnish but will work here because it is same as orignal). Also dummy has been translated to dummy. I also checked Translated radio. When I now build the project SL create Form1.fi.resx that contains the folllwing two items <data name="label2.Text" xml:space="preserve"> <value>dummy</value> </data> <data name="$this.Text" xml:space="preserve"> <value>Esimerkki</value> </data> Dummy because Translated is checked and Esimerkki because it is different to original. Is this case identical to your case. If not please explain me more. Jaakko Attachment: untitled.PNG (Downloaded 28 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
IanMcCarthy Member
|
Sorry to say, that's not what's happening on my system. Even with the "Translated" radio button ticked, the generated ".de.resx" files don't contain text entries where the German is the same as the English. Ian
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Sisusupport Administrator
|
What is your Sisulizer version? You can check if from Help | About Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
IanMcCarthy Member
|
Version 1.5.13 downloaded/installed it yesterday. Ian
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Sisusupport Administrator
|
I am out of ideas now. Can you send me the project? If you have added .csproj to SL project, create a new project that contains only one .resx. Then send me the .slp and the original .resx. I give a try. Use support (at) sisulizer.fi Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
IanMcCarthy Member
|
I've just noticed you created the SL project from the C# ".csproj", I've been selecting the ".sln" solution file. So I created a SL project from my ".csproj" file added the translations, selected the "Translated" radio button and built the project. Same text translations ARE now included in the ".de.resx" files. Does your example work if you build from the ".sln" file instead? Ian
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Sisusupport Administrator
|
You are right. I forgot to test .sln I just rested .resx and .??proj I will fix this in the next build (1.5.14) Jaako
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
IanMcCarthy Member
|
Much obliged. Thanks for the excellent support. Ian
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Sisusupport Administrator
|
I fixed this in 1.5.14. It will come out tomorrow. Thank you for your bug report. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 12:39 am | Page: 1 2 |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Not importing some resources | |
Sisulizer software localization tool - Three simple steps to localize
