Spent 40 minutes on reading discussions about difficulties with translating Mailchimp fields, but yet it doesn't work on Drupal 8.
Well, I also checked out all README files in the module(s) distribution and found absolutely no information about translating, localization or something.

We have a bilingual website: English and Italian. We don't use some i18n module - just core things. And I don't see any possibilities to translate those fields - neither on Form translation nor in User interface translation.

Using 1.3.0 version
Drupal 8.3.7

CommentFileSizeAuthor
#4 2903123-4_signupblock-formlabel-translation.patch534 bytesytsurk
#3 2903123-3_signupblock-formlabel-translation.patch531 bytesytsurk

Comments

OnkelTem created an issue. See original summary.

OnkelTem’s picture

OnkelTem commented
Issue summary: View changes
ytsurk’s picture

ytsurk
Location Switzerland
commented
Status: Active » Needs review
StatusFileSize
new 2903123-3_signupblock-formlabel-translation.patch531 bytes

The issue #2667782: How do I translate the subscription block? popped up again.

I don't know what's the purpose of the is_string check, but it makes no sense to translate an @-var ...

ytsurk’s picture

ytsurk
Location Switzerland
commented
StatusFileSize
new 2903123-4_signupblock-formlabel-translation.patch534 bytes

Sorry .. the patch was wrong ..

  • ruscoe committed dda064e on 8.x-1.x authored by ytsurk 
    Issue #2903123 by ytsurk, OnkelTem: Mergefields can not be translated:...
ruscoe’s picture

ruscoe commented
Status: Needs review » Fixed

Interesting.

t('@mergevar', array('@mergevar' => $mergevar->name)) has been in the code for years and I suspect it was intended to force $mergevar->name to always be a string.

However, I can't think of a situation where $mergevar->name would be anything other than a string or an empty value (unlikely) and your patch will handle both those situations perfectly well.

Committed. Thanks!

Status: Fixed » Closed (fixed)

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