Support forum of the software localization tool Sisulizer


Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 

 Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
Fake changes/new strings when scanning for changes several times (java .properties files) - 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 ...
AuthorPost
 Posted: Thu Aug 7th, 2008 11:30 am
PM Quote Reply
Olivier_ho
Member
 

Joined: Wed Jul 23rd, 2008
Location: Marseille, France
Posts: 46
Status: 
Offline
Steps for repro :
1. Create a new project and add the attached test.properties file, with English as the original language, and French as the target
2. in the string list, CTRL+A and then CTRL+ALT+C : all strings take the translated status
3. Edit the test.properties file, and add the following line :
myjavamodule.test01=Test string - 01
after the last resource
4. Scan for changes : the new line is found
5. Scan for changes again : an existing resource is duplicated and added at the end as translated
6. Scan for changes again : an existing resource is duplicated and added as not translated
etc.
Expected behaviour : don't detect inexistant changes
Workaround : closing the project after each update will solve the issue, but it is not very fulfilling

Attachment: test.zip (Downloaded 1 time)

Back To Top PM Quote Reply

 Posted: Thu Aug 7th, 2008 12:03 pm
PM Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 564
Status: 
Offline
Hi,

Thank you for sample , I have reproduced your issue, I will send your test project and description to R&D.

Best,
Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Quote Reply

 Posted: Thu Aug 7th, 2008 02:02 pm
PM Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 564
Status: 
Offline
After install V2008 I didn't used SL with Java, and for his reason I didn't set Java platform settings yet, but after tests your issue I set correctly Java path and now after scan your test project SL always give correctly results without false new strings. Try to set: menu Tools > Platforms > Java (of course your Java path could be different) and let me know about results.
Best,
Janusz

Attachment: screen.png (Downloaded 37 times)



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Quote Reply

 Posted: Thu Aug 7th, 2008 02:31 pm
PM Quote Reply
Olivier_ho
Member
 

Joined: Wed Jul 23rd, 2008
Location: Marseille, France
Posts: 46
Status: 
Offline
It was already set (to C:\programf files\Java\jdk1.6.0\bin\java.exe).
I set it to C:\programf files\Java\jre1.6.0\bin\java.exe, closed Sisulizer, restarted it, and got the same behaviour by following the same steps, exactly (this is important, as with a different file, I did not get the same behaviour, for example).

I'm a bit reluctant to upgrade to jdk 1.6.2, as the last time I upgraded to 1.6.1, I had to revert to 1.6.0 as my applications using Java had become unbearably slow.

I can try testing on another machine, but I'd like you to confirm first that you followed exactly the steps (new project, original file, etc.).

I'm sorry to be annoying, but I'm the SQA manager in my company (in addition to be the localizer...) and I've seen too many times bugs not reproduced (and a lot of lost time) because the steps were not followed precisely...

Attachment: Sisulizer-javaSetting2.gif (Downloaded 31 times)

Back To Top PM Quote Reply

 Posted: Thu Aug 7th, 2008 03:10 pm
PM Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 564
Status: 
Offline
I set my Java virtual machine path for already existing test project for your file, but after your reply I have created new project for this file and you are right: after copy original to translation and using scan feature new false items occurred again. Restart of Sisulizer resolve this problem, and scan feature after one Sisulizer restart always show correctly results on my PC. Could you attach to this topic output report (Output > Show report)? It maybe help us resolve this issue.
Best,
Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Quote Reply

 Posted: Thu Aug 7th, 2008 04:05 pm
PM Quote Reply
Olivier_ho
Member
 

Joined: Wed Jul 23rd, 2008
Location: Marseille, France
Posts: 46
Status: 
Offline
I'm a bit puzzled, now I have a different behaviour : I get an error right from the start.

I switched back to jdk (instead of jre), but same result;
if I saved the project, close it, re-open it, then no pb. But if I add a test2.properties to the project, and scan for changes right away, I get the problem again.

The error is
17:00:14    Error    Exception: Row "D:\Work\localisation\loc-tools\GeoScheduling\test.properties.callcenter.browther.noIFrame " allready exists

I attached the full log of when the error occurs.

Attachment: Sisulizer_pb-report.txt (Downloaded 2 times)

Back To Top PM Quote Reply

 Posted: Thu Aug 7th, 2008 06:36 pm
PM Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 564
Status: 
Offline
Hi,
I asked you output report, because I've got similar error stack in output pane. Now we can to compare your and my error lists.  Because your issue is reproducible, even in shorter version of your test (new project with your file and scan without any changes in source) I sent it to our developers. We will inform you about investigation results as soon as possible. Thank you for very detailed and concrete information about issue.
Best regards,
Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Quote Reply

 Posted: Thu Aug 14th, 2008 03:37 pm
PM Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 564
Status: 
Offline
Hello,

Our R&D fixed this in build 270. It will come out late next week.

Best regards,
Janusz

 



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Quote Reply

 Posted: Thu Aug 14th, 2008 03:49 pm
PM Quote Reply
Olivier_ho
Member
 

Joined: Wed Jul 23rd, 2008
Location: Marseille, France
Posts: 46
Status: 
Offline
Cool - I'll test that in September when I'm back from my holidays.
Thanks for the follow-up.

Back To Top PM Quote Reply

Current time is 04:33 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 > Fake changes/new strings when scanning for changes several times (java .properties files)



WowUltra 1.11 Copyright © 2007 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize