|
|||
|
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) > Bugs and Quirks in Sisulizer > Strings are auto-translated to (empty)
|
|
|||
|
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) > Bugs and Quirks in Sisulizer > Strings are auto-translated to (empty)
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Strings are auto-translated to (empty) - Bugs and Quirks in Sisulizer - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Frede Member
|
I have run into the same issue as described in this post. I don't know if the correct precedire is to continue in that thread or report it again. This is in SL 2008 by the way. http://forum.sisulizer.com/forum4/632.html
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello Frede, I tried to reproduce your issue with my own Sisulizer projects, but I've got always correctly auto-translate results for my language variant strings identical with main language version after update source files. You mentioned in your post that problem occurs randomly, and for this reason issue could be hard to reproduce. We could reproduce it if you will send to us your project version before scan where occurred issue and updated source file. It allows us repeat all scan and auto-translate steps for your files, and maybe we will reproduce your issue. If you have enabled option "Create backup project" in Sisulizer settings you can to send .~slp file, because it could keep project state before scan. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
bikemike Member
|
I also get these cells marked (empty) Has this been explained / resolved? I also found that this is messing up my pseudo translate for my test language. For one, the remove pseudo translations does not remove translations from 'Complete' rows, and for seconds, sisu seems not to remove translations from new rows. It also seems to remember statuses - if I remove pseudo translations for the column, then mark one problem row as 'for review' and leave another 'complete' then do pseudo translate again, the two rows go back to 'for review' and 'complete' respectively. Net effect, I starts to feel like pushing treacle.... :-( I had to select the whole columns' cells and do a clear (-> not translated) then run pseudo translate again. This cannot work if I am using slmake regularly.... So far I have used fillpseudo, I have just added removepseudo prior to those tasks but this is not effective. What to do?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Bikemike, your post is about two problems? - one related to TM - and one related to pseudo-translate? According the cited thread the TM problem was solved in 1.x. Perhaps there is still a situation not covered by the fix. Can you please generate some sample situation where this happens to you and send the .slp and the TM you used to support (at) sisulizer.fi. I'm a little bit puzzled about the second issue. Can you also make a short step by step example for that. What happens and what do you think should happen (e.g. what statuses do you expect). It should then be easy to sort out and fix. Please keep the issues separately to avoid pushing treacle. The issues might influence each other and we should solve these step-by-step :-) Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
bikemike Member
|
I have tried to recreate with a clean project but cannot. Certainly, I was getting the string {Empty} or (Emtpy) - can't recall. I have cleared this somehow by removing everything and rescanning... it was last week, memory fading. I will keep an eye on it and if I get it again will report.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
bikemike Member
|
OK, got it. Existing Sisu project with a pseudotranslated language. FAILS
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Frede Member
|
I have used pseudo language just once or twice and my problem is not related to that, but I still get strings that are auto-translated to empty from time to time. I don't know exactly when this occurs cause we build automatically so it can take a month between the time that I open the project in the Sisulizer IDE and that's usually when I discover that something is wrong. I'll try to keep this in mind to try and pinpoint when this problem occurs for me as well.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello Mike, Thank you for detailed description, now I've got identical result. Of course, we let you know about investigation results. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 06:35 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) > Bugs and Quirks in Sisulizer > Strings are auto-translated to (empty) | |
Sisulizer software localization tool - Three simple steps to localize
