In the transliteration processor, we currently just use the default language as the language of the transliterated text. This will of course be correct for unilingual sites, but is rather arbitrary for multilingual ones.
Instead we should:
- at index time, use the item's language;
- and at search time, maybe check if the query specifies a definite language, and only fall back to the site default as the last option.

Issue fork search_api-2891393

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

drunken monkey created an issue. See original summary.

drunken monkey’s picture

Status: Active » Needs review
Issue tags: +Vienna2025

  • drunken monkey committed e1680eed on 8.x-1.x
    [#2891393] fix: Fixed wrong base language used for transliteration on...
drunken monkey’s picture

Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

joseph.olstad’s picture

Can we please get this into a tagged release ASAP? ex: 8.x-1.40

There's other modules that require search_api tagged releases and they squeel on dev releases.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.