"Strings to remove" option missing translation support

Created on 7 December 2015, almost 9 years ago
Updated 31 July 2024, 4 months ago

The strings to remove are human language words. A user either needs to enter words in all their languages or we need to add translation support so that words in other languages may be included as well. That would help with shipping translations for the module too. As in people could translate the words on localize.drupal.org for various languages.

✨ Feature request
Status

Needs work

Version

1.0

Component

I18n stuff

Created by

πŸ‡­πŸ‡ΊHungary GΓ‘bor Hojtsy Hungary

Live updates comments and jobs are added and updated live.
  • 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.

  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

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.

  • Although the patch works I have the following doubt
    now I have this option to translate the string as seen in the image

    but if I enter the Spanish language, for example, it takes me to the normal route as seen in the image, so how would I separate the texts to be eliminated if in the end it joins everything

  • Open in Jenkins β†’ Open on Drupal.org β†’
    Core: 10.1.x + Environment: PHP 8.1 & MySQL 5.7
    last update 12 months ago
    48 pass
  • Hello,

    I encountered an issue with the max length of the translation field Strings to Remove. It allows only 128 characters, which is not enough for most of the suggestions per language ( https://www.drupal.org/node/847370 β†’ ).

    I am proposing a solution which is to change the type of the field from label to text. Tested it and it seems to be ok. Here is a patch for the change.

  • Status changed to Needs work 4 months ago
  • πŸ‡¨πŸ‡­Switzerland berdir Switzerland

    Thanks, should should be done as a merge request now to run current tests. A test for this would be really useful, as this is changing a lot of code, even if it's fairly simple, it's pretty easy to miss one of those cases.

Production build 0.71.5 2024