[Vim-latex-devel] Re: tex-refs project and xml to vim-help conversion
Brought to you by:
srinathava,
tmaas
From: Michael W. <mw...@mi...> - 2003-02-01 12:41:52
|
* Benji Fisher <be...@me...> [030131 16:12]: > That's too bad. I was under the impression that LaTeX output was > already standard. Especially for the tex-refs and vim-latex projects, > it would be nice to have some form of TeX output! There is at least one project which tries to convert DocBook XML to LaTeX (DB2LaTeX: http://www.sourceforge.net/projects/db2latex) but it's not yet usable. The author promised to start work at it again, but AFAIK nothing happened during the last months. The DocBook XSL Stylesheets to generate XSL-FO work quite good, but the backends to transform FO to PDF are not completley satisfying - at least if you have a 'real life' document using tables, etc. But for less complicated documents using FOP from the Apache project should give already good results. ... > We in the vim-latex project know very little about XML and > DocBook. What we really want at this point is a reading list to get > started. What is the structure of a DocBook document? What is the idea > behind it? What needs to be done to generate a specific output format? > Just point me to some good "getting started" guides, and I think I can > go from there ... or at least, it will keep me busy for a while. ;) The following links might be a bit out of date but should give you a start: Writing Documentation Using DocBook David Rugge; Mark Galassi; Eric Bischoff http://www.caldera.de/~eric/crash-course/HTML/index.html Introduction in DocBook from Marc Galassi http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro.html The Debian SGML/XML HOWTO http://people.debian.org/~bortz/SGML-HOWTO/potato/howto.html The Using DocBook HOWTO of the Linux Documentation Project http://metalab.unc.edu/godoy/using-docbook/using-docbook.html DocBook FAQ Dave Pawson http://www.dpawson.co.uk/docbook/ DocBook Wiki http://docbook.org/wiki/moin.cgi/ Michael -- mw...@mi... http://www.miwie.org mw...@mi... |