Can resw files handle not having xml elements present in some languages?

@Jay-o-Way @ChenYiLins Whenever we change, add or remove any translation files, I am losing 1 year of my life expectancy because I have to deal with not malding over the merge conflicts with other branches and weblate. Every single language file gets a conflict and I have to manually resolve them.

As it would be nice if I could maintain AutoDarkMode for longer than the next 3 months: Can we directly modify the Strings\en-us\Resources.resw without going through the Visual Studio editor, and only add new strings there? That would reduce the amount of merge conflicts to only one file in a language I can understand, which would make things way more manageable.

Would that cause any issues with Resource loading if strings are missing in some language? The entries for other languages are only copies of the source language anyway.

With the old resw format, this worked completely fine. We had this workflow prior for many years and it caused me to not age at dangerously accelerated rates.

---

[edit] https://docs.weblate.org/en/latest/admin/continuous.html#avoid-merge-conflicts

• Avoiding merge conflicts by changing translation files in Weblate only
• Avoiding merge conflicts by locking Weblate while doing outside changes
• Avoiding merge conflicts by focusing on Git operations