[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[mgp-users 00692] Re: Chinese support
- To: Zou Pengcheng <pzou@auto11.org>
- Subject: [mgp-users 00692] Re: Chinese support
- From: jg@pa.dec.com (Jim Gettys)
- Date: Mon, 3 Sep 2001 19:49:32 -0700 (PDT)
- Cc: Alex Madon <madon@cma-it.com>, mgp-users@mew.org
- Delivered-to: mailing list mgp-users@mew.org
- In-reply-to: <>
- Mailing-list: contact mgp-users-help@mew.org; run by ezmlm
When we designed the X Window System, we did not forsee the consequences
of some of the design decisions we made, particularly when combined
with outline fonts.
The core X protocol requires that the font metrics of the entire font
be returned. So when you image an outline font (still a gleam in various
people's eyes at the time we were doing the design work), you have to
render the *entire* font: all glyphs must be imaged to be able to return
the font metrics, most of which you will never use. All this has to happen
before you can paint a single character.
Needless to say, on eastern fonts with many glyphs, this can take a significant
amount of time.
Sorry. We goofed.
OK, so what is the solution? If someone would convert mgp to use the new
Xft library which uses the new X Render extension you will get:
1) incremental rendering of glyphs as needed. Startup time on eastern
fonts will be dramatically reduced.
2) anti-aliased text.
3) sub-pixel decimation on flat panel displays (something like Microsoft's
ClearType, but fundamentally better).
Xft has been designed to make it reasonably easy to retrofit applications,
and will fail-over to use bitmap fonts if outline fonts and/or Render
is not available. Render is now becoming pretty widespread on open source
systems.
So this is the solution I recommend.
- Jim Gettys
--
Jim Gettys
Technology and Corporate Development
Compaq Computer Corporation
jg@pa.dec.com