Translation workflow troubles

[mikhirev]

Hi!

I tried to enhance translation of FluffyChat but got in troubles because of very restrictive policy that enforces numerous checks. Some of that checks are not working correctly. There are very limited communication capabilities in Weblate, so I want to discuss this problem here.

First, there's a Weblate bug that triggers false error detection in pluralised translations in ARB. After I reported it, the Weblate developer applied a fix that only works if pluralized parameter name is count. However there are many strings where parameter names are different, e. g. number, seconds etc. There are also strings with two parameters that require pluralization, and obviously both of them can not be named count. According to project settings, translations with failed check are not accepted.

Second, there is a check in CI that forbids merging if Flutter tools output warning messages. I'm unsure if that warnings are printed because of mistake in Flutter checker or because the ICU MessageFormat processing in Flutter works differently from tools that I used to test my translations. This requires further investigation. Probably translated strings must be fixed, but probably that warning just should be ignored.

After strings I translated failed checks, the Weblate user @ChristianPauly (@krille-chan is it you?) changed that strings and approved them, so I'm unable to fix translation anymore. While most strings are just reverted to the previous state, some of them are wiped or edited incorrect way.

So there are three topics that need to be discussed:

1. Relaxing Weblate checks until they will be fixed.
2. Investigation of correcthess of some translations, in particular that ones containing plurals with both =1 and one cases and =n cases where n>2. I used this tool to test my translations. It is based on formatjs, so Flutter can handle them a bit differently.
3. Unlocking translations or giving me reviewer permissions. I promise I won't break checks that I'm aware about. ☺