Re: [ft-devel] Tiny Docs Patch

> I suggest this tiny patch in the documentation of the driver properties: > > ``` > diff --git a/include/freetype/ftdriver.h b/include/freetype/ftdriver.h > index 2384dc61..c893c545 100644 > --- a/include/freetype/ftdriver.h > +++ b/include/freetype/ftdriver.h > @@ -383,7 +383,7 @@

[ft-devel] Tiny Docs Patch

I suggest this tiny patch in the documentation of the driver properties: ``` diff --git a/include/freetype/ftdriver.h b/include/freetype/ftdriver.h index 2384dc61..c893c545 100644 --- a/include/freetype/ftdriver.h +++ b/include/freetype/ftdriver.h @@ -383,7 +383,7 @@ FT_BEGIN_HEADER * *

[ft-devel] Docwriter update: Docwriter 1.0 is out!

Hi all, MkDocs 1.0 was just released and the directory structure was finally fixed! This means that all links are now `docs/reference/page.html' instead of `docs/reference/page/index.html'. With this, the docs are now organized nicely in a single directory. I've released docwriter 1.0 with the

Re: [ft-devel] (no subject)

> Ah, this is the result of Emacs's `adaptive fill mode' that > automatically determines the fill prefix of paragraphs. Setting the > corresponding regexp explicitly fixes this. Attached is a patch – it > fixes some more places. > Great, this fixes it. Meanwhile, I had a look at the complete

Re: [ft-devel] success?

> > >> But, even after setting all the metric values and bitmap, it is not > >> displaying a glyph in `ftview' and just displaying a blank output. > > Thanks to your new branch in `freetype2-demos' I can finally test the > GF+TFM combo... > > Assuming that you are running a GNU/Linux box: Have you

[ft-devel] processing TFM metric data

Parth, now that parsing of TFM data works, you should do something with the data: Please fill `slot->linearHoriAdvance' – the TFM data is not specific to a pixel size, it thus makes sense to provide this field (this has to be documented later on). Similarly, the `slot->metric' data should be

Re: [ft-devel] success?

> FT2_DEBUG=any:7 valgrind ./ftview 20 cmr10.600gf &> cmr10.600gf.log For other people reading this I forgot to mention that you need `cmr10.tfm' in the same directory as `cmr10.600gf' to see the problems. Werner ___ Freetype-devel mailing

Re: [ft-devel] success?

>> But, even after setting all the metric values and bitmap, it is not >> displaying a glyph in `ftview' and just displaying a blank output. Thanks to your new branch in `freetype2-demos' I can finally test the GF+TFM combo... Assuming that you are running a GNU/Linux box: Have you ever used