> On Feb 23, 2021, at 3:28 AM, Frank H. Ellenberger
> wrote:
>
> google translated:
>> Microsoft has been using the then current forerunner of UTF-16 since NT
>> ("wide characters"), but don't ask me for the code page etc.
>
> To add my mustard: recommended since Windows 10 1903
> Microsoft a
A complex topic is brought up here.
I agree with the issues you bring up. I don't know if or how we can solve them
all.
In the gnucash project we currently only have experience with docbook for user
oriented documentation and doxygen for our api documentation.
On the premise what we have so fa
google translated:
> Microsoft has been using the then current forerunner of UTF-16 since NT
> ("wide characters"), but don't ask me for the code page etc.
To add my mustard: recommended since Windows 10 1903
Microsoft apps that want to use UTF-8 have that in their AppX manifest
then ALWAYS use UT
