From: Gernot Hassenpflug <gernot@kurasc.kyoto-u.ac.jp>
Subject: Re: LaTeX-Fill-Paragraph and inline images
Date: Thu, 27 Feb 2003 18:15:24 +0900 [thread overview]
Message-ID: <vc97kbmf5jn.fsf@kurasc.kyoto-u.ac.jp> (raw)
In-Reply-To: b3babo$esh$1@sapa.inka.de
Hello Felix,
I'm late on reading the group - and I hope this information is not
totally superfluous by now!
Reading through the RefTeX pages on sourceforge, the following link
from the main page (http://preview-latex.sourceforge.net/) might be
useful to you and the respondents in the discussion. In particular,
what is wrong with having say WhizzyTeX open a separate window and
therefore offers more clarity, while at the same time editing the
offending text segments with preview-LaTeX quick and dirty. A binding
of the LaTeX compilation could be done to run both p-L and w-T so that
updating is synchronized?
http://preview-latex.sourceforge.net/others.html
Programs & Packages Related to preview-latex
preview-latex is explicitly focused on placing identifiable previewed
scraps of TeX, compositions, right in your source buffer in the way
most convenient for editing. It does not cater for any other WYSIWYG
concepts. In particular, it does not change the manner in which you
have to enter your input: you still need to know what and how to
type. If you have had no previous exposure to LaTeX, are accustomed to
usual text processors, and do not need to work on LaTeX documents
together with other authors, then there may be more convenient ways
for you to harness the typesetting quality of LaTeX. Two TeX-related
word processors with a more `customary' user and input interface are:
* GNU TeXmacs is a true WYSIWYG system /snip/
* LyX is quite closer coupled to LaTeX /snip/
While both of these systems have ways of entering LaTeX code that the
processor itself does not understand, creating documents making
extensive use of this feature would be defeating their point.
Because of this and because they save their texts in their own
formats, those systems are not quite frontends to LaTeX, but rather
employ LaTeX as a backend. They provide you with convenient access to
LaTeX's quality, but not to its native flexibility, power, and
interchangeability.
So there may be good reason to bite the bullet, and use a real editor
intended for editing basically plain text, and Emacs is an excellent
contender. If you go for Emacs, here are additional packages worth
looking at:
* X-Symbol is a powerful input and display system for the vast variety
of math characters and accented character constructs that LaTeX
provides. It will replace those control sequences with more readable
characters, and it will offer both new and experienced users a
number of convenient and fast methods to enter them. While
preview-latex focuses on providing convenience for LaTeX's output,
X-Symbol tries this for the input.
* WhizzyTeX also plays in the previewing ballpark, but not in the
source buffer of Emacs. It updates a preview window interactively
while you are working on the source. Its preview is page-oriented in
a separate window.
* AUC TeX, is the LaTeX major-mode. preview-latex will currently not
work without it.
* RefTeX provides support for doing labels, references and citations
in LaTeX. It is already installed in Emacs and just needs to be
activated. See the info page.
--
G Hassenpflug RASC, Kyoto University
next prev parent reply other threads:[~2003-02-27 9:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-08 15:43 LaTeX-Fill-Paragraph and inline images Felix E. Klee
2003-02-09 15:53 ` Kai Großjohann
2003-02-09 16:23 ` Felix E. Klee
2003-02-09 16:37 ` David Kastrup
2003-02-09 17:44 ` Felix E. Klee
2003-02-10 20:38 ` David Kastrup
2003-02-21 15:02 ` Felix E. Klee
2003-02-21 15:50 ` David Kastrup
2003-02-21 23:02 ` Felix E. Klee
2003-02-21 23:18 ` David Kastrup
2003-02-21 23:35 ` Glenn Morris
2003-02-21 23:50 ` Stefan Monnier <foo@acm.com>
2003-02-22 9:44 ` Felix E. Klee
2003-02-22 20:53 ` Stefan Monnier
2003-02-22 21:07 ` Kai Großjohann
2003-02-23 20:20 ` Felix E. Klee
2003-02-27 9:15 ` Gernot Hassenpflug [this message]
2003-02-27 11:58 ` Felix E. Klee
2003-02-27 13:27 ` David Kastrup
2003-02-21 16:01 ` Stefan Monnier <foo@acm.com>
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=vc97kbmf5jn.fsf@kurasc.kyoto-u.ac.jp \
--to=gernot@kurasc.kyoto-u.ac.jp \
/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).