unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Roodwriter@core.com" <Roodwriter@core.com>
Subject: Re: Off-topic: Plain text, XML or LaTex?
Date: Mon, 23 Jun 2003 17:03:59 -0400	[thread overview]
Message-ID: <vfeqn3bh6vqtc3@corp.supernews.com> (raw)
In-Reply-To: 81u1ahq8ur.fsf@kwikemart.springfield.se

Mac wrote:

> 
> I apologize for this off-topic posting. But I really like to know how
> you fellow Emacsien feal about his.
> 
> I like plain text, and have for a long time used outline-mode to write
> both my own private notes as well as draft documents. I have also for
> a long time been thinking about moving to LaTex so that I also can
> produce my final documents in Emacs as well.
> 
> Now I have an opportunity to move to XML instead. So I would
> appreciate your thoughts about this.
> 
> How can I get up-to speed with writing XML inside Emacs? Is it worth
> it, or should I stick with plain-ol-text? Any pointers to tutorials,
> books etc is appreciated.
> 
> Perhaps you have a completely different setup that you are willing to
> share with me?
> 
> /mac
> 
> One reason for liking plain text is it's portability (but so are eg
> .pdf these days). Another is version control, I'm a heavy user of cvs
> (pcl-cvs is *great*).


I've never used XML but I have used LaTeX. I'm a big fan of it. I not only 
like its superior quality but the fact that the files are plain text.

File formats come and go but from my experience, plain text is forever.

LaTeX isn't for everyone, though. If what you're producing fits into the way 
it's set up, it'll be one of the easiest ways to go. If what you're 
producing doesn't fit in, you may be in for frustration. You can probably 
make it work but not without a lot of effort. Unless you like solving 
problems, or, like me, just fall in love with it.

For more opinions you could also post the question to comp.text.tex.

--Rod

-- 
Author of "Linux for Non-Geeks--Clear-eyed Answers for Practical Consumers" 
and "Boring Stories from Uncle Rod." Both are available at 
http://www.rodwriterpublishing.com/index.html

To reply by e-mail, take the extra "o" out of my e-mail address. It's to 
confuse spambots, of course.

  parent reply	other threads:[~2003-06-23 21:03 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 [this message]
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
     [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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vfeqn3bh6vqtc3@corp.supernews.com \
    --to=roodwriter@core.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).