Mooquackwooftweetmeow
Concatenating zoölogical onomatopœia since 1999
About Mooquackwooftweetmeow
Hi! This is Mooquackwooftweetmeow, a collection of stuff by Greg K Nicholson.
Entries labelled ‘XML’
- The Twaddlebot has been unleashed
Last night version 1.0 of The Twaddle went live. It uses arbitrary XML and XSLT to generate valid XHTML pages... offline.
- Adventures in XML
I did manage to get the XML+XSL-based jiggery-pokery for The Twaddle working - quite nicely, actually. Getting the entire contents of the content field onto the page took a little bit of effort, as described on the mozillaZine forums.
- IE + XML + XSL + XHTML + W3C = Get In!
As a prelude to some major back-end renovation I'm planning for The Twaddle, I decided to see if I could get Internet Explorer 6 to display this XSL-ified weblog nicely, not accounting for IE-unsupported CSS (which is already taken care of at The Twaddle). Previously, IE displayed the DOCTYPE declaration as plain text at the top of the page; using strategic HTML commenting, I've managed to prevent it from doing so.
- Klipfolio + Atom = 1/2
OK, I can't embed an Atom feed in a Klip, but you can view Atom feeds using Klipfolio. Its Feed Reader Klip (http://www.klipfarm.com/farm.php?page=info&klip=916) accepts Atom as well as RSS 2.0 and RDF (RSS 1.0).
- Isn't XML wonderful?
Despite an hour of valiant effort, I've been unable to convince Gecko to render XHTML embedded in an Atom feed. I've tried encoding the arrow brackets, various namespace trickery... to no avail. So you're gonna have to put up with plain text URLs, until someone can show me how it's done... anybody?
- Namespaces are fairly fun
The Feed Validator (http://feedvalidator.org) gave me a thumbs-down :( Entries' IDs have to be valid URLs, you see, and I'd been using them as arbitrary labels. I'd also been leeching off these arbitrary labels in order to create anchors in the XHTML representation of the feed; those using a web browser can check they work by clicking this item's title; those using a news aggregator can visit the alternate link; in both cases, the item's title should be at the very top of the browser window.
- Wow! Internet Explorer can even mangle XML!
Here's me thinking Internet Explorer wouldn't display this feed properly! Obviously, it doesn't... but it at least has a go at mangling it, leaving this text (and this) legible. You do get a nice piece of HTML above the title, however.
- Freewebs aren't very good at MIME types... part II
Sorta got side-tracked there... Anyway, to get around the incorrect MIME type problem (which made Gecko refuse to play ball), I've tagged .xml onto the end of the weblog's files; hopefully that'll satisfy most browsers.
- Copy and paste...
By the way, those URLs in the previous post are just plain text; unless your browser parses plain text URLs, you're just gonna have to copy and paste them for now - I'm not an XML expert and the prospect of digging about trying to force Atom and XHTML to work together to produce links, isn't appealing... maybe later.
- Hurrah once more!
That w3schools (http://www.w3schools.com/) is pretty decent. I've now concocted an XSL stylesheet for this feed, so visiting its URL in a (good) web browser should display it as a nice page.
- Hurrah!
Well, then... this is an atom weblog. Why's it only in atom format? Everything on Mooquackwooftweetmeow is done the old-fashioned way - using the human brain, a plain-text editor, and no PHP, ASP, SQL or any other fanciness. And I don't want to have to copy every entry out into an XHTML page. I'm thinking of having a bash at some XSLT, to automatically generate a fancy front for the weblog; I tried it with the RSS feed, but didn't quite manage it satisfactorily; perhaps my standards are just too high (after all, I am using a free web host).
About these entries
Questions? Comments? Plaudits? Microblog at me, @gregknicholson on Identi.ca, or with the tag #xml; or email me at greg@gkn.me.uk.