Re: Backslash ( \ ) in ordinary text
- From: "Jukka K. Korpela" <jkorpela@xxxxxxxxx>
- Date: Wed, 18 Aug 2010 23:18:18 +0300
James Dow Allen wrote:
Thank you very much to all responders!
This seems like a friendly group!
We are, at times... but beware of the Dark Side of alt.html! :-)
I've just now modifed the "qstyle.css" as you suggested.
(But omitted the "xxx," as I don't have any particular preference.)
Perhaps kind readers will click again and verify problem
has gone away.
Strangely, it hasn't. The page
http://fabpedigree.com/s061/f004932.htm
refers to "../qstyle.css", i.e.
http://fabpedigree.com/qstyle.css
(I admit that I accidentally tried http://fabpedigree.com/s061/qstyle.css first - and saw the funniest 404 error pages ever, though I'd hesitate to use such a page on a business site!)
which contains
td {font-family: serif; font-size: large}
and comes with HTTP headers saying
Last-Modified: Tue, 29 Sep 2009 13:36:30 GMT
And -- displaying my ignorance again -- what
exactly is needed to clear any cache?
Beats me! But this does not seem to be any normal cache issue. Even when I access the CSS resource on a browser that has never been used to retrieve it before, I get the version with font-family: serif. I think this is something between your authoring software and the server.
The only other errors reported by the HTML validator were
missing </small> after <small>, which I omitted deliberately
to save space: the <small> within <td> ... <td> is cancelled
by the end of the <td> region, or at least that's what I've
observed. Am I wrong again?
In practice browsers tend to imply a closing tag for any open text-level element when they encounter </td>. But it's still wrong, and I would not count on it. Saving a few characters is really immaterial. The load time of web pages is dominated by the size of images, bulky script codes, or sometimes very verbose CSS or HTML markup, but closing tags aren't really that verbose. And you would probably save more by using CSS for all rendering issues than by leaving elements unclosed.
By the way, it seems that Batang is the font that (some versions of) IE use as the font corresponding to the CSS keyword serif and that the only Ascii character that it gets wrong is the backslash "\". Batang has been designed especially for the Korean language, and this explains why "\" has been replaced by the won symbol, the symbol for the monetary unit of South Korea (looking like overstruck "W") - but it's still all wrong, since the won symbol has a code position of its own and should appear there, in any font that wants to support it. - And encoding "\" as "\,", though permitted in HTML, is useless, since the problem does not depend on the representation of the character in HTML source but in rendering, in some fonts.
--
Yucca, http://www.cs.tut.fi/~jkorpela/
.
- References:
- Backslash ( \ ) in ordinary text
- From: James Dow Allen
- Re: Backslash ( \ ) in ordinary text
- From: Sherm Pendley
- Re: Backslash ( \ ) in ordinary text
- From: James Dow Allen
- Backslash ( \ ) in ordinary text
- Prev by Date: Re: Form action= ?
- Next by Date: Re: Backslash ( \ ) in ordinary text
- Previous by thread: Re: Backslash ( \ ) in ordinary text
- Next by thread: Re: Backslash ( \ ) in ordinary text
- Index(es):
Relevant Pages
|
