Computer Old Farts Forum
 help / color / mirror / Atom feed
From: bakul at bitblocks.com (Bakul Shah)
Subject: [COFF] roff vs. Tex (was: Looking for final C compiler by Dennis Ritchie)
Date: Wed, 25 Jul 2018 23:38:09 -0700	[thread overview]
Message-ID: <20180726063816.EB9E2156E400@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Thu, 26 Jul 2018 14:22:20 +1000." <20180726042220.GC87618@eureka.lemis.com>

On Thu, 26 Jul 2018 14:22:20 +1000 Greg 'groggy' Lehey <grog at lemis.com> wrote:
>
> That's the case now, I assume.  I've just dragged out the TeXbook
> (February 1989), LaTeX user's guide and reference (referring to LaTeX
> 2.06 (April 1986)) and "TeX for the Impatient" (1990).  None of them
> mention this command, and after 20 minutes of searching I wasn't able
> to find any reference in any of them to any font family except CM, and
> thus also no way to change to one.  About the only titbit I found was
> that you needed separate commands for each font at each size, and that
> this was impractical.  A far cry from troff's .ps command.

You may be used to an earlier version of LaTeX (LaTeX 2e?).
Things are considerably better now. I didn't use LaTeX much
for over a decade but now, with editors such as TeXWorks and
faster machines, rendering is quite fast. There are also some
webbased TeX editors that are quite good (and show rendered
page in one pane). Many more fonts are available now. And
there is plenty of help available at tex.stackoverflow.com.

For short simple documents I generally use MarkDown or
AsciiDoc.  Their light markup means source files are quire
readable in a terminal window, and they still render well to
an html page or pdf (and you can include images).  For more
complex editing tasks I switch to LaTeX (or XeLaTeX). And
Unicode has helped for Indic scripts. I don't have to use
transliterated Roman with diacritics for Indian languages
(hard to read/write in this form for a native speaker).


  reply	other threads:[~2018-07-26  6:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8ECDA62D-1B54-4391-A226-D3E9ABEE4C07@planet.nl>
     [not found] ` <CACXZuxeJ3igMtfbLs1iUPMLhomQUG0dEjpaHHmV0L7hF0bvo4g@mail.gmail.com>
     [not found]   ` <CAC20D2OTsR0ZxqeUk2EBpZnWy2k4LVf8=VPKzitWhkT3n_vL8g@mail.gmail.com>
     [not found]     ` <20180723155552.GB19635@mcvoy.com>
2018-07-23 16:41       ` [COFF] [TUHS] Looking for final C compiler by Dennis Ritchie crossd
2018-07-24  3:52         ` [COFF] roff vs. Tex (was: Looking for final C compiler by Dennis Ritchie) grog
2018-07-24  4:01           ` lm
2018-07-24 14:43             ` cym224
2018-07-24 10:00           ` ralph
2018-07-27  1:04             ` lm
2018-07-25 21:24           ` perry
2018-07-26  4:22             ` grog
2018-07-26  6:38               ` bakul [this message]
2018-07-26 12:22               ` perry
2018-07-27  1:28                 ` grog
2018-07-27  2:52                   ` cym224

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=20180726063816.EB9E2156E400@mail.bitblocks.com \
    --to=coff@minnie.tuhs.org \
    /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 NNTP newsgroup(s).