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

Reinvestigate how we compile translation files #1535

Open
benlk opened this issue Sep 11, 2018 · 1 comment
Open

Reinvestigate how we compile translation files #1535

benlk opened this issue Sep 11, 2018 · 1 comment

Comments

@benlk
Copy link
Collaborator

benlk commented Sep 11, 2018

grunt pot po2mo shell:msgmerge should generate translation files, compile them into mo files, and merge those with msgmerge:

Merges two Uniforum style .po files together. The def.po file is an
existing PO file with translations which will be taken over to the newly
created file as long as they still match; comments will be preserved,
but extracted comments and file positions will be discarded. The ref.pot
file is the last created PO file with up-to-date source references but
old translations, or a PO Template file (generally created by xgettext);
any translations or comments in the file will be discarded, however dot
comments and file positions will be preserved. Where an exact match
cannot be found, fuzzy matching is used to produce better results.

But nowish, we're running into MicheleBertoli/grunt-po2mo#8

So ... yeah.

grunt pot can be rewritten to use https://developer.wordpress.org/cli/commands/i18n/, but what about po2mo?

@benlk benlk added this to the 0.6 - Performance & SEO milestone Sep 11, 2018
@benlk
Copy link
Collaborator Author

benlk commented Sep 14, 2018

@benlk benlk mentioned this issue Oct 31, 2018
8 tasks
@benlk benlk removed this from the 0.6 - Gutenberg, SEO, Performance milestone Nov 8, 2018
@benlk benlk mentioned this issue Dec 7, 2018
18 tasks
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

1 participant