Note that there are some explanatory texts on larger screens.

plurals
  1. PODisplaying Unicode characters above U+FFFF on Windows
    primarykey
    data
    text
    <p>the application I'm developing with EVC++ 4 runs on Windows CE 5 and should support unicode (AFAIK wchar_t uses UTF-16 on windows, so I'm using that), so I want to be able to test it with "more exotic" characters. Especially with characters that use 4 Byte in UTF-16 and not just 2. Therefore I'm trying to display such characters in a texteditor (atm on my desktop PC with Windows XP, not on the embedded device).</p> <p>But I haven't managed it to do so yet. As an example I've chosen <a href="http://www.fileformat.info/info/unicode/char/10800/index.htm" rel="nofollow noreferrer">this character</a>. Like mentioned <a href="http://www.fileformat.info/info/unicode/char/10800/fontsupport.htm" rel="nofollow noreferrer">here</a> "MPH 2B Damase" should support this character. So I downloaded the font and put it into Windows\Fonts. I created a textfile using a hexeditor (just to be sure) with following content:</p> <pre>FFFE D802 DC00</pre> <p>When I open it with notepad (which should be unicode-capable, right?) and use the downloaded font it doesn't display 1 char, as intended, but this 2:</p> <pre>˘Ü</pre> <p>What am I doing wrong? :)</p> <p>Thanks!</p> <p>hrniels</p> <p><b>Edit:</b> Flipping the BOM, as suggested, doesn't work. Notepad (and all other editors I tried, too) displays two squares in this case. Interesting is that if I copy the two squares here (with firefox) I see the right character: <pre></pre> I've also tried it with Komodo Edit with the same result.</p> <p>Using UTF-8 doesn't help notepad either.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload