• Arial Unicode Ms Windows 10

My web application allows user to write rich text inside CKEditor, then export the result as PDF with the Flying Saucer library.As they need to write Greek characters, I chose to add Arial Unicode MS to the available fonts, by doing the following: config.fontnames = '.several fonts.; Arial Unicode MS/Arial Unicode MS, serif';This font is now displayed correctly in the CKEditor menu, but when I apply this font to any element, I get the following result: some text As you can notice, I lost the UpperCase characters. This has pretty bad effect during PDF export, as then Flying Saucer doesn't recognise the font and so uses Helvetica which does not support Unicode characters, so the greek characters are not displayed in the PDF.If I change manually from code source some text to some text then it is working as expected, greek characters are displayed.Has anyone met this problem before? Is there a way to avoid UpperCase characters to be changed to LowerCase?I really want to avoid doing any kind of post-processing like: htmlString = htmlString.replace('arial unicode ms', 'Arial Unicode MS').

Arial Unicode Ms Windows 10

Hi,Our internationalized, unicode, MFC product explicity will try to use the 'Arial Unicode MS' font(ARIALUNI.TTF). With XP and Windows 2000, if the font isn't present, the OS reverts to a font that is similar enough so that characters appear okay (at least in english).With Vista on the other hand if the font isn't present (i.e, default Vista Ulitmate install for example), in some of our dialogs, displays, the backslash ' in english comes out garbled as if it were in the Japanese locale: ¥If I manually install ARAILUNI.TTF in Vista everything is fine. I know the system font for Vista is Segoe UI, and that font seems okay for displaying also, but my questions are as follows:1) If the font isn't found, why doesn't Vista find a font closer to what XP finds so characters aren't garbled?2) Is there a better default unicode font we can use for both XP and Vista that will handle this problem?3) Should we be dealing with fonts completely differently?Any help will be appreciated -thanks-lew.