Prev: Trying to install Safari Stand
Next: Safari 5.x cant copy images
From: Davoud on 13 Jun 2010 23:47
Davoud:
> > Look at your text encoding ("Default"). Check that you have the
> > appropriate font on your system. The only one mentioned in the source
> > code is Palatino.

gtr:
> So the problem is that *I* don't have the Palatino font installed?

I didn't say that, and I can't say. You tell me--is Palatino in either
of these two places: /Library/Fonts or
/Users/yourhomedirectory/Library/Fonts? If it isn't you probably need
to get it. If it is only in the latter location, try moving it to
/Library/Fonts.

I notice that in my reply that Jo�o did not render properly, probably
because I copied and pasted it. In the foregoing sentence I typed J o
option-n a o. We'll see how it comes out this time.

Davoud

--
I agree with almost everything that you have said and almost everything that
you will say in your entire life.

usenet *at* davidillig dawt cawm
From: Wes Groleau on 14 Jun 2010 00:49
On 06-13-2010 19:03, Davoud wrote:
> Look at your text encoding ("Default"). Check that you have the
> appropriate font on your system. The only one mentioned in the source
> code is Palatino.

Mac OS is quite skilled at substituting another font if the one in use
does not contain a particular glyph. The lack of Palatino would not
cause ã to be turned into a question mark (unless his Mac had NO fonts
containing that glyph).

The answer to the original question is "both." It's the OP _and_ the
web page. The web page is encoded in ISO Latin 1, but it fails to say
so in its header. OP's browser has a different default encoding, which
it uses on any page not having an encoding specified.

--
Wes Groleau

Measure with a micrometer, mark with chalk, and cut with an axe.
From: Mike Rosenberg on 14 Jun 2010 08:42
Davoud <star(a)sky.net> wrote:

> > > Here's a pic from a website as displayed in Safari 5.0 on my iMac (os
> > > 10.6.3). The tilde over the "a" in Jo�o Gilberto's name is "question
> > > marked" throughout.
> > >
> > > http://grab.by/4UD9
> > >
> > > Is this me, or is it the website? What can be done on my, or the
> > > website's end, to correct this?
> > >
> > > Simple answers for simple minds appreciated.
>
> Davoud:
> > You would have to provide the URL of the web site. A two dimensional
> > screen grab carries no evidence of what's wrong, gives no one the
> > opportunity to duplicate your problem.
>
> Never mind. I found the web page at...

I "found" the site by using the link the OP himself provided.

--
Favorite yoga position: Rosh hashavasana, the high holy pose

Mac and geek T-shirts & gifts <http://designsbymike.net/shop/mac.cgi>
Prius shirts/bumper stickers <http://designsbymike.net/shop/prius.cgi>
From: Wes Groleau on 14 Jun 2010 17:02
On 06-14-2010 12:21, Jolly Roger wrote:
> It's also always a good idea to encode such characters as HTML entities
> (either numeric or named):

I have to disagree. If my web pages are UTF-8 encoded and say so, then
the only browsers that won't render them correctly are either fifteen
years old or deliberately set to ignore the encoding spec.

Why should I trash the readability of my HTML to support those guys?

--
Wes Groleau

"Brigham Young agrees to confine himself to one woman,
if every member of Congress will do the same."
-- Weekly Republican, 1869
From: Jolly Roger on 14 Jun 2010 17:52
In article <hv65cd$nlj$1(a)news.eternal-september.org>,
Wes Groleau <Groleau+news(a)FreeShell.org> wrote:

> On 06-14-2010 12:21, Jolly Roger wrote:
> > It's also always a good idea to encode such characters as HTML entities
> > (either numeric or named):
>
> I have to disagree. If my web pages are UTF-8 encoded and say so, then
> the only browsers that won't render them correctly are either fifteen
> years old or deliberately set to ignore the encoding spec.

Actually, I've seen modern software malfunction or do the unexpected. If
that software happened to be some sort of editing software, for
instance, and mangled your extended characters into something else on
save, you'd be a little pissed, I imagine. With the extended characters
encoded as HTML entities there is no chance of that happening. IMO, it's
just a safer way to do it.

--
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.

JR
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Trying to install Safari Stand
Next: Safari 5.x cant copy images