Sent by Jukka K. Korpela on 19 August 2004 21:09
On Thu, 19 Aug 2004, Paul Novitski wrote:
> Here's a distantly related phenomenon:
Sounds so distant that I changed the Subject like.
> with IE6, if I include sans-serif in
> my CSS font list, I've found that high character values such as ’
> (apostrophe) don't resolve properly, even if the browser appears to be
> using my first choice font, e.g. Verdana.
Sounds very strange. Didn't happen in my simple test. Have you got a
minimal test case that demonstrates this? It might depend on a number of
> I've assumed that if
> a named font-family were found on the local machine then the browser would
> stop processing the font list
Yes and no. A browser should use the first available font in the list for
each character. This means that if I specify font-family: foo, bar
and both fonts exist on a user's system, the browser should use the foo
font for all characters in the text that exist in that font but switch to
the bar font for others. However, IE6 is known to work poorly in font
selection issues, and it may well try to use the foo font anyway and
display a symbol of unavailable character even if the character actually
exists in the bar font. Thus, when using fairly special characters, it is
best to specify the font-family property (if at all) so that the _first_
alternative contains _all_ the characters needed, without relying on
correct browser behavior. - But ’ is not really special on Windows
systems, and it would be surprising if it is not rendered when some common
font is used. (Typographically, ’ does not really look like an
apostrophe in many fonts, e.g. in Arial, but in Verdana it's "smart", i.e.
curly, as expected.)
--
Jukka "Yucca" Korpela, http://www.cs.tut.fi/~jkorpela/
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
