Further research reveals that we will also need to change brandShortName inside these two files:
browser/branding/official/locales/en-US/brand.dtd
browser/branding/official/locales/en-US/brand.properties
Further research reveals that we will also need to change brandShortName inside these two files:
browser/branding/official/locales/en-US/brand.dtd
browser/branding/official/locales/en-US/brand.properties
Also, Torbutton contains copies of these files in:
src/chrome/locale//brand.dtd
src/chrome/locale//brand.properties
so we will need to change the Torbutton files too (that is where localization is handled; the Torbutton files are the ones that are really used).
The good news is that some translations already use a space within brandShortName, so adding one to en-US and other locales is unlikely to cause major bustage.
This is probably not top priority given the ESR31 work on our plate, but here are the three commits needed to use "Tor Browser" in (hopefully) all user-visible places within the browser:
Looks good to me although I have no clue whether we need to update transifex instead which gives us then back the "official" .dtd and .properties files. Anyway, I merged the tor-browser-bundle bits (commit e21bb4837a7affd469e413a2664f4a2bb5c2de4e).
Space brakes strings produced for resource section in windows binaries. Instead "Tor Browser" it's just "Tor" now for Product Name and another fields. Windows using strings from resource section to report about problem with application, report "Tor has stopped working" is confusing for Tor Browser case.
Space brakes strings produced for resource section in windows binaries. Instead "Tor Browser" it's just "Tor" now for Product Name and another fields. Windows using strings from resource section to report about problem with application, report "Tor has stopped working" is confusing for Tor Browser case.
Thanks for looking into this, and I agree it causes confusion. I have a fix that I am testing now (added quotes when invoking version_win.pl inside config/version.mk).