Mooquackwooftweetmeow

Concatenating zoölogical onomatopœia since 1999

About Mooquackwooftweetmeow

Hi! This is Mooquackwooftweetmeow, a collection of stuff by Greg K Nicholson.

Entries labelled ‘the Web’

  1. Netscape 4 is newer than Internet Explorer 6 If you thought Netscape 4 was outdated, check out IE6.
  2. It's a Weblog Entry! What - the title isn't descriptive enough?
  3. IEBlank The Internet Explorer gang's collective web browsing knowledge
  4. UNcalled-for pUN The UN is a shining example of naffness.
  5. Don't hash those numbers! I just remembered XHTML ids aren't allowed to begin with numbers, so it's probably not a good idea to give weblog entries permalinks like mine.
  6. Hash those hs! A quick request of everyone who writes web pages, especially weblogs, or who designs web page templates:
  7. 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.
  8. On-the-fly page validation I wonder if this is possible. I've been dabbling with JavaScript a little recently, in order to produce The Twaddle's Expletatron and this seems like something that should be possible with JS:
  9. 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.
  10. Opera + XSL = Eugh Evidently Opera doesn't like XSL - this weblog shows up as a lot of plain text with the odd URL chucked in. The question is whether I care.
  11. 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.
  12. April Fool! Only kidding - it's not really.
  13. Apostrophes I'm now using the aforementioned RSS Reader to read this weblog. So it has to be valid Atom, the content must validate when RSSified, and still validate when XHTMLified. Thus, to save hassle relating to escape characters and other such technicalities, I'm now using straight apostrophes as quotes. It's ugly, but it works.
  14. The Twaddle is now printastic, and other web-authoring-related digressions A while ago I added a print stylesheet to Mooquackwooftweetmeow; now, The Twaddle's had the same treatment. On Saturday I also gave The Twaddle a site icon, so the site's now approaching Mooquackwooftweetmeow in completeness. Does this mean v1.0 any time soon? Probably not...maybe.
  15. RSSification 2RSS (http://www.2rss.com/) has a nice converteriser which outputs any Atom feed (such as this one - wink, wink) as RSS, available at http://www.2rss.com/software.php?page=atom2rss So now even if your newsreader isn't Atom-enabled you can still read this weblog; now you've got no excuse.
  16. Moo­quack­woof­tweet­meow's Going Nowhere I now have my own PURL top-level domain. What in the heck is a PURL top-level domain? PURL stands for Persistant Uniform Resource Locator - an URL is just a normal web address. A PURL is simply a redirect, designed so that it persists indefinitely; I can change what purl.org/mooquackwooftweetmeow/ points to, but the PURL itself never changes. This means that if I ever move to another webhost (which I don't expect to happen very soon), I can point purl.org/mooquackwooftweetmeow/ there instead. This weblog can be found at http://purl.org/mooquackwooftweetmeow/weblog, but unfortunately KlipFolio doesn't understand HTTP redirects. Bugger.
  17. 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).
  18. 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?
  19. 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.
  20. 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.
  21. 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.
  22. Freewebs aren't very good at MIME types Freewebs is obviously designed to cater for webmasters who've never heard of Jeffrey Zeldman... Like most, if not all, free web hosts, Freewebs use filename extensions to determine what MIME type to serve for a file; this is OK, until they get it wrong. Granted, Atom and XSL aren't the most commonly used file formats on the web but nonetheless Freewebs could bother serving them with the proper MIME types.
  23. 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.
  24. 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.
  25. 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).
  26. Take Back the Web This is the bit where I talk about Mozilla Firefox for a while

About these entries

Questions? Comments? Plaudits? Microblog at me, @gregknicholson on Identi.ca, or with the tag #theweb; or email me at greg@gkn.me.uk.

You Are Here

  1. Entries
  2. the Web