488588 - l18n problem with new "use XDG downloads dir as default downloads dir" functionnality

Status: UNCONFIRMED

(Toolkit :: Downloads API, defect)

Description

[antistress]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b4pre) Gecko/20090401 Ubuntu/9.04 (jaunty) Shiretoko/3.5b4pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3

With Firefox 3.1b3 my XDG_DOWNLOAD is automatically chosen by Firefox to store files that i've downloaded, which is great.

But although my user-dirs.dirs file says :
XDG_DOWNLOAD_DIR="$HOME/Téléchargements"
Firefox 3.1b3 offers me the choice to "Save files to Download" whereas it should
say "Save files to Téléchargements" in my case (which is the l18n version of
"Download" set in the user-dirs.dirs file)

Note that if i manually select my Téléchargements dir from the File Chooser, Firefox keep on saying Download instead of Téléchargements

To be perfectly clear, Firefox chooses the good dir (XDG_DOWNLOAD_DIR="$HOME/Téléchargements") but names it "Download" instead of "Téléchargements"

Reproducible: Always

Steps to Reproduce:
Open the Preferences menu within Firefox : Download is selected in front of the "Save files to :" option

Try to manually select the l18n XDG_DOWNLOAD dir within the File Chooser
Actual Results:  
Firefox keep on naming it Download even if its name has been translated in the user-dirs.dirs file

Expected Results:  
Firefox should use the translated name of Download : the translated name can be find in the user-dirs.dirs file

i'm running Ubuntu 9.04 Jaunty beta

Comment 1

[antistress]

For the record,  Bug 399498 has fixed "use XDG downloads dir as default downloads dir"

Comment 2

[Rimas Kudelis [use needinfo to ping]]

I think that's intended behaviour. It's "Downloads directory", not "directory named Downloads". French version of Firefox would call that folder in French (regardless of the environment language and actual XDG download dir name).

Comment 3

[[:Aleksej]]

Maybe without this the situation in bug 645052 would be a little bit more clear.