[META] Fix unsafe core translatable strings

Created on 15 July 2013, almost 12 years ago
Updated 24 April 2025, about 17 hours ago

Updated from #5

Problem/Motivation

According to the locale_string_is_safe function, used by translation interface, manual import and automated imports via Localization update, some HTML tags are not allowed in translated strings. This results in impossible to translate strings and also in multiple import errors.

Proposed resolution

Search and rewrite faulty strings.

Remaining tasks

  • Update the detection script to provide it documentation and make it reusable for contrib
  • Open one follow-up issue per module or per file to fix it.

Related Issues

Sub-Issues

📌 Task
Status

Postponed: needs info

Version

11.0 🔥

Component

user interface text

Created by

🇫🇷France duaelfr Montpellier, France

Live updates comments and jobs are added and updated live.
  • String freeze

    It affects the translatable strings and it should be committed before the string freeze milestone of the release cycle.

  • D8MI

    (Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.

  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇺🇸United States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024