XHTML output is now enabled for all browsers that support it. (Translation: not Internet Explorer.) This is not trivial, as it means each page must conform to strict XML standards.
If you come across a page that is not well formed, you will get a parser error. I've been using XML myself on a.cc for a while, and I know there are many of them. You should do two things if that happens:
report the url on this thread, or to me via PM when this thread is closed.
append ?xml=off (or &xml=off) to the URL to temporarily disable XML output
Note that the &foo; HTML entities (e.g., —) are not valid XHTML and are not translated. The number codes will still work. I will some day map the HTML entities to number codes automatically for convenience.
Google maps on profile pages are not working yet.
The switch to XML is primarily because I'm a masochist and secondarily because it forces the strictest adherence to the standards, eliminating most cross-platform issues. It will also let me enable MathML, which I have been testing.
Firefox's copy and paste works properly in XML mode, so the missing line breaks in code boxes will no longer be a problem.
(You'll need to refresh before Spell Check works.)
I've been using XML myself on a.cc for a while, and I know there are many of them.
There can't be too many left. I haven't seen any parsing errors for ages.
You should add a Valid XHTML link at the bottom (with the referral check against W3C checker).
The XML is well formed, but there are plenty of XHTML violations.
Update: profile maps are working.
{"name":"599847","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/1\/6\/1639d53d40eeaabf7daf82ce0cdb95a3.jpg","w":738,"h":562,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/1\/6\/1639d53d40eeaabf7daf82ce0cdb95a3"}
Note that the &foo; HTML entities (e.g., —) are not valid XHTML and are not translated.
Aww.
I actually thought they were XHTML valid actually. Maybe it's the XML parser not liking them when you don't use a doctype.
I actually thought they were XHTML valid actually. Maybe it's the XML parser not liking them when you don't use a doctype.
I agree (and in fact the doctype I'm using has them specified), but Opera refuses to display them.
Ah, it's Opera's fault. Okay then.
{"name":"599863","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/b\/0\/b06223ea6b99310806e737adc40b1c24.jpg","w":940,"h":596,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/b\/0\/b06223ea6b99310806e737adc40b1c24"}
It would be simpler if you just pasted in the URL (and the error message if so inclined) in plain text.
XML Parsing Error: not well-formed Location: http://www.allegro.cc/depot/KiGB/ Line Number 220, Column 16: ~ Mario & Yoshi<br /> ---------------^
http://www.allegro.cc/iotd/view/2005-03-10
XML Parsing Error: mismatched tag. Expected: </img>. Location: http://www.allegro.cc/iotd/view/2005-03-10 Line Number 81, Column 3: </div><div style="border-top: dashed #999 1px; margin: 0.5em; padding: 0.5em;" id="c-472"> --^
Currently the front page of the forums has this: "Allegro & Windows 7"
This page is completely broken for me:
http://www.allegro.cc/forums/thread/602399/840964#target
error on line 100 at column 146: Encoding error
I approve.
This thread is broken: http://www.allegro.cc/forums/thread/585707
When posting (I mean after clicking on 'post') I often have that one, which goes away after a refresh (and my post is taken in account)
XML Parsing Error: mismatched tag. Expected: </br>.
Location: http://www.allegro.cc/forums/reply/602508
Line Number 60, Column 233: <td colspan="2"><div style="margin: 1em; text-align: center; border: solid red 1px; padding: 1em;">Slow down ... you are over working your fingers, your keyboard, and MY SERVER!
<br><br>Only one post is allowed per 30 seconds.</div></td>
doubt this is a bug, just by design and nothing to do with the xhtml 
but on the hover doesn't work with code:
{"name":"600001","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/d\/3\/d384072340152a5915e138b9986ee6b7.png","w":324,"h":144,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/d\/3\/d384072340152a5915e138b9986ee6b7"}
It IS a bug. He forgot two / ;-p
I am 100% sure I got an error here:
http://www.allegro.cc/forums/board/4
Problem is, when I refreshed, it went away...