Migrate from GitHub to SourceForge with this tool. Check out all of SourceForge's recent improvements.

#2139 Swedish translation update for WinMerge 2.6.2


Hello all,
Here is an update of the Swedish translation for WinMerge 2.6.2 ...

Best wishes,
Hans Eriksson

Windows Vista is a bit different than other Windows versions,
since it has UAC (User Account Control),
so to see why the User Account Control dialog appears you can read
for example this:

Mark Russinovich's technical blog covering topics such as Windows troubleshooting,
technologies and security.
The Case of the Notepad that Wouldn't Run


Understanding and Configuring User Account Control in Windows Vista

so the reason the UAC dialog displays
"An unidentified program wants access to your computer"
is that "heuristic setup detection only applies to files that
don’t have an embedded manifest that specifies a security TrustLevel."


UAC allows for users, even administrators,
to run as standard users most of the time,
while giving them the ability to run executables with administrator rights
when necessary.
There are several mechanisms by which executables can trigger a request
for administrator rights:

1 If the executable image includes a Vista manifest file that specifies
a desire or need for administrator rights
(this would be added by the developer who creates the image).
2 If the executable is in Vista’s application compatibility database
as a legacy application that Microsoft has identified as requiring
administrator rights to run correctly.
3 If the user explicitly requests an elevation using
Explorer’s “Run as administrator” menu item in the context menu
for executables
(also can be set as an advanced shortcut property).
Note that this does not run the executable under the Administrator account,
but rather under the account of the logged in user,
but with the Administrator group enabled in the process security token.
4 If the executable is determined to be a setup or installer program
(for example, if the word “setup” or “update” is in the image’s name). "
(SOURCE: "The Case of the Notepad that Wouldn't Run" above)

So the Manifest in "WinMerge-" contains:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<description>Inno Setup</description>


and "WinMerge.exe" has the Manifest:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<description>WinMerge Application</description>

so if you look at the "Command Prompt Strings in Notepad.exe"-picture
in "The Case of the Notepad that Wouldn't Run" you will see that
these Manifest files as "XP Manifest"-files NOT "Vista Manifest"-files
since they do not have the required security parameters there...

