> Hey all, I am considering writing a simple/stupid XML parser. > Nothing fancy, but it will be enough for my needs.
> The number one thing I have against it is that /help > expects you to have an 80 column display. Very much in agreeance here... Locking the width like that is most certainly outdated, and a pain to change/extend in vi. ;) Also, using something like XML might fix up the small variances that invariably result from multiple maintainers. > My goal is to have all help files in epic converted to a very simple > XML DTD which epic itself would know how to read intrinsicly. This > DTD won't be much, but it will let epic preparse the help files and > print out the help contents at the appropriate size for the window as it > sits right now. Note, it won't work if you resize and there are perfectly > valid reasons for that based on how epic currently saves its text > buffer. I am also willing to help write XSLT filters for turning the help > into a real HTML manual, though I definitely do not currently > understand this enough to do it on my own. I rather like the separate files idea, though it DOES need to make use of links on those filesystems which support them... Unless it's "compiled" into an indexed binary format as needed which doesn't impose the very same limits we're trying to remove (ie. needs to be useable by several people at once all with different effective screen widths), and is recompiled as needed (have a help compiler, which can be either run by hand after editing, or launched suid by epic when needed). > C'mon guys, /help sucks ass and we all know it. Whaddaya say? Ahhh..... But not nearly as much as not having it. ;) *hic* Here's to the help command. _______________________________________________ List mailing list [EMAIL PROTECTED] http://epicsol.org/mailman/listinfo/list
