Re: [WSG] Need Assistance...

2004-01-03 Thread Adam Carmichael
Rob Halff wrote:

!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.1//EN
http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd;
html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en
head
meta http-equiv=Content-type content=text/html; charset=iso-8859-1 /
And since your using PHP, add this to your template, or what have you, 
to make sure that the webserver sends the appropriate Content-Type if 
the UA can read XHTML.

?php
if(stristr($_SERVER['HTTP_ACCEPT'],application/xhtml+xml))
  {
header('Content-Type: application/xhtml+xml');
  }
?
(Just as a tidbit, MSIE appears to be able to parse XHTML just fine, but 
when you throw the correct Content-Type at it, MSIE thinks it can't read 
it, so it'll ask the user to select an application which can read it - 
thankfully MSIE does not add application/xhtml+xml to it's accept 
string, so you won't get this problem.)

Out of curiosity, what does the CF source look like to do the same thing?

Adam

--
/--\
|Adam Carmichael, A+, 2xMCP (Windows 2000), Cert IV Helpdesk Admin |
|[EMAIL PROTECTED]   /( _,-,_ )\ _|  |_  /,||   |
|#1 Computer Services   \`/ \'/ _|  |_||   |
|BSD/UNIX Network Engineer\ /o\ /o\ /|  |_||_  |
\--/
*
The discussion list for http://webstandardsgroup.org/
* 



RE: [WSG] Need Assistance...

2004-01-03 Thread Chris Stratford

Hey Rob,
Wow thanks for all that help!
I don't really know how to code XHTML...
I mean I don't know the difference - I do know that it requires
everything to close like: br / and weird stuff like that...

I think at the moment I would rather stick to HTML - just because I find
it easier... and I don't know the little things about XHTML - although
im interested, I might make another website in XHTML if I get the
time (probably a photo album or something)...

I will try that code for the heading, since it looks very interesting!
I didn't realise CSS could transform text??
I think I once saw a tag: content:
It was in a menu I think it added  that before the menu when you
hovered over it... very interesting...
Thanks for that tip!
:)

-

at the moment, I really just need help with that IE bug, of not
displaying the code properly...
what I will do is, I will first go through and close all the P tags...

thanks for that.
I will write back and let you know how its going!
Cheers!

THANKS FOR THE GREAT HELP!

-
Chris Stratford
[EMAIL PROTECTED]
www.neester.com
-


-Original Message-
From: Rob Halff [mailto:[EMAIL PROTECTED] 
Sent: Saturday, January 03, 2004 8:52 PM
To: [EMAIL PROTECTED]
Subject: Re: [WSG] Need Assistance...


Ok, your lucky I'm in a helping mood :-)
Not many things have to be done to make you site XHTML strict.
I will only go throught the first page of your site:

1.
Change the doctype and head from:
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
http://www.w3.org/TR/html4/loose.dtd;
HTML
HEAD
META http-equiv=Content-Language content=en-au
META HTTP-EQUIV=content-type CONTENT=text/html; charset=ISO-8859-1

to:
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.1//EN
http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd;
html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en
head
meta http-equiv=Content-type content=text/html; charset=iso-8859-1
/

note: also use lowercase for tags..

2.
This could be changed just for fun:
h1nbsp;W W W . N E E S T E R . C O Mnbsp;/h1

to:
h1www.neester.com/h1
and add this to your div#div_header h1 class statement:
letter-spacing: 0.5em;
padding-left: 0.3em;
padding-right: 0.3em;
text-transform: uppercase;

3. pI apoligise for the delay,...
This tag never seems to be closed anywhere.

4.
ul
 listrikeINDEX - Build Page/strike
  ...
strike is not valid xhtml strict, also you are not closing the the
li
tags.
try something like:
ul class=checklist
  liemINDEX - Build Page/em/li


Where the checklist class look like:
.checklist em {
text-decoration: line-through;
}

5. /ulbr
Probably you want to close the open p tag here (see point 3). So make
it
/ul/p

6. pNEWS ITEM HERE   Close it :-)

7. In the footer use a span or something with a class:
so UBTime/B/U, becomes span class=infoboxTime/span
where the class look something like:
 .infobox {
text-decoration: underline;
font-weight: bold;
}
8. USE LOWER CASE FOR TAGS! :-D

9. update your validation button to xhtml strict.

Greeting,

Rob Halff

--- Original Message -
From: Chris Stratford
To: [EMAIL PROTECTED]
Sent: Saturday, January 03, 2004 9:00 AM
Subject: [WSG] Need Assistance...


