From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] Fonts
Date: Thu, 9 Jul 2009 11:02:00 +0100 [thread overview]
Message-ID: <20090709110200.ffa1c112.eekee57@fastmail.fm> (raw)
In-Reply-To: <de9eeab5c353876db234bcd9bf17f190@quanstro.net>
On Wed, 8 Jul 2009 23:17:22 -0400
erik quanstrom <quanstro@quanstro.net> wrote:
> > Which vera font? I just looked up http://google.gr/ in Firefox & pasted the text into a terminal using Bitstream Vera Sans Mono & don't see any missing letters. Nor do I if I set the font to Bitstream Vera Sans or Serif, or Bitstream Charter
>
> i don't recall. the date on the original conversion from .ttf is 2005.
>
> > Odd thing is if I use hget or curl to get the page I get a lot of nulls. The page is encoded in utf-8 so I don't know what the google.gr servers might be doing.
>
> ; hget http://google.gr/
> <!doctype html><html><head><meta http-equiv="content-type" content="text/html; charset=ISO-8859-7">
>
> i'm pretty sure that ISO-8859-7 != utf-8.
I guess that's server-side mucking about based on user-agent not reporting utf-8 capability or something stupid. Firefox page info feature reports the page as utf-8, and on inspection of the source:
<!doctype html><html><head><meta http-equiv="content-type" content="text/html; charset=UTF-8">
I wonder if there's some 'prefered encoding' message the UA can send to the server.
--
Ethan Grammatikidis
Those who are slower at parsing information must
necessarily be faster at problem-solving.
next prev parent reply other threads:[~2009-07-09 10:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 19:00 Devon H. O'Dell
2009-07-08 19:11 ` Joseph Stewart
2009-07-08 19:11 ` Joseph Stewart
2009-07-08 19:49 ` J. R. Mauro
2009-07-08 19:49 ` Bakul Shah
2009-07-08 20:05 ` Josh Wood
2009-07-08 20:14 ` erik quanstrom
2009-07-08 20:15 ` J. R. Mauro
2009-07-08 20:44 ` erik quanstrom
2009-07-08 21:44 ` J.R. Mauro
2009-07-08 21:51 ` erik quanstrom
2009-07-08 22:21 ` J.R. Mauro
2009-07-09 2:21 ` Ethan Grammatikidis
2009-07-09 3:17 ` erik quanstrom
2009-07-09 5:25 ` Russ Cox
2009-07-09 10:10 ` Ethan Grammatikidis
2009-07-15 21:01 ` David Leimbach
2009-07-15 21:34 ` Russ Cox
2009-07-09 10:02 ` Ethan Grammatikidis [this message]
2009-07-08 20:50 ` John Floren
2009-07-08 21:42 ` J.R. Mauro
2009-07-08 21:47 ` erik quanstrom
2009-07-08 21:49 ` J.R. Mauro
2009-07-08 20:23 ` Lyndon Nerenberg
-- strict thread matches above, loose matches on Subject: below --
2009-07-09 15:43 Chad Brown
2009-07-09 15:55 ` Federico G. Benavento
2002-01-07 19:04 forsyth
2002-01-07 18:41 Russ Cox
2002-01-07 20:16 ` Fariborz Tavakkolian
2002-01-07 9:38 skipt
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=20090709110200.ffa1c112.eekee57@fastmail.fm \
--to=eekee57@fastmail.fm \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).