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

Added makefile for maintaining translations as PO files #157

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

petterreinholdtsen
Copy link

This makefile allow the web2py translations to be maintained as
gettext po files to make easier for translators.

These rules assume the en-us.py file is generated from source and
contain every translatable string in the application. It further
ignore the default.py and plural-*.py files, because I do not know
how to best handle them as po files.

Too migrate once from py to po files, run this:
make migrate oztree.pot pofiles clean

To generate py files for use when building, run
make

To see translation status, run
make stats

You need a version of Translation Toolkit where
translate/translate#3254 is fixed, for
example the version from Debian.

Related to issue #138.

This makefile allow the web2py translations to be maintained as
gettext po files to make easier for translators.

These rules assume the en-us.py file is generated from source and
contain every translatable string in the application.  It further
ignore the default.py and plural-*.py files, because I do not know
how to best handle them as po files.

Too migrate once from py to po files, run this:
  make migrate oztree.pot pofiles clean

To generate py files for use when building, run
  make

To see translation status, run
  make stats

You need a version of Translation Toolkit where
translate/translate#3254 is fixed, for
example the version from Debian.

Related to issue OneZoom#138.
@hyanwong
Copy link
Member

hyanwong commented Apr 1, 2019

This is great, thanks @petterreinholdtsen and sorry to have only just spotted the PR. I'll get round to this in a week or so.

@petterreinholdtsen
Copy link
Author

petterreinholdtsen commented Apr 2, 2019 via email

@petterreinholdtsen
Copy link
Author

Did it work out?

@petterreinholdtsen
Copy link
Author

I guess from the feedback that there is no wish for maintaining translations as PO files. Do you have other preferences for handling translations, or do you not want to spend time on translations?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
outsource Translations tasks related to language support Version 3.6 nice to have Publication revision and sponsorship renewals
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants