public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: TeX WYSIWG Editor
Date: Mon, 07 Jul 2014 20:58:00 -0000	[thread overview]
Message-ID: <53BB09D7.1030307@cs.umass.edu> (raw)
In-Reply-To: <4B6A3638A81C45709E67D85B87D612BB@HPDV7TNotebook>

On 7/7/2014 4:41 PM, Arthur Schwarz wrote:
> Are there any TeX WYSIWG editors? In particular, ones that support managing
> changes in a distributed environment (as a minimum)? Changing TeX documents
> seems tedious (without a WYSIWG) if doing it by hand. Wordperfect and
> Microsoft Word hid the font/formatting commands from the user to produce a
> WYSIWG editor, hence the question. Is there support for the same capability
> in the FSF environments for TeX.
>
> TeX seems to be 36 years old (circa 78 in Knuth's TeX Manual) and it may be
> a good thing to change to a language that contains a more attractive
> interface, allows graphics/pictures, and provides the
> multi-computer/multi-terminal support that TeX has.

Yes, there are things out there.  It's kind of off-topic for the
cygwin list since it has more to do with TeX than cygwin.  Lyx is
one example; there may be others.

However, I have produced book-length works with multiple authors
using TeX (LaTeX actually) as is.  We used a subversion repository
to hold everything.  With some attention to how subversion commit
emails are configured, etc., it was easy to see what others were
doing, and the emerge package of emacs was helpful for going over
and adjusting edits made by others, etc.

For figures we tended to use Adobe Illustrator.

Regards -- Eliot Moss

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2014-07-07 20:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07 20:42 Arthur Schwarz
2014-07-07 20:58 ` Eliot Moss [this message]
2014-07-07 21:01   ` Eliot Moss
2014-07-07 22:08   ` Ken Brown

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=53BB09D7.1030307@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=cygwin@cygwin.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).