591584 - Localize the URLs in csshtmltree

Status: RESOLVED DUPLICATE of bug 591902

(DevTools :: General, defect)

Description

[Joe Walker [:jwalker]]

From csshtmltree.js:

>+function PropertyView(aTree, aGroup, aName)
>+{
...
>+  this.link = "https://developer.mozilla.org/en/CSS/" + aName;

This needs to either be localized, or use a language-agnostic link (which the
site would presumably redirect to as appropriate).

Not sure how to do this on DevMo; https://developer.mozilla.org/en/CSS/color
works bug https://developer.mozilla.org/CSS/color just redirects to the
toplevel page.

Comment 1

[Joe Walker [:jwalker]]

Also from csshtmltree.xhtml:

>+ <a class="link" href="https://developer.mozilla.org/en/CSS/Specificity"

Comment 2

[Joe Walker [:jwalker]]

I think we've got a good story for this already, but I'm raising this bug so we can track where we are on the raised issues.

Comment 3

[:Gavin Sharp [email: [e-mail]]]

I think this should probably block landing of that patch.

Comment 4

[Mihai Sucan [:msucan]]

As I understand from Kevin, (please correct me if I am wrong) the MDN people were not sure how the server-side code handles links to pages that do not exist in the target language. Say, we want to point users to the Romanian translation of the wiki page for the CSS color property. If that page does not exist, the user must be redirected to the English page.

It has been tentatively decided that we go to English pages only, until MDN provides the solution we need. I'd certainly prefer the links to point to the localized pages.

Comment 5

[Axel Hecht [:Pike]]

Please only make l10n decisions with the l10n people on board.

In general, I'm happy to not have URLs in l10n, as they're hard to do client-side, and should be easy to do server-side.

Is there a bug on file on MDN to support this use-case?

Comment 6

[Kevin Dangoor]

That's a good point that it should be easy enough to do this server-side. I've filed bug 591902 against MDN to support this.

Thanks for the suggestion.

Comment 7

[Kevin Dangoor]

Since MDN does not have a good solution for this today (and I have confirmed this with the MDN folks), and since this feature is going to be so amazingly useful even just in English, I'm going to propose that we include the links to MDN's English but do not make any attempt to localize them in Firefox 4.

Is that reasonable?

Comment 8

[Axel Hecht [:Pike]]

Yes, even more so as the translations of that page will actually be accessible from the English page in just another click. Not *really* server side as a solution, but close enough and better than trying to come up with something even hackier.

Comment 9

[Joe Walker [:jwalker]]

Should we close this bug now?

Comment 10

[Joe Walker [:jwalker]]

Ignore that - we shouldn't close it, just stop thinking about it for this release. I need to spend time fixing the meta bug.

Comment 11

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

The correct solution is for the MDN pages to redirect using the Accept-Language header. This will be done as part of bug 591902.

Comment 12

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

Bug triage, filter on PEGASUS.