From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Taco Hoekwater <taco@elvenkind.com>
Subject: Re: New logo proposal
Date: Wed, 30 Jan 2019 16:02:32 +0100 [thread overview]
Message-ID: <c091c1b2-dc66-5622-3ee8-baa4ed4cb608@xs4all.nl> (raw)
In-Reply-To: <7D1D2E35-5588-4027-8BBF-F565E6468361@elvenkind.com>
On 1/30/2019 10:31 AM, Taco Hoekwater wrote:
> Hi,
>
> Just a quick note on logo design:
>
> The ConTeXt logo could just as well be a set of tulips or
> some (TeX-styled) lion or a dutch cow or a windmill or
> some variation off the Pragma-ADE logo (see pragma-ade.com).
> There is no real need to display the letters “context”.
>
> In fact, having a pictograph instead of / along with
> textual content is probably a good idea.
>
> For use in actual text we already have \CONTEXT.
>
> My 2c,
ok, let me add 1c ... since 2011 in the distribution there is always a
file context-version.[pdf|png] which is a colorful representation of the
current context version (date and time) ... probably no one ever noticed
it (at some point i dropped the icon file)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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=c091c1b2-dc66-5622-3ee8-baa4ed4cb608@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=taco@elvenkind.com \
/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).