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

[Szabolcs_Horvat]

Hi Sanford,

Is it possible to localize the default error messages as well?

Thanks,

Szabolcs

[Troy_Larson]

Hey @SanfordWhiteman - 

I realize this is a bit of an old post, but wanted to shoot you a comment in an off chance you may be able to help my coworker and I out. 

We are having difficulties implementing your initial 1 form, many languages solution. Was wondering if you could spare a few minutes to help get us on the right track. What we are primarily stuck on is the ability to:

1. Store the json key value pairs on the actual form itself
2. If there have been any changes to the Form API
3. Ability to embed on CMS tools such as Wordpress with the JS functions wrapped in a script tag
4. Understanding the media query to talk to JS file and JSON values

Thanks for your help and hopefully we hear from you soon

[SanfordWhiteman]

It's possible that there's been a (very) recent bug introduced in the forms library w/r/t JS in a Rich Text Area. I'm looking into that with a client today.

Don't understand what you mean about the media query...

[tmoi]

Hi Sanford! I have a very interesting issue with this method. I'm testing it on a Progressing Profiling-enabled form and the label translation works flawlessly if I view this form in incognito mode and all the progpro fields appear. There is a catch though, the progpro fields have to be defined in the translation <div> first, then should come the rest, otherwise the progpro fields are not translated at all if they are defined at the bottom of the <div>.

The second part of this anomaly is when I view the same form normally in a browser where my munchkin cookie is already stored and the progpro fields won't appear as all of them are filled, then the script doesn't translate my default fields. The order in the <div> is the following now:

1. Industry (progpro) - Not appearing
2. Phone (progpro) - Not appearing
3. FirstName - No translation
4. LastName - No translation
5. ... - No translation

--

Now if I reorder the arrays in the <div> and move the progpro set slightly below, it only translates the progpro fields and the ones above, nothing below. Now the order:

1. FirstName - Gets translated
2. LastName - Gets translated
3. Industry (progpro) - Gets translated
4. Phone (progpro) - Gets translated
5. Company - No translation
6. ...  - No translation

I mostly wish to use this function on Marketo LPs, and the progpro fields are quite important in this case for us. Do you know perhaps how should I overcome the above challenge? Thanks a lot!