Can we fix translation related tags

Question

I was about to edit the localization tag. Then I realized that there is no internationalization tag. However, there is a wrongly created l18n (should be l10n) tag as a tag synonym for localization, even though the correct synonym l10n exists separately. Also, i18n is set as another synonym for localization, although internationalization is a separate topic.

There is also a translation tag which essentially has questions that are either related to localization or internationalization. Not to mention, there are separate tags for textdomain, language, po and mo, phew!

Finally, there is a separate multi-language tag, which is rightly separate from the other tags I've mentioned above, although most of the questions there are not related to multi-language, but related to either internationalization or localization (i.e. translation).

I don't have the privileges to fix all that, and if I edit / alter all of these tag wiki, those who will approve it may become confused without proper context. That's the reason why I'm writing this question.

Now my question is: what should be the correct combination of tags related to translation?

My suggestion is, we need to have only two from all the above:

1. translation - all the others will be synonym to this.

2. multi-language - as it is a separate topic all together.

OR,

we can have 4:

1. translation - everything generally related to translation. With language, x (yes, it's already there) and textdomain synonyms.

2. internationalization - with i18n synonym.

3. localization - with l10n, po, mo synonyms.

4. multi-language

Please suggest.

Update:

For ease of discussion, I'm providing the number of posts we have (at the time of writing this) against the available tags:

• localization (with synonym i18n and l18n) - 266

• l10n - 21

• translation (with synonym x) - 344

• textdomain - 41

• language - 140

• po - 30

• mo - 21

• multi-language - 267

Answer 1

Less is better. I like your first idea with just two tags. Most are not sure what tag to use, no matter what we try. Having less tags makes that easier.

I can do that, but it'll be quite some work that needs to be handled very carefully.

And more important, it needs the support of the active community members, so please raise your concerns now, or show your support!

Answer 2

I like the idea of two tags only, but I would opt for textdomain in stead of translation.

The reason for this is that more serious developers, whom I see as our core users, will use textdomain to describe the development issue they are addressing. translation is a colloquial synonym, but not the correct WP term.

Answer 3

For me, out of the list of terms given, the ones that should not be there are translation, language, l10n, po and mo. translation is the process of producing text in different language which wordpress has nothing to do with, the rest are just not meaningful.

textdomain is a technical term used as part of localization so it should stay, localization obviously should stay, and multi language (should be multi locale but lol no one will use or understand it) is a way to set wordpress for multiple localizations.

BTW i18n for me is not a useful term, in many countries you need to handle two or more languages just for the country itself, calling it a i18n is a little be of stretch. So maybe i18n should be a synonym of localization.

.. and out of https://www.w3.org/International/questions/qa-i18n

Internationalization is the design and development of a product, application or document content that enables easy localization for target audiences that vary in culture, region, or language.