Bug 3117 is pretty funny -- I wonder how that got in there!
My guess, though I've not tracked it down, is that there is an existence check on the keyword somewhere and perl evaluates it to 0/false because of the leading 0 in the string.
IIRC, last time I looked at the export bugs there were a couple, including general improvement of the existing export tool, and a specific request to export as pdf. My thought was to find my way around the API (*sigh* document where necessary), and that ideally dreamwidth probably only wants to support exporting to a single format (XML) - at least for basic accounts. But if the XML were well enough documented then third parties (or dreamwidth could provide the source code but not host the application) could easily write conversion tools to act on the XML. I'll need to get the hang of the queuing system as well - so lots of learning involved.
no subject
My guess, though I've not tracked it down, is that there is an existence check on the keyword somewhere and perl evaluates it to 0/false because of the leading 0 in the string.
IIRC, last time I looked at the export bugs there were a couple, including general improvement of the existing export tool, and a specific request to export as pdf. My thought was to find my way around the API (*sigh* document where necessary), and that ideally dreamwidth probably only wants to support exporting to a single format (XML) - at least for basic accounts. But if the XML were well enough documented then third parties (or dreamwidth could provide the source code but not host the application) could easily write conversion tools to act on the XML. I'll need to get the hang of the queuing system as well - so lots of learning involved.