At 01:49 PM 12/18/2002 +0900, you wrote:
>Here is my comment and question on the new feature of ConTeXt supporting
>the UTF8 encoding.
>
>Actually I tried to test the following short ConTeXt document containing
>two Korean characters. At the second line I used the Bitstream Cyberbit
>font and the corresponding TFM files were generated by ttf2tfm with 
>Unicode.sfd
>(the same way as the UTF8 support in CJK-LaTeX).
>
>\enableregime [utf]
>\definefontsynonym [UnicodeRegular] [cyberb]
>\chardef\utfunihashmode=1
>\starttext
>^^eb^^bf^^a1
>^^ec^^80^^80
>\stoptext
>
>Here, ^^eb^^bf^^a1 = U+BFE1 and ^^ec^^80^^80 = U+C000.
>
>1. Without the third line (\chardef\utfunihashmode=1), I could not see
>    any characters. Why?
>
>2. After enabling \utfunihashmode, I could see the first character. But
>    not the second character. The difference was that the value of \unidiv
>    were 191 for the first character and 192 for the second character.
>    In fact, all characters with \unidiv >= 192 and \unidiv <= 223
>    (from U+C000 to U+DFFF; half of Hangul Syllables) were not shown
>    correctly. Why?

I'll work this out asap; this is what i use as test file (unfortunately 
this font does not show chars, so i have do download a proper font first); 
i attached a script that i apply to a ttf file ( ttftfmxx.pl htfs.ttf 0 255 )


\chardef\utfunihashmode=1

\pdfmapfile{+htfsxx.map}

\definefontsynonym [TestRegular] [htfs]

\defineunicodefont [SomeFont] [Test]

\SomeFont \enableregime[utf] % todo: autoutf, else problem

\starttekst

%^^eb^^bf^^a1
%^^ec^^80^^80
\utfunifontglyph{\numexpr("BFE1)}
\utfunifontglyph{\numexpr("C000)}

\stoptekst