1) HTML 4.01 Strict, unless you've got really ambitious plans and a very good idea what user agents will be in play: keeping in mind Internet Explorer doesn't support XHTML served as application/xhtml+xml, so it's still going to be parsed as straight HTML in that browser.
2) So far as I'm aware, that's what mod_gzip does on servers that support it. Whitespace supposedly compresses really well, so there's no real harm in leaving it if your server is compressing content. For a non-server-side-dependent solution, http://www.freshstartcafe.com/css-compress/ looks good for CSS compression, and if you're interested in compressing your HTML + Javascript I think you'd probably have to do it manually. I can't see how it'd make any great different so search engines, particularly if your pages are well-formed. Regards, Josh. On 1/31/06, Roberto Santana <[EMAIL PROTECTED]> wrote: > Hello, > > 1) > > I'm going to create a new website fully standard, CSS, XHTML, WAI... > > I'd like to know your opinion about which DTD I should use, advantages and > disadvantages... > > XHTML 1.0 Transitional > XHTML 1.0 Strict > XHTML 1.1 > > ???? > > 2) > > What's your opinion about HTML, CSS and Javascript compresion techniques, > removing spaces, line breaks... these could save a lot of bandwidth in a > high visited website... But this could affect to spiders, Googlebot? > > Thanks! > ________________________________ > :: Roberto Santana ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