This is explained in
"Understanding and Configuring User Account Control in Windows Vista"
and in more detail here:



  • Nobody/Anonymous

    Swedish translation update for WinMerge 2.6.2

  • Kimmo Varis

    Kimmo Varis - 2006-12-13
    • labels: --> Resources and Language DLLs
    • milestone: --> Trunk
    • status: open --> open-accepted
  • Kimmo Varis

    Kimmo Varis - 2006-12-13

    Logged In: YES
    Originator: NO

    Committed to SVN trunk.
    Completed: At revision: 3960

    The new string you translated is not in 2.6 branch, it is trunk-only feature.

    Thanks a lot for all the information, I'll look at it...

  • Nobody/Anonymous

    Logged In: NO

    Hello Kimmov,
    I may have expressed myself a bit unclear,
    so maybe there is a need to rephrase what
    I write before...

    There has been changes made in the InnoSetup version
    5.1.8 and 5.1.9 in view of compability with Windows Vista...

    The changes I refer to are these:

    5.1.9 (2006-12-10)

    Change in default behavior: The PrivilegesRequired [Setup] section directive now defaults to admin. The default in all previous versions was none. More often than not, installations do need administrative privileges to run successfully; therefore, none should not be used unless you have actually tested your installation on unprivileged accounts.
    On Windows Vista, the setting of the PrivilegesRequired directive now influences whether elevated rights are requested when the installation is started under a user account that does not have administrative privileges. Installations built with previous versions of Inno Setup always requested elevation on Vista. Beginning with this version, elevation will not be requested if the user is unprivileged and PrivilegesRequired is set to none.
    On Windows Vista, the uninstaller will no longer request elevation when Setup was never run with administrative privileges.
    URLs (web site addresses) may now be specified in the Filename parameter of [Icons] section entries. When a URL is detected, Setup will create an Internet Shortcut (.url) file instead of a regular shortcut.
    (Note: While you could sometimes get away with specifying URLs in previous versions of Inno Setup, it was never recommended because the shortcuts would fail to resolve on Windows 95 or NT 4.0. Internet Shortcuts, on the other hand, will work on any version of Windows, as long as Internet Explorer is installed.)
    Added workaround for bug in the 64-bit version of Windows Vista: The fields on the User Information wizard page would default to "Microsoft".
    Pascal Scripting: Added new FontExists function.
    The uninstall program's version is now
    Minor tweaks.
    5.1.8 (2006-10-11)

    Converted the documentation to HTML Help format for compatibility with Windows Vista, which does not support WinHelp-based help files at all (as of RC2). HTML Help is also said to work better with screen readers. Much of the conversion process was done by hand, so there may be some mistakes. Please report any problems you encounter.
    Updated the LZMA SDK compression/decompression code to version 4.43. Compression is noticably faster in this version. (Compiling Inno Setup's own installer used to take 7 seconds; now it takes 4.)
    Added a "requestedExecutionLevel" setting to Setup's manifest resource to disable Windows Vista's legacy application compatibility hacks. Now you should no longer see bogus "This program might not have installed correctly" dialogs when cancelling installations or after running installations that do not create an Uninstall key.
    Note: It is possible that you were unwittingly relying on some of these application compatibility hacks, so it is recommended that you re-test your installations on Windows Vista after upgrading to this version.
    When deleting a .chm file, the uninstaller will now automatically delete any corresponding .chw file as well.
    Paths that are accessed at compile time may now include a "userdocs:" prefix, which is replaced with the path of your My Documents folder. For a usage example, see any of the example scripts.
    Setup now creates an "InstallDate" value in the Uninstall key so that Vista's Programs and Features Control Panel applet doesn't have to guess the "Installed on" date.
    Pascal Scripting changes/improvements:
    The StringChange function now returns an Integer indicating the number of changes made. Performance was also improved.
    Introduced new StringChangeEx function, which adds support for strings containing double-byte characters (used in Chinese, Japanese, and Korean languages). Unless you require binary safety, this function should be used instead of StringChange, especially if you're working with strings containing paths or filenames.
    IDE changes:
    The Open and Save As dialogs now permit sizing and include a places bar.
    On Windows Vista, the IDE no longer requests administrative privileges when started. (You will, however, still see UAC popups when launching compiled installations from within the IDE.)
    When you compile an unsaved script, the output is now placed under your My Documents folder (instead of the current directory). It asks if you want to save the script first, though.
    Updated bzip2 library to version 1.0.3.
    Minor tweaks.


    in http://www.jrsoftware.org/files/is5-whatsnew.htm ...

    id est 6 changes due to Windows Vista...

    So in [Setup] "PrivilegesRequired=admin" in "WinMerge.iss" should be set and
    not "PrivilegesRequired=none" or "PrivilegesRequired=poweruser"
    that you will find a reference to for example here:


    Windows NT/2000/XP/2003 & Administrative Privileges
    A typical Inno Setup installation running on Windows NT/2000/XP/2003 does not require administrative or "power user" privileges. However, there are exceptions as noted below.

    Things that require administrative privileges on both Windows NT/2000/XP/2003:

    Using "PrivilegesRequired=admin" in the script's [Setup] section. This causes Setup to abort with an error message if the user lacks administrative privileges.
    Using the "restartreplace" flag in the [Files] section. This flag causes Inno Setup to call the MoveFileEx function, which attempts to write to "HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Control\ Session Manager". Write access to this key is restricted to Administrators.
    Writing to any key under HKEY_USERS\.DEFAULT using the [Registry] section. Write access to this key is restricted to Administrators.
    Things that require either administrative or "power user" privileges on Windows 2000/XP/2003:

    Using "PrivilegesRequired=poweruser" in the script's [Setup] section. This causes Setup to abort with an error message if the user lacks either administrative or "power user" privileges.
    Using the "regserver" flag in the [Files] section. In most cases registering a DLL involves writing to HKEY_CLASSES_ROOT, a privilege not granted to ordinary users.
    Using the "sharedfile" flag is the [Files] section. This flag causes Inno Setup to create/update a value in "HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Windows\ CurrentVersion\ SharedDLLs". Ordinary users are not allowed to write to that key.
    Using the FontInstall parameter in the [Files] section.
    Writing to any key under HKEY_LOCAL_MACHINE or HKEY_CLASSES_ROOT using the [Registry] section. Ordinary users are not allowed to write to those keys.
    Inno Setup itself does not require write access to the WINNT directory, or any other registry keys not mentioned above.

    What is different when an installation is run by a user without administrative privileges?

    The registry key for the Add/Remove Programs Control Panel entry is created under HKEY_CURRENT_USER instead of HKEY_LOCAL_MACHINE. Thus, only the user who installed the program will see an Add/Remove Programs entry for it.
    The "{group}" constant always points to the current user's profile, as opposed to the All Users profile.
    All "{common...}" constants are equivalent to the "{user...}" constants.
    The program may be uninstalled by any user. (When an administrator installs a program, only an administrator is allowed to uninstall it.)

    ,,so "PrivilegesRequired=poweruser" can also be used on Windows NT/2000/XP/2003
    while "PrivilegesRequired=admin" is recommended/default instead in view of
    Windows Vista and due to compability with Windows Vista InnoSetup version 5.1.9
    is highly recommended by me...

    Note also that "requestedExecutionLevel=requireAdministrator" in the
    Vista Manifest have been added to "isetup5.1.9.exe" id est to the setup file
    to install InnoSetup 5.1.9 ...

    that closely corresponds to this:

    Developer Best Practices and Guidelines for Applications in a Least Privileged Environment
    Understanding User Account Control in Microsoft Windows Vista Beta 1
    Windows Security Access Control

    Microsoft Corporation

    September 2005

    Summary: This white paper provides guidelines and suggested best practices for independent software vendor (ISV) developers on how to integrate with the new security infrastructure of User Account Control (UAC) on Microsoft Windows Vista Beta 1. By following these guidelines, developers will be able to gain a more thorough understanding of UAP and how to develop their applications in a more secure fashion. (41 printed pages)

    Note This white paper is an early release of the final product documentation. It is meant to accompany software that is still in development. Some of the information in this white paper may not be an accurate representation of the functionality of the final product. Microsoft assumes no responsibility for any damages that might occur either directly or indirectly from these inaccuracies.

    You can verify that if you like by opening this file in for example
    XN Resource Editor that is available here:


    and looking at the "XP Theme Manifest" for that file and the Windows Vista
    files in Windows Vista that should have "requestedExecutionLevel" set...

    Best wishes,
    Hans Eriksson

  • Kimmo Varis

    Kimmo Varis - 2007-03-12
    • status: open-accepted --> closed-accepted
  • Kimmo Varis

    Kimmo Varis - 2007-03-12

    Logged In: YES
    Originator: NO

    Thanks a lot for all the information!

    I'm using Innosetup 5.1.9 at the moment, and will use it for future 2.6.x. releases also. I'm not taking the risk breaking installer in stable releases.

    However, for 2.8. stable releases I'll update the installer.

    I understand this can cause problems for Vista users, but they still are the minority compared to other Windows versions.


Log in to post a comment.