Suggestion here would be to use a csv serialisation (from weblate) for translations, en.csv:
location,source,target,id,fuzzy,context,translator_comments,developer_comments
,gypsumForms-G-label,“gazha” (clayey water-saturated layer with high gypsum,,False,,,
,gypsumForms-G-definition,,,False,,,
,gypsumForms-HL-label,hard cemented layer or layers of gypsum (less than 10 cm thick),,False,,,
,gypsumForms-HL-definition,,,False,,,
What would be the most optimal way to add label-definition for codelists in alternative languages?
Suggested is to add extra columns to the csv for alternate languages, however it is probably better to add dedicated translation files, per language
Maybe we can even adopt a translation format, then these files can be managed in the typical translation tools:
Suggestion here would be to use a csv serialisation (from weblate) for translations,
en.csv: