Dedicated to my late brave, beautiful and silly mummy, Debra Ross. I love you mumster.

Skip navigation

Category archive for xml

Because archives are so much easier than having just hundreds of posts on the home page. I learned that the hard way.

Camino and Google Reader atom problems

Sharon777 on Twitter pointed out a possible problem with either the Camino browser or Google Reader. If you use Camino to browse someone’s Google Reader Shared Items page (such as mine or Whole Wheat Radio’s), an web feed notification icon doesn’t appear in the address bar:

Google Reader in Camino not showing a web feed icon

However if you click View Page Source in the View menu, you can clearly see the link to the web feed:

Google Reader in Camino not showing a web feed icon

I can’t really think why it shouldn’t find it. Perhaps Camino has trouble with Atom feeds as opposed to RSS. When I have some more time I’ll see if I can reproduce the error somehow.

The Internet Explorer Q Continuum

As you may have gathered from reading previous posts, I’m a Mac OS X user on laptops and a hopeless FreeBSD fanboy on desktops. Therefore it probably wouldn’t surprise you to find out I’m not a fan of Internet Explorer, or Windows Internet Explorer, or Chuck Norris Explorer or whatever they’re calling it at the moment.

Why though? Is it the fact that it successfully and demonstrably held back innovation on the intertubes for so many years? Is it the silly user interface in version 7 which I get calls from people constantly asking me how they get to the menu bar? Is it the fact their CSS support is so patchy and inconsistent it makes a part of my work even more difficult than it has to be? Is it because it was bundled with a monopolistic operating system? Is it because the e logo just looks plain silly?

No. It’s for one simple fact: Internet Explorer doesn’t support the <q> tag!

Look at that browser Jean Luc, it doesn't support my existence!
Look at that browser Jean Luc, it doesn’t support my existence!

You could be forgiven for not knowing about this tiny little tag; it was included by the W3C back in the HTML 4.0 specification in 1997 to delimitate small inline quotations which are not large enough to justify the use of a block level element, but current versions of IE are the only browsers even in 2008 not to support it, despite every other game in town having no trouble with them.

For example, one of the sentences below is enclosed in <q> tags. If you’re using Internet Explorer they will look exactly the same:

Ruben Schade is an incredibly smart, devilishly attractive and very self deluded person.

Ruben Schade is an incredibly smart, devilishly attractive and very self deluded person.

But why is the lack of support for a seemingly insignificant and easily replaceable tag my number one gripe with Internet Explorer? Because of its stupefying simplicity! How difficult would it have been for Microsoft to have added full support for such a simple tag? It’s mind blowing!

<q>This is an inline quote, complete with CSS support!</q>

<span class="quote">Here's another inline quote, but with support for IE </span>

I guess until Internet Explorer 12 comes out some time after 2095, I’ll have to stick with using the latter example above. What a mess!

FOOTNOTE: For what it’s worth, Opera, Mozilla Firefox, Netscape Navigator (rest in peace), Apple’s Safari, KDE’s Konqueror and even zippy little dillo, links and lynx support the <q> tag. Obviously it’s not hard!

Further Reading

Insanely useful webapp to convert PDF to SVG

Sometimes you find a webapp on the intertubes that’s so useful you’d be charged for criminally negligent conduct if you didn’t tell other people about it. As far as I understand it.

In this case it’s Texterity’s FreeSVG service which takes PDFs you upload, breaks them down into their individual components (including text, images, fonts and vector drawings), converts it all into an SVG file, bundles all the material into a zip file, then emails you a 48 hour link to fetch it. Very, very nice.

Choosing the file to upload and convert

From their site:

FreeSVG is provided by Texterity to encourage the use of SVG (Scalable Vector Graphics) on the web and enable free, highly functional conversion of PDF documents into fully accessible and navigable SVG.

SVG is an industry standard, W3C (World Wide Web Consortium) specification describing text and graphics in XML. To learn more about SVG visit the W3C site at http://www.w3.org/Graphics/SVG/.

Now obviously for security reasons you’d definitely not want to use this service for confidential or sensitive information, but for general use it’s a fantastic solution, and has saved my arse many times!

WordPress eXtended RSS fun

WXR

I haven’t been having much luck with technology this week, but this seems to be the icing on the cake so to speak. The problem is no matter how hard I try I just can’t get WXR working.

WXR is of course the WordPress eXtended RSS format which allows you to quickly export the entire written contents of your weblog including posts, pages, categories, tags and kitchen sinks. It means you can pick up the guts of your weblog, then do a backup of your wp-content folder which contains all your uploaded media, plugins and themes, then import them somewhere else.

Only problem is, this is the seventh time and I still can’t get it to work on one WordPress installation. I have a local web server running on my MacBook Pro which I’ve set up to test new themes and plugins I’m working on, and on this local installation of WordPress I can import my Rubenerd Show material without any trouble at all, but I’ve had no end of trouble when I try to do the same thing from the Rubenerd Blog.

The curious thing is that there’s no consistency to the errors. On Thursday I tried importing from this weblog and WordPress silently failed; the import page just stopped rendering after it had uploaded the file. Then yesterday I tried again and it was able to import posts but only up to September 2006 when it decided to stop.

The only things I can think of that could be causing this problem is the WXR export php file in WordPress wasn’t uploaded to the server correctly, or the file (2.2MiB) is too big somehow for my local web server to handle, or maybe there’s some malformed HTML in one of my posts which breaks the resulting XML file it’s contained in… maybe it’s just gremlins.

One clue though showed itself when I tried to open the exported WXR file in Smultron:

So perhaps it’s an encoding issue? Or does Wordpress not output UTF-8? Could it be failing because some of my posts have East Asian characters which need UTF-8?

Whatever this blasted problem is, it looks like this is going to be a very, very, very long Saturday.

Using HTML, XHTML for word processing

EDIT: I just realised that the draft version (without any links) of this post was the one that was published, not the final one. It’s been all fixed up.

With all the talk these days about online word processors such as Google Documents and gOffice replacing traditional client installed office suites such as OpenOffice.org, it got me thinking: do more technically inclined computers users actually need word processors at all anymore?

Think about it: if you’re a web programmer or have any experience in HTML (preferably one of the XHTML varieties) and CSS you have everything you need to create a professional looking document, and as I discovered, it takes a lot less effort.

With any word processor I’ve ever used I’ve always found it to be a struggle to use the inbuilt templates and formats for headings, lists and so forth. With HTML I have complete control over what everything looks like and where everything goes, I can change the entire formatting of a document on the fly, and the resulting document (if done correctly) is a standards based file which can be read on virtually any computer with a simple web browser, and it’s in a format which I know many years from now I will still be able to open and access, I can embed microformats such as hCards into my documents (very useful for letters), I can create different stylesheets for screen and print views, I can use easily edited meta tags to denote the copyright, language, date, author, keywords, owner and description of a document… the list goes on.

Now granted there could be some downsides depending on who you are. Some people might find the use of <tags /> to be cumbersome and annoying, and I certainly don’t expect everyone to pick it up, but if you have the experience it can work out to be a very efficient and quick way to type something up.

And the best part of it all? You don’t need a fancy word processing programme with bucket loads of features you’ll never use: all you need is a lightweight text editor, and maybe a PDF exporting programme to help with creating separate, printable pages if you run a flavour of Windows.

So how do I use HTML to create documents? Argh, two rhetorical questions in the one post. This is no good. I now have a file called master.html sitting in my home directory that I use as a template for new documents; I simply copy the file, change the meta data and write up the document.

<?xml version=”1.0″ encoding=”UTF-8″?>
<!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-AU”>
<head profile=”http://www.w3.org/2006/03/hcard”>
<title>DOCUMENT NAME By Ruben Schade</title>

<meta http-equiv=”Content-Language” content=”en-AU” />
<meta http-equiv=”Content-Type” content=”text/html; charset=UTF-8″ />
<meta name=”author” content =”Ruben Schade” />
<meta name=”copyright” content=”http://creativecommons.org/licenses/by/3.0/” />
<meta name=”description” content=”DOCUMENT DESCRIPTION” />
<meta name=”owner” content=”Ruben Schade” />

<style type=”text/css” media=”all”>
body {
  font-family: Georgia, Antiqua, “Times New Roman”, Times, sans-serif;
  line-height : 1.6em;
  padding: 2em;
  text-align:justify;
}
</style>
</head>

<body>
<!– DOCUMENT GOES HERE –>
</body>

</html>

How does the McDonald’s theme song go? “I’m loving it!”

RSS vs. RSS - A Tale of Two Icons

A blog entry posted on SomeRandomDude.net has got some pretty lively discussion about which icon is better suited for mainstream use to represent XML feeds on websites and in browsers.

Which do I prefer? Dave Winer’s original XML one!

Why?

  • It was the first one
  • Its still [currently] the most widely used one on websites
  • It can be represented with just CSS: XML
  • Because it doesn’t say rss or atom it can be used to represent any type of XML feed. Aggregators these days are sophisticated enough to tell the difference; we as humans shouldn’t be fussing over what it is at this point… I would hope.
  • I think the Mozilla (and now IE7) version with the lines is misleading because it implies a wireless signal, or it could be music, or it could be energy… in any event regardless XML feeds are client pull anyway, they don’t broadcast anything!

Eventually though I don’t care which one wins. We’re talking about tiny pixels on a screen, this is not an Earth changing event!

RSS vs. RSS - A Tale of Two Icons

The Myth of RSS Compatibility


Interesting look into the history and evolution of the RSS XML thingy and all the different incompatible “standards”. And I thought there was just RDF, RSS 0.9x, RSS 1.0 and RSS 2.0!

From the site:

I have often stated (1, 2, 3) that there are 7 different and incompatible versions of RSS. This was based on an embarassingly simple formula: I counted the version numbers in use (0.90, 0.91, 0.92, 0.93, 0.94, 1.0, and 2.0) and came up with the number 7. But recently some people have taken to claiming that there are not 7 versions (despite obvious evidence to the contrary), and even if there are, that they are somehow compatible with each other so it doesn’t really matter. So I dug a little further to precisely document the incompatible changes in each version of RSS.

I would like to publicly apologize for my previous misstatements. There are not 7 different and incompatible versions of RSS; there are 9.

The Myth of RSS Compatibility

Just Registered for OPML.org

Speaking of Dave Winer, I just registered for my own OPML.org account :)

Thanks for signing up!

The first thing to do is to save a copy of this email for future reference. It’s important, without this password you may not be able to login next time you visit, and you may not be able to access information that we’re storing for you on our server.

Next time you visit the site, and you want to Login, you can go to this page and enter your email address and password:

http://www.opml.org/member/login

When you click on OK, the server will store a cookie on your computer, allowing you to access all of our services. As long as you use the same computer, you won’t have to manually enter the password again.

Again, thanks for signing up!

It’s so refreshing to get a more personal conformation email that isn’t just “You registered as XYZ. Please confirm.”

I’m in the process of downloading the Mac OS X version of the OPML Outliner, it’s going to be very interesting.

RichardDawkins.net