Babblebird, translations that live in your repository
I read the Fluent files in your GitHub repository and send the translations back as commits. That’s the whole setup.
Translators get a field for every plural form, with { $count } kept where it belongs and the screen it shows on.
Add me to a repository → Luft is here already: 5,140 strings in 36 languages →Translating into Croatian? You get the three forms Croatian has, not the two English needs, and a preview with real numbers.
Maintainers see how far each language has come and what’s still missing. This is Luft, right now.
Luft
Loading
Your repository only gets the lines that changed, in a commit that credits everyone who wrote them.
How a string gets around
-
A push changes the English. Only the files that changed are read again.
-
Translators see it in their language, with what changed marked for review.
-
Their work goes back as one small commit, merged once your checks pass.
Let everyone use what you made
Add Babblebird to a repository and the people who speak your users’ languages can start today. Their work comes back to you as commits, with their names on it.