converting to div was easy

am 01.01.2008 02:58:35 von unknown

Post removed (X-No-Archive: yes)

Re: converting to div was easy

am 01.01.2008 03:37:44 von dorayme

In article ,
richard wrote:

> http://littleworldofours.com/1960e.html
>
> As before, it validates with a few warnings I'll clean up later.
>
> In FF it is presented nearly the way I expected.
> In IE, however, the output is less than equal.
>
> So what tricks can I apply to make IE display nearly the same as FF?
>

Looks about the same in both. Why do you want it to look this
way? What way do you want it to look?

O my... I feel so seedy today... your colours and layout are not
helping...

--
dorayme

Re: converting to div was easy

am 01.01.2008 17:43:22 von lws4art

richard wrote:
> http://littleworldofours.com/1960e.html
>
> As before, it validates with a few warnings I'll clean up later.
>
> In FF it is presented nearly the way I expected.
> In IE, however, the output is less than equal.
>
> So what tricks can I apply to make IE display nearly the same as FF?
>

You do know that to use CSS does *not* mean *never* use tables. One
could argue that your page contains tabular data that would best be
served in a table.

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

Re: converting to div was easy

am 01.01.2008 20:27:54 von unknown

Post removed (X-No-Archive: yes)

Re: converting to div was easy

am 02.01.2008 11:46:25 von Andy Dingley

On 1 Jan, 16:43, "Jonathan N. Little" wrote:

> You do know that to use CSS does *not* mean *never* use tables. One
> could argue that your page contains tabular data that would best be
> served in a table.

Agreed. I'd strongly suggest

for this. The generator language
should cope perfectly well with either approach. A bit of colspan, if
you wish.

Richard could also lose the

elements in favour of using a border
from CSS (top, bottom or both)

Some padding (left and right) would improve readability too. It's hard
to read text that runs right into a vertical border line.

The double curly quote characters are also incorrectly represented by
the numeric entities “ & ” They ought to be “ and
” instead.

The reason for this is a little obscure. The "keyboard code" to enter
them is indeed 147 or 148 decimal, and those are valid character
references in the Windows 1252 codepage. This web page is even being
served as Windows-1252 (Not something I'd do, but it's perfectly
correct to do so). However the rule for numeric entities in HTML is
that the numbers _always_ refer to the Unicode codepoint, no matter
what the page's encoding. 147 & 148 aren't correct in Unicode, thus
aren't correct in HTML.