[Devel] CFF charmaps are working

[David Turner]

Hello,

  I've just completed a round of changes to add charmaps support
  to the CFF/OpenType font driver. I haven't tested it on a lot
  of fonts, so please test it.

  Here's a small note on how it works:

    - the new code synthetizes a Unicode charmap from the
      glyph names extracted from the Charset table within
      a CFF font. This is very similar to what is done
      within the Type 1 driver

      For OpenType fonts, the new charmap is only synthetized
      if the "cmap" table of the font doesn't contain a Unicode
      table already. (Should we change this behaviour ??)


    - Otherwise, the Encoding table is used to generate a new
      charmap for the Adobe "platform_id" (7). This strictly
      corresponds to the behaviour of the Type 1 driver. i.e.

        platform_id    encoding_id     encoding

             7              0          ft_encoding_adobe_standard
             7              1          ft_encoding_adobe_expert
             7              2          ft_encoding_adobe_custom

      note that these encodings are limited to 256 character codes.


  There were also quite a number of bugs in the Encoding and
  Charset loaders that are now fixed. The code is now much more
  robust to invalid input.

  The CFF driver source code has also been slightly reformated
  (all internal function names are now lower-cased). I intend to
  perform similar changes in other modules in the future..


Best Regards,

- David Turner
- The FreeType Project  (www.freetype.org)