Change Package name to Multilingual

I think i18n used to use the same as l10n_client (l10n_client did not change packages and this used to not be an issue). I think that maybe i18n needs to change back?

Again? :-) :-(

Really, I don't mind too much the package name. Though I can see some advantage in all the submodules that are mostly depending on each other showing up together, but also in all the 'Multilingual' related features being grouped somehow.

The better schema IMHO would be:
- All language/multilanguage/localization packages sharing some common first name.
- Each big package having some own second name.

Something like 'Multilanguage - Internationalization', 'Multilanguage - Localization', 'Multilanguage - Entities'.

This way all these modules would be listed together, while at the same time, grouped by package.

So.... could we agree on something like this?

I'm totally fine with the proposed scheme.

I have no strong preference about which term use as first one, but core is using the term "Multilingual" everywhere in the UI so perhaps we should stick with that.

Ok,

Renamed the package to "Multilingual - Internationalization"

Please take proper action for other packages.

Do you think single modules, like ET, can share the 'Multilingual' package?

I think yes, single modules should be in a generic 'Multilingual' package. I thought ET would became a bigger collection though.

At the moment it only features an additional submodule implementing the upgrade path from node based translations. I guess we can stick with the 'Multlingual' package until we get more submodules (if we do).

Ok, well, let's get back to l10n_client then and get it changed there.

Committed renaming "Multilanguage" to "Multilingual" for the l10n_client package name. Should be done to l10n_update too.

Done in l10n_update too. The Drupal 6 versions of all these modules says "Multilanguage", so no fix needed there.

Well, for other other multilingual related modules like i18n, translation_table, and language_icons. it currently is:

package = Multilingual - Internationalization

So can this module (again) be changed to be in line with that?

Related issue for l10n_client: #1617814: Change package to Multilingual - Internationalization

@fietserwin:

In #2-#7 we agreed to always have a common "Multilingual" prefix and group single modules into the main "Multilingual" package: translation_table and language_icons are "wrong" here.

Let's put it in the same group as https://www.drupal.org/project/i18n and the majority of multilingual related modules. http://cgit.drupalcode.org/i18n/tree/i18n.info?h=7.x-1.x

The Multilingual - Internationalization group is used by i18n to specifically subgroup itself from the other multilingual modules. If we are to get into that group, then that is subverted.

Right. I was confused by 'Rules translation' putting itself in there. But in that case it makes sense.

Thanks.