Confirmed users, Bureaucrats and Sysops emeriti
1,531
edits
L10n:WorldReady: Difference between revisions
→General Strategy for Improved l10n
ChrisHofmann (talk | contribs) |
|||
| Line 22: | Line 22: | ||
In general, we need to not treat localization as an addition to projects, but an early and integral part of the development work. For example when on a tight schedules we need to avoid deferring consideration of localization issues and say 'we'll do l10n in phase 2. | In general, we need to not treat localization as an addition to projects, but an early and integral part of the development work. For example when on a tight schedules we need to avoid deferring consideration of localization issues and say 'we'll do l10n in phase 2. | ||
We are inventing all kinds of new technical terms in creating new features on the web and in browsers so we need to use the most simple language that will provide the greatest widespread meaning for our users around the world. | We are inventing all kinds of new technical terms in creating new features on the web and in browsers, and attempting a number of creative ways to spread the word about Mozilla and Firefox, so we need to use the most simple language that will provide the greatest widespread meaning for our users around the world. As in real estate where location, location, location are the three most important things, "context, context, context" is important for localizers to try and understand the feature or idea behind an engagement campaign. | ||
We need to think about, and document, workflows and apply an engineering discipline to creative work to find points where the localization peer review and global feedback can be injected. This includes improving the way we communicate information about feature names, marketing campaigns and all the content we produce. We need to find ways to 'test and evaluate' the global understandability of product names, features, and content we produce; and where possible communicate in terms that attempt to be widely understood without instruction. The feedback from this testing and evaluation will help us to simplify they way we communicate to all users around the world including those in English or have minimal technical skills. | We need to think about, and document, workflows and apply an engineering discipline to creative work to find points where the localization peer review and global feedback can be injected. This includes improving the way we communicate information about feature names, marketing campaigns and all the content we produce. We need to find ways to 'test and evaluate' the global understandability of product names, features, and content we produce; and where possible communicate in terms that attempt to be widely understood without instruction. The feedback from this testing and evaluation will help us to simplify they way we communicate to all users around the world including those in English or have minimal technical skills. | ||