Ok.
Internet Explorer Bug here.
How can I get around this.

www.neester.com

the NEWS REEL at the bottom.
the background is meant to be YELLOW!!
With a dotted border.

In my IE (v6) it doesn't work.
It only works when you hightlight the text, or when you scroll over it
(like
hide it, then show it again).
It works 100% in mozilla, and on a smaller resolution of IE.
Currently im running 1400x1050 and its very very annoying.

Im not going to make any changes for the next few hours.
Any help would be APPRECIATED GREATLY!
btw - the website is 100% CSS compliant too.
Not 100% IE compliant I guess. :P

Thanks!

-
Chris Stratford
[EMAIL PROTECTED]
www.neester.com
-


*
The discussion list for http://webstandardsgroup.org/
* 


*
The discussion list for http://webstandardsgroup.org/
* 



RE: [WSG] Need Assistance...

2004-01-03 Thread Peter Firminger
Hi Adam,

To send the header, I believe it is cfcontent type=application/xhtml+xml

I use cfcontent type=text/xml for XML and RDF AGLS harvest control lists
and metadata. e.g.: http://gtconnect.webboy.net/meta/index.cfm (HCL) and
http://gtconnect.webboy.net/meta/metadata.cfm (metadata for other documents
that can't hold embedded AGLS data).

Not sure about parsing the request for the accept string, but seriously, why
would you bother if you are marking up content for presentation and nothing
else?

I really really really don't think it's good advice to suggest that Chris
changes to XHTML without reason (sorry lucky Rob) so I'm glad he decided not
to.

There is absolutely nothing wrong with using valid HTML 4.01 (or even
earlier versions like 3.2) for presentation. XHTML only comes in to play if
you are presenting structured data with a reason to use mark-up for purposes
other than presentation. You cause far more problems going to XHTML than you
fix, especially 1.0 strict or 1.1 and even more so if you are building a CMS
to run it.

Having said that, if you're willing to do the extra work to go to XHTML on a
site that doesn't really need it (like we did with the WSG site for example)
and you're confident that your clients won't have any chance of screwing it
up, then go ahead. I'm not saying XHTML is bad, but there are no compelling
reasons around to make it worth the trouble of changing the mime type etc.
if you don't use the xml component for the data related reasons.

We did quite a few XHTML sites before realising this. Others (and big names
too) have come to the same conclusions.

We will be re-working the webboy/maxdesign/purpleprodigy site back into HTML
4.01 shortly and I'm thinking about doing the same with WSG as it is
technically incorrect at the moment (though I think the whole issue is
bollocks) sending it as text/html and I'm not willing to change it while the
major browser doesn't like it.

There has been much discussion on this list and in other places about this.
Might be a good idea to log in and do a search on the WSG archive.

P

 -Original Message-
 From: Adam Carmichael [mailto:[EMAIL PROTECTED]
 Sent: Saturday, January 03, 2004 11:19 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [WSG] Need Assistance...


 Rob Halff wrote:

  !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.1//EN
  http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd;
  html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en
  head
  meta http-equiv=Content-type content=text/html;
 charset=iso-8859-1 /
 

 And since your using PHP, add this to your template, or what
 have you,
 to make sure that the webserver sends the appropriate Content-Type if
 the UA can read XHTML.

 ?php
 if(stristr($_SERVER['HTTP_ACCEPT'],application/xhtml+xml))
{
  header('Content-Type: application/xhtml+xml');
}
 ?

 (Just as a tidbit, MSIE appears to be able to parse XHTML
 just fine, but
 when you throw the correct Content-Type at it, MSIE thinks it
 can't read
 it, so it'll ask the user to select an application which can
 read it -
 thankfully MSIE does not add application/xhtml+xml to it's accept
 string, so you won't get this problem.)

 Out of curiosity, what does the CF source look like to do the
 same thing?

 Adam

 --
 /-
 -\
 |Adam Carmichael, A+, 2xMCP (Windows 2000), Cert IV Helpdesk
 Admin |
 |[EMAIL PROTECTED]   /( _,-,_ )\ _|  |_
 /,||   |
 |#1 Computer Services   \`/ \'/ _|  |_
 ||   |
 |BSD/UNIX Network Engineer\ /o\ /o\ /|  |
 _||_  |
 \-
 -/
 *
 The discussion list for http://webstandardsgroup.org/
 *



*
The discussion list for http://webstandardsgroup.org/
*