The confirmation message and the submit button of the subscribe block is not translateable.

Issue fork mailchimp-2932189

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:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ytsurk created an issue. See original summary.

ytsurk’s picture

Anybody’s picture

Well I think it would be cleaner to solve this via configuration translation, but the patch can be seen as hotfix....

samuel.mortenson’s picture

Status: Needs review » Needs work

@Anybody I agree - some values that come directly from Mailchimp may need wrapped in t(), but values from config entities should be translatable. What do we need to do to enable that in the module?

ytsurk’s picture

It needs a correct configuration schema, according to https://www.drupal.org/docs/8/multilingual/translating-configuration, i have not reviewed the one in this module so far.

This then probably will need an update hook for existing installations ... so good testing is needed

mvonfrie’s picture

There are some other UI texts which need to be translated, e. g. the #2968016: Add GDPR checkbox for opt-in consent consent message. Please make all texts translatable!

We are using this module in a site which currently is translated to English, German and Czech will follow within the next months. As many of the users of that site don't speak English we need to translate everything. Thanks.

joco_sp’s picture

Category: Feature request » Bug report
Status: Needs work » Needs review
FileSize
2.53 KB

I changed the category to Bug report, becasue if you have a multilingual site you can't translate those strings.

I updated the patch, so it should work with the latest dev version of the module. I also found two descriptions on the form without the translation possibilities.

joco_sp’s picture

drupal.ninja03’s picture

I have added more changes for the deprecated t() calls.

gcb’s picture

Assigned: Unassigned » 5adiyah
gcb’s picture

Assigned: 5adiyah » spncr
Shashwat Purav’s picture

Status: Needs review » Needs work

The patch in #9 failed to apply to 8.x-1.x branch.

anoopsingh92’s picture

Hi

Anyone is working on this issue? Because I am not seeing any activity from the last 3 months on that issue. If someone is not working then I request you to please realize it and change it to unassigned.

Thank You

anoopsingh92’s picture

Hello @spncr,

I want to review the provided patches. If I will get any issues with the patches or other things then I will try to provide a clean patch for this.
Thanks

gcb’s picture

Assigned: spncr » Unassigned

Hey @anoopsingh92. @spncr isn't working on this project anymore. I've unassigned this ticket. Any feedback or testing results you have would be welcome.

anoopsingh92’s picture

Assigned: Unassigned » anoopsingh92

Hi @gcb,

Thank you so much for thae change assign value as unassigned. Now i will check this ticket if i will get any issue on this then i will try to fix and give my feedback on this.

I am working on it.

Thanks

anoopsingh92’s picture

Assigned: anoopsingh92 » Unassigned
Status: Needs work » Needs review
FileSize
5.56 KB

Hello,
Please review this patch. I didn't change related to the Coding standards in this patch.
Thanks

xenophyle’s picture

It looks like the changes from the latest patch exist in the current 2.x dev branch. Does anything else need to be done to close this issue?

MegaChriz’s picture

I see that indeed everything in #17 is addressed.

I do however see in the code base that there is more usage of literal strings where I think that translated strings should be used. You could search in the code base for:

  • '#title' => '
  • '#title' => "

Note: on '#description' I did not find anything that should be changed.

Would it be good to address '#title' strings translations here, or is that out of scope?

xenophyle’s picture

@MegaChriz Might as well make translatable strings a new issue.