Bug 1492052 - Add naming convention for Fluent messages to documentation r=zbraniecki

Differential Revision: https://phabricator.services.mozilla.com/D6124

--HG--
extra : moz-landing-system : lando
This commit is contained in:
Francesco Lodolo (:flod) 2018-09-18 16:06:55 +00:00
parent 9464df5529
commit f8e0411407

View File

@ -159,6 +159,14 @@ a more complex example like:
The above, of course, is a particular selection of complex strings intended to exemplify
the new features and concepts introduced by Fluent.
.. important::
While in Fluent its possible to use both lowercase and uppercase characters in message
identifiers, the naming convention in Gecko is to use lowercase and hyphens, avoiding
CamelCase and underscores. For example, `allow-button` should be preferred to
`allow_button` or `allowButton`, unless there are technically constraints like
identifiers generated at run-time from external sources that make this impractical.
In order to ensure the quality of the output, a lot of new checks and tooling
has been added to the build system.
`Pontoon`_, the main localization tool used to translate Firefox, has been rebuilding