588360 - Wrap all localizable strings in gettext tags

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: Wiki pages, defect, P1)

Description

[Fred Wenzel [:wenzel]]

In order to internationalize MDN, after string freeze all strings need to be wrapped in _() and friends.

Comment 1

[Fred Wenzel [:wenzel]]

Note: This bug is about the Django app only, which I know how to localize.

The forums will probably be English-only, I assume? That's how AMO handles it, and it makes sense as the discussions are probably in English anyway.

And then Dekiwiki is out of scope here too, but I assume that's largely translated already as well.

Speak up if any of these assumptions are wrong.

Comment 2

[Jay Patel [:jay]]

Fred's assumption are correct.  This bug and first round of l10n activity will be focused on the new MDN landing pages, so just want to make sure we:

1. Get the UI translated (nav, titles, headings, etc)
2. Explore adding special feeds for locales (eg. swapping out the web news feed with a Japanese link from https://dev.mozilla.jp/)

That's pretty much all we want to start with.  We can look into more stuff once the l10n community has a chance to provide more feedback.

Comment 3

[Jay Patel [:jay]]

Does Verbatim allow localizers to also update the links on pages?  I ask because a lot of the content that is linked from the new MDN pages have localized versions in Deki and I would like to make it easy for people to point to those for their locale's pages.

Comment 4

[Fred Wenzel [:wenzel]]

Well, we can also make these URLs localizable, yes. Or if it's only about Deki URLs, we could drop the right locale in straight away. That only has two problems that we need to figure out before:
- If I link to a site in French that only exists in English, will that forward / fall back, or do something ugly like a 404?
- Is there a list of locales Deki has? In some cases we don't use the same locale codes on Django (like en_US vs. "En") and would need to do some sort of mapping so we generate valid target URLs.

Comment 5

[Jay Patel [:jay]]

(In reply to comment #4)

> - If I link to a site in French that only exists in English, will that forward
> / fall back, or do something ugly like a 404?

We want to always fall back to en-US if the localized version of a page doesn't exist.

> - Is there a list of locales Deki has? In some cases we don't use the same
> locale codes on Django (like en_US vs. "En") and would need to do some sort of
> mapping so we generate valid target URLs.

Localizers have translated many pages, but the number of locales varies per page.   Therefore I want to work towards cleaning up both the locale codes we use (stick to our en_US codes that we use elsewhere)... and find a way to automate the redirects for the old pages that live under two letter codes for various locales.

We can discuss in more detail soon... let me think about how things are setup and talk to Sheppy to see what our best bet will be for the URLs.

Comment 6

[Fred Wenzel [:wenzel]]

As promised, I'll work on internationalizing the static strings for this. It'll be just the Django part for now. Deki is already localizable, and for the forums template, we need to research a little.

Comment 7

[Fred Wenzel [:wenzel]]

All strings should be wrapped in: http://github.com/fwenzel/mdn/commit/34c21e9

I'll make sure this shows up on Verbatim, then close this bug.

Comment 8

[Fred Wenzel [:wenzel]]

Done.