Which lands right in the trap I think should be avoided.  I don't only think that it would be nice if the logo can be generated in LaTeX and CSS without recourse to an image. I think it fits the spirit and nature of Pandoc and is a desideratum and a Good Thing.
Not that my opinion has any weight but I hope jgm will consider it. At the very least it also diminishes the risk that people (ab)use a bitmap image where vector graphics are appropriate.


Den ons 15 jan. 2020 09:19Alexis BRENON <brenon.alexis-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev:
I agree that it doesn't have to be a real/specific font.
In the beginning, the idea was to be able to insert the logo without relying on a "premade" image.
But as we can see, using the chosen pilcrow as a letter inside a word doesn't feel well.
Moreover, as it is a manually reversed pilcrow, it can't be easily added to all formats.
In my opinion, designing a "pictural" logo would let us more room to make a good one, and would better fit the use cases (like the one showcased by @allefeld).

From this idea, I made a variant of the Vollkorn pilcrow taking some ideas from the whole conversation.
John seems to like to see the "pi" letter as well as a "D", and most of us agree on using something looking like a "P".
So I separated the bowl from the vertical lines bringing some advantages:
* The "pi" and the "D" are more visible (I can still do more works on the upper junction to make the "pi" more evident -- adding some curve similar to the left one, making some offset overlap to highlight the separation, etc.)
* We keep a "P" shape related to the first letter of "Pandoc"
* It is not a "simple" pilcrow anymore, so decrease the risk of confusion from the users.

Using a box around is a good idea making it stands as "I am a logo".
However, a simple square or diamond doesn't bring much meaning.
I used an ISO A4 page symbol which was often used in the previous logo propositions.
One more time, some more work can be done here, like using a letter-sized page (which would make it more squarish).

logo_512.png

What do you think about this compromised: starting from a well-designed pilcrow and customizing it to make it looks like a logo.

Kind.

Le mar. 14 janv. 2020 à 21:46, BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> a écrit :
Does it necessarily have to be a specific font? I doubt people will care about such details as long as the general look is the expected one, the pilcrow, a box (the idea of a square rotated 45 degrees, i.e. a lozenge, seems a good one to me BTW) and the expected general color in a color document. OTOH if the font is the "right" one but other details are wrong, like a non-reversed pilcrow, a circle instead of a box or the wrong color the "right" font doesn't help.  Most people who aren't font nerds (I used to be one when I was younger actually) won't notice any font differences less gross than filled vs. not filled, w/o a "leg" or sans vs. serif.


Den tors 9 jan. 2020 18:52allefeld <c_a-1KBjaw7Xf1+zQB+pC5nmwQ@public.gmane.org> skrev:
I did have the concern expressed above that the reversed Pilcrow
in a box e.g. in an editor menu looks like it should create a new
paragraph,

I wouldn't be too concerned about that. The Pilcrow is familiar as an end-of-paragraph symbol, but I have never seen an editor that uses it to stand for "create paragraph".

Apparently there is a Pilcrow button in MS Word, but that stands for "show hidden formatting".

For my own package, I think that the documentation
should make it completely clear.

And once the symbol is used on the Pandoc website, users will automatically start associating it with Pandoc.

 
and isn't obviously recognizable as a logo.

A properly designed logo would certainly be nice. A while ago there was a comment from a designer on the repo offering to design a logo. I left a comment, maybe he chimes in.

But I would propose that for the moment we just settle on a font, and leave possible further logo design for the future.

And that would mean that you, John, have to decide which font it is supposed to be. :)

C

--
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@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/921cd6a2-2d51-4c82-bf29-97627318519f%40googlegroups.com.

--
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhARUsq4GnQAuykH4tXjHAaRe%3DYB2EKEwnshJZ9496K-9Q%40mail.gmail.com.

--
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-/JYPxA39Uh4Ykp1iOSErHA@public.gmane.orgm.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CAJPB9o0-2RT%3DKd733Xj2vqDTgGoozqX%2B7V_SCd%3DLD%3D6EbuGChg%40mail.gmail.com.

--
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhAnKavwk3CkT77h5Z4jQJetmko-pjR-xhh-DQ%2B6Ci_sRA%40mail.gmail.com.