L10n:Localizing Projects and Content: Difference between revisions

L10n:Localizing Projects and Content (view source)

Revision as of 22:41, 18 January 2012

3,232 bytes added , 18 January 2012

no edit summary

Jbeatty

Account confirmers, canmove, Confirmed users

2,357

edits

@@ Line 1: / Line 1: @@
-One of the prides of Mozilla is our localization skills. Our expansive community of localizers are expert at taking a project and adapting it to suit the needs of their region's user base and target audience. The L10n community is very active, highly organized, and super dedicated to spreading Mozilla's mission throughout the world. That being said, our community requires a lot of planning, design, infrastructure, and organization to take a project and spread it around the globe.
+__NOTOC__One of the prides of Mozilla is our localization skills. Our expansive community of localizers are expert at taking a project and adapting it to suit the needs of their region's user base and target audience. The L10n community is very active, highly organized, and super dedicated to spreading Mozilla's mission throughout the world. That being said, our community requires a lot of planning, design, infrastructure, and organization to take a project and spread it around the globe.
-If you're visiting this page, you are interested in getting your particular project localized and are wondering where to even begin. Don't worry, take a deep breathe, and know that we, the l10n-drivers, are here to help and answer your questions. Here we'll talk about a few consideration you need to make before submitting your L10n request. We'll also include a wiki template which is to be used as a form to fill out and submit to have your project included in the wide array of Mozilla L10n projects.
+If you're visiting this page, you are interested in getting your particular project localized and are wondering where to even begin. Don't worry, take a deep breathe, and know that we, the l10n-drivers, are here to help and answer your questions. Here we'll walk you through the process of starting your project's successful L10n program. We'll identify some considerations to keep in mind when submitting your L10n request. We'll also include a wiki template which is to be used as a form to fill out and submit to have your project included in the wide array of Mozilla L10n projects. Finally, we'll point out some resources that could be valuable to you as you prepare for localizing your project.
+=The process=
+# Fill out the [https://wiki.mozilla.org/Template:L10n:ProjectRequestForm L10n request form]. When naming the your completed form, use this naming convention: https://wiki.mozilla.org/L10n:''[your project's name]''Proposal.
+# File a bug under Mozilla Localizations>Other and include the URL to your completed L10n request form & assign it to l10n@mozilla.com (i.e., Pike).
+# Your request from will then be reviewed by us, the L10n-drivers. Anticipate being contacted for all of the following:
+#* asking questions
+#* nailing down specifications
+#* helping to prioritize content
+#* discussing potential L10n blocks that you should be aware of.
+# Set up the L10n infrastructure for your project.
+#* Choose the [[mdc:Web_Localizability/localization_formats|localization format]].
+#* Set up a staging server.
+#* Notify QA lead that L10n is a requirement.
+# Create the localizable content and templates.
+#* Request a review by QA.
+#* Request a content review by l10n-drivers.
+# Verify all that the strings you are using ''will not change'' after localizers start working.
+#* Localizers will not start working until there is a final sign-off.
+# Have the L10n-drivers file bugs to begin localization and announce that the project is ready to be localized.
+# Test on the staging server.
+# Launch your localized project!
+# '''Mathjazz, Pike, Stas: Anything I've missed????'''
+=The considerations=
+Below are some considerations that you should make when planning a rocking L10n program for your project:
+* Our localization community is overall very active and enthusiastic. However, non-target locales may ask why they weren't targeted for your project and may request to participate. Should that be the case, be prepared to have an answer for them.
+* Have a plan in mind if a localization team does not have time to take on your request or simply says, "No."
+* Depending on the project's scope, the l10n-drivers will need anywhere from '''6 weeks to a quarter''' of planning time.
+* Consult with [mailto:l10n@mozilla.com Pike] to know the current localization workload and where your project could fit within it.
+* It's been our experience that highly visible, critical pages, like the "What's new" page, can require '''3 weeks for 40 locales to localize'''. If your project has less exposure, please allow for more time.
+=The template form=
+[https://wiki.mozilla.org/Template:L10n:ProjectRequestForm Here] is the form that we need you to fill out. Fill out everything underneath the heading '''What we need from you'''. Keep in mind, the more information you provide us, the easier it will be to kick off a successful L10n program for your project.
+=Resources=
+[[mdc:Web_Localizability/Creating_localizable_web_content|Creating localizable web content guidelines]].
+Follow the template guidelines at [[mdc:Web_Localizability/Creating_localizable_web_applications|Creating localizable web applications guidelines]]
+[[mdc:Web_Localizability/Setting_up_the_infrastructure|Setting up the infrastructure guidelines]].