<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.text.markdown.general">
    <title>gmane.text.markdown.general</title>
    <link>http://blog.gmane.org/gmane.text.markdown.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.markdown.general/3566"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.markdown.general/3545"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.markdown.general/3534"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.markdown.general/3531"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.markdown.general/3529"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.markdown.general/3528"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.markdown.general/3526"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.markdown.general/3525"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.markdown.general/3522"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.markdown.general/3517"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.markdown.general/3515"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.markdown.general/3510"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.markdown.general/3509"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.markdown.general/3505"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.markdown.general/3502"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.markdown.general/3493"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.text.markdown.general/3566">
    <title>Media type for markdown?</title>
    <link>http://comments.gmane.org/gmane.text.markdown.general/3566</link>
    <description>&lt;pre&gt;I think it's about time that markdown had its own IANA media type.   
Markdown is mature enough and there are plenty of implementations.  I  
suggest text/markdown.

Here's a list of currently registered text subtypes: http://www.iana.org/assignments/media-types/text/

What are your thoughts?

--Dietrich Epp
&lt;/pre&gt;</description>
    <dc:creator>Dietrich Epp</dc:creator>
    <dc:date>2010-03-06T21:46:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.markdown.general/3545">
    <title>Markdown development</title>
    <link>http://comments.gmane.org/gmane.text.markdown.general/3545</link>
    <description>&lt;pre&gt;Not only is [Markdown] dead, it's starting to smell really bad. (Apologies to Pike.)

It's author appears to have little interest in developing the tool and participating in the community which uses it.

I'd like to see the community cooperate toward a specification which addresses the shortcomings and ambiguities of Markdown (even if it need be released under a new name).
&lt;/pre&gt;</description>
    <dc:creator>Albert Skye</dc:creator>
    <dc:date>2010-03-05T18:32:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.markdown.general/3534">
    <title>multiline header</title>
    <link>http://comments.gmane.org/gmane.text.markdown.general/3534</link>
    <description>&lt;pre&gt;Hi,

first of all thanks for such a great syntax, so far it's the best I know!

I have a document with quite long titles and I was wondering if it was 
possible to hard-break them:

e.g.:

This is a veeeeeeeeeeeeeeeeeeerrrrrrrrrrrrry long title
=======================================================

would be

This is a veeeeeeeeeeeeeeeeeeerrrrrrrrrrrrry
============================================
long title
==========

Right now it produces two &amp;lt;h1/&amp;gt; tags.


Best,

Alexandre
&lt;/pre&gt;</description>
    <dc:creator>Alexandre Leray</dc:creator>
    <dc:date>2010-03-01T21:22:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.markdown.general/3531">
    <title>markdown's reference links with the implicit name syntax -improvement suggestion?!?</title>
    <link>http://comments.gmane.org/gmane.text.markdown.general/3531</link>
    <description>&lt;pre&gt;I like to use markdown's reference links with the implicit name syntax.  It allows keeping a table of links seperate from the referencing link.

However, what I don't like is that I have no way of (optionally) including the table of links in the markdown's output.

For instance, in the example:


I get 10 times more traffic from [Google][] than from
[Yahoo][] or [MSN][].

  [google]: http://google.com/        "Google"
  [yahoo]:  http://search.yahoo.com/  "Yahoo Search"
  [msn]:    http://search.msn.com/    "MSN Search"

The hypertext it produces is fine, and includes the links as defined by the reference links.  But I would like additionally to be able to have the table of links appears elsewhere in the html output.  

Is there some way of extending markdown in this direction.

Perhaps a syntax like [][] would produce a table of links, and [][id1,id2] would produce the table for just links with ids of id1 or id2.....

Malcolm Cook
Stowers Institute for Medical Research -  Bioinformatics
Kansas City, Missouri  USA
&lt;/pre&gt;</description>
    <dc:creator>Cook, Malcolm</dc:creator>
    <dc:date>2010-02-04T22:08:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.markdown.general/3529">
    <title>Markdown settings for vim?</title>
    <link>http://comments.gmane.org/gmane.text.markdown.general/3529</link>
    <description>&lt;pre&gt;Anyone recommend a markdown plugin/(syntax highlighting, indentation and
other filetype-dependent settings) for vim? There seems to be a bunch of
files floating around, I wondered if anyone had any opinions about which
is best.

thanks
&lt;/pre&gt;</description>
    <dc:creator>chombee</dc:creator>
    <dc:date>2010-01-25T18:07:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.markdown.general/3528">
    <title>PHP Markdown Extra Math</title>
    <link>http://comments.gmane.org/gmane.text.markdown.general/3528</link>
    <description>&lt;pre&gt;This is a minor extension to Michel Fortin's work that helps me add
