Steven Peck wrote:
> 
> Well,
> 
> Worse for me.  I'm a cross over NT sys engineer, though I did start in DOS.
> 
> I'll give you a clue, then I have to go to bed.  If you would like I'll do a
> brief summary of what I've figured out.  I'm probably going to do it anyway.
> 
> Here's a brief brief, not verified for errors, but it'll do for now.  Mike
> probably knows more.  :)
> 
> The LDP Authors guide is being updated as we speak, and they have released a
> newer version this last week IU think.  SGML is the older, more robust
> standard that has been around a while.  The tools are more advanced, the
> documentation is more developed, etc.
> 
> The whole thing is in transistion and standards approval for XML support
> (which the LDP Authors How To recommends) just started about 2 months ago.
> They are updating the docs and such, but as recent LDP list discussions that
> I and another started indicate, they too are a volunteer organization that
> is struggling to keep up.  (Though I had a pretty good rant on their list
> myself -did you see it Mike N? :)  The problem is that their Authors guide
> wasn't updating when I started and my and one others prompted the update.
> 
> Worse than slaughtering HTML, different.  With HTML you say BOLD or ITALICS
> or CENTER, etc.  With Docbook you don't.  You say <emphasis>words</emphasis>
> and the DTD when fed through Openjade with determine HOW the emphasis is
> handled.  In HTML it might be BOLDed, in PDF it might be italisiced,
> whatever the DTD rules said.
> 
> One other guy whom I started corisponding with is in the same boat.  I may
> do a 'cross' over guide for what I have learned int he last month.  I also
> have O'Reilly's Learning XML book.
> 
> Near as I can figure, a DTD is an instruction set for how 'tagged' text is
> expected to be handled when it is converted to a format.  ie.  <para>words
> here</para>
> If you render that in HTML, then it will behave one way, but if you have it
> render into PDF or RTF format, then the DTD determines 'how' that will look
> in that form.  You can write your own DTD's, but I figure the experts have
> one they agree on, so I will use it.
> 
> You also have to have to run it through a third party (openjade in this
> case) engine to do the conversion, if the engine thinks your document
> (source code) has problems, then it will puke and give you a line number to
> check.  I have to figure out how to do the that step in a few days when I am
> done.  Evidently, there can be no errors.
> 
> Now, what I have done, is downloaded the XML source for the LDP's Authors
> Guide and I am using that as a template for my how to.  Simple eh?
> 
> In any case, nite all, WAY past my bedtime.

Steven

I think you stated this rather succinctly, that's just about what I got
out of the LDP docs when I was considering converting an html howto to
DocBook. The 'write it once, spew forth multiple formats' is quite
appealing. When I looked at it, it was SGML, now they want XML?

I do prefer messing with these tagged documents with a wysiwyg type
editor, call me a wuss:) I just need one that will do XML I guess. Of
course an html to xml converter would be trick, think one exists?

Regards
Paul
> 
> ----------------------------------------------
> Steven Peck                   [EMAIL PROTECTED]
> Sacramento, CA          http://leaf.blkmtn.org
> 

-- 
-----------------------------------------
It's a Linux world....well, it oughta be.
-----------------------------------------

_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to