Overview: To increase the reach and impact of the existing "Be a Web Hero" Facebook tab, we are planning on adding localization support and allowing users to send a pre-written Facebook message to a friend. Once a user sends a message, they'll be presented with a "I'm a Web Hero" badge that they can post on their own Facebook Wall. Project scope: The tab code will be updated by Zach Allia and he's already started working on it. We will need L10n to localize the tab content (~200 words), QA to test the site, and Web Dev to push the site to stage+production (Zach only has commit access to mozilla.com trunk). Dependencies: Legal: Don't think so Security: Don't think so Finance: No Timing: Zach is planning to complete implementation in the next two days so we'll have this staged later this week. Would ideally like this to go live the week of May 16 with some initial locales, and then we can add additional locales as they're ready. Not sure if this needs to be part of the mozilla.com release schedule or could be pushed outside of that. I realize this is a rather quick schedule, but we think it's one of the best ways we can help current Firefox users move to Firefox 4 sooner. Deliverables: - Updated tab design (bug 651901) - completed - "I'm a Web Hero" badge design (bug 652994) - completed
We were hoping to have the update to the Web Hero Facebook tab staged by today, but after talking with Zach a few minutes ago it's not going to be ready until this weekend. That means the earliest we could start testing and localization is Monday. Stas and I chatted on IRC and we'll shoot for Monday to start localization. I imagine the QA tag-team can start then as well, but let me know if there are any concerns. At this time, we're still planning to release on May 17. Stas and I also talked about doing a follow up release on May 24 to add any locales that aren't ready by May 16. We'll discuss this more next week and decide then if we'll go with that plan.
Stas, William: do you already have plans on how to translate the pdfs? Sadly, it is the only material that works here for l10n as neither the videos or Mozilla central (https://www.mozilla.com/en-US/firefox/central) are localized :( Pascal and I have already started discussing this for the web part of the campaign and figured we have two options: 1/ convert the doc to libre office and have the localizers translate directly and convert back to pdfs once everything is ready. 2/ have the localizers translate the copy and make the screenshots and have the creative team generate the pdf for each locale (+ will require 1 additional back & forth for proofreading) Does that make sense? Do you have any thoughts?
(In reply to comment #2) > Stas, William: do you already have plans on how to translate the pdfs? > Sadly, it is the only material that works here for l10n as neither the > videos or Mozilla central (https://www.mozilla.com/en-US/firefox/central) > are localized :( > > Does that make sense? Do you have any thoughts? Thanks for bringing this up Greg. After chatting with Jane, I think option 1 is best as well as easier and less resource intensive. Since translating the pdfs should block this bug, I think it's okay to push back the release of the updated tab a week or so to give localizers enough time. I'll check in with Stas on his recommendation. Is there currently a bug for translating the pdfs? Another question: Since the other material mentioned in the tab (videos and Mozilla central) are not localized, what replacement content do you suggest we put there for other locales? We can point to localized sites instead of Mozilla central, but I'm not sure what we can put in place of the videos.
The pdfs are part of the larger bug 650843. So in order to achieve solution one, we will need to get the document in the .ppt equivalent of libre office (localizers will not use MSFT Office). Do you know who did it? In terms of replacing Mozilla Central and video, this is a tough one. I don't believe there is any great content out there. My suggestion would be to replace Mozilla Central (aka "tour") with the localized feature pages (e.g. http://www.mozilla-europe.org/de/firefox/features/). It is far from ideal as the page is highly unattractive but I guess it's the lesser of two evils. Re: videos. We really don't have much decent l10n'ed content for now so I suggest scraping this part.
It just occured to me that they might be an easier way... How about we use the SUMO pages. Most languages offer a standard answer (along with screenshots) for "How to install Firefox on Windows / Mac" We can either recycle the content there to create pdfs, or even simpler but less fancy, redirect to these pages directly. Thoughts?
(In reply to comment #5) > It just occured to me that they might be an easier way... How about we use > the SUMO pages. Most languages offer a standard answer (along with > screenshots) for "How to install Firefox on Windows / Mac" Great idea, Greg! > We can either recycle the content there to create pdfs, or even simpler but > less fancy, redirect to these pages directly. > > Thoughts? I think linking to the localized SUMO pages still achieves what we want and it will require less L10n resources. We'll need to rework gettext code around those steps on the tab so localizers can put the appropriate text and links in. We should also make the sharing a video step optional, since we won't have that material in all locales. I'll work with Zach on these changes. I feel like a similar approach would work well for updating the mozilla.com Web Hero page as well.
Sounds good. I did a quick check to see if this worked on all major locales (fr, de, es-ES, it, ru) and here is the result: DE: Windows = OK / Mac = OK FR: Windows = OK / Mac = 3.6 IT: Windows = 3.6 / Mac = OK ES: Windows = 3.6 / Mac = 3.6 PL: Windows = 3.6 / Mac = 3.6 RU: Windows = 3.6 / Mac = not available (ok for Russia) So it look like in order for this solution to work, we would need to make sure the appropriate SUMO anwsers are updated. William, do you know who we should ask about that? Looks like a change that needs to happen anyway (maybe there is even a way to make it version agnostic)? I will discuss the moz.com web hero part with Pascal upon his return.
Kadir tells me the SUMO content is up-to-date (apart from some screenshots which we won't have any time soon). Here are the links: https://support.mozilla.com/kb/Installing+Firefox+on+Windows https://support.mozilla.com/kb/Installing+Firefox+on+Mac Language should be adapt to user's system language automatically.
Thanks Greg. Stas updated the code so localizers can easily add the appropriate links for their locale. Greg, is there anything else needed here or can this bug be closed? The Web Hero Facebook tab has already supported localization for a couple weeks.
It appears that the latest modifications (bug 663410?) broke the localized string for the 2nd item on the checklist. Several other strings on the landing pages (https://bugzilla.mozilla.org/show_bug.cgi?id=650843#c2) also reverted to English for most locales. We need to do two things before we can close this: - fix the broken strings for all impacted locales - change the copy for the check list so it reflects the actual available content. See bug 650843 for the copy. Note: not sure of the status for Italy and Russia but the entire tabs are in English. Stas, have they not been localized?
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.