Has someone published a modernized set of rules for web-safe fonts
that ensure larger character sets are displayed correctly?
You'd think that by 2014 curly quotes would be safe, but I encountered
missing-glyph icons for some just the other day, on a page where the
character set was UTF-8, using the latest version of Firefox on
At my last job, one of the single-source targets for some of my docs
was 7-bit ASCII.
On Mon, Aug 4, 2014 at 9:08 AM, Davis, David
> Any modern operating system comes with unicode fonts which contain a
> perfectly good selection of glyphs for the sort of punctuation characters
> we're talking about here.
> Even Windows XP (and officially end-of-life, dead, deceased and gone to join
> the choir invisible operating system) has fonts with glyphs for curly quotes.
> -----Original Message-----
> From: robert.lauris...@gmail.com [mailto:robert.lauris...@gmail.com] On
> Behalf Of Robert Lauriston
> Sent: 04 August 2014 17:05
> To: Davis, David; firstname.lastname@example.org
> Subject: Re: Quoted speech
> I think you're missing my point. On my computer, the text on Japanese,
> Korean, and Chinese sites is mostly a bunch of boxes, since those fonts
> aren't installed and the glyphs don't exist in whatever font my web browser
> is substituting.
> On Mon, Aug 4, 2014 at 1:28 AM, Davis, David
> <david.da...@non.schneider-electric.com> wrote:
>> Oh come on, Robert, it's not 1995 any more. There is such a thing as Unicode.
>> I'd like to see you write a webpage in Japanese using just ISO 8859-1
>> Message: 3
>> Date: Fri, 1 Aug 2014 09:53:43 -0700
>> From: Robert Lauriston <rob...@lauriston.com>
>> To: "email@example.com" <firstname.lastname@example.org>
>> Subject: Re: Quoted speech
>> Content-Type: text/plain; charset=UTF-8
>> Coding the HTML correctly doesn't ensure that the reader's system has the
>> necessary character.
>> Best practice is generally to stick to the extended 8-bit ASCII
>> character set (ISO 8859-1), which does not include U+2018, U+2019,
>> U+201C, or U+201D.
>> On Fri, Aug 1, 2014 at 12:48 AM, Davis, David
>> <david.da...@non.schneider-electric.com> wrote:
>>> There should be no problem with those characters in HTML, so long as
>>> you put the correct declarations in the Header part of the page (to declare
>>> what character set you are using). If you look at a Japanese, Korean or
>>> Chinese site, for instance, you'll generally see they manage to have a
>>> plenty of non-ASCII characters in them ;) Alternatively, you can put &
>>> escape sequences in your HTML for those characters.
You are currently subscribed to framers as arch...@mail-archive.com.
Send list messages to email@example.com.
To unsubscribe send a blank email to
Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.