Alastair Rankine wrote:
Seems simple enough, but there's almost certainly some complexity that
I'm overlooking.
Yep. What if the images aren't subdirectories of the blog. e.g.
Say we had a blog at http://example.com/foo/bar/blog which in turn
referenced images at http://example.com/images/* and enclosures at
http://example.com/enclosures/*, the resulting zipfile would contain:
foo/bar/blog/index.xml
images/1.jpg
images/2.jpg
...
enclosures/1.mp3
enclosures/2.mp3
Either you need to rewrite URLs are you need one new file at a know
location, not present in the blog itself, to identify where the master
index is.
Or maybe not. xml:base attributes in the index.xml might be sufficient
to straighten this all out. Indeed that might be necessary because
different blog entries live at different URLs themselves. e.g.
images/dog.png means one thing at http://example.com/blog/2006/Hello and
another at http://example.com/blog/2005/Hello
Perhaps it would be helpful to back up a step. Rather than starting with
format design let's try to get a list of everything we need to include
in this format. E.g.
1. Complete source text for every blog entry.
2. Metadata for each blog entry
A. Title
B. Catgeory
C. Tags
3. All media referenced by relative URLs from blog entry
4. URL of blog entry
What else?
--
Elliotte Rusty Harold [EMAIL PROTECTED]
Java I/O 2nd Edition Just Published!
http://www.cafeaulait.org/books/javaio2/
http://www.amazon.com/exec/obidos/ISBN=0596527500/ref=nosim/cafeaulaitA/
