On Sep 16, 2006, at 5:52 PM, Brian Weed wrote:
Hartwig Wiesmann wrote:
Hi,
the file path parameter is a pointer to a constant char type. A
lot of OS are not using ASCII characters but Unicode to describe
the file name and its path. Is there any workaround to have also
access to font
[...] on Win32, when the filename is known to be UTF-8, it can be
converted to UTF-16, and _wfopen() can be called instead of
fopen(). That works. (I've tested it on XP with text files, but not
with fonts.) It might be good for FT_New_Face to support that method
on Win32, if it doesn't
On Sep 17, 2006, at 11:48 AM, Sergey Tolstov wrote:
You already provide a way for platform specific file loading -
FT_Open_Face. It is good enough for Windows platform.
That's good news. Could anyone point to sample code for using
FT_Open_Face on MS-Windows?
Tom
Sergey
-Original
At 2:15 PM -0700 9/17/06, Wenlin Institute wrote:
You already provide a way for platform specific file loading -
FT_Open_Face. It is good enough for Windows platform.
That's good news. Could anyone point to sample code for using
FT_Open_Face on MS-Windows?
I tend to use
Hi Leonard,
I tend to use FT_New_Memory_Face() on Windows, having first found
the font data using native OS API calls and then loading the font data
into memory from there...
We do that too in Prince, however this method is difficult to use for
TrueType Collection (TTC) fonts such as
Hi,
i know this is the mailing list from freetype but i think here are the
most valueable persons for my question.
I have to generate postscript from emf. All is working fine. And with
thanks to werner i also managed to include fonts. Im embedding the
fonts as type 3 fonts. This means the font
