Closed
Bug 1416160
Opened 7 years ago
Closed 7 years ago
Document basic Pontoon+FTL workflow
Categories
(Core :: Internationalization: Localization, enhancement)
Core
Internationalization: Localization
Tracking
()
RESOLVED
FIXED
People
(Reporter: zbraniecki, Assigned: flod)
References
Details
As we're introducing first Fluent localizations of Firefox, it becomes valuable to have some basic documentation of the Fluent specific Pontoon UI/UX features. Pike suggested to start with the list of Pontoon features that are being added as part of bug 1407256.
Reporter | ||
Comment 1•7 years ago
|
||
Flod, Jeff - would you be able to take this?
Flags: needinfo?(jbeatty)
Flags: needinfo?(francesco.lodolo)
Assignee | ||
Comment 2•7 years ago
|
||
I can take care of this. Ideally, I'd prefer to document every UI change related to FTL when it lands, more than doing it afterwards. A ping in in the bug or PR would be enough.
Assignee: nobody → francesco.lodolo
Flags: needinfo?(francesco.lodolo)
Assignee | ||
Updated•7 years ago
|
Flags: needinfo?(jbeatty)
Assignee | ||
Comment 3•7 years ago
|
||
Note: I don't think this blocks first migration. If nothing else, because we already have projects using FTL in Pontoon.
Reporter | ||
Comment 4•7 years ago
|
||
Pike - you set this bug on the dependency for first-migration. Do you agree with :flod?
Flags: needinfo?(l10n)
Comment 5•7 years ago
|
||
I'm wondering if we shouldn't at least have attributes documented. They are already used, but sparsely, and only in screenshots and the test pilot website AFAICT. Pontoon DB says we have 74 locales with existing translations for those strings.
Flags: needinfo?(l10n)
Assignee | ||
Comment 6•7 years ago
|
||
(In reply to Axel Hecht [:Pike] from comment #5) > I'm wondering if we shouldn't at least have attributes documented. They are > already used, but sparsely, and only in screenshots and the test pilot > website AFAICT. Pontoon DB says we have 74 locales with existing > translations for those strings. They are, maybe not in full depth https://mozilla-l10n.github.io/localizer-documentation/tools/pontoon/ui.html#translation-workspace Not sure if, at some point, we'll have to put all the FTL information in one doc.
Reporter | ||
Comment 7•7 years ago
|
||
Flod - can you make a call on whether this should block First Migration pls? Based on your comment 3 I'd like to take it off from the blocker list, but I'd like to know which milestone this bug should block.
Flags: needinfo?(francesco.lodolo)
Comment 8•7 years ago
|
||
We should have specific bugs for specific fluent features for milestone, I think. As far as first migration goes, I think we're documentation-complete with the last update. Not sure if we should resolve this bug or leave it open.
Assignee | ||
Comment 9•7 years ago
|
||
(In reply to Zibi Braniecki [:gandalf][:zibi] from comment #7) > Flod - can you make a call on whether this should block First Migration pls? > Based on your comment 3 I'd like to take it off from the blocker list, but > I'd like to know which milestone this bug should block. If the call is mine, documentation shouldn't block the first migration (see also comment 3). Given the subject of the bug ("basic ftl workflow"), I think we're covered and I'll close this one. We use issue to track documentation needs https://github.com/mozilla-l10n/documentation/issues (internal) https://github.com/mozilla-l10n/localizer-documentation/issues (localizers) My suggestion would be to file an issue there for every feature implemented in Pontoon, and likely use a whiteboard flags to make search possible (e.g. l10n-docs-needed). Since I have visibility on Pontoon's bugs, I can take care of both.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(francesco.lodolo)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•