Weblate translation form xml file

[kmikkels]

I have now used two days translating the form_ca.xml.
And a long way to go.
For absolutely no use.
The Danish users who needs canadian census, will understand, and probaly want to have the original wording.
And if anyone already uses Canadian Census, I will have broken their database with new attributes.
I love the weblate approach, but will do traditional po editing for forms, if I should suddenly feel an urgent need to translate the xml (Not likely).
Do I sound frustrated? Yes.
I will stop my translation via weblate, until the forms xml files are removed from this.

[comeng]

Not sure why anyone would want to translate the xml forms for the
following reasons not in any particular order

1. Surely it is better to leave in the language of the original
   enumerator so use the current language version. They are really only
   samples of what you might do or how to use the Forms Addon
2. Am I alone in tinkering with the xml files so they are all custom
   anyway. I do not have any of the standard Forms (.xml) on my system
3. Would suggest that most people would follow the pattern that I do but
   stand to be corrected.
   Most of my Census data is England (100’s), Wales (10’s), Scotland(1’s)
   and therefore the language is not an issue I have some US census but a
   relatively tiny number measured in the 10’s not hundreds and a few
   Canadian measured in single digits.
   phil

[emyoulation]

Perhaps it would help the various forms should have unique locale option?

Or perhaps, force a lower priority on Form strings.

There are also areas where Human-based translation seems like overkill. Form labels are an example. Maybe a there could a option to take a Template.pot and pass it through a translate LLM to make a rough lookup dialog?

As another example, consider the Configuration options — the labels, tooltips and menu items. While I love the flexible Configuration options of some addons, the most flexible addons (e.g., CardView, FTV) use very unique labels and menu items. When there are hundreds of options, most will never be touched … except by a tiny number of users. And often, there are many strings that could be made to use existing translated strings.