From: "Paul Schalck" <schickele@web.de>
To: ntg-context <ntg-context@ntg.nl>
Subject: New logo proposal
Date: Tue, 29 Jan 2019 19:58:40 +0100 [thread overview]
Message-ID: <trinity-1da17e4f-173e-4956-a9b4-4b86c2f85485-1548788320032@3c-app-webde-bs08> (raw)
Hello,
thanks for your feedback. Again, I don't want to impose or dismiss anything. I wanted to share this because I believed somebody else in the ConTeXt community could be interested.
@Taco: Actually, I stumbled upon the nice ConTeXt group logo recently and was wondering who made it. To answer your questions: I tried to avoid any logic or rainbow-type color sequence to create something more unique. The first square had to be in blue and the middle area in a warm color. (I played around a lot with the color combinations.) Regarding the outside circle: I tried different variations, with and without a surrounding circle or round background, with and without rounded squares, and was most pleased with this solution. It's true, "clean and simple" can easily lead to "too informal".
@Clyde J: Valid point. I use the logotype with the subscript 'E' whenever I can in inline text.
@Floris vM: Font, spacing, overall appealingness. No Helvetica/Nimbus Sans, which has less meaning to me for ConTeXt than a DIN-ish/technical one. Colors are fun. If you don't see it this way, it's perfectly fine.
@Alan B: I've uploaded MetaPost files of the main version.
Yes, the horizontal version is not very exciting nor very TeX-aware. I made this one primarily because I wanted something small for a little GUI script. Now I think it's just superfluous.
Greetings!
Paul
___________________________________________________________________________________
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 reply other threads:[~2019-01-29 18:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 18:58 Paul Schalck [this message]
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
-- 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-30 13:00 Paul Schalck
2019-01-30 18:51 ` Lars
2019-01-30 20:11 ` Henning Hraban Ramm
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=trinity-1da17e4f-173e-4956-a9b4-4b86c2f85485-1548788320032@3c-app-webde-bs08 \
--to=schickele@web.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).