Re: relation between unicode and font

From: Michael \(michka\) Kaplan (michka@trigeminal.com)
Date: Mon Jan 08 2001 - 12:09:00 EST


I am hesitant to even call it user error.

Its not like the person who does not have another option when it comes to
sending Tamil e-mail from their Windows 98 machine really has a choice.

The USER is doing the best they can with what they have... and since the
customer is always right I feel very comfortable saying its a limitation of
the software. :-)

MichKa

Michael Kaplan
Trigeminal Software, Inc.
http://www.trigeminal.com/

----- Original Message -----
From: <Peter_Constable@sil.org>
To: "Unicode List" <unicode@unicode.org>
Sent: Monday, January 08, 2001 7:26 AM
Subject: Re: relation between unicode and font

>
> On 01/06/2001 12:50:00 AM Jukka Korpela wrote:
>
> >It's still a browser bug if the document is declared or implied to be
> >ISO 8859-1 encoded and <font face="Tikkana">A B </font> causes something
> >else than A B to be displayed.
>
> A government or industry agency can provide specifications related to the
> composition of gasoline, and pumps can be configured to support the
> specifications, but if a particular trucker delivers a load of sugar-water
> to a station and fills their tanks without telling anybody, then there's
> not much that the pump can do to stop putting sugar-water in your car.
> There is no way that a browser can tell whether the glyph outlines in a
> font are appropriate for the character set that has been specified. This
is
> user error, not a browser bug.
>
>
>
> - Peter
>
>
> --------------------------------------------------------------------------
-
> Peter Constable
>
> Non-Roman Script Initiative, SIL International
> 7500 W. Camp Wisdom Rd., Dallas, TX 75236, USA
> Tel: +1 972 708 7485
> E-mail: <peter_constable@sil.org>
>
>
>



This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:17 EDT