unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: LEE Sau Dan <danlee@informatik.uni-freiburg.de>
Subject: Re: Book writing mode?
Date: 26 May 2004 23:33:42 +0200	[thread overview]
Message-ID: <m3oeoa3mbt.fsf@mika.informatik.uni-freiburg.de> (raw)
In-Reply-To: Pine.LNX.4.44.0405261226190.1529-100000@localhost.localdomain

>>>>> "gebser" == gebser  <gebser@speakeasy.net> writes:

    gebser> I'm sure that latex is very nice, but if you want to get
    gebser> published, you should submit manuscripts in a format which
    gebser> the agent or editor desires.

Many academic publishers, esp. those specializing in computer science,
math, do accept LaTeX manuscripts.


    gebser> For electronic submissions this is generally Word (.doc)
    gebser> format or plain text (ASCII).

Postscript has  been the industry  standard for decades, and  more and
more electronic submissions accept also  PDF files.  Both of these can
be easiliy generated from LaTeX.


    gebser> If you're submitting only hardcopy, then this matters much
    gebser> less.  If you don't care about being published, then you
    gebser> can use whatever you want.  :)

I've published a  few journal articles and conference  papers.  I only
use LaTeX.

Nowadays, I use Emacs with AUCTeX and preview-latex.  Also 'pclcvs' so
that I can use CVS to keep track of the revisions and branches.


-- 
Lee Sau Dan                     李守敦                          ~{@nJX6X~}

E-mail: danlee@informatik.uni-freiburg.de
Home page: http://www.informatik.uni-freiburg.de/~danlee

  reply	other threads:[~2004-05-26 21:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.7498.1085581424.1061.help-gnu-emacs@gnu.org>
2004-05-26 15:02 ` Book writing mode? Bastien
2004-05-26 15:36 ` Michael Slass
2004-05-26 16:35   ` gebser
2004-05-26 21:33     ` LEE Sau Dan [this message]
2004-05-27 13:59       ` Micha Feigin
2004-05-28 19:55       ` gebser
2004-05-29 12:04         ` Kai Grossjohann
2004-05-29 16:37         ` Micha Feigin
     [not found]   ` <mailman.7535.1085590987.1061.help-gnu-emacs@gnu.org>
2004-05-26 21:56     ` Peter Milliken
2004-05-26 22:11       ` Stefan Monnier
2004-05-26 22:21         ` David Kastrup
2004-05-26 22:35           ` Miles Bader
2004-05-26 22:44       ` upro
2004-05-27  9:35         ` Micha Feigin
2004-05-26 16:44 ` Roodwriter
2004-05-26 18:07   ` Kevin Rodgers
2004-05-26 20:31     ` Roodwriter
2004-05-26 20:20   ` Raimund Kohl-Fuechsle
2004-05-26 20:34   ` Roodwriter
2004-05-26 20:39 ` Stefan Monnier
2004-05-29 16:44 Joe Corneli
  -- strict thread matches above, loose matches on Subject: below --
2004-05-28  5:05 Joe Corneli
2004-05-29  2:30 ` Luis O. Silva
2004-05-29 17:22   ` Micha Feigin
     [not found] <mailman.7517.1085586605.1061.help-gnu-emacs@gnu.org>
2004-05-26 16:56 ` Thien-Thi Nguyen
2004-05-26 13:23 juman
2004-05-26 16:36 ` Brad Collins
2004-05-26 19:07 ` David Abrahams
2004-05-26 12:59 juman

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=m3oeoa3mbt.fsf@mika.informatik.uni-freiburg.de \
    --to=danlee@informatik.uni-freiburg.de \
    /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).