Choice of translation glossary

[discobot]

Give back to the authors the priority on the slack teams for the translations of their plugin.
In some local teams, a small self-proclaimed group decides for everyone, even if the author does not agree on a term, he can not oppose it without leaving the WordPress repository.

---

Read-only archive: Issues · ClassicPress/ClassicPress · GitHub

Author: Mat Meis

Vote count: 4

Status: open

Tags:

• difficulty-moderate
• request-modify-feature

---

Comments

This is something that we discussed on polyglots.
The consistency is very important and we cannot have for a button like Edit 8 different localization in the same language to avoid confusions.
In Italian as example happen a lot that for the same term we have 14 different localizations, for that reason I written that tool GitHub - Mte90/BulkRejectGP: Bulk reject of approved string on GlotPress with Firefox automation

Also is important that the community check the localization to check if follows the guidelines like for bad words. Anyway you can integrate a local po file in your plugin as premium plugins do.

~ posted by Daniele Scasciafratte

I think that @Mat Meis means exactly that.

If the plugin author wants to use a certain word for his/her plugin, then shouldn’t that be possible?

~ posted by Pieter Bos

In WordPress there is the rule confirmed in many case to improve the consistency, for every singleo locale (are like 90).
There are terms that can be translated in different ways in every language and track them is quite impossible.
Take as example Toggle, there is a ticket (that I cannot find) to find other terms to use because in english has different meaning and in many languages there is no alternative.
This happen also on Collapse.
I think that this is something we can discuss on i18n with termcase, also to see if this can create conflicts with the same plugin/theme with different localization between WordPress/ClassicPress.

~ posted by Daniele Scasciafratte