Re: [ft-devel] Z/OS status
> 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 correct.
> I can send a new version of the tttags.h file for inclusion in CVS
> if required.
Mhmm, as mentioned in the other mail, this isn't an elegant solution
since it uglifies the source code. I'm currently thinking of tagging
all affected strings with a no-op macro, say,
ASCII("This is a string which must stay in ASCII")
and replacing all character constants with C_A, C_B, etc.:
#define C_A 0x41
#define C_B 0x42
...
After this has been done, a small script just needs to catch those
tags.
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. I highly suspect that my naïve EBCDIC approach in
file src/psaux/psconv.c doesn't work correctly...
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Z/OS status
> 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, TrueType tags must be handled as such, which currently isn't the case. Is there a possibility for the z/OS compiler to select the encoding of an input file? This would be the easiest solution. Otherwise I could also imagine that we provide a script which converts strings and character constants to the right (ASCII) value, this is, replacing everything with character code values using the \x notation. > Any ideas what might be wrong, or how I can get further with this? In case z/OS is no longer EBCDIC, please call your test program with FT2_DEBUG=any:7 your_program &> your_program.log Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Z/OS status
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 )
(I just wrote a small java program to convert the 'a' to 0x61 etc) and
the sample program below now works.
I've yet to actually try and produce any output with it yet, but at
least the fonts load which is a good sign.
I can send a new version of the tttags.h file for inclusion in CVS if
required.
Tom Quarendon wrote:
What's the status of FreeType on z/os?
There are a number of previous posts that indicate that it should work,
but I'm having trouble loading a truetype font.
I'm trying to load the Bitstream Vera.ttf TrueType font, which I've
copied in binary to my z/os machine. I've got the FT_DEBUG_LEVEL_ERROR
and FT_DEBUG_LEVEL_TRACE options turned on in my freetype build, but
when I run a small program like
#include
#include FT_FREETYPE_H
int main(int argc, const char* argv[]) {
FT_Library library;
FT_Init_FreeType( &library );
FT_Face face;
FT_Error error = FT_New_Face(library, "/u/wpcuk02/fonts/Vera.ttf",
0, &face);
printf("FT_New_Face returned %d\n", error);
}
I get
FT_Stream_Open: could not open `/u/wpcuk02/fonts/._Vera.ttf'
FT_Stream_Open: could not open `/u/wpcuk02/fonts/%Vera.ttf'
FT_Stream_Open: could not open `/u/wpcuk02/fonts/.AppleDouble/Vera.ttf'
FT_Stream_Open: could not open `/u/wpcuk02/fonts/Vera.ttf/rsrc'
FT_Stream_Open: could not open `/u/wpcuk02/fonts/resource.frk/Vera.ttf'
FT_Stream_Open: could not open `/u/wpcuk02/fonts/.resource/Vera.ttf'
FT_New_Face returned 2
It is possible that I've not built freetype right, because I've made
some Makefiles to build it that fit in with our build system, but I've
managed on the PC and it all works wonderfully.
Any ideas what might be wrong, or how I can get further with this?
___
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] Z/OS status
What's the status of FreeType on z/os?
There are a number of previous posts that indicate that it should work,
but I'm having trouble loading a truetype font.
I'm trying to load the Bitstream Vera.ttf TrueType font, which I've
copied in binary to my z/os machine. I've got the FT_DEBUG_LEVEL_ERROR
and FT_DEBUG_LEVEL_TRACE options turned on in my freetype build, but
when I run a small program like
#include
#include FT_FREETYPE_H
int main(int argc, const char* argv[]) {
FT_Library library;
FT_Init_FreeType( &library );
FT_Face face;
FT_Error error = FT_New_Face(library, "/u/wpcuk02/fonts/Vera.ttf", 0,
&face);
printf("FT_New_Face returned %d\n", error);
}
I get
FT_Stream_Open: could not open `/u/wpcuk02/fonts/._Vera.ttf'
FT_Stream_Open: could not open `/u/wpcuk02/fonts/%Vera.ttf'
FT_Stream_Open: could not open `/u/wpcuk02/fonts/.AppleDouble/Vera.ttf'
FT_Stream_Open: could not open `/u/wpcuk02/fonts/Vera.ttf/rsrc'
FT_Stream_Open: could not open `/u/wpcuk02/fonts/resource.frk/Vera.ttf'
FT_Stream_Open: could not open `/u/wpcuk02/fonts/.resource/Vera.ttf'
FT_New_Face returned 2
It is possible that I've not built freetype right, because I've made
some Makefiles to build it that fit in with our build system, but I've
managed on the PC and it all works wonderfully.
Any ideas what might be wrong, or how I can get further with this?
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] Rendering problem with 'y' character
Hi, Attached patch shows a rendering problem with 'y' character with Tahoma font (in "python" and "system" ). Notice that top-left part of y looks cropped. Dpi is 96, and font size is 9 pts. I only see the problem when italic text is used. Does anyone know if this is a problem in KDE/Qt or a known problem? And how to debug this better? P.S: The screenshot is taken from python.org with Konqueror 3.5.4 Regards, ismail rendering-problem.png Description: PNG image ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
