1 Reply Latest reply on Oct 30, 2018 7:03 PM by Sanford Whiteman

    One Form to Rule All Languages

    Joseph Moran
    Joseph Moran Oct 30, 2018 1:35 PM

      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?

      • 111 Views
      • Categories: Marketing: Marketing Operations (MOPS) & Data, Marketing: Lessons Learned (Practitioners and CMOs), Solutions, Marketing, Products , Web Personalization
      • Tags:
        • Re: One Form to Rule All Languages
          Sanford Whiteman
          Sanford Whiteman Oct 30, 2018 7:03 PM (in response to Joseph Moran) 
          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.

          1 of 1 people found this helpful