>
> >> Well, simply follow the documentation, i.e., set `pitch' to
> >>
> >> w + 7) / 8) + 1) / 2) * 2
> >>
> >> (but with some better C code :-) and use this value for creating
> >> the bitmap.
> >
> > Ok, I did change the value of pitch (6) and tried to draw `a', it is
> > giving a wrong gl
> Hi Armin,
Hi pat, great to see you :D
> My graduate student Zeming has been making good progress this term on TTF
> bytecode analysis. So we don't have a corpus, but we can now easily manipulate
> bytecode for existing fonts. If there's anything specific you have in mind, we
> should figure out
Hi Armin,
On Tue, Jul 10, 2018 at 1:04 PM, wrote:
> Does anyone know font geeks?
> ===
>
> If possible, I would love to ditch the "old" corpus since its fonts are huge
> (they are proper fonts) and repetitive (not exactly the initial fuzz corpus
> of your dreams). While
>> Well, simply follow the documentation, i.e., set `pitch' to
>>
>> w + 7) / 8) + 1) / 2) * 2
>>
>> (but with some better C code :-) and use this value for creating
>> the bitmap.
>
> Ok, I did change the value of pitch (6) and tried to draw `a', it is
> giving a wrong glyph, then I change
Hello dear readers of this wonderful mailing list :)
I want to give you a quick update on the fuzzing side of things:
The targets are growing on a daily basis and will be integrated into
OSS-Fuzz in a matter of hours, maximum a day or two :) They will not be
complete by then (technically, they w
>
> > [...] I still have a doubt about pitch value, currently it is set to
>> > (w+7) / 8 (w: glyph width ). The documentation says `For the B/W
>> > rasterizer, ‘pitch’ is always an even number.' but this is also
>> > returning odd values. Is there any problem in this?
>>
>> Well, simply follow
>
> > [...] I still have a doubt about pitch value, currently it is set to
> > (w+7) / 8 (w: glyph width ). The documentation says `For the B/W
> > rasterizer, ‘pitch’ is always an even number.' but this is also
> > returning odd values. Is there any problem in this?
>
> Well, simply follow the d
> [...] I still have a doubt about pitch value, currently it is set to
> (w+7) / 8 (w: glyph width ). The documentation says `For the B/W
> rasterizer, ‘pitch’ is always an even number.' but this is also
> returning odd values. Is there any problem in this?
Well, simply follow the documentation
>
> > I have removed all the memory leak errors in the gf driver. But now
> > when I run `ftview', it is still not loading the glyphs.
>
> Before delving into this issue: Does your `ftexample' now work
> correctly?
>
Yes, I can't say for sure as I didn't draw every glyph by the gdb
method (It tak
> I have removed all the memory leak errors in the gf driver. But now
> when I run `ftview', it is still not loading the glyphs.
Before delving into this issue: Does your `ftexample' now work
correctly?
> ==11084== Invalid read of size 1
> ==11084==at 0x10E758: my_face_requester (ftcommon.
Hi all,
I have removed all the memory leak errors in the gf
driver. But now when I run `ftview', it is still not loading
the glyphs. I did `valgrind ftview 20 /home/parth/cmr10
.600gf' and it is showing invalid reads in the `FTC...'
functions.
I am not able to understand the problem. Please help.
11 matches
Mail list logo
