ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Scott Steele <scottlsteele@gmail.com>
To: ntg-context@ntg.nl
Subject: ConTeXt name/branding
Date: Mon, 26 Apr 2010 18:41:43 -0400	[thread overview]
Message-ID: <m2tffe608d81004261541p4092489ak6b28831b5c8e4c30@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2425 bytes --]

Sidenote: If anyone has ever considered changing the name of the ConTeXt
project, I'd like to support that. Name consistency is important, but there
are two unnecessary problems that the current name creates.

The first is that the unusual capitalization and pronunciation are a barrier
to new users. I've used macro packages in the TeX family for about four
years now (though it seems much longer! I can't believe for how long I was
putting out such ugly papers!), but I'm now consciously trying to remember
to pronounce them as tecks, latecks, zeetecks, conteckst, etc, and to type
them as Tex, Latex, Xetex, and Context (outside of this message/forum). The
odd capitalization doen't win fans among people who appreciate typographic
tradition, and the pronunciation requires that, instead of explaining first
how powerful and useful these systems are, one explain the Greek chi and
Donald Knuth. It doesn't give a good impression when one's first exposure to
TeX involves being told one is wrong in how one pronounces a word that is
less than 40 years old (The same goes for many open source projects).
Further, if the name is brought up in conversation and piques the interest
of a potential user, they will have a difficult time later searching for it
when they type in contekt or conteckt.

The second problem with the ConTeXt name is its shared spelling with
context. When I google context and font, I get so many pages imploring me to
consider the context of my document when choosing between Arial, Times New
Roman, and Comic Sans. Many of the things I'll be searching for while using
ConTeXt yield thousands of irrelevant pages because of how context can pop
up in so many topics that share major keywords with the typesetting process.

Of course, I myself am in no position to advocate a name change, and if the
two issues I listed are the price for having a cutting-edge typesetting
system, then I'm still a pretty happy camper. But if any of the people who
have actually worked really hard to put this together have ever thought
about bringing up a branding change, here's my two pence.

Scott

-----
This is a work of fiction.  Names, characters, places, and incidents either
are the product of the writer's imagination or are used fictitiously, and any
resemblance to actual persons, living or dead, businesses, companies,
events, or locales is entirely coïncidental.

[-- Attachment #1.2: Type: text/html, Size: 2567 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 bytes --]

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

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2010-04-26 22:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 22:41 Scott Steele [this message]
2010-04-26 23:16 ` Hans Hagen
2010-04-27  8:27 ` Patrick Gundlach
2010-04-27  8:29   ` luigi scarso
2010-04-27  8:48   ` Mojca Miklavec
2010-04-27  8:58     ` Tobias Burnus
2010-04-27  9:31       ` Vedran Miletić
2010-04-27  9:35         ` Hans Hagen
2010-04-27 11:18           ` Khaled Hosny
2010-04-27 12:28 ` Procházka Lukáš Ing. - Pontex s. r. o.
2010-04-27 13:31   ` Arthur Reutenauer

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=m2tffe608d81004261541p4092489ak6b28831b5c8e4c30@mail.gmail.com \
    --to=scottlsteele@gmail.com \
    --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).