View that lists localized terms

[laryn]

I've run into a case where a view that displays localized taxonomy terms is showing them in the source language always. There is no option (for example) for adding the term name in localized format.

We can probably pluck out a handler or two from i18nviews and add it to the i18n_taxonomy module.

[laryn]

Possibilities:

• Term name: https://github.com/laryn/i18nviews/blob/1.x-3.x/includes/i18nviews_handler_field_taxonomy_term_name.inc
• Term description: https://github.com/laryn/i18nviews/blob/1.x-3.x/includes/i18nviews_handler_field_taxonomy_term_description.inc

[indigoxela]

Hey, @laryn you already gave porting a try.

How far did you get? Does i18nviews help with the exposed forms?

[laryn]

@indigoxela Yes, I have enabled the port on this dev site and both issues are resolved. I have linked my best guess as to which handlers are needed for each issue.

[indigoxela]

Hm, only the two linked files won't do the trick, it needs a lot more. Probably most files from the includes directory and then all autoload info and views_data_alter stuff.

This makes me think that this module might better stay its own project, i18n is already a hard to tame monster.

[indigoxela]

A quick hint re https://github.com/laryn/i18nviews/blob/343ea42c71bbeb2ea3db643ec9561a1b33c875ad/i18nviews.module#L30

That's $plugin = config_get('views.settings', 'views_localization_plugin');

[indigoxela]

Hm... there seems to be a bug in i18nviews filters. The filter shows localized terms, but doesn't filter correctly for them - nodes using a language neutral localized term do not appear in the result list. Could be my sloppy quick setup, though.

It feels a bit odd, to discuss this in the i18n queue, when I resist to include that module in the i18n project. :smile:

[laryn]

This makes me think that this module might better stay its own project, i18n is already a hard to tame monster.

Since views is in core, my thought was it should not require a separate download. If it can't easily be integrated directly into i18n how about bundling it as a submodule in i18n?

[laryn]

Hm... there seems to be a bug in i18nviews filters. The filter shows localized terms, but doesn't filter correctly for them - nodes using a language neutral localized term do not appear in the result list. Could be my sloppy quick setup, though.

Easily there could be bugs. This is a very quick port and I just tested for my immediate need so far...

[indigoxela]

If it can't easily be integrated directly into i18n how about bundling it as a submodule in i18n?

Not as long as I'm the only active maintainer. I spent way too many hours with i18n, and that's still ongoing. Why should I increase my pain. :grin:

[laryn]

Fair enough!

[indigoxela]

As this issue is mostly about the different i18nviews module, and there hasn't been activity for months, I'm closing this one (issue queue cleanup).

[indigoxela]

Reopening this, as it now turned out where the problem is: we missed this i18n issue and commit, which got merged in 2017.