Closed Bug 661178 Opened 8 years ago Closed 8 years ago
[el] translate plugin check page for Firefox 5
The Plugin Check page is becoming an in-product page linked from the addons manager in Firefox Please translate the following files on mozilla.com svn repository for the release: /plugincheck/index.html: http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/en-GB/plugincheck/index.html?revision=89672&content-type=text%2Fplain&view=co /plugincheck/content.inc.html: http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/en-GB/plugincheck/content.inc.html?revision=89690&content-type=text%2Fplain&view=co You can see the page on the staging server here: http://www-trunk.stage.mozilla.com/el/plugincheck/ Send them directly to svn indicating in this bug comments the revision number or alternatively, attach the files to this bug. Repo: https://svn.mozilla.org/projects/mozilla.com/trunk/el Thanks!
Done for el with revisions 90028 & 90036. I've tried to keep the Greek text minimal but obviously we need some tweaking in the CSS since some text overlap. I've also removed the RMS link for my locale and changed some text to make it compatible with Firefox 4+. I hope there's no problem with that.
As far as I can see, the page is live. However, the css of the page on stage is slightly different than the live one - the live page looks better than the stage. I don't want to expirement on the page right now since it's live, but it would be better if we could have the main-feature's h2 span break in two lines ("προσθετων λειτουργιων") or a different colour for it. The layout is fine the way it is right now live, but the h2 is overlapping the image and the colours make it difficult to read. Anyway, since it's already live and the layout looks ok on the live page, I guess this bug can be closed?
yes, let's mark this one fixed :)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Component: www.mozilla.org/firefox → www.mozilla.org
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.