[Freetype-wiki-commit] [A freetype Wiki] Update of "AsianCharacters"

[webmaster at freedesktop.org]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "A freetype Wiki" for change notification.

The following page has been changed by AaronBrady:
http://freetype.freedesktop.org/wiki/AsianCharacters

------------------------------------------------------------------------------
  {{{
- I would guess that this can be caused by the fact that you are not using bytecode interpreter (that is disabled by default because it is patented). Some Asian fonts relays strongly on bytecode interpreter and cannot be 
+ I would guess that this can be caused by the fact that you are 
+ not using bytecode interpreter (that is disabled by default because 
+ it is patented). 
+ 
+ Some Asian fonts relays strongly on bytecode interpreter and cannot be 
  rendered well without it.
  
- If this is an issue, you may be getting right characters on certain font sizes - there where the font provides embed outlines. But whenever font engine has to create outline itself (normally only a few font sizes are embed) it fails because of lack of bytecode interpreter.
+ If this is an issue, you may be getting right characters on certain font
+  sizes - there where the font provides embed outlines. But whenever font 
+ engine has to create outline itself (normally only a few font sizes are 
+ embed) it fails because of lack of bytecode interpreter.
  
- You can test if this is the problem by turning on the bytecode interpreter (compile time option - TT_CONFIG_OPTION_BYTECODE_INTERPRETER
+ You can test if this is the problem by turning on the bytecode interpreter
+  (compile time option - TT_CONFIG_OPTION_BYTECODE_INTERPRETER
  in include/freetype/config/ftoption.h), and later use 
  TT_CONFIG_OPTION_UNPATENTED_HINTING (same file - below) workaround.
  
- Unfortunately unpatented hinting often fails rendering latin alphabet (eg. Arial font), that normally works well without bytecode interpreter at all.
+ Unfortunately unpatented hinting often fails rendering latin alphabet
+  (eg. Arial font), that normally works well without bytecode interpreter at all.
  }}}
  
  The problem didn't pop up with some fonts, like msgothic (as far as I could tell). So you may or may not experience this.