Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding gettext #243

Open
Waitak opened this issue Jan 8, 2021 · 2 comments
Open

Adding gettext #243

Waitak opened this issue Jan 8, 2021 · 2 comments

Comments

@Waitak
Copy link

Waitak commented Jan 8, 2021

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.

@nicksnyder
Copy link
Owner

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.

@KuSh
Copy link
Contributor

KuSh commented Oct 15, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants