[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Newer proposed change for z1load.c
From: |
Tom Kacvinsky |
Subject: |
Re: Newer proposed change for z1load.c |
Date: |
Mon, 16 Oct 2000 12:08:20 -0400 (EDT) |
I have one fix for this already:
Instead of
char *notdef_glyph = "0x8B0xF70xE10x0D0x0E";
Use:
FT_Byte notdef_glyph[] = {0x8B,0xF7,0xE1,0x0D,0x0E};
Using a signed char and having the eighth bit set in some of those
bytes was causing a problem...
Tom
On Mon, 16 Oct 2000, Tom Kacvinsky wrote:
> Hi all,
>
> Attached is a new patch for z1load.c. Please review it. It works for me,
> but...
>
> Anyway, here is what I changed:
>
> /.notdef is *always* put into index 0. If /.notdef is not defined in the
> font,
> I add a /.notdef that corresponds to:
>
> 0 333 hsbw
> endchar
>
> The code the to do the above is not elegant, but it accomplishes its goal.
>
> The encoding array is `zeroed' out by adding .notdef to each and every
> code point. Probably not necessary.
>
> Regards,
>
> Tom
>
- Proposed change for z1load.c, Tom Kacvinsky, 2000/10/15
- Re: Proposed change for z1load.c, Werner LEMBERG, 2000/10/16
- Re: Proposed change for z1load.c, Tom Kacvinsky, 2000/10/16
- Re: Proposed change for z1load.c, Just van Rossum, 2000/10/16
- Re: Proposed change for z1load.c, Werner LEMBERG, 2000/10/16
- Newer proposed change for z1load.c, Tom Kacvinsky, 2000/10/16
- Re: Newer proposed change for z1load.c,
Tom Kacvinsky <=
- Re: Newer proposed change for z1load.c, Leonard Rosenthol, 2000/10/16
- Re: Newer proposed change for z1load.c, Tom Kacvinsky, 2000/10/16
- Re: Newer proposed change for z1load.c, Leonard Rosenthol, 2000/10/16
- Re: Newer proposed change for z1load.c, Werner LEMBERG, 2000/10/17
- Re: Newer proposed change for z1load.c, Tom Kacvinsky, 2000/10/17