You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When application is started from a path that contains unicode characters, then you will see a "No input file specified." message in the browser window. Example location on XP:
C:\Documents and Settings\Unicode ąć\My Documents\Downloads\
Where "Unicode ąć" is the user's account name on Windows XP.
The solution would be to check the content of the initial web page during application startup, if it equals to "No input file specified" then application should be terminated immediately and a message should be displayed to user, something like:
Application has detected that it has been placed in a location on your hard drive that contains unicode special characters (%DISPLAY_PATH_HERE%). Due to some constraints this is not allowed. Application will terminate immediately.
This kind of problem occurs when your Windows account name contains non-standard characters. The solution is to put application directory in a location that contains only standard ASCII characters, put it to "C:" or to "C:\Program Files". Application must have permission to write files in that location.
Original issue reported on code.google.com by [email protected] on 1 Feb 2014 at 1:54
The text was updated successfully, but these errors were encountered:
When application is started from a path that contains unicode characters, then you will see a "No input file specified." message in the browser window. Example location on XP:
Where "Unicode ąć" is the user's account name on Windows XP.
The solution would be to check the content of the initial web page during application startup, if it equals to "No input file specified" then application should be terminated immediately and a message should be displayed to user, something like:
Original issue reported on code.google.com by
[email protected]
on 1 Feb 2014 at 1:54The text was updated successfully, but these errors were encountered: