: 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.
All the win32 widgets are coded to use only the System font, unless you send them a message (or change the initialization code) to use your own font. The encoding field doesn't have anything to do with this. What do you mean by the bounds problem? Does this occur normally without your font being builtin? (or the field set as above?) Regards, Greg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
