>Dragen,
>according to me the chri value will show the asci from the font.
>If a font contains the image of a s with accentgrave than it will have a certain chri value.
>The codepage is not involved.
>Select font Wingdings and activate the chr value of 81 it will show you an airplane and not Q which is the value of 81 in font Arial

Quite so, for non-unicode fonts. Which regularly came with windowses up to W2000 or thereabouts. Can't say I remember quite clearly about XP, but since NT4 at least most of the standard fonts are unicode. Which means that the characters up to 255 are western. Characters from other codepages take positions in the rest of the address space, which in unicode is 16-bit. The codepage gets involved when you have a non-unicode app, so the OS has to map a certain subset of that 16-bit space into 8-bit. Depending on that mapping (aka codepage for non-unicode), chr(156) will be ś in 1250, oe diphtong in 1252 and turkish, empty in greek and baltic, њ in cyrillic etc etc. In actuality, the unicode for њ is not 156, it's 0x045A and for ś it's 0x015B.