From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: New logo proposal
Date: Wed, 30 Jan 2019 16:14:02 +0100 [thread overview]
Message-ID: <d6b3e8a8-5993-1526-c08f-500e5f193736@uni-bonn.de> (raw)
In-Reply-To: <7D8527CA-BE17-4D70-A03C-3BF5574C1EC9@boede.nl>
On 1/30/19 1:50 PM, Willi Egger wrote:
> I would say, that the multicolor version is dissecting the word ConTeXT to unidentifiable crumbles. It is to my taste to less connected to typesetting, herewith agreeing partly with Clyde.
It is useless to argue about taste, but it may be of interest to see how
users react. I would agree with Willi. The colors look too random to me.
A fine-tuned palet with a smaller range of colors that are visually and
intuitively related would be preferable, IMHO. But again: de gustibus
non est disputandum; if Paul likes this look, he should by all means use
it in his presentations and documents. And of course, thanks for
sharing your design with us!
Thomas
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-01-30 15:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
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-30 13:00 Paul Schalck
2019-01-30 18:51 ` Lars
2019-01-30 20:11 ` Henning Hraban Ramm
2019-01-30 19:57 Paul Schalck
2019-01-30 22:06 ` Hans Åberg
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=d6b3e8a8-5993-1526-c08f-500e5f193736@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).