From: Mike Kazantsev <mike_kazantsev@fraggod.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Browsers not seeing symbol font
Date: Wed, 25 Mar 2009 23:41:55 +0500 [thread overview]
Message-ID: <20090325234155.24b56924@coercion> (raw)
In-Reply-To: <9acccfe50903250938h618c3409w451cfbb7a1738ff8@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On Wed, 25 Mar 2009 09:38:31 -0700
"Kevin O'Gorman" <kogorman@gmail.com> wrote:
>> 2. Character encodings are easy: use Unicode. :)
>> http://www.unicode.org/charts/symbols.html
>
> Yes they're easy. My question is about whether they have any effect
> on use of Symbol So far I see no evidence of it.
They shouldn't, since such fonts' glyphs aren't aligned with any
encoding afaik - it'd be rubbish, at best.
> It works in MS Works, Dreamweaver and on Gentoo, in OpenOffice.
Well, it also works for me, if I change 'Symbol' to 'Luxi Mono', for
example, which is a valid font name on my system.
Since handling of such stuff as font-family is defined by browser, it's
at best unwise to rely on 'Symbol' font definition, and, while IE6 is
still around, even more so.
You can use any decent font-rendering library to make
browser-independent representation of such stuff, which is probably the
only solution if you care whether end-user can see it or not.
--
Mike Kazantsev // fraggod.net
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2009-03-25 18:45 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
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 ` Mike Kazantsev [this message]
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=20090325234155.24b56924@coercion \
--to=mike_kazantsev@fraggod.net \
--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