What's with the fonts on this page?
OPERA
Look at any apostrophe. There is a capital A inserted there. Anybody know why this is happening?
Same in Firefox. Could it be how Opera is using a font supplied by Windows XP?
"Try and put yourself in my shoes for a moment. I was an avid audiophile in the early 90�'s going
virtually weekly to audio shops and homes auditioning people�'s/store�'s systems. I was hooked from
one of my Dad�'s friends who in the early 1990s had thousands of laserdisc movies and a big discrete
surround sound system with separates room treatments the whole works."
Beauregard T. Shagnasty
> http://www.canuckaudiomart.com/forum/viewtopic.php?t=11401
> Look at any apostrophe. There is a capital A inserted there. Anybody
> know why this is happening? Same in Firefox. Could it be how Opera
> is using a font supplied by Windows XP?
It isn't Opera, nor Firefox either. My guess is the bulletin board font
chosen for the body of posts is a Mac font, and the author composed in a
Microsoft program (possibly using MS SmartQuotes) and the glyph isn't in
your fallback font. The font assigned to the post bodies is "Lucida
Grande" - a Mac font.
From the page's style sheet:
.postbody {
font-size: 1.3em;
line-height: 1.4em;
font-family: "Lucida Grande", "Trebuchet MS", Helvetica, Arial,
sans-serif;
}
I read another page that suggested you install Safari for Windows, and
it will add a Windows version of Lucida Grande to your fonts. (but I
wouldn't do that.)
--
-bts
-Friends don't let friends drive Windows
SaGS
news:fRnHm.1867$Ce1....@newsfe06.iad...
> http://www.canuckaudiomart.com/forum/viewtopic.php?t=11401
> Look at any apostrophe. There is a capital A inserted there. Anybody
> ...
The file contains a <META/> tag specifying the character encoding as being
UTF-8.
The part between "90" and "s" is encoded as the following 5 bytes:
bytes (hex) Corresponding char after UTF-8 decoding
------------ -----------------------------------------------
C3 80 U+00C2 "Latin Capital Letter A With Circumflex"
E2 80 99 U+2019 "Right Single Quotation Mark"
The display is correct (assuming you see an accented A, not a plain
unaccented A), that's what the file contains. Adding/ removing fonts *should
not* "fix" the issue.
Since I encountered similar errors in other places, I'm curios if anyone has
an explanation as where do these come from.
Peter Krefting
> Since I encountered similar errors in other places, I'm curios if anyone
> has an explanation as where do these come from.
It is usually a case of an incorrectly encoded page. The
"capital-A-with-something-on-it-before-a-lot-of-characters" is normally a
sign of a UTF-8 page being sent out as ISO 8859-1 or something similar.
In this case, the Info panel tells us that the page is indeed correctly
labelled as UTF-8, so in this case it is probably a doubly-encoded page,
i.e., the source data was in UTF-8 but were thought to be ISO 8859-1 and
then converted to UTF-8 under that assumption, leading to the "capital-A"
problem even with the page being sent out as UTF-8.
--
\\// Peter Krefting - Core Technology Developer, Opera Software ASA
Swifty
> Since I encountered similar errors in other places, I'm curios if anyone has
> an explanation as where do these come from.
When I've encountered these, they have usually been because the webpage
was created using something like Word, saving as HTML. Then the page was
put on a webserver and was served in such a way that the browser didn't
preserve the formatting. Presumably because the encoding wasn't preserved.
--
Steve Swift
http://www.swiftys.org.uk/swifty.html
http://www.ringers.org.uk
Whiskers
> SaGS wrote:
>> Since I encountered similar errors in other places, I'm curios if anyone has
>> an explanation as where do these come from.
>
> When I've encountered these, they have usually been because the webpage
> was created using something like Word, saving as HTML. Then the page was
> put on a webserver and was served in such a way that the browser didn't
> preserve the formatting. Presumably because the encoding wasn't preserved.
Some people like to compose articles for web forums using a program on
their own computer - that certainly helps overcome connectivity or
stability problems with the web forum, which can get expensive on dial-up
or lose all your typing when the connection breaks. Unfortunately, some
of those people use a full-blooded 'word processor' and don't set it to
compose in 'plain text only', and when they copy/paste the result into the
web forum interface various artefacts get carried across and interfere
with the code of the web site's own composer. There can also be character
set clashes.
I've seen the same sort of thing in emails sent from webmail.
--
-- ^^^^^^^^^^
-- Whiskers
-- ~~~~~~~~~~
andreas koppa
reading yours.
On Mon, 02 Nov 2009 10:58:49 -0500, Whiskers <catwh...@operamail.com>
wrote:
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Swifty
> Some people like to compose articles for web forums using a program on
> their own computer - that certainly helps overcome connectivity or
> stability problems with the web forum, which can get expensive on dial-up
> or lose all your typing when the connection breaks.
I've seen instances with � appearing in English webpages authored by BBC
journalists, probably from a similar sequence to that in the original
post. At least the BBC has a feedback mechanism for reporting such
problems, which works quite well.