RE: [WSG] IE problem with ?xml version=1.0 encoding=iso-8859-1?

2005-08-26 Thread Patrick Lauke
 Duncan Stigwood

 ?xml version=1.0 encoding=iso-8859-1?
 which I think I understand is the Document Character Set, 
 i.e. V. important.
 
 However having it in my document makes IE screw up all 
 absolute positioning!!

IE goes into quirks mode when there's ANYTHING in front of the opening html 
...
tag. Just drop the ?xml ...? declaration, as it's still valid as per Appendix 
C
of the XHTML spec http://www.w3.org/TR/xhtml1/#C_1

Patrick
__
Patrick H. Lauke
Webmaster / University of Salford
http://www.salford.ac.uk
__
Web Standards Project (WaSP) Accessibility Task Force
http://webstandards.org/
__
**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



Re: [WSG] IE problem with ?xml version=1.0 encoding=iso-8859-1?

2005-08-26 Thread sam sherlock




You can leave out the xml prolog, its IE messing things up again (yet
again - over and over)

if you choose to put it in IE (aka inferior explorer) will use
quirksmode and ignore all mannor of things such as absolute
positioning, and a whole raft of other things, other compliant browsers
will be fine and respond according to the rule book.


sam



Duncan Stigwood wrote:

  HELP!

Tidy puts in 
?xml version="1.0" encoding="iso-8859-1"?
which I think I understand is the Document Character Set, i.e. V. important.

However having it in my document makes IE screw up all absolute positioning!!

What am I doing wrong?

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

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**


  







Re: [WSG] IE problem with ?xml version=1.0 encoding=iso-8859-1?

2005-08-26 Thread James Ellis
Hi

Depending on the tidy library you are using, you should be able to
pass in the parameter

add-xml-decl as boolean false. The Tidy library that you use should
then not add the XML prolog.

See:
http://tidy.sourceforge.net/docs/quickref.html#add-xml-decl;

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

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



Re: [WSG] IE problem with ?xml version=1.0 encoding=iso-8859-1?

2005-08-26 Thread Duncan Stigwood
Thank you both of you!

I love this list :)
**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



RE: [WSG] IE problem with ?xml version=1.0 encoding=iso-8859-1?

2005-08-26 Thread Richard Ishida
Duncan,

As the others have said, you can omit the declaration if you want to avoid
affecting standards mode in IE (see
http://www.w3.org/International/articles/serving-xhtml/ )

The key thing is to check that your file is encoded in the encoding you
want, ie. do you want it to be encoded in iso-8859-1 or in utf-8?  I'm just
about to release a new article that might help here:
http://www.w3.org/International/questions/qa-changing-encoding




If you want more information about this:

The 'Document Character Set' is actually utf-8 (see
http://www.w3.org/International/questions/qa-doc-charset )

You should at least check that you do declare the encoding in a meta tag,
and that it is correct. For more info see
http://www.w3.org/International/tutorials/tutorial-char-enc/

HTH,
RI


Richard Ishida
W3C

contact info:
http://www.w3.org/People/Ishida/ 

W3C Internationalization:
http://www.w3.org/International/ 

Publication blog:
http://people.w3.org/rishida/blog/
 
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of Duncan Stigwood
 Sent: 26 August 2005 13:32
 To: wsg@webstandardsgroup.org
 Subject: [WSG] IE problem with ?xml version=1.0 
 encoding=iso-8859-1?
 
 HELP!
 
 Tidy puts in
 ?xml version=1.0 encoding=iso-8859-1? which I think I 
 understand is the Document Character Set, i.e. V. important.
 
 However having it in my document makes IE screw up all 
 absolute positioning!!
 
 What am I doing wrong?
 
 Thanks guys
 **
 The discussion list for  http://webstandardsgroup.org/
 
  See http://webstandardsgroup.org/mail/guidelines.cfm
  for some hints on posting to the list  getting help
 **
 

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

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



RE: [WSG] IE problem with ?xml version=1.0 encoding=iso-8859-1?

2005-08-26 Thread Patrick Lauke
To make things a bit more explicit (and I hope I'm not talking rubbish,
as I'm going from memory here)

 Richard Ishida

 The key thing is to check that your file is encoded in the 
 encoding you
 want, ie. do you want it to be encoded in iso-8859-1 or in 
 utf-8? 

The default encoding of an XML document that's assumed in the absence
of the ?xml ...? is utf-8.

 You should at least check that you do declare the encoding in 
 a meta tag,
 and that it is correct.

Although it's best to also send the correct HTTP header to specify
the document's encoding (otherwise it's the weird situation in which a
browser needs to start receiving the document, then find out via the
META what encoding it's in...which can cause problems in edge cases,
if I remember correctly). Of course, the header and the META should
not contradict each other either.

Patrick
__
Patrick H. Lauke
Webmaster / University of Salford
http://www.salford.ac.uk
__
Web Standards Project (WaSP) Accessibility Task Force
http://webstandards.org/
__
**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



Re: [WSG] IE problem with ?xml version=1.0 encoding=iso-8859-1?

2005-08-26 Thread Anders Nawroth



Patrick Lauke skrev:


Richard Ishida
   

You should at least check that you do declare the encoding in 
a meta tag,

and that it is correct.
   



Although it's best to also send the correct HTTP header to specify
the document's encoding (otherwise it's the weird situation in which a
browser needs to start receiving the document, then find out via the
META what encoding it's in...which can cause problems in edge cases,
if I remember correctly). Of course, the header and the META should
not contradict each other either.
 

If you are using META providing charset info, put it immediately after 
the HEAD element, to not not make
this construct more weird than necessarily. Even if using HTTP headers 
is the first choice,
including the META tag can prove useful for people saving the page for 
offline use,
as HTTP headers are usually not saved with the page. I always use both 
methods.


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

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**