* wmlxgettext: Support extracting all textdomains at once
- -o now expects a folder.
- --domain is now treated as an optional filter.
* wmltools/gui/wmlxgettext: Update input handling
- Fix --initialdomain
- Textdomain is no longer mandatory.
- Accept output dir rather than output file.
Some users of wmlxgettext have scripts that already provide the file list in
a deterministic order, and the sorting added in 3761faf925 was choosing a
different order to the one desired.
(cherry picked from commit 904bb9bfb82c391d20e89dfbaacc1e71749dc3d9)
Add a sort inside wmlxgettext so that the order of filenames on the command
line doesn't affect the output. The sort is run unconditionally, because I
don't see a usecase for not enabling it. For consistency with xgettext and
msgcat, if there was an option to enable it then it would be called
`--sort-by-file`.
The aim of this change is to reduce the number of changes in .po files caused
by a pot-update. When multiple comments refer to the same translatable string,
separate runs of pot-update could generate them in a random order. If I've
understood the root cause correctly, wmlxgettext itself was deterministic, but
the order of the files on wmlxgettext's command line was not deterministic.
For testing, I tried reversing the sort order; the resulting reordering hit
lines that commonly swap order during pot-updates.
This affects the ordering of the lines beginning `#.` that are generated from
`#po:` comments and also those auto-generated from `[message]speaker=`, etc.
