782548 - i18n/l10n support for Developer Guide

Status: RESOLVED FIXED

(Add-on SDK Graveyard :: Documentation, defect, P2)

Description

[dynamis (Tomoya ASAI)]

Addons SDK Developer Guide
https://addons.mozilla.org/en-US/developers/docs/sdk/latest/dev-guide/
is generated from:
https://github.com/mozilla/addon-sdk/tree/master/doc/dev-guide-source

We Japanese team already translated Tutorial section of the guide:
https://dev.mozilla.jp/addon-sdk-docs/dev-guide/tutorials/

But it don't support i18n/l10n yet and cannot merge translated document into the master repository.

Our translated file are in my repository forked from mozilla/addon-sdk:
https://github.com/dynamis/addon-sdk/tree/japanese-docs

Please support i18n/l10n for the Developer Guide.

Comment 1

[Will Bamberg [:wbamberg]]

Wow, it's just fantastic that you've translated the tutorials!

I think there are possibly two stages of i18n:

(1) we could enable the static web docs to be localized (https://addons.mozilla.org/en-US/developers/docs/sdk/latest/)

(2) we could enable the downloadable docs to be localized

I think (1) is simpler (and possibly more useful) than (2), and we should do that first.

For (1): we plan to move the SDK docs to MDN in the future, and to take advantage of MDN's i18n system for the static web docs. However, we have been saying this for a long time, and it still seems like quite a long way off, and I am now wondering whether we should try implementing (1) without waiting for MDN?

For (2): we need to think about what this will look like: whether the SDK would contain all translations, or whether we would build separate SDKs for different locales, and how we would manage updates to the docs.

Jeff: can we talk about this in London, and try to make a plan for both (1) and (2)?

Comment 2

[Will Bamberg [:wbamberg]]

Finally, fixed now the SDK docs are in MDN: https://developer.mozilla.org/en-US/Add-ons/SDK.