BTW, how are PS fonts handled on z/OS? Or, more general, how is
PostScript handled on z/OS? Since PS is plain text normally, it
could be EBCDIC also.
And another follow-up: What about BDF and PCF? The former are pure
text files, and the latter could be different too (in case they are
based
Is there a possibility for the z/OS compiler to select the encoding of
an input file? This would be the easiest solution.
There is, but this doesn't completely work. It only covers cases where
they may be string literals in the code which are expected to be in
ascii. It still leaves open the
I've never actually run the XWindows system on Z/OS [...]
Oops, this answers the question in my previous mail. Still wondering
what kind of fonts are used for the z/OS graphics display...
Werner
___
Freetype-devel mailing list
What's the status of FreeType on z/os?
This is EBCDIC, right? I believe that is the reason of your problems.
All FreeType source files which contain character constants like 'A',
must preserve those constants as ASCII values, because FreeType always
opens files in binary mode. In particular,
In partial answer to my own question, I modified
include/freetype/tttags.h as aluded to in a previous post, to change
all of the lines like
#define TTAG_avar FT_MAKE_TAG( 'a', 'v', 'a', 'r' )
to lines like
#define TTAG_avar FT_MAKE_TAG( 0x61, 0x76, 0x61, 0x72 )
So my guess was