Re: [ft-devel] Unpatented hinting when vertical and horizontal point sizes are different
I'm having some weird results when I vary the point size of some fonts, for example if I desire a character with vertical point size 20 and horizontal point size 10 @ 203 DPI with unpatented hinting enabled the output is really bad. If I set the point size to 10x10 or 20x20 the result is great! It almost seems if the output for 20x10 is only partially using the horizontal point size information. Graham, can you have a look at it? Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
RE: [ft-devel] Re: disappointing results with autohinting
Antoine, For my purposes the quality shown in the image I sent is completely unacceptable. To give just one example, the two bottom points of the letter 'w' are at different heights at small sizes. This makes it impossible to use. Yes, it is readable, but that is not enough. Best regards, Graham -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Antoine Leca Sent: 25 May 2007 09:02 To: freetype-devel@nongnu.org Subject: [ft-devel] Re: disappointing results with autohinting Graham Asher wrote: I am getting very bad results autohinting Times New Roman (times.ttf from Microsoft): see the attached image. I know this is highly subjective, but I will not qualify the image you sent as very bad. Surely there are defects, but it seems readable to me. In fact I remember looking at the bitmaps used at the beginning of the GUIs, around 1985, and in my record the ones used by Microsoft (TmsRmnE/F.fon) was more or less of this quality, perhaps a bit better but not much. Also keep in mind that Times New Roman (from Monotype) is one of the most carefully hinted font available, so the comparison between the result of a real-time algorithm (even done in 200x) versus several man×month of work done by specialists (even done in 1991) should invariably shows the latter as better. Furthermore, Times Roman itself is a very carefully studied font (to get the highest possible efficiency of ink and space over words), so while it is a good --and valid-- basis for testing, perhaps more easy fonts such as Verdana, Helvetica, Cheltemham, Century Schoolbook, might yield better results, at the price of a bigger advance for each character. My 0.02 €, which may or may not help. Antoine ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] Warnings building 2.3.4 on Solaris 7 with Sun C compiler
I get the following warnings building 2.3.4 on Solaris 7 with the Sun C compiler: cc -I/opt/TWWfsw/libz12/include -I/opt/build/freetype-2.3.4/objs -I./builds/unix -I/opt/build/freetype-2.3.4/include -c -mr -Qn -xstrconst -xO2 -xtarget=ultra2 -xarch=v8plusa -DFT_CONFIG_OPTION_SYSTEM_ZLIB -DFT_CONFIG_CONFIG_H=ftconfig.h -DFT2_BUILD_LIBRARY -DFT_CONFIG_MODULES_H=ftmodule.h -I/opt/build/freetype-2.3.4/src/psnames /opt/build/freetype-2.3.4/src/psnames/psmodule.c -KPIC -DPIC -o /opt/build/freetype-2.3.4/objs/.libs/psnames.o /opt/build/freetype-2.3.4/src/psnames/psmodule.c, line 95: warning: integer overflow detected: op /opt/build/freetype-2.3.4/src/psnames/psmodule.c, line 135: warning: integer overflow detected: op /opt/build/freetype-2.3.4/src/psnames/psmodule.c, line 159: warning: integer overflow detected: op /opt/build/freetype-2.3.4/src/psnames/psmodule.c, line 171: warning: integer overflow detected: op /opt/build/freetype-2.3.4/src/psnames/psmodule.c, line 172: warning: integer overflow detected: op /opt/build/freetype-2.3.4/src/psnames/psmodule.c, line 218: warning: integer overflow detected: op /opt/build/freetype-2.3.4/src/psnames/psmodule.c, line 285: warning: integer overflow detected: op /opt/build/freetype-2.3.4/src/psnames/psmodule.c, line 333: warning: integer overflow detected: op /opt/build/freetype-2.3.4/src/psnames/psmodule.c, line 354: warning: integer overflow detected: op -- albert chin ([EMAIL PROTECTED]) ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Warnings building 2.3.4 on Solaris 7 with Sun C compiler
I get the following warnings building 2.3.4 on Solaris 7 with the Sun C compiler: This has been fixed in the CVS, I think, based on patches from Graham. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] [Regression] Font doesn't open with Freetype CVS but works with Freetype 2.2.1
Hi all, Attached font doesn't work with freetype CVS but works fine with Freetype 2.2.1 . The font was embedded in a pdf file and works fine with Fontforge. Regards, ismail -- Perfect is the enemy of good fontc.ttf Description: application/font-ttf signature.asc Description: This is a digitally signed message part. ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] [Regression] Font doesn't open with Freetype CVS but works with Freetype 2.2.1
Attached font doesn't work with freetype CVS but works fine with Freetype 2.2.1 . The font was embedded in a pdf file and works fine with Fontforge. Hmm, this font doesn't have a `cmap' table, which is invalid according to the OpenType standard, and the behaviour is defined as `implementation specific' in PDF standard (see section 5.5. in the PDF 1.6 specification). Please see http://lists.gnu.org/archive/html/freetype-devel/2007-04/msg00046.html for the reason to the change behaviour. David, do you have a better fix? Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] [Regression] Font doesn't open with Freetype CVS but works with Freetype 2.2.1
On Saturday 26 May 2007 02:13:52 Werner LEMBERG wrote: Attached font doesn't work with freetype CVS but works fine with Freetype 2.2.1 . The font was embedded in a pdf file and works fine with Fontforge. Hmm, this font doesn't have a `cmap' table, which is invalid according to the OpenType standard, and the behaviour is defined as `implementation specific' in PDF standard (see section 5.5. in the PDF 1.6 specification). Please see http://lists.gnu.org/archive/html/freetype-devel/2007-04/msg00046.html for the reason to the change behaviour. I see but lots of real world PDF files have this kind of fonts :-/ Regards, ismail -- Perfect is the enemy of good signature.asc Description: This is a digitally signed message part. ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] [Regression] Font doesn't open with Freetype CVS but works with Freetype 2.2.1
On Saturday 26 May 2007 02:13:52 you wrote: Attached font doesn't work with freetype CVS but works fine with Freetype 2.2.1 . The font was embedded in a pdf file and works fine with Fontforge. Hmm, this font doesn't have a `cmap' table, which is invalid according to the OpenType standard, and the behaviour is defined as `implementation specific' in PDF standard (see section 5.5. in the PDF 1.6 specification). Please see http://lists.gnu.org/archive/html/freetype-devel/2007-04/msg00046.html Btw reverting that change on src/sfnt/sfobjs.c doesn't seem to fix the problem. Regards, ismail -- Perfect is the enemy of good signature.asc Description: This is a digitally signed message part. ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
