@████████ Any updates on this feature? Thanks

It looks like they just released it for LF Cloud, so Self-hosted systems should be next.

Did this end up getting implemented in the latest version to use in the new designer.

Yes, the ability to update text elements was included in Forms 11 Update 5.

Is this part of the HTML or the JS.  I can't seem to get the translate element to work in Modern.  

This is what I was using in classic.  

$.getScript("//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit");
function googleTranslateElementInit() {
    new google.translate.TranslateElement({pageLanguage: 'en'}, 'google_translate_element');

You are still not able to use that method. The method that Zachary was referring to is that there were new interfaces within the LFForms object to change the field labels, which can in turn be used to change a field label to a different language. I haven't seen any examples of code on how to accomplish this yet though.

Also, jquery is not available in the new form designer, I would recommend using the JS fetch method directly to interact with Google's API. The general flow I designed was

1. Finalize form design
2. Establish the languages I want to support
   1. Include these languages in a radio/dropdown on the form
3. Run the form and fields through the Google translate API to the desired languages, including english
4. save these values to the form JS in the form of a JSON object that allows you to simply map the fields and ids back to their various settings 
   {
      "en": {

           39: {
               "label": "Contract Upload",
               "subtext": "",
               "tooltip": "",
               "buttonLabel": "Choose files"
          }

      }
   }
5. disable the translation
6. run code on field change of the language field to parse the saved JSON onto the form field settings
    

A video of the solution that I built was shown in the cloud release video here
https://doc.laserfiche.com/releases/Content/2023.10.htm at the 2:50 mark

We do at some point hope to have more native support for designer defined languages without scripting but we believe this feature filled as a stop gap for those that needed the feature asap. Please do let me know if you need help or if this does not quite meet your needs!

Will this work on Custom HTML as well as fields?

@████████, would it be possible to not even use the Google Translate API now? For example, if you had a radio button where each option was a Language value (English, Spanish, and French). And when the radio button value is changed, update the field labels accordingly using the changFieldSettings? Granted you would have to manually set each value instead of using the Google API to do it. If yes, are you able to share some code of how that would work?

Also, if you are able to share the code for using the Google Translate API that is shown in the video, that would be great. The video doesn't show the full code because of the width of the screen and it stops short of scrolling to the bottom.

Yes you could definitely build the JSON yourself instead of relying on Google's translations to generate the JSON. It is just a matter of making sure you format it properly so you can easily parse it.

Let me locate the code and I will email it to you.

can you send it to me too please?

Zachary, could you send me the code as well? The youtube video has an old link to the forms that does not work.

The link from the YouTube video works when I try it. Are you getting an error?