Add support for multilingual sites

Created on 25 August 2025, 20 days ago

Problem/Motivation

The module currently does not support multilingual sites. The rules detect only original (source) language texts. And views alt_text_report only displays source language alt-texts.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Active

Version

1.0

Component

Code

Created by

🇫🇮Finland sokru

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @sokru
  • 🇺🇸United States swirt Florida

    Thank you for the suggestion. It should be added, however it gets a pretty complicated because not only do you have to load all the published translations of the fields to validate but you also have make the Rules translatable because a rule for looking for text string "Photo of " would need to know what the Spanish variant of that would be and be able to offer feedback about the rule also in Spanish.

    The risk is mitigate a bit by , if the source language validates, likely the alternate language would also validate... but that is mainly an assumption.

  • 🇺🇸United States swirt Florida
  • Merge request !64Resolve #3542896 "I18n support" → (Open) created by sokru
  • 🇫🇮Finland sokru

    AI assisted PR for this feature, I got it working on my machine, but this would require more work to clean-up the code. So considered the current state as POC.

  • Pipeline finished with Success
    19 days ago
    Total: 125s
    #581889
  • 🇺🇸United States swirt Florida

    Wow!! This is amazing! Thank you Sokru for working on this. I will need to try this out. Unfortunately I do not have a project right now that is multi-lingual so I am going to have to get a test site set up to play around with this and make any refinement. I probably can't get to it this week but after that I might.

  • 🇺🇸United States dmundra Eugene, OR

    I can take a shot at reviewing this.

  • 🇺🇸United States swirt Florida

    After going through this with the help of dmundra we noticed that the customizable headings for the error and warning messages are problematic for translations. That feature is of low value so it makes sense to remove that feature and replace it with properly translatable hard coded text. I create the child issue 📌 Remove custom warning and error headings Active to make it so that it does not slow down this PR.

    This is looking really good. and I think will be mergeable once we get the version of the View updated in the config/install so that language appears in both the View columns and filter as well as the CSV version of the report.

  • 🇺🇸United States swirt Florida
  • 🇺🇸United States dmundra Eugene, OR

    Thank you @swirt. Sorry for the delay in my sharing. I used https://www.drupal.org/docs/user_guide/en/language-add.html to setup the second language and then test the changes. I agree that the changes look good and worked for me. Schema issue needs fixing and also tweaking some of the strings to make sure they are going through the t() function so they can be translated (what Steve said)

Production build 0.71.5 2024