Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support 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: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
Build makes project 'dirty' - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Tue Sep 26th, 2017 08:10 am
PM Private Upload Quote Reply
MikeBz
Member
 

Joined: Wed Aug 8th, 2007
Location: United Kingdom
Posts: 35
Status: 
Offline
If I open my project, select Project->Build in selected language->[my .exe file], and then close the project I am prompted to save my changes - but I haven't made any changes, all I have done is build the executable.

Back To Top PM Private Upload Quote Reply

 Posted: Tue Sep 26th, 2017 10:39 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


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

Sisulizer always scan source during build operation. If source has been changed in the meantime, Sisulizer detects it and asks about saving those changes. Please check output build log via "Show history" button on Output tab toolbar. You can find there detailed info about build process.

Janusz



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

 Posted: Tue Sep 26th, 2017 10:45 am
PM Private Upload Quote Reply
MikeBz
Member
 

Joined: Wed Aug 8th, 2007
Location: United Kingdom
Posts: 35
Status: 
Offline
Thanks for the quick reply. I assumed that if I scanned for changes, saved the file, and then scanned for changes again (with no changes to the source in between) then this would not require the project to be saved (since nothing has changed). However that does not seem to be the case - scanning for changes always requires the project to be saved even if nothing has changed in the source since the last scan.

Back To Top PM Private Upload Quote Reply

 Posted: Tue Sep 26th, 2017 02:25 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1977
Status: 
Offline
This should not happen if there are no changes in the source. It seems that Sisulizer has so trouble scanning your file and that causes the project become dirty.

Can you zip your Sisulizer project files (.slp) and the .exe file it contains into a zip file and upload it to us. Click the Private Upload button above to send the file.

Ilkka



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

 Posted: Tue Sep 26th, 2017 02:26 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3014
Status: 
Offline
Janusz is right. Sisulizer dirties the project because it does a scan for changes. My guess is, that it writes that the stauts of the scan but I have to ask R&D if that is true.

Markus



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

 Posted: Tue Sep 26th, 2017 04:00 pm
PM Private Upload Quote Reply
MikeBz
Member
 

Joined: Wed Aug 8th, 2007
Location: United Kingdom
Posts: 35
Status: 
Offline
Thanks Ikka, I've uploaded a zip file containing the Sisulizer project and the executable. It's a minor irritation, not a major problem.

Back To Top PM Private Upload Quote Reply

 Posted: Tue Sep 26th, 2017 06:00 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1977
Status: 
Offline
Thank you for the file. I found the reason. Some of your string table resources has English (UK) and same has English (US) as language tag. Sisulizer stores all string table resource into single node (Strings -> String Table) and set the language to match the string table. If there are several string tables in the EXE and two or more have different language id the language id in the node keeps changing and this makes project dirty.

You can just ignore this or if you can modify your RC files such way that all STRINGTABLE use

STRINGTABLE LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_UK
{
...
}

Ilkka



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

 Posted: Tue Sep 26th, 2017 06:14 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1977
Status: 
Offline
Another solution is to uncheck Single string table. By default it is unchecked. That makes each STRINGTABLE to stored into its own node and there cannot be a language mismatch. See the screenshot.

Ilkka

Attachment: Untitled.png (Downloaded 6 times)



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

 Posted: Wed Sep 27th, 2017 07:44 am
PM Private Upload Quote Reply
MikeBz
Member
 

Joined: Wed Aug 8th, 2007
Location: United Kingdom
Posts: 35
Status: 
Offline
Thanks Ikka.

I tried unchecking 'Single string table' - so then I had many many string tables (all marked as new) and the old string table marked as unused. I resolved all of that so there were no new or unused rows, saved the project, rescanned it and it still marks it as dirty. I don't really want a large number of string tables in the Sisulizer project anyway, so I won't pursue that approach.

Next I looked in the .rc file. It has the following language statement in it at the top of the file:

LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_UK

There are multiple string tables, this is something Visual Studio seems to do of its own accord, but none of them have any kind of language statement in them. The resource view in Visual Studio only shows one string table, with language English (United Kingdom).

Next I looked in the Visual Studio project and found that in the project's Resources properties there is a 'Culture' parameter which was set to English (United States) which contradicts the SUBLANG ENGLISH_UK in the .rc file. So I changed that, rebuilt the .exe, rescanned the Sisulizer project and saved it, then scanned it again and... it's still dirty.

Time to look at the .rc file again. I find that there is a TEXTINCLUDE statement near the end of the file which looks like this:

3 TEXTINCLUDE
BEGIN
[... stuff deleted]
"#if !defined(AFX_RESOURCE_DLL) || defined(AFX_TARG_ENU)\r\n"
"#ifdef _WIN32\r\n"
"LANGUAGE 9, 1\r\n"
"#pragma code_page(1252)\r\n"
"#endif //_WIN32\r\n"
[... stuff deleted]
END

And then again right at the end of the file is an almost identical sequence which is commented as having been 'Generated from the TEXTINCLUDE 3 resource'.

In both places I changed "LANGUAGE 9, 1" to "LANGUAGE 9, 2", rebuilt the .exe, rescanned the Sisulizer project, saved it, rescanned again and now it stays 'clean'.

Thankyou for your very quick support service!

Last edited on Wed Sep 27th, 2017 08:03 am by MikeBz

Back To Top PM Private Upload Quote Reply

Current time is 03:53 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Build makes project 'dirty'



WowUltra modified by Sisulizer Copyright © 2007-09 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize