[ja] Translate new update billboard for Firefox 5+

RESOLVED FIXED

Status

RESOLVED FIXED
7 years ago
6 years ago

People

(Reporter: pascalc, Assigned: kohei)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

7 years ago
I am not seeing a bug for Japanese, so adding it for Kohei. Kohei can you make sure this is done either on mozilla.jp or mozilla.org? Thanks

+++ This bug was initially created as a clone of Bug #683526 +++

We've created one more billboard that's encouraging users to update to the newest version of Firefox, and it should be translated in all languages Firefox is available in.

This is really important because that way we make sure to let our users know that they could use better and newer version of Firefox - in their language!

This time we have 2 billboards. One is for our Firefox 3.6 users, and the other one is for all others who're not using the latest version of Firefox.

Files to translate have been put in:

https://svn.mozilla.org/projects/mozilla.com/trunk/ja/firefox/latest/details/

As you can see, there are 2 files: index.html and from-3.6.html. Both files are actually PHP files, and they contain strings to translate.

Once you translate those files, please commit your changes and paste the revision number here.

As always,

If you need any help with translating these files, don't hesitate to ask. You can find me on IRC(irc.mozilla.org, channel #l10n, nick Milos), or you can email me - milos@mozilla.com
Will do.
Status: NEW → ASSIGNED
Kohei, can we have this localized and live before the Firefox 8 release on Nov 8th ?
Sorry for the late, I'll check this today or tomorrow.
(Reporter)

Comment 4

7 years ago
Kohei, any news on this one?
Sorry to keep you waiting, done in r97254.
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
We would like to have ja availabe by https like the other locales. Bug 645568 is an earlier instance of this. Right now we're redirecting to mozilla.jp, which redirects from https to http:

url -IL https://www.mozilla.org/ja-JP-mac/firefox/latest/details/from-3.6.html
HTTP/1.1 301 Moved Permanently
Server: Apache
X-Backend-Server: pm-web03
Vary: Accept-Encoding
Cache-Control: max-age=900
Content-Type: text/html; charset=iso-8859-1
Date: Mon, 07 Nov 2011 20:41:05 GMT
Location: https://www.mozilla.org/ja/firefox/latest/details/from-3.6.html
Expires: Mon, 07 Nov 2011 20:56:05 GMT
Transfer-Encoding: chunked
X-Robots-Tag: noodp
Connection: Keep-Alive
X-Cache-Info: caching

HTTP/1.1 301 Moved Permanently
Server: Apache
X-Backend-Server: pm-web04
Vary: Accept-Encoding
Cache-Control: max-age=900
Content-Type: text/html; charset=iso-8859-1
Date: Mon, 07 Nov 2011 20:40:52 GMT
Location: http://mozilla.jp/firefox/latest/details/from-3.6.html
Expires: Mon, 07 Nov 2011 20:55:52 GMT
Transfer-Encoding: chunked
X-Robots-Tag: noodp
Connection: Keep-Alive
X-Cache-Info: cached
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Note, in the other bug the files were hosted on mozilla.com (now mozilla.org) because mozilla.jp didn't have a cert.
Oh OK, I'll prepare from-3.6.html soon. (If the file exists on mozilla.org, the redirect to mozilla.jp won't happen)
Status: REOPENED → ASSIGNED
The from-3.6.html file already exists here:
http://www-dev.allizom.org/ja/firefox/latest/details/from-3.6.html

I just translated the content in r97437.
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago7 years ago
Resolution: --- → FIXED
Pardon me, but lets mark this fixed when the change is available from the production site. Likely to get lost otherwise.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Reporter)

Comment 11

7 years ago
pushed to production in r97443

http://www.mozilla.org/ja/firefox/latest/details/index.html
http://www.mozilla.org/ja/firefox/latest/details/from-3.6.html
Status: REOPENED → RESOLVED
Last Resolved: 7 years ago7 years ago
Resolution: --- → FIXED
Component: www.mozilla.org/firefox → www.mozilla.org
Product: Websites → Websites
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.