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
We've really enjoyed this package. One thing that would help us tremendously is if we could share translation files between platforms. What would need to happen to make a gettext unmarhaller that could seamlessly read in a Django-style collection of po/pm translations? As is, we've had to write tools to turn the latter into the former. That works, more or less, but having a single, shared source of translations would be much more desirable.
The text was updated successfully, but these errors were encountered:
What would need to happen to make a gettext unmarhaller that could seamlessly read in a Django-style collection of po/pm translations?
I honestly don't know. There might be a fundamental data model incompatibility (i.e. mo/po files don't provide the necessary information to be able to fulfil the API that go-i18n provides), or it might be as simple as adding an unmarshal method and implementing the logic. If it is as simple as adding a new load/unmarshal method, I would be happy to review a PR.
Why not use already existing tools that exactly do that? Like the translate-toolkit or a higher level tool like weblate which internally use the former to be able to export translations in multiple formats
We've really enjoyed this package. One thing that would help us tremendously is if we could share translation files between platforms. What would need to happen to make a gettext unmarhaller that could seamlessly read in a Django-style collection of po/pm translations? As is, we've had to write tools to turn the latter into the former. That works, more or less, but having a single, shared source of translations would be much more desirable.
The text was updated successfully, but these errors were encountered: