Open
Bug 1519334
Opened 5 years ago
Updated 2 years ago
Document "how to do localization" in DevTools
Categories
(DevTools :: Documentation, enhancement, P3)
DevTools
Documentation
Tracking
(Not tracked)
NEW
People
(Reporter: ogasidlo, Unassigned)
References
(Blocks 2 open bugs)
Details
In a discussion we had in a review for about:debugging-new, we decided it would be great to have some documentation for the devtools localization and best practice.
@jdescottes wrote:
[...]
For instance how to setup fluent with our vendored library, mention the shared
l10n.js for non fluent projects, mention that we already cache simple calls to
getStr... Probably also the bit about avoiding to concatenate ids.
Localization is complicated, so I would like to keep it short and forward to
existing resources maintained by Localization team:
https://mozilla-l10n.github.io/localizer-documentation/#how-to-contribute
https://projectfluent.org/fluent/guide/selectors.html
[...]
Updated•5 years ago
|
Severity: normal → enhancement
Keywords: dev-doc-needed
Comment 1•5 years ago
|
||
Localization documentation should stress that variants should not be abused and should point to https://github.com/projectfluent/fluent/wiki/Good-Practices-for-Developers#prefer-separate-messages-over-variants-for-ui-logic
Updated•3 years ago
|
Component: General → Documentation
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•