ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <texml@fiee.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Wiki - test/proposal to further clarify documentation
Date: Wed, 17 Apr 2024 10:47:51 +0200	[thread overview]
Message-ID: <11dfcdb1-f3c2-4efd-abe4-6a3bd0ccd66a@fiee.net> (raw)
In-Reply-To: <5b3ef2d2-a911-4e7e-8bb0-f095d5586903@xs4all.nl>

Am 17.04.24 um 10:36 schrieb Hans Hagen:
> On 4/17/2024 8:32 AM, Thomas A. Schmitz wrote:
>>
>>
>>> On 16. Apr 2024, at 21:56, Peter Hopcroft via ntg-context 
>>> <ntg-context@ntg.nl> wrote:
>>>
>>>
>>>
>>>> On 17/04/2024, at 7:11 AM, Henning Hraban Ramm <texml@fiee.net> wrote:
>>>>
>>>> In my poster (still WIP) I wrote:
>>>> …
>>>
>>> Excellent
>>
>> No, I must admit I don’t like the first two paragraphs. The question 
>> is “what is ConTeXt,” and the answer is “we’re not LaTeX.” And why 
>> “infamous”?
> I agree. It sounds the same as "we're not msword" or "we're not google 
> docs". (In the end the only thing that latex and context have in common 
> is that they use the tex language / ecosystem.)

In my experience, most people interested in ConTeXt know LaTeX, so it 
makes sense to compare.
And I actually just say “LaTeX is the most known command-based 
typesetting system” (that’s just true) to shortcut explaining what a 
cbts might be.

Your critique applies to JUH’s quote, though.

I used “infamous” as a funny way to say “not famous, but somewhat known” 
(and yes, I know Latin and what the words really mean).

Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2024-04-17  8:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-14 11:21 [NTG-context] " garulfo
2024-04-14 14:14 ` [NTG-context] " Henning Hraban Ramm
2024-04-14 19:45   ` Peter Hopcroft via ntg-context
2024-04-16 19:07     ` Henning Hraban Ramm
2024-04-16 19:56       ` Peter Hopcroft via ntg-context
2024-04-17  6:32         ` Thomas A. Schmitz
2024-04-17  8:36           ` Hans Hagen
2024-04-17  8:47             ` Henning Hraban Ramm [this message]
2024-04-17  9:10               ` Joaquín Ataz López
2024-04-17  9:32                 ` jbf
2024-04-17 11:57 ` Bruce Horrocks
2024-04-17 12:17   ` Henning Hraban Ramm
2024-04-18 12:48     ` Bruce Horrocks
2024-04-17 21:25   ` Garulfo
2024-04-18  6:32     ` Henning Hraban Ramm
2024-05-17 20:40 ` garulfo
2024-05-18 11:27   ` Bruce Horrocks
2024-05-19 12:44     ` garulfo

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=11dfcdb1-f3c2-4efd-abe4-6a3bd0ccd66a@fiee.net \
    --to=texml@fiee.net \
    --cc=ntg-context@ntg.nl \
    /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).