emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "briangpowell ." <briangpowellms@gmail.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-ref video
Date: Wed, 23 Dec 2015 21:15:28 -0500	[thread overview]
Message-ID: <CAFm0skHDeY7cp4i4X50U8uL4G9qXHvwL2ZJuwdPMs1Jx8Uh3iw@mail.gmail.com> (raw)
In-Reply-To: <877fk5rg1r.fsf@pierrot.dokosmarshall.org>

[-- Attachment #1: Type: text/plain, Size: 2992 bytes --]

I believe I read how to correctly pronounce LaTeX as Lay-Teck (and why its
important--to honor the creator of TeX's wishes+intentions, Donald Knuth)
in Leslie Lamport's book on LaTeX--in the preface.

And when you think about it, pronouncing it as "Lay" does make sense "La"
only means "the" in some romance Languages and the "L" and "A" don't stand
for anything in particular either--LA isn't an acronym--and it has no
"foreign language" meaning.  Its not "The TeX"--TeX is "The TeX"--the
lowest primal language itself, programmed in C.

As for any relationship to Latex in paint or whatever; well, that's
patently absurd.

And its important for newbies to realize especially--before even using
LaTeX--that LaTeX is a macro language and any newbie can program directly
in TeX, create their own macro language--built on top of TeX too--and/or
that they themselves can program in TeX and extend the language and embed
it into LaTeX by creating libraries, style .sty files, etc.

But I must say, of all the videos I've ever seen, I believe Dr. Kitchin has
produced the most well-pronounced and clearly spoken ones ever--not just on
Emacs, etc.  Thanks again.


Thanks Nick for the link: This reminds me of a strange and hilarious job
interview I had long ago, when LaTeX wasn't fully well-known as a
computerized typesetting packaged (used to publish more books on higher
math than any other system).

The interviewers asked what my "favorite computer software is"--well I
smiled and said "Lay-Tecks"--this conjured up smirks, giggles and a wink or
two--they thought I was into some other "favorite activities"--they
obviously thought I was into latex clothing, etc.  Not quickly realizing
it, I went on: "Oh yes, I use it a lot, I use it as much as possible--I'm
way into it; and, the whole free [soft-wear] community--I'd have to say
I've been part of the community for many years."

Obviously, people that don't know EXACTLY what you're talking about, can
lead themselves to many very strange conclusions about you.  So, such
things can be very important indeed.







On Tue, Dec 22, 2015 at 10:37 PM, Nick Dokos <ndokos@gmail.com> wrote:

> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
> > Thanks!
> >
> > You might add your interpretation of the pronunciation here:
> http://tex.stackexchange.com/questions/17502/what-is-the-correct-pronunciation-of-tex-and-latex
> ;)
> >
> > John
> >
>
> The vexing issue of how to pronounce "LaTeX" has reared its ugly head
> before, e.g in this thread on the comp.text.tex group ca 1999:
>
>
> https://groups.google.com/forum/#!searchin/comp.text.tex/Robin$20Fairbairns$20rubber/comp.text.tex/Ts9l6CPcjCk/g_89W2rJsPcJ
>
> with the entertaining subject "anyone have a source of all rubber
> panties".  I would recommend that you read the whole thread but in any
> case don't give up until you read Robin Fairbairns's followup to his
> (Robin's) suggestion that the OP should read the FAQ.
>
> How's that for a Christmas present?
> --
> Nick
>
>
>

[-- Attachment #2: Type: text/html, Size: 4240 bytes --]

  reply	other threads:[~2015-12-24  2:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 16:10 org-ref video John Kitchin
2015-12-22 17:28 ` B.V. Raghav
2015-12-22 18:53   ` John Kitchin
2015-12-22 22:10 ` briangpowell .
2015-12-22 23:39   ` John Kitchin
2015-12-23  3:37     ` Nick Dokos
2015-12-24  2:15       ` briangpowell . [this message]
2015-12-24 14:49         ` Nick Dokos
2015-12-25  4:02           ` briangpowell .
2015-12-24  7:00   ` Marcin Borkowski

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.orgmode.org/

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

  git send-email \
    --in-reply-to=CAFm0skHDeY7cp4i4X50U8uL4G9qXHvwL2ZJuwdPMs1Jx8Uh3iw@mail.gmail.com \
    --to=briangpowellms@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).