in reply to POD as a general documentation system
I document (lately) my java in pod (javadoc--) :)
I take notes in pod (always!) ;)
I write essays in pod (not that I care to share).
How the mind works (association) is a part of it, but I'll bet another part is exposure. Most people just haven't a clue what pod is, or it doesn't seem appealing enough. Here's what they may be thinking:
- How do you embed images in POD? they'd ask
- What? No Images?? they'd say, to which i'd respond:
Most documentation needs no images (even though there is plenty of users who might prefer it), so most writing documentation don't mind (i sure as feck don't), and neither should you (plain is plenty). But if you're desperate, you can always embed html (as in =begin html html =end html).
- What? =begin html?? they'd say, to which i'd respond:
It may seem weird to embed other formats into pod, but that's the beauty of pod. You may argue why not use html to begin with, but you know why. And if you don't like doing it because you have more than one target format like html, well you got Pod::Parser (among many others) baby, so invent your own ( =for imageEmbedderInAllMyTargetFormats filename anybody? powerful indeed).
- What? No Images?? they'd say, to which i'd respond:
|
MJD says you can't just make shit up and expect the computer to know what you mean, retardo! I run a Win32 PPM repository for perl 5.6x+5.8x. I take requests. ** The Third rule of perl club is a statement of fact: pod is sexy. |