equations using LaTeX syntax (via jsMath) to my blog posts. It's based
on v. 1.2.4. There's a brief description here

http://www.leancrew.com/all-this/2009/12/php-markdown-extra-math/

and the GitHub repository is here

http://github.com/drdrang/php-markdown-extra-math

The display math code seems fairly clean to me, but the inline math is
a bit messy, as I had to pry open Michel's handleSpanToken function.
The code works for me, but suggestions for improvement are welcome.
&lt;/pre&gt;</description>
    <dc:creator>Dr. Drang</dc:creator>
    <dc:date>2009-12-22T19:26:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.markdown.general/3526">
    <title>[ANN] kramdown - a fast new Ruby Markdown-superset parser</title>
    <link>http://comments.gmane.org/gmane.text.markdown.general/3526</link>
    <description>&lt;pre&gt;Hi everybody,

wanted to let you know that I have just released version 0.2.0 of
kramdown.

kramdown is a *free* GPL-licensed [Ruby](http://www.ruby-lang.org)
library for parsing a superset of Markdown. It is completely
written in Ruby, supports standard Markdown (with some minor
modifications) and various extensions that have been made popular by
the PHP Markdown Extra package and Maruku.

It is probably the fastest pure-Ruby Markdown converter available
(December 2009), being 5x faster than Maruku and about 10x faster
than BlueFeather (although still 30x slower than native code like
BlueCloth 2 or rdiscount). It also seems to be on par with PHP
Markdown but way faster than PHP Markdown Extra and Markdown.pl (but
this has not been tested extensively).

Since the conversion of a kramdown document is done in two steps,
first building an intermediate tree representation of the
document while parsing and then rendering the tree as HTML fragment, it
should also be easy to add additional converters for outputting, for
example, a PDF file via LaTeX.

I have also written a detailed syntax description for the kramdown
syntax (the superset of Markdown which kramdown parses) which is
available at &amp;lt;http://kramdown.rubyforge.org/syntax.html&amp;gt; and a [quick
reference sheet](http://kramdown.rubyforge.org/quickref.html) for quick
lookup purposes.
Homepage for installation instructions and documentation:
    http://kramdown.rubyforge.org

Best regards,
  Thomas
&lt;/pre&gt;</description>
    <dc:creator>Thomas Leitner</dc:creator>
    <dc:date>2009-12-03T20:06:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.markdown.general/3525">
    <title>New Markdown parser in Perl: Markdent</title>
    <link>http://comments.gmane.org/gmane.text.markdown.general/3525</link>
    <description>&lt;pre&gt;I've recently released a new Markdown parser in Perl, called Markdent. 
This differs from the existing Perl tools (and most other language tools 
I've seen) in that it's an event-driven parser.

This lets you analyze the document in much more interesting ways, as well 
as cache parse results (but not HTML generation), and do other fun stuff.

The module is also designed so that it's relatively easy(ish) to create 
Markdown dialects. Right now it ships with a dialect that supports David 
Wheeler's table syntax proposal at 
http://www.justatheory.com/computers/markup/markdown-table-rfc.html. The 
actual implementation is slightly different from David's proposal, but 
mostly with his blessing ;)

The module is on CPAN at http://search.cpan.org/dist/Markdent/

I also wrote a bit about why this module can be useful in a blog post at 
http://blog.urth.org/2009/11/whats-the-point-of-markdent.html


-dave

/*============================================================
http://VegGuide.org               http://blog.urth.org
Your guide to all that's veg      House Absolute(ly Pointless)
============================================================*/
&lt;/pre&gt;</description>
    <dc:creator>Dave Rolsky</dc:creator>
    <dc:date>2009-11-29T18:51:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.markdown.general/3522">
    <title>A Suggestion for Strikethrough Syntax</title>
    <link>http://comments.gmane.org/gmane.text.markdown.general/3522</link>
    <description>&lt;pre&gt;_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss&amp;lt; at &amp;gt;six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
&lt;/pre&gt;</description>
    <dc:creator>Bill Eccles</dc:creator>
    <dc:date>2009-11-04T23:06:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.markdown.general/3517">
    <title>Order of Markdown and SmartyPants filters (was: Re: Markdown Support in Drupal6.14?)</title>
    <link>http://comments.gmane.org/gmane.text.markdown.general/3517</link>
    <description>&lt;pre&gt;_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss&amp;lt; at &amp;gt;six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
&lt;/pre&gt;</description>
    <dc:creator>Joonas Pulakka</dc:creator>
    <dc:date>2009-10-22T17:29:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.markdown.general/3515">
    <title>Markdown Support in Drupal6.14?</title>
    <link>http://comments.gmane.org/gmane.text.markdown.general/3515</link>
    <description>&lt;pre&gt;_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss&amp;lt; at &amp;gt;six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
&lt;/pre&gt;</description>
    <dc:creator>AJG Baeumel</dc:creator>
    <dc:date>2009-10-19T19:20:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.markdown.general/3510">
    <title>Treetop or like grammar for Markdown (in Ruby)</title>
    <link>http://comments.gmane.org/gmane.text.markdown.general/3510</link>
    <description>&lt;pre&gt;Has anyone seen any attempts to give Markdown a PEG (parsing
expressions grammar) recognizable by some ruby PEG parser generator
grammar like Treetop?
http://treetop.rubyforge.org/
&lt;/pre&gt;</description>
    <dc:creator>Costa Shapiro</dc:creator>
    <dc:date>2009-10-19T00:27:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.markdown.general/3509">
    <title>PHP Markdown 1.0.1n &amp; Extra 1.2.4</title>
    <link>http://comments.gmane.org/gmane.text.markdown.general/3509</link>
    <description>&lt;pre&gt;Hello all.

This is an update to PHP Markdown and PHP Markdown Extra correcting a  
couple of bugs that got reported since last release.

I also decided to enable in this release shortcut-style reference  
links (as present in Markdown.pl 1.0.2 beta), as most implementations  
of Markdown accepts them by default. It's also because waiting for  
John to release officially version 1.0.2 as an actual release (instead  
of a beta) for enabling this feature looks like a dead end at the  
moment.

So you can download it from here:
&amp;lt;http://michelf.com/projects/php-markdown/&amp;gt;

As usual, you can also grab the latest release from the PEAR channel  
at &amp;lt;http://pear.michelf.com/&amp;gt; or the Git repository mirror at &amp;lt;http://git.michelf.com/php-markdown/ 
 &amp;gt;


Here is the detailed list of changes.


1.0.1n (10 Oct 2009):

*Enabled reference-style shortcut links. Now you can write reference- 
style
links with less brakets:

This is [my website].

[my website]: http://example.com/

This was added in the 1.0.2 betas, but commented out in the 1.0.1  
branch,
waiting for the feature to be officialized. [But half of the other  
Markdown
implementations are supporting this syntax][half], so it makes sense  
for
compatibility's sake to allow it in PHP Markdown too.

  [half]: http://babelmark.bobtfish.net/?markdown=This+is+%5Bmy+website%5D.%0D%0A%09%09%0D%0A%5Bmy+website%5D%3A+http%3A%2F%2Fexample.com%2F%0D%0A&amp;amp;src=1&amp;amp;dest=2

*Now accepting many valid email addresses in autolinks that were
previously rejected, such as:

&amp;lt;abc+mailbox/department=shipping&amp;lt; at &amp;gt;example.com&amp;gt;
&amp;lt;!#$%&amp;amp;'*+-/=?^_`.{|}~&amp;lt; at &amp;gt;example.com&amp;gt;
&amp;lt;"abc&amp;lt; at &amp;gt;def"&amp;lt; at &amp;gt;example.com&amp;gt;
&amp;lt;"Fred Bloggs"&amp;lt; at &amp;gt;example.com&amp;gt;
&amp;lt;jsmith&amp;lt; at &amp;gt;[192.0.2.1]&amp;gt;

*Now accepting spaces in URLs for inline and reference-style links.  
Such
URLs need to be surrounded by angle brakets. For instance:

[link text](&amp;lt;http://url/with space&amp;gt; "optional title")

[link text][ref]
[ref]: &amp;lt;http://url/with space&amp;gt; "optional title"

There is still a quirk which may prevent this from working correctly  
with
relative URLs in inline-style links however.

*Fix for adjacent list of different kind where the second list could
end as a sublist of the first when not separated by an empty line.

*Fixed a bug where inline-style links wouldn't be recognized when the  
link
definition contains a line break between the url and the title.

*Fixed a bug where tags where the name contains an underscore aren't  
parsed
correctly.

*Fixed some corner-cases mixing underscore-ephasis and asterisk- 
emphasis.


Extra 1.2.4 (10 Oct 2009):

*Fixed a problem where unterminated tags in indented code blocks could
prevent proper escaping of characaters in the code block.


&lt;/pre&gt;</description>
    <dc:creator>Michel Fortin</dc:creator>
    <dc:date>2009-10-10T17:23:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.markdown.general/3505">
    <title>Scripting: Invoke Markdown *before* SmartyPants</title>
    <link>http://comments.gmane.org/gmane.text.markdown.general/3505</link>
    <description>&lt;pre&gt;I could not find anywhere in John Gruber's documentation the  
recommended order of Markdown vs. SmartyPants in a scripted process.   
I guessed SmartyPants first, and that worked until I tried to encode a  
link with a title like this:

    An [example](http://url.com/ "Title")

SmartyPants encoded the quotes, which created a mess.

So, I changed the order to process text through Markdown first, then  
SmartyPants.  So far, so good.
&lt;/pre&gt;</description>
    <dc:creator>Jerry Krinock</dc:creator>
    <dc:date>2009-09-22T16:42:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.markdown.general/3502">
    <title>lunamark - markdown in lua using a PEG grammar</title>
    <link>http://comments.gmane.org/gmane.text.markdown.general/3502</link>
    <description>&lt;pre&gt;Markersdown:

I was fooling around with lua and decided to write a markdown parser
using the terrific lpeg library.  Here's the result:
http://github.com/jgm/lunamark/tree/master

There are already two markdown libraries for lua, one a native lua
implementation based on global substitutions, the other a binding
to discount.  What makes lunamark different is that it is based
on a PEG grammar (adapted from my peg-markdown).  This can be found
in the file lunamark/markdown_parser.lua in the source tree.

Lunamark converts standard markdown to HTML and LaTeX.  Adding
a new output format is easy (the LaTeX writer took about 20 minutes
to add).  It is also possible to add new input formats.

Lunamark passes the Markdown 1.0.3 test suite (except for one edge
case involving loose/tight lists, and here its behavior is consistent
with the markdown syntax description -- see the README for peg-markdown
for discussion).

As for performance, lunamark is about the same speed as PHP Markdown in
my tests.

John
&lt;/pre&gt;</description>
    <dc:creator>John MacFarlane</dc:creator>
    <dc:date>2009-09-12T03:30:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.markdown.general/3493">
    <title>tables with Unicode box drawing characters?</title>
    <link>http://comments.gmane.org/gmane.text.markdown.general/3493</link>
    <description>&lt;pre&gt;Hello,

I read David Wheeler's table proposal[1] for Markdown and very much
agree with his conclusion and PostgreSQL-inspired proposed format.  I
also read the mailing list archives for 2009 but did not find any
clear concesus on whether DW's format was officially accepted (I hope
it is soon!).

However, I want to ask: has anyone considered taking these simple
ASCII table drawings to the next level of realism with Unicode box
drawing characters[2]?  I have long admired the w3m browser[3]'s
ability to render HTML tables using Unicode box drawing characters.
For example, w3m renders this[4] demo page as follows[5]:

                     A more complex table-within-a table.
               An inner table showing a variety of headings and data items.
            ┌────────────────────────────────────────────────────────────────┐
            │                          Inner Table                           │
            ├───────────────────┬────────────────────────────────────────────┤
            │                   │                   Head1                    │
            │      CORNER       ├────────────────────────────┬───────────────┤
            │                   │                            │     Head3     │
            ├───────────┬───────┤           Head2            ├──────┬────────┤
            │   Head4   │ Head5 │                            │Head6 │        │
   Outer    ├───────────┼───────┼────────────────────────────┼──────┴────────┤
   Table    │A          │       │  • Lists can be table data │   Two Wide    │
            │           │       │  • Images can be table data│               │
            ├───────────┤       ├────────────────────────────┼──────┬────────┤
            │           │Two    │A Form in a table: Your age:│      │        │
            │           │Tall   │            [  ]            │  No  │Multiple│
            │HTML       │       │ What is your favorite ice  │border│line    │
            │Station    │       │           cream?           │Little│item    │
            │           │       │    [Chocolate         ]    │Table │        │
            │           │       │       [OK] [Cancel]        │      │        │
            └───────────┴───────┴────────────────────────────┴──────┴────────┘


What if Markdown used Unicode characters to express tables in this manner?

All we need are two essential subsets of the Unicode box drawing characters:
* thin ones for normal cells: ┌ ┐ └ ┘ ─ │
* thick ones for heading cells: ╔ ╗ ╚ ╝ ═ ║

Thanks for your consideration.

[1]: http://justatheory.com/computers/markup/markdown-table-rfc.html
[2]: http://en.wikipedia.org/wiki/Box_drawing_characters
[3]: http://w3m.sourceforge.net/
[4]: http://www.december.com/html/demo/table.html
[5]: http://snk.tuxfamily.org/tmp/w3m-tables.png
_______________________________________________
Markdown-Discuss mailing list
Markdown-Discuss&amp;lt; at &amp;gt;six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
&lt;/pre&gt;</description>
    <dc:creator>Suraj Kurapati</dc:creator>
    <dc:date>2009-09-09T04:18:56</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.text.markdown.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.text.markdown.general</link>
  </textinput>
</rdf:RDF>
