Click here to Skip to main content
Click here to Skip to main content


, 14 Feb 2001
Rate this:
Please Sign up or sign in to vote.
Display Chinese & Japanese characters on unicode & non-unicode systems
<!-- Link to source file download -->
  • Download source files - 51 Kb
  • <!-- Link to demo file download -->
  • Download demo project - 39 Kb
  • <!-- Article image -->

    Sample Image - KanjiFont_Demo.jpg

    <!-- Add the rest of your HTML here -->


    As you may know, Windows 2000 and Windows NT contain natural support Unicode, and can make use of the Windows API functions for displaying and using wide characters. However, the behavior of those API functions is not always completely the same between NT and 2000. Furthermore, under Windows 95 & 98 Unicode character functions are not supported at all.

    This makes it very frustrating for a developer to create an application that needs to display such characters. Recently, I needed to write a small Japanese dictionary for myself. This article contains the small set of classes that encapsulate some simple character translations and the methods for displaying Unicode characters reliably on Windows95/98/NT/2000 to solve this problem. I based my code on some older code done by Glen Rosenthal who wrote JWPce (a very nice Japanese text editor) and on an MSDN article that had some dated examples of a similar solution (Q241020).

    Basically, all TrueType fonts contain encoding tables based on the Unicode mappings for the characters those fonts contain. Microsoft distributes a few large fonts with MS Office and with newer version of Internet Explorer that contain characters or 'glyphs' for many different globale regions. Normally, a device context will do the translation from character code to glyph index for the systems locale when you call the TextOut or the ExtTextOut functions. This does not work on non-Unicode versions of Windows, and it does not work on some configurations for systems that are Unicode compatible. So in order to display the character you want on all version of windows you have to calculate the index of the 'glyph' within the true type font for the charcter code you want to display. Then a call to the ExtTextOut API function will allow you to display the 'glyph' you have selected; so long as it is present in the selected font.

    These classes provide a simple set of objects to easily use a true type font that contains glyphs foreign to your system locale, as well as some character code translation objects. To assist in debugging and just generally getting used to seeing Unicode character codes; most programmers are used to ASCII. I've included some iostream manipulators that allow you to easily translate character codes from one encoding format to another.

    If you have any enhancements or improvements, please let me know and the source can be updated here.


    This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

    A list of licenses authors might use can be found here


    About the Author

    Eric Crahen

    United States United States
    No Biography provided

    Comments and Discussions

    QuestionDoes it work for arabic? Pinmembervenomelektro28-Mar-05 9:07 
    GeneralThe correct character position. PinmemberJames Cao28-Sep-04 13:12 
    QuestionHow can I know which kind of font is suitable to a string? Pinmembercharcoalc29-Feb-04 20:33 
    Questionhow about GetCharacterPlacementA? Pinmemberdiamant22-Dec-03 3:45 
    GeneralRegarding Kanji fonts PinsussLeela Prasanna Kumar22-Nov-02 0:14 
    QuestionAlso in the title caption bar? PinmemberPep27-May-02 3:19 
    Generalnewbie question PinmemberArthur Chen12-May-01 12:05 
    QuestionWhy not simply use ExtTextOutW? PinsussPeter Kenyon27-Aug-00 13:25 
    AnswerRe: Why not simply use ExtTextOutW? PinsussEric Crahen29-Aug-00 4:25 
    GeneralRe: Why not simply use ExtTextOutW? PinsussPeter29-Aug-00 14:27 
    ExtTextOut and TextOut are implemented with Unicode versions on all platforms- see the MSDN library. I have used them myself to output Chinese on the original version of Windows 95.
    GeneralRe: Why not simply use ExtTextOutW? PinsussBrian Peterson29-Aug-00 14:48 
    GeneralRe: Why not simply use ExtTextOutW? PinmemberMd. Nura Azom Lipon4-Jan-03 4:16 
    GeneralGood work, but we need more! PinsussPaul Selormey26-Aug-00 10:40 
    GeneralRe: Good work, but we need more! PinsussEric Crahen29-Aug-00 4:23 
    GeneralLibrary Rocks! Pinsusstyson25-Aug-00 17:25 

    General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

    Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

    | Advertise | Privacy | Terms of Use | Mobile
    Web01 | 2.8.150327.1 | Last Updated 15 Feb 2001
    Article Copyright 2000 by Eric Crahen
    Everything else Copyright © CodeProject, 1999-2015
    Layout: fixed | fluid