TBB Alpha does not start in a folder with the Russian text

See the screenshot. tor-browser-linux64-3.0-alpha-3_en-US.tar.xz, Debian Wheezy.

Trac:
Username: lesov

added component::applications/tor launcher owner::erinn priority::medium reporter::lesov resolution::fixed status::closed type::defect labels

Trac:
Username: lesov

Trac:
Username: lesov

You are using the en-US version as "tor-browser_en-US" on your screenshot shows. I just downloaded the russian version and it seems to work fine.

Trac:
Resolution: N/A to worksforme
Status: new to closed

You are using the en-US version as "tor-browser_en-US" on your screenshot shows. I just downloaded the russian version and it seems to work fine. So you need localized bundle to start torbrowser if path contains non ascii codes? Did you tested it?

There's a report that the stable TBB works fine with non-ascii paths under circumstances like these. If so, that's a regression. Reopening until I hear differently.

Trac:
Status: closed to reopened
Resolution: worksforme to N/A

https://developer.mozilla.org/en-US/docs/XPCOM_Interface_Reference/nsIFile has a fun warning about UTF-16 versus native encoding for filenames. In the tl-process.js , should we be using .nativePath rather than .path to build the command line?

Trac:
Component: Tor bundles/installation to TorBrowserButton

Hm. Maybe I have it backwards. :/

Or maybe not. https://developer.mozilla.org/en-US/docs/XPCOM_Interface_Reference/nsIProcess says that the arguments to runAsync() need to be in the native character set.

Skruffy reports that using runwAsync() [which takes UTF16 characters for its arguments] is the answer here.

Trac:
Component: TorBrowserButton to Tor Launcher

Replying to cypherpunks:

You are using the en-US version as "tor-browser_en-US" on your screenshot shows. I just downloaded the russian version and it seems to work fine. So you need localized bundle to start torbrowser if path contains non ascii codes? Ah, no. I misread your bug report. Sorry for that.

Trac:
Cc: N/A to mcs, brade

It looks like a fix for this was committed a while ago by Mike:

https://gitweb.torproject.org/tor-launcher.git/commit/991e6307ea8de836587abdc39d0d71d415a317b9

Can someone verify that this is fixed in TBB 3.0a4 or the upcoming 3.0beta1?

Trac:
Cc: mcs, brade to mcs, brade, mikeperry

Confirmed working for me. I started it from a dir called ~/src/test/СтенаЦоя/tor-browser_en-US and it launched fine.

Trac:
Status: reopened to closed
Resolution: N/A to fixed

closed

mentioned in issue #10416 (moved)

moved to tpo/applications/tor-launcher#9593 (closed)