ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: New logo proposal
Date: Wed, 30 Jan 2019 21:11:48 +0100	[thread overview]
Message-ID: <711C0259-0615-4A73-AECE-C48A96B66CC5@fiee.net> (raw)
In-Reply-To: <trinity-d314e1c7-de3a-4d7e-8e84-63ad69935a0b-1548853229531@3c-app-webde-bap11>

Am 2019-01-30 um 14:00 schrieb Paul Schalck <schickele@web.de>:

> @Floris vM: I'm glad that my nemesis on the matter felt himself challenged to make his own proposal. While I think it's too minimalistic (only insiders know what 'CTX' stands for), I like your idea of the subscript 'T'. Your concept with the crosses reminded me of the visual identity of Amsterdam. I do not see, however, how it reflects better "typesetting beautiful readable typography". And it lacks some colors ,-)

You don’t need to understand the signs of a good logo (see e.g. Deutsche Bank).

Floris’ proposal is clear and looks like math, that’s TeX-y enough IMO.

Every good logo works without color, even if there is a color version.


Myself, I suggest a Dodo as mascot. (Save the \dodo !)


Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD

___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2019-01-30 20:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 13:00 Paul Schalck
2019-01-30 18:51 ` Lars
2019-01-30 20:11 ` Henning Hraban Ramm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-30 19:57 Paul Schalck
2019-01-30 22:06 ` Hans Åberg
2019-01-29 18:58 Paul Schalck
2019-01-30  9:10 ` Floris van Manen
2019-01-30  9:15 ` Floris van Manen
2019-01-30  9:20   ` Taco Hoekwater
2019-01-30  9:31   ` Taco Hoekwater
2019-01-30 15:02     ` Hans Hagen
2019-01-30 15:32       ` Arthur Reutenauer
2019-01-30  9:34   ` luigi scarso
2019-01-30 10:09     ` Floris van Manen
2019-01-30 20:04       ` Henning Hraban Ramm
2019-01-30 10:11 ` Procházka Lukáš Ing.
2019-01-30 15:02 ` Alan Braslau
2019-01-28 23:18 Paul Schalck
2019-01-29 10:32 ` Taco Hoekwater
2019-01-29 16:26   ` Hans Hagen
2019-01-29 17:30   ` Alan Braslau
2019-01-30 12:50   ` Willi Egger
2019-01-30 15:14     ` Thomas A. Schmitz
2019-01-30 16:34     ` mf
2019-01-29 10:42 ` Clyde Johnston
2019-01-29 11:44   ` Floris van Manen
2019-01-29 11:52     ` Hans Hagen
     [not found]       ` <01CB743F-2750-42C8-B8A6-0C09E6DAF5CB@klankschap.nl>
     [not found]         ` <0fb9e8d6-3a4d-cb4a-8f9f-017e08c827f0@xs4all.nl>
     [not found]           ` <9D47C6C4-D5C3-4EA0-8220-6D33BD1E84C6@klankschap.nl>
2019-01-29 14:31             ` Hans Hagen
2019-01-29 16:25   ` Hans Hagen
2019-01-31 20:14 ` Henri Menke

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=711C0259-0615-4A73-AECE-C48A96B66CC5@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).