From: Andrew Dunbar (firstname.lastname@example.org)
Date: Wed May 01 2002 - 01:36:26 EDT
--- Leonard Rosenthol <email@example.com> wrote:
> At 8:32 AM -0700 4/30/02, Paul Rohr wrote:
> >Here's how I'd interpret WYSIWYG for zoom cases,
> where "correct" is defined
> >as how it will print:
> > The line breaks are correct.
> > The page breaks are correct.
> > The font is as readable as possible.
> the latter is actually irrelevant. If the user
> zooms to a
> certain percentage, the readability of the text (or
> other page
> content) is going to be simply be a crap-shoot based
> on all other
> factors (which is why the whole concept of "greeking
> text" came into
> being). You should NOT attempt to make text
> readable at the loss of
> correct behavior for layout.
I think this is overstating it a little. I want it
to be perfectly readable at "Page width" or 90% or
110% or 200% but at 10% or 500% it's probably not
going to be readable anyway.
> The correct behavior when zooming is (IMHO) to
> simply adjust
> the scaling factor for all objects - provided that
> everything is able
> to be affine transformed. Now that we are
> (hopefully) moving to a
> consistant font system (FreeType) which supports
> affines on the data
> - text is easily addressed by simply specifying that
> to FT as part of
> the glyph extraction process. (NOTE: we may have to
> Pango to support this - I don't know). Other types
> of elements such
> as pictures and lines can easily have be scaled as
> You NEVER change the size of a font - you won't get
> correct results since font size scaling doesn't
> necessarily maintain
> a consistant scaling factor while affine
> transforming does. And
> hence our problem today...
So let's do the affine transformation. What's the
problem? It sounds perfect to me.
> Leonard Rosenthol
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
This archive was generated by hypermail 2.1.4 : Wed May 01 2002 - 01:38:30 EDT