|
|
| Line 26: |
Line 26: |
| ===== Formality and Tone ===== | | ===== Formality and Tone ===== |
|
| |
|
| <div id="magicdomid18">
| | We currently use formal tone on Firefox Desktop and informal tone on Firefox for Android and web content. |
| | This will change in a recent future, so please check later. |
| | If it's possible, begin with the verb. For example "haga clic aquí" instead of "usted haga clic aquí" |
|
| |
|
| <span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">When determining the formality or tone of a Mozilla l10n project in your language, ask yourself these questions:</span>
| |
|
| |
| </div>
| |
| * Who is the target user for this project and what is their background?
| |
| * How would a target user for this project expect to interact with this project? For example, would they expect a friendly, casual interaction?
| |
| * Is formal language appropriate for all of your language's Mozilla l10n projects, or only some of them? Which ones?
| |
| * Is informal language appropriate for all of your language's Mozilla l10n projets, or only some of them? Which ones?
| |
|
| |
| <div>
| |
|
| |
| <span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">In fact, localization should not use a level of formality higher or lower than required by this community-defined style guideline. An example of this would be using "click here" (not formal) vs. "please click here" (more formal). Also, the tone employed throughout a l10n project(s) should stay consistent within itself. </span>
| |
|
| |
| </div>
| |
| <div>
| |
|
| |
|
| |
|
| |
| </div>
| |
| ===== Natural expression ===== | | ===== Natural expression ===== |
|
| |
|