From: Galen Boyer <galenboyer@hotpop.com>
Subject: Re: Off-topic: Plain text, XML or LaTex?
Date: 24 Jun 2003 22:37:19 -0500 [thread overview]
Message-ID: <uwufaq18n.fsf@standardandpoors.com> (raw)
In-Reply-To: mailman.8506.1056397474.21513.help-gnu-emacs@gnu.org
On Mon, 23 Jun 2003, jeff.rancier@softechnics.com wrote:
> the power of using docbook is the fact that you have your
> source written once in XML, then the theory is you can generate
> various output formats (with possibe intermediate
> translations), from the same source. I.e., HTML, FO, PDF, etc.
Plus, the sales factor to your fellow compadres and upper
management includes the letters, XML. My company is on the verge
of moving to docbook as its publication format (based solely on
my publications with it) and the fact that it has XML in its
description has the sexiness needed. I could have never sold
some version of TEX, no matter how much better it might have
been. Either way, one source for the documentation is the key,
and tagged documentation is the way to go.
--
Galen Boyer
next prev parent reply other threads:[~2003-06-25 3:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 12:21 Off-topic: Plain text, XML or LaTex? Mac
2003-06-23 13:49 ` Phillip Lord
2003-06-25 9:24 ` Mac
2003-06-25 19:30 ` Robert Mecklenburg
2003-06-23 16:39 ` Martin Stemplinger
2003-06-23 17:27 ` Ted Zlatanov
2003-06-23 19:23 ` Jeffery B. Rancier
2003-06-23 21:03 ` Roodwriter
2003-06-24 7:11 ` Kai Großjohann
[not found] ` <mailman.8506.1056397474.21513.help-gnu-emacs@gnu.org>
2003-06-25 3:37 ` Galen Boyer [this message]
[not found] <E19URxP-0007tH-2A@monty-python.gnu.org>
2003-06-23 14:57 ` Urban Gabor
-- strict thread matches above, loose matches on Subject: below --
2003-06-24 4:37 Dmitri.Minaev
[not found] <mailman.8464.1056380372.21513.help-gnu-emacs@gnu.org>
2003-06-25 3:40 ` Galen Boyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uwufaq18n.fsf@standardandpoors.com \
--to=galenboyer@hotpop.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.