We should also take a quick look at the builtin font structure
where you specify your builtin .c font: its very important what
you use for the "encoding" member.

There is another strange effect: with fontprocs->encoding field set to MWTF_UC16 the text is showed correctly but all the win32 widgets seem to use the "System" builtin font ad all bounds is ignored by the text.

Regards, Cristian.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to