Translate the form experience
Open Languages in MegaForm to manage the languages available to the form interface. Translate labels, help text, validation messages, button text and confirmation content. Review option labels and widget text too.
Keep field keys and stored option values stable across languages. A translated label should not create a different SQL column mapping or workflow branch.
Coordinate with Umbraco cultures
Umbraco content variants control the page's culture and published content. MegaForm's form translations are a separate configuration. Test the selected form on each published language variant and check that the intended language is used rather than assuming page translations automatically translate a form.
For a language-specific experience, editors may select a separate published form in each culture variant of a Form Picker property. Decide whether those forms should keep separate entry sets or share a single operational process.
Review before release
Submit a fictional entry from each language. Check required-field errors, dates, decimal separators, email content, choice labels and the final confirmation. Verify the fallback language when a translation is missing.
See Form Picker & Razor for the content property and After-submit confirmation for messages and notifications.