Convert documentation files to UTF-8

[numeredev]

DESCRIPTION

Is your change request related to a problem? Please describe. git does not seem to handle CP1252 that well and switches the encoding to UTF-8 on every application of a suggestion.

Describe the solution you'd like Documentation and language files should be encoded in UTF-8 and the internal logics shall support it.

Describe possible alternatives you've considered An alternative would be to have a script to always restore the encoding before merging any translation file PR (which is itself tedious)

Additional context Add any other context or screenshots about the feature request here.

(Do not write below this line)

---

DEVS' SECTION

ANALYSIS

Should not be too difficult, because that requires only to convert the UTF-8 encoded text with the documentation files to CP1252 internally or even only to switch the font encoding of the documentation browser to UTF-8. The more time consuming task is to convert the actual files. It might be needed to do that differently for the language files.

IMPLEMENTATION STEPS

(see also our Wiki for implementation guidelines)

• Implement the necessary changes in a new branch created here on GitHub
• Test your implementation

DOCUMENTATION STEPS

(see also our Wiki for further information)

• Update the changes log
• Add comments to your implementation
• Add Doxygen documentation comments
• Create or update the documentation articles (*.NHLP and *.NDB files, if needed)
• Update the language strings (*.NLNG files, if needed)

PULL REQUEST

• Create a pull request for your changes
• Fill out the template
• Assign @numere-org/maintainers as reviewers

[numeredev]

Tiny additional change would be to enable code highlighting for function and method documentations created by the doc_help() function.