split off a metadata language file for "forms"

[we-sell-bags]

Currently there is no way to have a standard form , then to have a language file for that form.

When building forms you can add questions and other items, but this does not allow a standard set of language files to be built to use with the form. this would allow the same form to be translated correctly, using corporate terms that are standardized for each language.

it would be useful to have a form & revision counter , when the form is updated it could flag any language files that are out of sync with the form when drafted.

[btry]

Hi

The version 2.12.0 contains a feature to translate a form in many languages, and making forms maintenance easier. There are still 3 weeks for the community to test this version and feedback bugs. Please, test the feature and the general behavior of this version.

A screencast of the feature is available here: https://glpi-project.org/formcreator-2-12-0-beta-translatable-forms/

The design adopted for the translations makes it is not necessary to maintain a revision counter. The form conceptor just need to check if strings are submitted for translation after an update.

[we-sell-bags]

sorry that won't work.... auto translation is rubbish when going from English to Chinese or visa versa. it also does not correctly translate or provision for company wide terms, where a department or procedure MUST remain in a specific language or a passage be translated in a specific way.

[btry]

The next version of Formcreator does not provides auto translation. This is a task for a human. If you watched the video you can see that the user translates himself all strings of the form.