You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 12, 2024. It is now read-only.
It would be useful to work on translations and seeing them in Foodsoft right away.
This is possible with the localeapp integration, but perhaps Crowdin's in-context feature is more friendly. I'd like to setup a Foodsoft master instance (with just a demo foodcoop) that integrates with it, so translators can more easily work with it.
The text was updated successfully, but these errors were encountered:
It seams like almost every changes to the language files in the past were commited directly to the Foodsofts's repository. What do you think: Is a translation instance still useful?
Now and then someone comes by Crowdin and starts a new language, rarely completing it. It lowers the barrier, but as I think it takes development time, we'd better remove it. I guess we'd better make an issue in the Foodsoft repo to remove all references to Crowdin, and explain how to do translation/i18n these days.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be useful to work on translations and seeing them in Foodsoft right away.
This is possible with the localeapp integration, but perhaps Crowdin's in-context feature is more friendly. I'd like to setup a Foodsoft master instance (with just a demo foodcoop) that integrates with it, so translators can more easily work with it.
The text was updated successfully, but these errors were encountered: