Unicode in Source files

[gunterkoenigsmann]

@daute and @richardgobeli have found out: If there is no BOM at the end of a source file it is up to the C compiler to decide if the file is unicode or an exotic codepage => We need to replace all 8-bit letters by an "\uxxxx" command that explicitly specifies that this is meant as an Unicode char.

[gunterkoenigsmann]

A regex that seems to find this kind of characters is

"[\x80-\xFF]"

[gunterkoenigsmann]

Grep doesn't like that one if not in the form

grep --color -nH --null -P -n -e "[\x80-\xFF]" * -R

[richardgobeli]

What does the & character do in the string in front of ad?
series_sub->Append(menu_pade, _("P&ad\u00E9 Approximation..."),

There must be more to it than just putting \u00E9 because the character is still wrong from yesterday.

[gunterkoenigsmann]

The "&" character makes that character an accellerator (I believe you can press that key or alt + that key) for reaching the menu entry faster.

But that unicode still isn't treated correctly is weird...

[daute]

Fixed with commit 5cbec07.