Hi! Suggestions can be posted here? I made a change to the code - markdown.php (included in the Yii framework) to support target="_blank" in urls. This change doesn't affect the existing markdown texts. Regards,
Hello, FYI: If anyone is interested I've prepared a talk on Markdown for the vienna.rb meetup last night with the title "Using Markdown for Websites, Presentations, or Books" [1]. Use the left/right cursor keys (or space bar) to browse the slides. Or check the all-in-one-page markdown source [2]. Slides include: * What's Markdown? * Syntax - Text Formatting * Syntax - Header Formatting * Syntax - Hyperlink * What is Markdown good for? * Example - Website * Example - Presentation * Example - Book * Markdown Parsers in Ruby * What's the `markdown` Gem? * Tooling - Websites * Tooling - Presentations * Tooling - Books * That's it. Thank you. * Appendix: What's EPUB? * Appendix: Zen Writing - Zen Text Editor * Appendix: What's Markdown Extra? * Appendix: What's Babelmark2? What's Markdown Dingus? All content is public domain. Feel free to reuse as you please. Cheers. [1] http://slideshow-s9.github.io/markdown.html(Continue reading)
Hello, What's the markdown Ruby gem? The Markdown Engine Wrapper (markdown) Ruby gem lets you use your markdown library of choice using environment or markdown.yml settings. Preconfigured engines include kramdown, redcarpet, bluecloth, maruku, and others. What's new? The markdown Ruby gem now includes a builtin web service/server. Try the markdown web service/HTTP API running on Heroku <at> http://hypertext.herokuapp.com (or http://hypertext.herokuapp.com/service ) or start your own server issue the command: markdown server or markdown s More info <at> https://github.com/geraldb/markdown Cheers. PS: The service on Heroku offers Babelmark2 Dingus services for kramdown, redcarpet, bluecloth and maruku. Use/try these links: - http://hypertext.herokuapp.com/dingus?lib=redcarpet&text=Hello+World - http://hypertext.herokuapp.com/dingus?lib=bluecloth&text=Hello+World(Continue reading)
sherwood said: > Several people have spoken eloquently that > this is a Bad Thing (tm) and no one has agreed. > I must abide by the Will of the People, and > withdraw to the Cave of the Curmudgeons. we don't yet know the will of the people, sherwood. because "the people" generally do not even realize there is a problem with markdown fractionalization. all we have, thus far, are markdown _developers_ who continue to assert that "there isn't a problem" -- over and above what michel terms "edge cases" and "extensions to the core syntax" -- as if those "extensions" weren't absolutely necessary so as to overcome the primitive nature of "the core syntax". but when "the people" come to learn the reality of the inconsistencies that will break their documents, they will squawk loudly, and we'll know their "will"... you can hear the beginning of the rumbling already, from the techies who are using markdown, and are -- as a result of that normal usage -- thus becoming aware of the problems once their users go past the superficial nature of the 10-minute markdown intro. ergo, outcry from stack-overflow and github people.(Continue reading)
Hi guys, I wrote a markdown based Web editor thing for my sister: http://ws.dabase.com/ And she has trouble styling blocks of markdown. Since <div markdown=1>markdown here</div> does not work on my Debian markdown binary. Is there a formal definition of markdown? Or some sort of conformance test? And certain markdown implementations I should be using, and certain ones I should be avoiding? Why doesn't markdown work within div blocks? Is there some technical reason? Out of interest, I would like to know why, since my expectation was to mix&match markdown with HTML. Is there some other way I'm not thinking of, in order to style sections of markdown? Oh and is there something better that Pagedown? Because that also doesn't seem to grok <div markdown=1>markdown here</div>. Many thanks!
This is the first release of PHP Markdown Lib. This package requires PHP version 4.3 or later and is designed to work with PSR-0 autoloading and, optionally, with Composer. You can download it from the PHP Markdown website: <http://michelf.ca/projects/php-markdown/> You can also read the official announcement here: <http://michelf.ca/blog/2013/php-markdown-lib/> Also note new versions of PHP Markdown 1.0.1q & Extra 1.2.7 were just released too. They're now labeled as the "classic" version, and as previously mentioned on this list I will stop updating those next year, focusing in the Lib version. <http://michelf.ca/projects/php-markdown/classic/> Here is a list of the changes in Lib since the previous classic release (some of the changes are also included in the classic version, see the website for details): PHP Markdown Lib 1.3 (11 Apr 2013): * Plugin interface for Wordpress and other systems is no longer present in the Lib package. The classic package is still available if you need it: <http://michelf.ca/projects/php-markdown/classic/> * Added `public` and `protected` protection attributes, plus a section about what is "public API" and what isn't in the Readme file. * Changed HTML output for footnotes: now instead of adding `rel` and `rev` attributes, footnotes links have the class name `footnote-ref` and backlinks `footnote-backref`. * Fixed some regular expressions to make PCRE not shout warnings about POSIX collation classes (dependent on your version of PCRE).(Continue reading)
Markdown is a fantastic program (which I am sure you already know). It saves me a lot of time. Currently, I use the dingus located at: http://daringfireball.net/projects/markdown/dingus However, I am trying to set one up just like that, locally - on my own system, without having to use that one (wasting the bandwidth, and having to switch to the site every time to use it). I am running Ubuntu. (I have seen some alternatives but, so far, using the dingus as above is the easiest by far.) Thanks, Lee Underwood
Last night I released version 2.3 of Python Markdown (see the release
notes [1] for all the details). In addition to various other
improvements, a new **experimental** extension was included that added
a syntax for generating rST-style admonitions [2]. For a summary of
the syntax, see the documentation [3]. A broader sample of the output
can be seen on this page [4]. The source text can be found by swapping
the ".html" file extension for ".txt" [5]. You can test it here [6]
(be sure to enable the extension).
!!! Warning
Experimental code has been released into the wild!
As noted, this is considered experimental. It is subject to change. I
realize that I could have overlooked something obvious and am not yet
completely committed to the syntax. Interestingly, I had drafted a
proposal some time ago (maybe a year ago) but never finished it.
Independently, "slig" [7] proposed an almost identical proposal [8].
Seeing how close our proposals were, we tweaked the syntax (meeting in
the middle) and "slig" wrote all the code.
So what does everyone think? I know the examples in the
Python-Markdown docs aren't the best. We're using the Python default
documentation theme (CSS) which makes the title inline with the first
paragraph - which is a little weird. What's great about it though, is
that no changes needed to be made to the CSS for it to work. Same
applies to any Sphinx themes [9].
[1]: http://pythonhosted.org/Markdown/release-2.3.html
[2]: http://docutils.sourceforge.net/docs/ref/rst/directives.html#specific-admonitions
[3]: http://pythonhosted.org/Markdown/extensions/admonition.html
(Continue reading)
Question: what should be the output for this: > for me the point of having my blog as a static site is mainly easy deployment<br> > I don't have to worry about even configuring PHP<br> > I just put html on a web server and boom! instant win > > <footer>— [Igor Wiedler wins](https://igor.io)</footer> The real question is how to treat `<footer>`. Is it a block-level element like `<div>`? That should mean that the content would be passed to the output literally. One thing for sure, it's not a span element, as the HTML spec forbids putting it inside a `<p>`. Perhaps is should be something in between. Many of the new HTML5 elements are in that same situation. In PHP Markdown 1.0.1p I started treating them as block-level elements and they get the same treatment as `<div>`, but implementations don't seem to agree on this (and yes PHP Markdown Extra gives something that makes no sense): http://johnmacfarlane.net/babelmark2/?normalize=1&text=%3E+for+me+the+point+of+having+my+blog+as+a+static+site+is+mainly+easy+deployment%3Cbr%3E%0A%3E+I+don't+have+to+worry+about+even+configuring+PHP%3Cbr%3E%0A%3E+I+just+put+html+on+a+web+server+and+boom!+instant+win%0A%3E%0A%3E+%3Cfooter%3E—+%5BIgor+Wiedler+wins%5D(https%3A%2F%2Figor.io)%3C%2Ffooter%3E%0A I find it somewhat worrying that the reference tool (Markdown.pl) treats it as a span element. Well, I don't care that much about what old Markdown.pl does, but I do care about people trying it there on the dingus and finding that it works as they intended (if they only look at the rendered output, they won't see the mess in HTML tags), and then getting an unexpected and undesired result with other implementations. Reference: https://github.com/michelf/php-markdown/issues/67 -- -- Michel Fortin michel.fortin <at> michelf.ca http://michelf.ca/(Continue reading)
_______________________________________________ Markdown-Discuss mailing list Markdown-Discuss <at> six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
I just received a [bug report] for Python-Markdown complaining that colons are used in the ids of footnotes. For reference, we [output] the same format at PHP Markdown Extra. The general complaint is that the colon in the id attribute (`id="fnref:1"`) causes jquery to choke when referencing that id from javascript because jquery uses colons to indicate pseudo elements (as does CSS). As expected, jquery supports escaping the colon - which eliminates the problem - except that apparently the escaping causes a performance hit. My initial reaction is to say that this is jquery's problem, but what do you think? Should the various implementations that support footnotes all change to not use colons? I couldn't help but note that Gruber's unreleased implementation (what he uses on daringfireball.com) appears to use dashes instead. Any thoughts? [bug report]: https://github.com/waylan/Python-Markdown/issues/180 [output]: http://michelf.ca/projects/php-markdown/extra/#fn-output -- ---- \X/ /-\ `/ |_ /-\ |\| Waylan Limberg
RSS Feed2 | |
|---|---|
4 | |
17 | |
6 | |
4 | |
8 | |
15 | |
22 | |
106 | |
9 | |
50 | |
4 | |
46 | |
19 | |
10 | |
6 | |
36 | |
23 | |
29 | |
51 | |
98 | |
44 | |
63 | |
40 | |
79 | |
88 | |
35 | |
12 | |
26 | |
23 | |
14 | |
19 | |
2 | |
24 | |
6 | |
14 | |
23 | |
18 | |
77 | |
3 | |
2 | |
3 | |
4 | |
14 | |
15 | |
10 | |
7 | |
30 | |
17 | |
20 | |
17 | |
96 | |
2 | |
4 | |
18 | |
4 | |
44 | |
1 | |
31 | |
6 | |
61 | |
29 | |
186 | |
100 | |
23 | |
33 | |
18 | |
61 | |
45 | |
54 | |
41 | |
37 | |
34 | |
2 | |
38 | |
31 | |
73 | |
79 | |
11 | |
95 | |
70 | |
50 | |
56 | |
34 | |
37 | |
24 | |
1863 |
