I’m a skunkworks coder at a for-profit company. Our entire app, dev environment and stack is built on open source (Debian, postgres, python, node, git etc).
We want to go all-in on Fluent as a massive upgrade to our localization. We would like to convert our existing gettext translations to ftl. Any thoughts on what this would take?
Could we help the Moz community and ourselves at the same time by providing the developer time to build a conversion script, perhaps as part of
We are ok that the resulting ftl may need hand tweaking beyond what a tool can do, because ftl is more expressive than gettext. We just seek to automate as much of the work as possible, so we can move existing translations out of .po files (which in our case are quite numerous) and into .ftl format where they can be improved on, and eventually instrumented thru Pontoon.
I confess I don’t really understand the separation of concerns between the Fluent sub-projects. I don’t know what moving parts are specific to Mozilla project structures vs more general. If
fluent-migrations is one of the former, then we can look at other ways e.g. yacc scripts.
If there’s any interest, as I said we can donate the dev-hours. I would just need some advice on how to get started, e.g which parts of the
fluent-migrations API we should start with in order to have a hello world converter that we can iterate on. Or if there is a better part of the codebase to leverage. I’m not averse to reading loads of code and working with undocumented APIs. But early decisions about where to begin from the veterans will be a big help in making sure I don’t make any false starts (or at least, not too many :-))
Kia kaha from New Zealand.