At 12:44 PM 11/11/2007 , you wrote:
>Well the time has come for you to make your own mind up. As you saw,
>loro, Cary and me have different preferences and we all have good
>reasons for ours.
>I'll try to sum up both choices, doctype and charset:
>1) 4.01 strict
>Cleaner from a purist point of view, no presentation in the markup.
>2) 4.01 traditional
>Allows some presentational attributes and makes it more possible to
>cater for old browsers without css support.
Is "traditional" the same as Transitional?
>The simplest and most compatible of all. You need to restrict
>yourself to the first 127 characters and write everything else als
>entities like ä – “.
The need to use an umlaut entity is clear to me - no way to get that from
my keyboard - I think.
I have always seen NTabs Special Character selection for pasting, now I
know what it for. Took me long enough!
It would be nice it Tidy had a drop menu choices with the Character next to
I see no curly quotes in the Special Character menu list.
But, to be clear, if I needed curly quotes I would use: “ and get "
It seems curlies are preferred.
For straight quotes I would use the keyboard and get "
For me, the entity – is longer than the keyboard - .
Is that the reason for using &ndash instead of - ?
>In practice you need to run a
>converter over stuff you typed and validate to catch the odd missed
Tidy converts a pasted curly quote to “
So, I guess I am safe there as long as I *remember* to run Tidy.
I added “ and ” to my Blockquote clip:
^!InsertHtml <blockquote cite='****'>“ and
”^p^$GetSelection$^p<p class="source"><strong>Source:</strong> Source
This should be a good prompt/reminder for me to use them.
This is sloooowly oozing into my brain.
So, I think I can live with 95 printable characters and hope I do not
introduce anything into my pages which are not compatible.
>I have tried to be fair and objective to all choices, now it's for you
>to choose which one suits you best. Axel
Looks this will be my choice:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
<meta http-equiv="content-type" content="text/html; charset=us-ascii">
Thanks for taking the time to write up this comparison.
I was not successful in finding such a thing on the web, but I am sure it
is out there.