|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page:   1 2 |
|
|||||||||||||||
| Error message when scanning - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
meta Member
|
Janusz, there are THOUSANDS of files... I cannot think of any way to zip them than to zip ALL files and that would take all day... I will also send you a copy of the slp file dated 110310. I also conviced one of our developers to take a look at the issue from our side....
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
We needn't all your source files (all csproj files) from your SLP. I think files belong to one example csproj (where occurred issue) will be enough for manage it. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
meta Member
|
From the log I sent yesterday you can see that issues appear on many places... anyway I will upload a new zip right away.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Thank you for files. I finally reproduced this issue. We let you know about results of our investigation. From the log I sent yesterday you can see that issues appear on many places... Don't worry about it. I think issues have this same nature, so if we fix it for one csproj it automatically fix this issue also for other csproj files. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
meta Member
|
That was a relief... I hope for a quick solution then 
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
meta wrote: That was a relief... I hope for a quick solution then I already forwarded it to our R&D. Potential workaround: Your MainForm.cs file contains public class ExampleTreeNode item. Try change it to public class MainForm and next check and fix other cs where occured this same issue. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
meta Member
|
Thanks Janusz, I forwarded your notes to the developers and keeps on crossing my fingers... Meta
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
meta Member
|
Janusz, while waiting for this problem to be fixed we are discussin reversing to build 311 and add hot fixes that Jaakko got me late January. The problem is that we no longer have the 311 installation file and it is no longer available for download. Can you get me a link to download 311? Thanks in advance Meta
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
meta Member
|
Also - what will happen if I open the slp project saved in build 313 in an earlier version (311 + hot fix from Jan 24). Will it totally crash the project or what? We have several deployments this weeks so I need to no my options... Best regards Meta
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi, You can download it from our version archive: http://www.sisulizer.com/support/versionarchive.shtml The link can also be found at the bottom of our download page: http://www.sisulizer.com/support/downloads/download-updates.shtml Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
meta wrote: Also - what will happen if I open the slp project saved in build 313 in an earlier version (311 + hot fix from Jan 24). No, it should work OK. I tested behavior your example csproj project (sent to us) and after downgrade, Sisulizer correctly scanned source files. However, I haven't access to other your csproj files, so I recommend you copying backup of your SLP to other location - just in case. BTW Don't remove unused translations from your invalid SLP (build 313), because after fixing issue or downgrade to earlier build Sisulizer re-use those translations. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
meta Member
|
Thanks guys, seems to work. We will know for sure after the big nightly build.... Meta
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, I keep my fingers crossed. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
meta Member
|
Hello, Thanks... some builds went better than others... I am fighting another annoying thing. I keep on getting "Auto translated" string even though I am of the opinion that I have short cutted that options in the Sisulizer settings. How can that be??? Since we have used the samt text strings for Button text and tool tip it gets a mess. I fixed this in January but now I am back on square 1. UC text strings include a & sign for short cut - and Auto translate f-s it up... Please advise! Meta
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
I am fighting another annoying thing. I keep on getting "Auto translated" string even though I am of the opinion that I have short cutted that options in the Sisulizer settings. How can that be??? I need more details for managing this issue. Could you tell me when it happens (e.g. when Sisulizer detect new items in source during scan) and something about your settings in "Translations" tab of "General settings" dialog"? Some advices: 1. When you uncheck "Translate new rows automatically after scanning" in "Translations" tab of "General settings" dialog , Sisulizer won't use translate duplicate feature for new items. 2. When you select "General settings" dialog -> "Translations" tab -> "How to select duplicate strings" -> "By Original and Context", Sisulizer use automatic translation only for items with identical context. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
I fixed the bug that caused "MainForm.resx: type names in the resource and source code files are not same ("MainForm" vs. "ExampleTreeNode"). Please fix the value in ">>$this.Name" property in "MainForm.resx" file." The bug was that Sisulizer incorrectly read the type name from the source file (.cs). The fix will be in the next build (314) Jaakko
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
meta Member
|
That was good news! So when will 314 be released? Any chance of a Beta version? BR Meta
|
||||||||||||||||
| |||||||||||||||||
| Current time is 06:11 pm | 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 > Error message when scanning | |
Sisulizer software localization tool - Three simple steps to localize
