David,
I noticed that the orginal author says he sometimes gets a bus error.
This indicates that he is running on a SPARC. On the SPARC architecture, you
can only access 16 bit values on 16 bit address boundaries, 32 bit values on 32
bit address boundaries etc. Whilst on an x86
Hi Werner, this is great news! Thanks for taking the time to investigate
this. The (small) difference in character widths and shapes between
freetype and MS has always been a pain - and hopefully this goes a long
way to reducing that issue.
Ian
-Original Message-
From: [EMAIL PROTECTED]
David, I'm not sure that your arguments below are valid. From what I can
divine, ClearType and Avalon are only concerned with sub-pixel rendering
and anti-aliasing. The original issue, however, is about non-aliased
rendering ... i.e. monochrome rendering.
When using freetype to render bitmaps for
PROTECTED]
Sent: 07 June 2005 16:19
To: Ian Brown
Cc: freetype@nongnu.org; Werner LEMBERG
Subject: Re: [ft] loading CID fonts and CMAPS
Hi
I have a CID font in memory that is immediately followed by a number
of CMAPs. If I load the font using FT_New_Memory_Face then the
CMAPs do not seem
