public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Browsers not seeing symbol font
Date: Wed, 25 Mar 2009 09:50:35 -0500	[thread overview]
Message-ID: <58965d8a0903250750t5f835b5ar999498ecec078bae@mail.gmail.com> (raw)
In-Reply-To: <9acccfe50903250702y7f6869f0xfd0e28002d4ca9c0@mail.gmail.com>

On Wed, Mar 25, 2009 at 9:02 AM, Kevin O'Gorman <kogorman@gmail.com> wrote:
> I have discovered that the symbol font does not render reliably in
> browsers.  Only one of my audience (of about a dozen people) could see
> the font properly, in a variety of browsers.  The one who could is
> using Firefox, and I have not been able to determine what makes this
> one special -- I do not have access to that machine to check out
> configurations.
>
> I have a very simple HTML example at
> http://www.kosmanor.com/~kevin/symbol.html.  By rights it should show
> "The quick brown fox" transliterated into greek letters.  On most
> browsers set up for English, it seems to come out in latin letters,
> but there are no latin letter in that font, although these same
> browsers honor requests for a variety of other fonts.  This is true
> even on some machines that definitely have the symbol font, and it's
> usable in word processing documents.
>
> Of course, that sample page is ancient HTML, but the problem first
> surfaced in HTML email being received on a much more sophisticated
> page by Yahoo Mail.
>
> There's a lot I don't know about character encodings, i18n and the
> rest, but this still seems discrimination against the symbol font.
> Any clues out there?

1. "Symbol" is not a defined CSS font family. Your choices are: serif,
sans-serif, cursive, fantasy, monospace.

2. Character encodings are easy: use Unicode. :)
http://www.unicode.org/charts/symbols.html

3. Because neither your HTML nor your HTTP headers declare which
character encoding the page uses, it is left up to the browser to make
that decision (which obviously causes unpredictable results). You
should really define this.

4. Similarly, check the character encoding setting on the browser to
make sure it's not forcing it to be wrong. Firefox also has options to
allow or disallow the page from using its own fonts, etc.

5. Make sure the requisite fonts exist on the viewer's computer and is
properly installed.



  parent reply	other threads:[~2009-03-25 14:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 14:02 [gentoo-user] Browsers not seeing symbol font Kevin O'Gorman
2009-03-25 14:15 ` Albert Hopkins
2009-03-25 16:33   ` Kevin O'Gorman
2009-03-25 14:50 ` Paul Hartman [this message]
2009-03-25 16:38   ` Kevin O'Gorman
2009-03-25 18:33     ` Paul Hartman
2009-03-26  6:35       ` Kevin O'Gorman
2009-03-26 15:39         ` Paul Hartman
2009-04-06  2:12         ` [gentoo-user] " »Q«
2009-03-25 18:41     ` [gentoo-user] " Mike Kazantsev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=58965d8a0903250750t5f835b5ar999498ecec078bae@mail.gmail.com \
    --to=paul.hartman+gentoo@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox