130
edits
(Added CSS and SVG to the coding standards section) |
(Added a section about l10n guidelines) |
||
| Line 252: | Line 252: | ||
* File: <tt>/devtools/shared/locales/en-US/gcli.properties</tt> | * File: <tt>/devtools/shared/locales/en-US/gcli.properties</tt> | ||
* Usage: <tt>chrome://devtools-shared/locale/gcli.properties</tt> | * Usage: <tt>chrome://devtools-shared/locale/gcli.properties</tt> | ||
=== Guidelines === | |||
Localization files should follow a set of guidelines aimed at making it easier for people to translate the labels in these files in many languages. | |||
[https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_content_best_practices Find these guidelines on MDN]. | |||
In particular, it's important to write self-explanatory comments for new keys, deleting unused keys, changing the key name when changing the meaning of a string, and more. So make sure you read through these guidelines should you have to modify a localization file in your patch. | |||
= Making and Submitting a Patch = | = Making and Submitting a Patch = | ||
edits