Opened 5 years ago

Last modified 5 years ago

#4716 new task (blessed)

Improve translations for gutenberg mobile

Reported by: dekervit's profile dekervit Owned by:
Milestone: Priority: normal
Component: Translate Site & Plugins Keywords:


Gutenberg mobile, the native version of Gutenberg, is currently part of the gutenberg repository even though it has a custom build and custom dependencies (that currently live outside in its own repository but are meant to move into gutenberg in the near future)

The problem we currently have is that the command run to generate the POT file for gutenberg, wp i18n make-pot, takes the plugin file as input. As a result, strings from the *.native.js files that mobile uses are not getting uploaded to the gutenberg GlotPress project (because they’re not a part of the build for the web side).

We'd like to figure out a solution to get the strings from the *.native.js files uploaded to GlotPress. We see two options at this point

(a) Gutenberg mobile gets its own GlotPress project and starts sending off its own translations to GlotPress independently of gutenberg (excluding anything that will get sent off by gutenberg to avoid duplication)

(b) We update the GlotPress script that runs for gutenberg to take a custom POT file that includes both the web and native strings (Replacing wp i18n make-pot with wp glotpress import-originals custom.pot).

We would prefer to go with (b) as having our own GlotPress project would add overhead in our deployment process and gets us further from our goal of merging the two repositories.

Change History (3)

This ticket was mentioned in Slack in #core-editor by tug. View the logs.

5 years ago

#2 @swissspidy
5 years ago

  • Component changed from General to Translate Site & Plugins

As mentioned in the Slack discussion at my opinion is that creating a separate GP project is the only viable option.

#3 @ocean90
5 years ago

Making exceptions for plugins like done in the past is no longer an option due to maintenance burden. So the only available option for this is a separate project.

gets us further from our goal of merging the two repositories.

The files still can be in the same repository. A separate import task will just handle what ever needs to be parsed/imported.

Noting that Matt Chowning has already asked me the same in a DM and he got the same answer.

Note: See TracTickets for help on using tickets.