Re: FT2 design question

[Werner LEMBERG]

> On the other hand there is the scene graph.  You can do a lot of
> things with it, not just drawing.  So we have an abstract traversal
> operation for it with two particularly important variants, draw
> traversal and pick traversal.  Both need detailed layout information
> of the nodes (characters/glyphs are nodes in this scene graph as
> well) to be able to pick and modify the scene.  Drawing can then be
> done to different devices.  Screen, printer etc.  Therefore the hope
> is that we can initialize the region requirements of the glyphs with
> some 'canonical' value (say, the size to be used by the canonical
> DrawingKit which is the one to be used most opten, namely to draw on
> screen) and then only adjust/compensate if another DrawingKit is
> used such as for printing.  The aim is not to be able to replace one
> font with another without changing the layout (line break etc.) but
> to allow this abstract formulation of fonts, which are matched by
> different font renderers in the openGL driver (based on FreeType)
> and PostScript (ghostscript).  WYSIWYG should be the aim not only
> for very specialized DTP tools but for the whole windowing system.

If line breaks aren't an issue, why bothering with ligatures at all?
This is a typographical issue, usually completely hidden to the end
user -- you specify the font, have an input character string and get a
glyph string back.

WYSIWYG only works if you use the same font for the screen and
printing IMHO.

I think I haven't understood you completely (but I have read the very
interesting paper to which you've given a pointer).  Can you give a
real example of the problem you have?


    Werner