Re: RFC: Designing Logo of Pandoc

[BPJ <bpj-J3H7GcXPSITLoDKTGw+V6w@public.gmane.org>]

[-- Attachment #1: Type: text/plain, Size: 6198 bytes --]

IMHO a simple design like those I created with LaTeX and CSS earlier in
this thread, just a pilcrow in a framed or colored box is actually
preferable.

I really don't think the reversed pilcrow should be used as the P in
"Pandoc". That would only be confusing. If the name "Pandoc" is included it
should be spelled out in regular letters beside or beneath the pilcrow logo
itself.

As for colors I think that if there are more than one (two?) it would be
nice if they be chosen with color blind friendliness in mind.

Below are some links to a 15 color color blind friendly palette I have been
using with the blessing of a client who cares enough to want his link
colors be CB friendly (which the classic blue, red and purple for
unvisited, dead and visited links actually are for most people). I even
found a LaTeX implementation of it on GitHub.

I see a blue color has been suggested, and as it happens the blue colors in
that palette have the virtue that according to the first image they look
reasonably similar to everyone.

Note the equivalent colors in the second image: as long as one only uses
one color from each column one can use any of those in that column.

OTOH those colors marked with a white dot or triangle in the first image
are not distinct for people with blue color blindness (less than one per
cent of all people).

http://www.somersault1824.com/wp-content/uploads/2015/02/color-blindness-palette.png

http://mkweb.bcgsc.ca/colorblind/img/colorblindness.palettes.simple.png

http://mkweb.bcgsc.ca/colorblind/

https://github.com/jfdm/sta-latex/blob/master/colour-blind.sty

Den fre 3 jan. 2020 13:03T. Emil Rivera-Thorsen <thoger.emil-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
skrev:

> Lots of companies and projects have logos that are not used as a letter in
> spelling out the company name. That is perfectly fine in my opinion.
> Better to
> have something which is graphically recognizable.
>
> In that vein, I think perhaps a diamond-shape or even better, 45 degree
> rotated
> square, a bit like the old TextWrangler one, would be a good background, it
> could make it clear this was not just an oddly formatted pilcrow/paragraph
> sign
> but that this is in fact on purpose.  I would also suggest that the
> filled-in
> pilcrow on such a background, whether reversed or not, might be a better
> logo
> then than an unfilled one, because it is less likely to be mistaken as
> part of
> the actual product name and more likely to be seen as an image or symbol.
>
> That being said, I agree that done is better than perfect.
>
> On 02/01/20 10:48, allefeld wrote:
> > Agreed, using the reversed pilcrow as a letter P is not a good idea.
> >
> > For the moment I would propose that we just settle on a font so we have
> > *something* for a logo.
> >
> > Beyond that, someone with at least some graphic design skills would be
> > needed.
> >
> > For me, the motivation was that I needed something to put on a button in
> an
> > Atom package I'm developing, see attached.
> >
> >
> >
> > On Thursday, January 2, 2020 at 10:19:40 AM UTC, mb21 wrote:
> > >
> > > I find the pilcrows don’t work very well when used to write Pandoc
> without
> > > some further graphical editing. It just shows that it’s not the letter
> P of
> > > that font. If we’d want to use the pilcrow as part of a wordmark, some
> > > qualified person will probably need to do some designing.
> > >
> > > Speaking of which, the pandoc website could probably also use a
> graphical
> > > update. Not saying the current state of things is bad, but if we are
> going
> > > to have an official logo, might as well do it properly, with something
> > > resembling a visual identify to go along with. Nothing fancy, but
> something
> > > consistent and with proper spacing etc. that’s less historically grown
> than
> > > the current website.
> > >
> > > P.S. I know open source projects are known to struggle with design
> work
> > > (probably because it requires skills so different to programming? I
> don't
> > > know...) As a commandline-tool/library, pandoc so far didn't have the
> need
> > > for it at all...
> > >
> >
> > --
> > You received this message because you are subscribed to a topic in the
> Google Groups "pandoc-discuss" group.
> > To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/pandoc-discuss/1bKIuyBnWaQ/unsubscribe.
> > To unsubscribe from this group and all its topics, send an email to
> pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/c3dcb843-c8c9-4ea1-8dcc-7cd742f8f746%40googlegroups.com
> .
>
>
>
> --
>
> --------------------------------------------------------------------------------
> Thøger Emil Rivera-Thorsen                    Post: AlbaNova
> Universitetscentrum
> Astrophysicist, Postdoctoral fellow                   SE-10691 Stockholm,
> Sweden
> Department of Astronomy, Oskar Klein Center   E-Mail:
> trive-1s38ZZnEJkowFerOooGFRg@public.gmane.org
> Stockholm University                          Mobile phone:   +46 (0)737
> 703 603
>
> --------------------------------------------------------------------------------
>
> --
> You received this message because you are subscribed to the Google Groups
> "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/20200103120238.y6ob3i52lpzkyxtb%40syenite
> .
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhA4Uk4SZf0uTd1FzJ1%2B3DuwHJSkrf4yPZXdOkAHUynfBQ%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 8632 bytes --]