From: P. J. Patterson (pj@ctt-inc.com)
Date: Thu Sep 26 2002 - 14:15:37 EDT
Actually, as a publisher, we do have a problem with this. I publish
scientific abstract data which is collected from authors all over the
world. Since the information becomes dated so quickly, we are always
looking for ways to reduce turn around time from collection to
publication. The books are sometimes 600 pages, and overhead must be
kept low. Unicode helps us keep the data accurate, but we are still
running into problems identifying missing glyphs prior to printing - for
the most part it comes down to visual recognition. This is complicated
by the fact that the submission and review processes are all browser
based.
I spoke with a few people from Adobe at the conference, and the concept
of fall-back fonts was very appealing, at least to minimize the missing
glyphs and still allow for wider font selections. But some sort of
alert system beyond the unrecognized character display is really what we
are looking for.
I think, ideally, I would be looking for a program to examine a
document, compare to the selected fonts (with fallback), and then list
the missing glyphs for individual handling.
Anyone have any thoughts?
--------------------------------------------
P.J. Patterson
Director of Product Research and Development
Coe-Truman Technologies, Inc.
e. pj@ctt-inc.com
p. 217-398-8594
f. 217-355-0101
--------------------------------------------
> -----Original Message-----
> From: Tex Texin [mailto:tex@i18nguy.com]
> Sent: Thursday, September 26, 2002 12:21 PM
> To: John Cowan
> Cc: tc31@cornell.edu; unicode@unicode.org
> Subject: Re: glyph selection for Unicode in browsers
>
>
> Hi,
> Yes, these fonts do not solve everything. (Nor should they.)
>
> We should be careful not to apply the requirements for high
> end publishing systems to software that just needs to have
> adequate rendering, such as browsers and other software.
>
> I would like to have adequate coverage for the Unicode space,
> with some language awareness or sensitivity, before we raise
> the bar to the level of requiring publishing quality.
>
> I would guess high end publishers are quite comfortable
> choosing (acquiring, installing, selecting) specialized fonts
> for different situations, including for rendering different languages.
>
> However, for people that are not so adept at choosing fonts
> and assigning them by language, browsers and other software
> need to have a reasonable, solution.
>
> tex
>
> John Cowan wrote:
> >
> > Thomas Chan scripsit:
> >
> > > But changing the example to fonts like Arial Unicode MS doesn't
> > > completely solve everything--a sans serif font is not the
> norm for
> > > non-trivial quantities of CJK text (compare any book or
> newspaper).
> >
> > Nor any other kind of text, indeed, until the widespread use of
> > Arial/Helvetica, which properly is only a display font, as
> a text font
> > (ugh).
> >
> > --
> > John Cowan jcowan@reutershealth.com www.ccil.org/~cowan
> > www.reutershealth.com "If I have not seen as far as others, it is
> > because giants were standing on my shoulders."
> > --Hal Abelson
>
> --
> -------------------------------------------------------------
> Tex Texin cell: +1 781 789 1898 mailto:Tex@XenCraft.com
> Xen Master http://www.i18nGuy.com
>
> XenCraft http://www.XenCraft.com
> Making e-Business Work Around the World
> -------------------------------------------------------------
>
>
This archive was generated by hypermail 2.1.5 : Thu Sep 26 2002 - 15:04:25 EDT