The Markdown Mark by Dustin Curtis
dcurt.is
dcurt.is
(Most implementors feel Markdown could use some expansion — see MultiMarkDown, PHP Markdown Extra, Python Markdown — but Gruber is having none of it and stopped moderating the group, and no consensus has been reached about how to unify the various flavors, except that it can’t be done without significant time investment and a rough consensus.)
At some point several years ago, I was naming all my markdown files like foo.m↓, but after a while I decided that foo.mdown probably plays nicer w/ typical software. :-)
Edit: Having said that, I think Dustin's is probably easier to understand without explanation.
Personally I like this one the most http://dribbble.com/shots/424394-Markdown - as the dashes are really reminding me Markdown.
https://plus.google.com/102359018718464872517/posts/LKJA5Uua...
_ _
| V | ||
|_v_| \/
MARKDOWNEDIT: Is it? Text files should be readable by everyone, which rules out special characters like "" (I can't even write it).
However, what's the corner radius? What's the width of the stroke on the M? The depth of the point of the arrow or the width of its sweep?
It seems like he's got the spacing and sizing of line-width elements specified to a 'T' (or an 'X' as the case may be), but can we typeset the M in, say, Times? Can the down arrow be a chevron instead?
Particular, but if he's going for particular he's taking it nearly far enough. :P
Bullet points 1 and 2, for instance:
1. Do not change the aspect ratio of the rounded box enclosure.
2. Do not change the border radius of the rounded box enclosure.
Neither of these properties were defined as far as I could see. Perhaps it's one of those cases where you're expected to "see" it from the graphics; I typically don't operate well that way. :)Personally -- and apologies if this sounds brash as I don't think we need empty back patting here -- I think his proposed logo is ugly and amateurish. The M already has an arrow in it if one really needs to make such a literal indicator.
The GNU Unifont, which is GPL licensed, support all the basic unicode characters (that's 65,536 characters!) and can be downloaded from here: http://unifoundry.com/unifont.html
If you use Debian (and possibly in other Linux distros), you can just install the ttf-unifont package.
Another font with (I think) more or less equal character support is http://en.wikipedia.org/wiki/Code2000
In any case, I agree, but the proper solution should be for OSs to come with fonts to cover that Unicode spectrum. It eliminates much of the utility of having Unicode in the first place if you can't safely use them.
My question is on the adoption on text based interfaces, like HN input. Using html entities … ...
Html entities save a better explicit defination in web. Image rendering will get you there, building another context will definitely ease adoption. What do you think?
http://dribbble.com/shots/423934-This-Means-Markdown/rebound...
I wonder though, shouldn't any serious effort to do this try to get Gruber on board? He seems to have some design sense and declaring "this is the markdown logo" without his approval just seems a bit.. disrespectful?
I guess all jokes eventually come around.
http://dribbble.com/shots/423934-This-Means-Markdown
Another nice one:
Embedding the context doesn't help with the second one.
encoding with the first one solves them. Dustin, how would this keep the context in application and web?
It definitely looks nice, though.
Having a bit of delight and 'aha!' in a logo is a good thing.
I'd love to see it being used in more blog commenting systems.
Some implementations (like the one here on HN) support only a couple of features. It's more of an archetype than a proper standard.
Anyways, it's great to see this come from concept (Dribble) to a detailed mark/brand. What other languages have their own mark?
Thought it would look better like a button or badge.