Marketo Dynamic Form Field Labels - Multiple Languages

[Anonymous]

We're fairly new to Marketo and just about to implement forms across our website.

Is there a way to dynamically change form field labels i.e. First Name to Naam if country = Netherlands ?

Any help would be much appreciated!

[Anonymous]

Unfortunately you need separate forms if you want to do multiple languages.

[SanfordWhiteman]

Huh?  Not at all.  You only need one form.  I've outlined this recipe a few times recently.

See Re: How do I update the submit button and error message to reflect local language (i.e French)

And demo code at:

• http://codepen.io/figureone/pen/mJWgjE?editors=001&lang=en-US (translates the LastName's label and validation text for en-US)
• http://codepen.io/figureone/pen/mJWgjE?editors=001&lang=fr-FR (translates the FirstName's label, placeholder, and submit button text for fr-FR)

[Jeff_Boakye_Yia]

Hi Sanford, this is very handy! Thanks for this! I've been able to translate mine entire form except for the "Please Wait" button text, that shows after hitting on the submit button. Please any tips how I will be able to change that as well in the script? Thanks!

[SanfordWhiteman]

Set the Waiting Label to completely empty first:

Then add a submitProgress property to your data block:

{
   "en-US" : {
      "LastName" : {
         "label" : "Surname",
         "validation" : "Make sure that's your real last name.",
         "submit" : "Go",
         "submitProgress" : "Going..."
      }
   },
   "fr-FR" : {
      "FirstName" : {
         "label" : "Prénom",
         "placeholder" : "Victor",
         "submit" : "Envoi",
         "submitProgress" : "Envoi en cours..."
      }
   },
   "jp-JP" : {
      "FirstName" : {
         "submit" : "アンサブスクライブ"
      }
   }
}‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

And the latest code from https://codepen.io/figureone/pen/mJWgjE

[Jeff_Boakye_Yia]

Awesome! It worked! You're simply the best!

[Robb_Barrett]

Can you walk me though this code at some point?  I'd like to understand it in better detail as it's something I could use.

[SanfordWhiteman]

Sure, no problem.  Hit me at sandy@figureone.com

[Anonymous]

Thank you for your help Sanford! I think we want to start with default functionality of Marketo, but it is good to know that we have an option for the future. I will keep this on file.

[SanfordWhiteman]

Browyn, one more thing while we're on the topic: as a veteran of some major after-the-fact localization projects, I want to stress that you should localize from the beginning if you can. That is, even if your only language is English to start, store English in a translation/dictionary file rather than hard-coding it. You will thank yourself later. Frankly I can't imagine managing even two otherwise identical forms... every time you want to change the length of a field or change custom CSS... *shudder*.

[Anonymous]

Hi Sanford,

You make a very valid point here. We are going to investigate into this a little further -- to your point, we don't want to overcomplicate things down the track when we need to update fields/CSS.

Thank you again for your valuable insight - much appreciate!

Bronwyn

[SanfordWhiteman]

Well, I consider Marketo's Forms 2.0 API and basic HTML/JS to very much be default functionality... if you couldn't extend Mkto forms I wouldn't use them at all. But that's me I guess.

[SanfordWhiteman]

... also, the language-switching logic is part of our FormsPlus library (in progress) so all you'll have to do is include FormsPlus in your page (plus your translations, of course!).

[Anonymous]

Yea, of course, there's usually a code-based solution The user mentioned that they were new to Marketo so I was presuming we were using default functionality, which as you point out, may not be the case.

[Anonymous]

Thank you so much for your help!

[Anonymous]

FYI. I moved your post to Products and Support​

[Anonymous]

OK thank you! Will be sure to do the same for future product related posts!