Software & More > WinPatrol Help & Information

[Winpatrol 2012] Localization issue stops a module in Winpatrol

<< < (2/2)

BillPStudios:
Thanks for taking the time to post information on your experience.
So far it's high on my list of bugs that make absolutely no sense but I'm told computer do what you tell them to do so I'm sure there's a fix somewhere.

Thanks,
Bill

Max_ita:
Hi Bill,

Unfortunately I can still reproduce it with 25.0.2012.5 + WinPatrol v25 German package.

Have you ever considered to rewrite localization feature?

Most programs use a folder called languages to store localization strings. And editing registry entries could be very messy.

BillPStudios:
Hey Max,

Thank you for the follow up.  Yes, I am looking at our localization process for two reasons.

As you know, currently our local languages are stored as a registry script that stores translations in the registry. In the past most browsers except Internet Explorer wouldn't allow running registry scripts. Instead, the browser will just display the script in its text form.  This is for the protection of users since it was very common for malware to use .reg files to infect users and infiltrate a computer.  Even Outlook won't allow you to receive files with a .reg extension.  Many security programs change the file type assocation of both .reg and .scr filetypes so they open Notepad so even if you want to use registry scripts you can't.  .SCR file type is a screen saver type also commonly used to infect computers.
The new Internet Explorer now displays .reg scripts instead of running them.  The only way to run a registry script is by using RegEdit or calling it from within a program.

As I've mentioned elsewhere last year my wives illness reduced the time I devoted to WinPatrol and localized versions suffered from lack of attention.  Things are going well now and it's very important for me to show respect to all our non U.S. WinPatrol fans.  Thanks to the quick response from volunteers I have already built and updated a half dozen setup programs so they install localized versions. By building it into the setup program users don't have to run the script. I'm just waiting for other volunteers and probably need to follow up to see if they're still on board.

The 2nd reason motivating me to make a change is %#&ing 64 bit Windows. The 64 bit versions won't allow scripts to add our local text to the HKEY_LOCAL_MACHINE registry hive. In a quick decision to support users, the scripts now add text to the HKEY_CURRENT_USER tree. The downside or upside, depending on your view is that localization only applies to the single user.  If you have multiple users on a machine it means the script or WinPatrol setup must run for each user.

This still doesn't explain why sorting columns doesn't work for you if the local text is found in the registry but I'll tackle that when I make the change. Now that I have upgraded Visual Studio I also need to modify the function I use for comparing text. I have to replace all "lstrcmpi(...)" to "CompareString(..)" to support non English. Unfortunately, this isn't a simple change for XP machines so I'l need to pay special attention to every single piece of code where I compare text. I'll also need to test each routine to be sure it works as planned on XP, Vista, Windows 7, Windows 8 AND 64 bit versions of each including 64 bit versions of XP which is growing.

Luckily as I said, my wife is doing great so I am able to devote proper attention to WinPatrol this year.

Thanks again,
BIll

Navigation

[0] Message Index

[*] Previous page