>> On Unix-like systems, tracing and error messages are sent to stderr
>
> I tried to compile the Freetype by putting some messages through
> fprintf like putting this fprintf( stderr, "File cannot be opened
> \n" ); under some obvious code which always runs, but i couldn't see
> the output on screen.
Well, *this* is definitely a problem on your side that you have to
solve. Are you sure that you are linking to the right FreeType
library version?
> One thing to make the picture clear to you my application which
> prints any type1 or truetype styled font on screen uses Xft to show
> output. [...]
I can't help here, but you might try the FreeType demo programs to
check whether your extra debugging messages do appear on stderr.
> Is there any direct test program which i can use to test type1 font
> driver and print my error messages on terminal?
Try the FreeType demo programs (ftview, ftstring, etc.).
Werner
_______________________________________________
Freetype mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype
