Opened 2 years ago

Last modified 14 months ago

#27562 new enhancement

Detect the locale and automatically serve the language specific support portal

Reported by: sukhbir Owned by: hiro
Priority: Medium Milestone:
Component: Webpages/Support Version:
Severity: Normal Keywords:
Cc: ggus, emmapeel, antonela, arthuredelstein Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by arma)

The support portal should detect the browser locale and then automatically serve the language page of that locale.

Note: This is probably an enhancement ticket and warrants further discussion, including how to do this.

Child Tickets

Change History (11)

comment:1 Changed 2 years ago by arma

I had in mind a language-neutral type of url which would look at what is configured in the browser and give you the best available language.

The current ones, like, are actually perfect for this language-neutral url. That way the user can either explicitly ask for a language by using a url with the language in it, or leave it up to our webserver by omitting it.

For comparison, see how Tor website urls like do the language negotiation automatically (or you can explicitly ask for the english one by appending .html.en to it). That approach leaves all the work to Apache's language negotiation, which is great because then mirrors (if they run apache) can auto-do it too.

comment:2 Changed 2 years ago by arma

Description: modified (diff)
Summary: Detect the locale and redirect to the language specific support portalDetect the locale and automatically serve the language specific support portal

We probably would want to serve the right language automatically, not to do any redirects. Updating the ticket to reflect that.

Also, I know translations is a topic that many people have opinions about, and especially about the user-side experience for them. So if you -- the one doing this ticket -- have a better way to let the user's browser negotiate a language with the webserver, that sounds good to me too.

comment:3 Changed 2 years ago by emmapeel

I like this, as long as the users can also choose a specific language by hand and not being redirected to the one on the Browser.

Many users have the Browser, specially Tor Browser, configured in English to be more anonymous, or because they are using a computer that is not theirs, etc.

comment:4 Changed 2 years ago by emmapeel

Cc: emmapeel antonela added

Also: currently we have only completed translations on the support portal, we should decide what to do with languages that have the tb bundle localized but still no translation completed on the support portal.

Antonela, what do you think?

comment:5 Changed 2 years ago by antonela

hey, thanks emma!

Yes, the support portal should detect the browser locale and then automatically serve the language page of that locale.

If that locale doesn't exist at the support portal, then it should show the English one[0] (not a 404).

[0] or

comment:6 Changed 2 years ago by antonela

Cc: arthuredelstein added

Arthur added because we need him :)

comment:7 Changed 2 years ago by arthuredelstein

Hello! :) This sounds closely related to the situation with the TBB user manual. Currently we have a link to the user manual in the Tor Browser start page (about:tor) localized to the Tor Browser locale. I believe that mechanism is *independent* of whether the user chooses to spoof their locale to en-US. That might be something we should change -- I don't know. But if we use arma's suggested mechanism via Apache, then it would very easy link to a language-neutral URL in Tor Browser and have the Accept-Language header (spoofed or unspoofed) take care of the locale.

Also, we hide the user manual link to the Tor Browser manual when the right locale isn't available. But it would be easy to change this to an en-US fallback.

It also occurred to me today (given other discussions) that we could somehow merge the user manual and support portal. They serve very similar purposes, of explaining how to use Tor to users. So maybe that means we would need just one link instead of two. (By "merging" only I mean have the manual and support FAQ on the same website, not changing the content of either).

But any arrangement is possible of course. :)

comment:8 Changed 2 years ago by emmapeel

Parent ID: #24597

comment:9 Changed 2 years ago by emmapeel

Parent ID: #24597#24129

comment:10 Changed 2 years ago by emmapeel

for example, if i am browsing a document in Spanish, inside the portal, and I click an internal link that goes:


I should be able to click and be taken to a page with the contents in Spanish.

Regarding the URL, although, maybe I am forwarded to /es/administrar-identidades/#nueva-identidad (but I don't know how that would be possible with the way the header anchors are done now)

Last edited 2 years ago by emmapeel (previous) (diff)

comment:11 Changed 14 months ago by antonela

Parent ID: #24129

We want to close #24129. We are keeping this ticket open to make sure that this is happening.

Note: See TracTickets for help on using tickets.