1243629 - Move Japanese security advisory translations to www.mozilla.org

Status: RESOLVED WONTFIX

(www.mozilla.org :: L10N, defect)

Description

[Kohei Yoshino [:kohei]]

Mozilla Japan offers Japanese l10n of all the Mozilla Foundation Security Advisories that I have continuously translated since 2003(!) I'd like to figure out a way to move the content to www.mozilla.org, if the security team allows.

https://www.mozilla.org/en-US/security/advisories/
http://www.mozilla-japan.org/security/announce/

Proposal:

1. Create the security-advisories-l10n repo under Mozilla's GitHub organization
2. Give me r/w access to the repo
3. Export the content from www.mozilla-japan.org
4. Import the localized content to Bedrock in the same way as the English equivalent

Comment 1

[Paul [:pmac] McLanahan]

Could we just utilize our current l10n framework? I could have the current system automatically wrap the strings for translation and we could move your translations into .lang files instead of a separate thing. Maybe we can't, but I ask because that would give us all of our current machinery for locale detection, redirection, and listing, which we otherwise may have to custom build for this case.

Comment 2

[Kohei Yoshino [:kohei]]

I'm not sure the current l10n workflow is appropriate here because there are a bunch of documents as you see. Another possible way is to 

1. Migrate the security advisories to Nucleus
2. Make Nucleus localizable (Bug 722914)

Comment 3

[Al Billings [:abillings - ex-MoCo]]

Existing advisories (in English) are in Bedrock. Why not...use bedrock?

Comment 4

[Kohei Yoshino [:kohei]]

Unlike other static pages on Bedrock, the source of the security advisories (and release notes) are *not* in Bedrock, as you know ;) I guess it may be easier than other options to implement my first proposal and maintain docs.

https://github.com/mozilla/foundation-security-advisories

Comment 5

[Kohei Yoshino [:kohei]]

One more reason why the current l10n framework is not suitable for this is that l10n is updated only when Bedrock has a production push, that may happen only once a week. I'd like to post my translation as soon as the English equivalent is published. I'll figure out if my proposal works.

Comment 6

[Paul [:pmac] McLanahan]

(In reply to Kohei Yoshino [:kohei] from comment #5)
> One more reason why the current l10n framework is not suitable for this is
> that l10n is updated only when Bedrock has a production push, that may
> happen only once a week. I'd like to post my translation as soon as the
> English equivalent is published. I'll figure out if my proposal works.

That l10n is only updated on deployment is a bug that the l10n team would very much like us to fix asap. I hope that we'll be able to do that. So this will not be an issue with the bedrock l10n system for very long. There are other issues with said system for this case though, you're right.

Comment 7

[Kohei Yoshino [:kohei]]

The security advisories are no longer translated into Japanese as I don't have enough time to work on it. Closing as WONTFIX.