[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

OT: newbieDoc and XML -- can you help?



okay. see the tip-of-the-moment at the bottom of this email?
they're getting rave reviews for the newbieDoc team at
http://newbieDoc.sourceForge.net/ -- but there's a problem:

right now these tips are in a home-grown text format that's
only slightly more ugly than your average perl hack.

	# ...skip ahead to the tip we want...then
	$tip = ''; $author = '';
	while(<TIP>) {
		if ( !/\S/  ) {                 last; };
		if ( s/^=// ) { $author .= $_ ; next; };
		$tip .= $_;
	}

<alert="newbie">i hear XML can do this kind of thing.

	...
	</tip>
	<tip approximation="vague" quality="wild guess">
		<title>Getting Apache to lie</title>
		<author><first>Will</first><last>Trillich</last><email>will@serensoft.com</email></author>
		<author><first>...
		<text>First, munge your <file>/etc/apache/httpd.conf</file>:
		...
		</text>
	</tip>
	<tip>
	...

</alert>

so--

who among us debianistas has knowledge of the names of the tools
we'd need in order to:

1) get started with the right command-line XML gizmo
   (maybe a document-structure-definition thing, too?)

2) do cgi/mod_perl interface for a web front-end to
   create/browse these tips

3) munge the back-end data into and out of xml, including
   (ignorance showing, here) gizmos needed to create the
   data structure of the xml

i've seen LOTS of this-and-that for xml, including extensions,
style sheets, path stuff (?) and more. a bit overwhelming.

i'm looking for something like
	"oh, grab Frammistat::XML-wonk from cpan, and use it
	with apache/clavis (available at www.somewhere.there) or
	maybe try the webmin module newbie-xml-toolbox ..."

ideas (and, of course, newbieDoc xml volunteers) welcome...

-- 
DEBIAN NEWBIE TIP #5 from Will Trillich <will@serensoft.com> 
:
What's a "MANPAGE"? It's the documentation you get when you enter
"man <something>" such as "man sources.list" or "man interfaces"
or "man bash".

Also see http://newbieDoc.sourceForge.net/ ...



Reply to: