canmove, Confirmed users
1,448
edits
L10n:Meetings/2018 Ljubljana: Difference between revisions
Jump to navigation
Jump to search
→Monday: Fluent Design Process
(→Monday: Fluent Design Process) |
|||
| Line 199: | Line 199: | ||
*Lunch:TBD | *Lunch:TBD | ||
;Afternoon | ;Afternoon | ||
*Fluent Design Process | |||
**Cross-channel impacts the design of Fluent. | |||
***Any future syntax changes must consider the fact that xchannel takes the liberty to walk through the history of mozilla-central | |||
***Effectively, python-fluent must provide some sort of parsing support for all syntax starting from 0.4. | |||
***This will also benefit the use-case of mining the contribution | |||
**We are not going to do xchannel in ESR 60: | |||
***It allows us to migrate away from DTDs and remove them when not needed in release anymore. | |||
***Translations can be fixed in a single place (the FTL file). | |||
***We don’t have to work on adapting the sign-off process for release/ESR. | |||
***In Fluent, we can solve the indentation issue by implementing whitespace relaxation. | |||
***We can ask early adopters for feedback on Fluent and act on it. | |||
*Dinner:TBD | *Dinner:TBD | ||