NVDA won't restart itself if path to application contains non-ASCII character #2079

Closed
nvaccessAuto opened this Issue Feb 2, 2012 · 6 comments

1 participant

@nvaccessAuto

Reported by ateu on 2012-02-02 16:05
Hello,

This is an older problem.
It has been tested for myself on 2 computers runing windows 7 with the most recent snapshot.
This problem doesn't exists in windows xp.
Also in windows 7, using installer versions, this problem doesn't exists.
Steps to reproduce:
1: Run a portable version of NVDA;
2: Open the General setings dialog;
3; Change the language and press ok.
Expected results: NVDA should change to the new language and restart.
Result: nvda change the language but doesn't restart.
Also some dialogs doesn't appears into the new language, so that the new language to take afect, I need manually restart.

Thanks for your great work

@nvaccessAuto

Comment 1 by jteh on 2012-02-02 22:14
I can't reproduce this. What is the file path to your portable copy of NVDA?

@nvaccessAuto

Comment 2 by ateu on 2012-02-03 01:00
Hello,

The folder where I umpaked the 7z file was called nvda portable.
I have renamed to nvda. After this, the problem is no longer appearing.

Thanks

@nvaccessAuto

Comment 3 by jteh on 2012-02-03 02:13
Can you please provide the full path name (right from the drive letter)? I tried with a space in the directory name, but it still worked fine, so there must be something else happening here.

@nvaccessAuto

Comment 4 by ateu on 2012-02-06 16:26
Hello,

I placed the files in C:\NVDA Portátil, which means portable.

After I removed the accented letter from the name, the problem was fixed.
This means the problem appears because the accented letter.

@nvaccessAuto

Comment 5 by jteh on 2012-02-06 23:08
Thanks. I suspected something like this.
Changes:
Changed title from "In windows 7, it's not posssible restart portable versions of nvda after changing the language" to "NVDA won't restart itself if path to application contains non-ASCII character"
Milestone changed from None to 2012.1

@nvaccessAuto

Comment 6 by jteh on 2012-02-07 04:56
Fixed in f3740b0.
Changes:
State: closed

@nvaccessAuto nvaccessAuto added the bug label Nov 10, 2015
@nvaccessAuto nvaccessAuto added this to the 2012.1 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment