Skip to content

NVDA installation may fail with an error if system UI language and language for non-unicode programs don't match #5166

@nvaccessAuto

Description

@nvaccessAuto

Reported by k_kolev1985 on 2015-06-20 07:56
Hello,

The tests are done on 2 machines with Windows 7 Ultimate 32-bit, but I think that the issue will occur on every version of Windows supported by NVDA, if the conditions are met. In both cases, the UI language was set to "bulgarian", but the language for non-unicode programs was set to something else, witch doesn't support cyrillic (bulgarian) text ("English (United States)" is such a language). In such a case, NVDA will display an error message dialog with the information that the installation failed and for more details to check the NVDA log file. The log file reports an error related to the creation of the NVDA desktop shortcut (see the attached log files). However, the shortcut seams to be created OK - it works as it should, including the Control+Alt+N keyboard shortcut to launch or restart NVDA (it is set in the shortcut's properties). If the UI language and the language for non-unicode programs match, there is no issue. I suspect that the issue will occur only if the language for non-unicode programs set doesn't support displaying of text in the UI language set.

BTW: As far as I know, it is not a common thing for the UI language and the language for non-unicode programs to mismatch on a standard PC configuration (at least the language for non-unicode programs is set correctly). But sometimes (such as in the case mentioned above), it may be set so by mistake. In normal circumstances, we here in Bulgaria set the language for non-unicode programs to "Bulgarian", so we don't have issues with displaying cyrillic text in non-unicode programs.

Steps to reproduce the issue:

  1. In Control Panel -> Region and Language, set the UI language and the language for non-unicode programs to such values, so the language for non-unicode programs will not support displaying of text in the UI language set. Reboot if required.
  2. I'm not sure that it is required, but just to be sure - delete the NVDA shortcut on the desktop.
  3. Start installing or updating NVDA from a downloaded installer.
  4. In the installer, check the option to create a shortcut for NVDA on the desktop.
  5. Wait for the installer to do its job.

Actual results:
NVDA will display an error message dialog with the information that the installation failed and for more details to check the NVDA log file.

Expected results:
The NVDA installation/update should complete with no such errors, even if the UI language and the language for non-unicode programs don't match.

Test environment:

  • Operating system: Windows 7 Ultimate 32-bit.
  • NVDA version: 2015.2.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugcomponent/i18nexisting localisations or internationalisationp4https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityz Python 3 transition (archived)Python 3 transition

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions