Global translation for all plugins and themes, 5-8 thousand words

[alexvorn2]

The idea is to create a very big list of phrases in English that will be used for translation in all plugins and themes for like 5-8 thousand phrases and the community will translate to their language.

So in future when someone creates a new plugin or a theme (or can update existing theme or plugin), the translation will be ready from this list.

So we will eliminate the need for translation for every theme or plugin, and most themes and plugins will be translation ready in all languages.

What do you think?

[tobifjellner]

A suggestion would be to use _x() in a thoughtful way, to distinguish phrases that otherwise would be ambiguous, say:
Post (noun)
Post (verb)

[ocean90]

Closing as invalid since this isn't the appropriate place to discuss things like this. Feel free to start the discussion on ​https://make.wordpress.org/polyglots/.

[alexvorn2]

Replying to ocean90:

Closing as invalid since this isn't the appropriate place to discuss things like this. Feel free to start the discussion on ​https://make.wordpress.org/polyglots/.

Can you please add close tag instead of closing my ticket so fast, why you do this?

Why I need to write there (​https://make.wordpress.org/polyglots/)?
That page is for people that are interested into translation, but I am interested into adding new features for non-translation people that will have opportunity to have a plugin or a theme translated easily, I am not interested into translating directly, from English to other language..., I am interested into making translation less painful.

This ticket is for developers and core members, the idea can be only implemented here. I imagine that if I will go to that page - someone will say go here to meta trac and write you idea there. Why here is not the place to have my ticket?

[alexvorn2]

I am reopening because I thought my idea will get positive attention and not ignoring and closing the ticket. That's not nice.

[ocean90]

Can you please add close tag instead of closing my ticket so fast, why you do this?

As mentioned above, you want to start a discussion and Trac is a tool to track bugs/issues with the current system. As the maintainer of this component I took the right to close it accordingly.

That page is for people that are interested into translation, but I am interested into adding new features for non-translation people that will have opportunity to have a plugin or a theme translated easily

That's still a decision which has to be made by the Polyglots team since at the end of the day those are the people who'd have to translate your list of translations. Also this site is open to everyone.

I can ensure you that your idea isn't an easy task because we already tried this, see ​https://github.com/GlotPress/GlotPress-WP/issues/337 for background. Re-adding something similar is currently not on the roadmap of both teams, GlotPress (including Meta) and Polyglots.

But, we're looking into adding a proper translation memory system to GlotPress and thus translate.w.org which would not just include a limited list of words but rather "all" strings with a way to retrieve similar segments too.

[SergeyBiryukov]

Replying to alexvorn2:

Why I need to write there (​https://make.wordpress.org/polyglots/)?

Because plugin and theme translations are ​managed by the Polyglots team, not by developers or Core team, and that blog is the right place to discuss ideas and get feedback from the translators community. Trac tickets are for actual implementation details.

As noted above, cross-project string matching has been attempted before. It's now disabled, as there are lot of instances where the same strings have different context is different projects, and it resulted in many incorreсt propagations, see #1411 and #1703.

We'll try another approach with translation memory in the future, it's on the ​GlotPress roadmap.

[SergeyBiryukov]

Also previously suggested in ​#WP14972.