From: Andrew R. <and...@us...> - 2004-12-13 22:59:10
|
I've implemented and committed changes to cf/freetype.ac to allow the freetype fonts to be selected at configure time. The new options are --with-freefont use free fonts rather than MS fonts [default=yes] --with-freetype-font-dir user-specified directory for freetype fonts --with-freetype-normal-font user-specified normal freetype font --with-freetype-roman-font user-specified roman freetype font --with-freetype-italic-font user-specified italic freetype font --with-freetype-script-font user-specified script freetype font --with-freetype-symbol-font user-specified symbol freetype font Fonts are set to appropriate defaults depending on --with-freefont unless overridden with a --with-freetype-*-font option. Freefont does not include a script font so I default to FreeSerif.ttf. All fonts are specified relative to the freefont-font-dir. For the free fonts the path is /usr/share/fonts/truetype/freefont if left unspecified. For the MS fonts it checks /usr/share/fonts/truetype/msttcorefonts and /usr/share/fonts/truetype/ for the fonts and sets the directory appropriately so we can compile on old and new debian systems. There is currently no check for MS fonts if you select the free fonts but they are not found or vice versa. Perhaps this would be useful? Andrew |
From: Arjen M. <arj...@wl...> - 2004-12-27 14:04:39
|
A quick report on my experiments with freetype fonts on Windows: 1. The freetype library compiles smoothly with VC++ as far as I can tell 2. After some manipulation of the make file for the static version of the PLplot library, I can include the FT library in PLplot 3. Unfortunately plfreetype.c does not compile cleanly under Windows: - Debug(...) and Verbose(...) are macros VC++ does not like (the ellipsis!) - unistd.h is unknown under Windows - there is no access() function available it seems For now I am just ignoring these issues (commenting out the offending parts in the source) .... Regards, Arjen |
From: Arjen M. <arj...@wl...> - 2004-12-27 14:14:31
|
Arjen Markus wrote: > > A quick report on my experiments with freetype fonts on Windows: > > 1. The freetype library compiles smoothly with VC++ as far as I can tell > > 2. After some manipulation of the make file for the static version of > the PLplot library, I can include the FT library in PLplot > > 3. Unfortunately plfreetype.c does not compile cleanly under Windows: > - Debug(...) and Verbose(...) are macros VC++ does not like (the > ellipsis!) > - unistd.h is unknown under Windows > - there is no access() function available it seems > > For now I am just ignoring these issues (commenting out the offending > parts in the source) .... > Yes, that works :) Andrew (Roach): thanks for the encouragement. The things that require sorting out now are: - A good location for the freetype library - Changes to the documentation of where to get freetype - Update to the win3 driver to make it freetype-aware (Though I am afraid I will not have time to formalise the changes this year ... It will be early january) Regards, Arjen |
From: Arjen M. <arj...@wl...> - 2005-01-05 09:11:33
|
Andrew Roach wrote: > > At 08:13 AM 28/12/2004 +0100, you wrote: > > > > That's a real pity - they are two of my all time favourite macros > > > [Sad smiley] If you can follow the logic of them, do you have any > > idea > > > how to get them working under VC++ ? > > > > > > > VC++ complained about the ellipsis. I have seen similar macros that > > do work, even with VC++ - so it should not be too tough :) > > If you come up with something, let me know. freetype has those Debugs > and Verboses all through it, and there are more than ever right now > since I am adding unicode to freetype at present. > I changed the two macros to this: /*--------------------------------------------------------------------------*\ * Some debugging macros \*--------------------------------------------------------------------------*/ #define Verbose(ARGS) do {if (pls->verbose){fprintf(stderr,ARGS);}}while(0) #define Debug(ARGS) do {if (pls->debug){fprintf(stderr,ARGS);}}while(0) (so no ellipsis or __VA_ARGS__) This does the trick. As the macros are simply text manipulators, there is no problem with the complicated list of arguments ... Regards, Arjen |