SOLVED

One Form to Rule All Languages

Go to solution
Joseph_Moran2
Level 2

One Form to Rule All Languages

Sanford Whiteman

We are working through this approach for translations, https://blog.teknkl.com/smoothing-embedded-marketo-form-loads/ . Three questions came up today that I was wondering if you could shed some light on.

​How do you manage/translate the "This field is required" message and other validation error messages?

​How do you handle the translation of drop downs, checkboxes (multi-selects)?

Related to question 2, ​is it possible for us to translate the stored values or is this method just for front end translations?

1 ACCEPTED SOLUTION

Accepted Solutions
SanfordWhiteman
Level 10 - Community Moderator

Re: One Form to Rule All Languages

How do you manage/translate the "This field is required" message and other validation error messages?

That's the ValidationMessage property of the field in the descriptor.

How do you handle the translation of drop downs, checkboxes (multi-selects)?

Similarly, those will be in the PicklistValues property.

Related to question 2, is it possible for us to translate the stored values or is this method just for front end translations?

You can translate just the value or the label, too. All up to you.

View solution in original post

1 REPLY 1
SanfordWhiteman
Level 10 - Community Moderator

Re: One Form to Rule All Languages

How do you manage/translate the "This field is required" message and other validation error messages?

That's the ValidationMessage property of the field in the descriptor.

How do you handle the translation of drop downs, checkboxes (multi-selects)?

Similarly, those will be in the PicklistValues property.

Related to question 2, is it possible for us to translate the stored values or is this method just for front end translations?

You can translate just the value or the label, too. All up to you.

View solution in original post