Forms: Best way to translate and save to repository

asked on March 25, 2024 • Show version history

I've seen quite a few great posts on translating a form using Google Translate. Has anyone saved a 'translated' form to the repository?

EDIT: Since I have this out here, I'm going to add a few questions to this post:

How can we translate customHTML fields?
Will the characters change to the input fields if say we change the translation to Russian? Or will users See and read it in Russian but then have to respond in English characters?
What about existing values in a field? If a previous step has set a value in a field, when it is translated, will the fields input value also get translated? Is there a method to accomplish this?

0 0

replied on March 25, 2024 • Show version history

I haven't done it, but I have played with multiple different options, and have a reasonable understanding of how they function.

If you're using the Google Translate plug-in on the Classic Designer method - then I don't think you can, because it does it on the fly, modifying the DOM of the page, and isn't really based on anything that is saved beyond the submission of the form.

If you're using the options that have been published on LFAnswers for the New Designer following the Forms 11 Update 5 (11.0.2311) release, that uses a radio button to select the language and the LFForm interface to apply the changes to all the fields and labels - as long as the script is written so that it runs on form load and not just on the language selection changing, you should be able to apply it to both the in-progress form and the read-only/archival version of the form.

3 0

replied on March 26, 2024 • Show version history

For anyone else's reference, here is the post where Zac and Blake spell out the steps for using Google Translate API with modern designer. In case you haven't seen it already...

FYI, a few answers to my questions are now at the above link.

2 0

Question

Question

Forms: Best way to translate and save to repository

Replies

Sign in to reply to this post.