list-rules seems to generate UTF-16 encoded JSON when CDISC rules, UTF-8 when custom rules

It looks as that when using (on Windows)
.\core.exe list-rules > rules.json
This produces an UTF-16 encoded JSON file
whereas when using
.\core.exe list-rules --custom_rules -s {custom_standard} -v {version} > custom_rules.json
this produces an UTF-8 encoded JSON file

Can this be checked?

In my application, this caused problems when reading in these files for setting up a GUI dialog where the user can select which rules to have executed and which none.
I do currently have a workaround, so not a high priority ...