From svicalifornia at gmail.com Mon May 3 22:13:36 2010 From: svicalifornia at gmail.com (Shawn Van Ittersum) Date: Tue, 4 May 2010 12:13:36 +1000 Subject: [kramdown-users] Problem with new extension syntax In-Reply-To: <20100428205248.5c5a0cfa@noeato.local> References: <20100416112353.01646de1@noeato.local> <4BCCB0F8.6070403@sunshineco.com> <20100420142426663263.59e9c710@gmail.com> <20100420101706.0399325f@noeato.local> <20100420183120360818.87d63fce@gmail.com> <20100428082619.6c66c7c8@noeato.local> <20100429003337514102.1cd62f4f@gmail.com> <20100428205248.5c5a0cfa@noeato.local> Message-ID: <20100504121336267908.1974bb06@gmail.com> Just that there is some confusion between single and double colons. It's not a big deal, but it might help to use another character. Shawn On Wed, 28 Apr 2010 20:52:48 +0200, Thomas Leitner wrote: > On Wed, 28 Apr 2010 23:33:37 +1000, Shawn Van Ittersum wrote: >> Well, I prefer {:!comment...}, but double-colon works too. > > Why the bang instead of the colon? Does it mean something special in > such a context? > > -- Thomas > _______________________________________________ > kramdown-users mailing list > kramdown-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/kramdown-users From t_leitner at gmx.at Tue May 4 14:15:58 2010 From: t_leitner at gmx.at (Thomas Leitner) Date: Tue, 4 May 2010 20:15:58 +0200 Subject: [kramdown-users] TOC In-Reply-To: <20100425115647.7303ea3f@noeato> References: <20100425155357139214.3dd0fc8a@gmail.com> <20100425115647.7303ea3f@noeato> Message-ID: <20100504201558.23c40e8c@noweto> On Sun, 25 Apr 2010 11:56:47 +0200 Thomas Leitner wrote: > > Was the {:toc} extension added to kramdown, or is it still on the > > to-do list? > > It is still on my TODO list. I'm thinking about whether to add this as > an extension -- it doesn't not provide a real value regarding parsing, > therefore I would rather not have it as an extension -- or by adding a > additionaly processor between parsers and converters which works in > the same manner as Maruku's implementation of the TOC and the current > implementation of syntax highlighting. I have implemented ToC generation using Maruku's method, ie. assigning the reference name 'toc' to an ordered or unordered list. This is purely a feature of the converters, so no change was needed parser-wise. Both the HTML and the LaTeX converter have been updated to support this. -- Thomas From svicalifornia at gmail.com Wed May 5 01:48:45 2010 From: svicalifornia at gmail.com (Shawn Van Ittersum) Date: Wed, 5 May 2010 15:48:45 +1000 Subject: [kramdown-users] TOC In-Reply-To: <20100504201558.23c40e8c@noweto> References: <20100425155357139214.3dd0fc8a@gmail.com> <20100425115647.7303ea3f@noeato> <20100504201558.23c40e8c@noweto> Message-ID: <20100505154845225269.9f1e34dd@gmail.com> I'm confused about what this means. 1. If I put {:toc} in a kramdown document, will it be replaced (in-place) by an ordered or unordered hierarchical list of links to section headings in the document? 2. How do I specify whether the list should be ordered or unordered? Shawn On Tue, 4 May 2010 20:15:58 +0200, Thomas Leitner wrote: > On Sun, 25 Apr 2010 11:56:47 +0200 > Thomas Leitner wrote: > >>> Was the {:toc} extension added to kramdown, or is it still on the >>> to-do list? >> >> It is still on my TODO list. I'm thinking about whether to add this as >> an extension -- it doesn't not provide a real value regarding parsing, >> therefore I would rather not have it as an extension -- or by adding a >> additionaly processor between parsers and converters which works in >> the same manner as Maruku's implementation of the TOC and the current >> implementation of syntax highlighting. > > I have implemented ToC generation using Maruku's method, ie. assigning > the reference name 'toc' to an ordered or unordered list. This is > purely a feature of the converters, so no change was needed > parser-wise. Both the HTML and the LaTeX converter have been updated to > support this. > > -- Thomas > _______________________________________________ > kramdown-users mailing list > kramdown-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/kramdown-users From t_leitner at gmx.at Wed May 5 02:16:37 2010 From: t_leitner at gmx.at (Thomas Leitner) Date: Wed, 5 May 2010 08:16:37 +0200 Subject: [kramdown-users] Attributes on li elements In-Reply-To: <7B44B995-04CF-446D-A891-DD8791AE8D08@gmail.com> References: <20100314215737038231.a8d43853@gmail.com> <20100314193005.4a98d022@noeato> <20100315044750538443.4df2c4c9@gmail.com> <4B9D3014.1070804@sunshineco.com> <20100315000109.148edfa9@noeato> <20100315213202191412.246ae227@gmail.com> <20100315201112.2fc850c2@noeato.mat.univie.ac.at> <20100316054803764011.030ebd66@gmail.com> <20100315212709.4991971b@noeato.mat.univie.ac.at> <20100316064901474967.8f2f943b@gmail.com> <20100315221651.154f92be@noeato.mat.univie.ac.at> <7B44B995-04CF-446D-A891-DD8791AE8D08@gmail.com> Message-ID: <20100505081637.00d42aaa@noweto> On Tue, 16 Mar 2010 07:28:39 +1000 Shawn Van Ittersum wrote: > Yep, that's it. :) > > Shawn > [sent from mobile phone] > > On Mar 16, 2010, at 7:16 AM, Thomas Leitner wrote: > > >> The list item is itself a block-level element, and I'm requesting > >> that * {attribute} and 1. {attribute} become the syntax for > >> applying attributes to list item elements themselves (not some > >> other block element inside). > > > > Ah... okay! I didn't see "outside the box" ;-) This way it makes > > much more sense (and should be easier to implement). So the > > modified syntax would be: > > > > A list is started with a list marker (in case of unordered lists > > one of > > `+`, `-` or `*` -- you can mix them -- and in case of ordered lists > > a number followed by a period) followed by one tab or at least one > > space, > > optionally followed by an IAL that should be applied to the list > > item and then the first part of the content of the list item. > > > > Does this sound right? The only change to your proposed syntax > > would be > > that a real IAL is used instead of the `{.classname}` syntax. I have implemented this syntax now and it will be available with the next release. -- Thomas From t_leitner at gmx.at Wed May 5 03:29:59 2010 From: t_leitner at gmx.at (Thomas Leitner) Date: Wed, 5 May 2010 09:29:59 +0200 Subject: [kramdown-users] TOC In-Reply-To: <20100505154845225269.9f1e34dd@gmail.com> References: <20100425155357139214.3dd0fc8a@gmail.com> <20100425115647.7303ea3f@noeato> <20100504201558.23c40e8c@noweto> <20100505154845225269.9f1e34dd@gmail.com> Message-ID: <20100505092959.289daa44@noweto> On Wed, 5 May 2010 15:48:45 +1000 Shawn Van Ittersum wrote: > I'm confused about what this means. > > 1. If I put {:toc} in a kramdown document, will it be replaced > (in-place) by an ordered or unordered hierarchical list of links to > section headings in the document? 2. How do I specify whether the > list should be ordered or unordered? It will be replaced by a simple unordered list, ie. the list where the "{:toc}" was placed will be replaced with an unordered list containing the table of contents. There is currently no way to modify the way the toc is generated from the document itself but you can just subclass the HTML converter and modify the method where the toc is generated. -- Thomas From svicalifornia at gmail.com Wed May 5 03:49:00 2010 From: svicalifornia at gmail.com (Shawn Van Ittersum) Date: Wed, 5 May 2010 17:49:00 +1000 Subject: [kramdown-users] TOC In-Reply-To: <20100505092959.289daa44@noweto> References: <20100425155357139214.3dd0fc8a@gmail.com> <20100425115647.7303ea3f@noeato> <20100504201558.23c40e8c@noweto> <20100505154845225269.9f1e34dd@gmail.com> <20100505092959.289daa44@noweto> Message-ID: <20100505174900147103.ce7bb21a@gmail.com> So it will be necessary to supply an empty list to be replaced? * {:toc} Or will {:toc} stand on its own? Shawn On Wed, 5 May 2010 09:29:59 +0200, Thomas Leitner wrote: > On Wed, 5 May 2010 15:48:45 +1000 > Shawn Van Ittersum wrote: > >> I'm confused about what this means. >> >> 1. If I put {:toc} in a kramdown document, will it be replaced >> (in-place) by an ordered or unordered hierarchical list of links to >> section headings in the document? 2. How do I specify whether the >> list should be ordered or unordered? > > It will be replaced by a simple unordered list, ie. the list where the > "{:toc}" was placed will be replaced with an unordered list containing > the table of contents. There is currently no way to modify the way the > toc is generated from the document itself but you can just subclass the > HTML converter and modify the method where the toc is generated. > > -- Thomas > _______________________________________________ > kramdown-users mailing list > kramdown-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/kramdown-users From svicalifornia at gmail.com Wed May 5 03:47:34 2010 From: svicalifornia at gmail.com (Shawn Van Ittersum) Date: Wed, 5 May 2010 17:47:34 +1000 Subject: [kramdown-users] Attributes on li elements In-Reply-To: <20100505081637.00d42aaa@noweto> References: <20100314215737038231.a8d43853@gmail.com> <20100314193005.4a98d022@noeato> <20100315044750538443.4df2c4c9@gmail.com> <4B9D3014.1070804@sunshineco.com> <20100315000109.148edfa9@noeato> <20100315213202191412.246ae227@gmail.com> <20100315201112.2fc850c2@noeato.mat.univie.ac.at> <20100316054803764011.030ebd66@gmail.com> <20100315212709.4991971b@noeato.mat.univie.ac.at> <20100316064901474967.8f2f943b@gmail.com> <20100315221651.154f92be@noeato.mat.univie.ac.at> <7B44B995-04CF-446D-A891-DD8791AE8D08@gmail.com> <20100505081637.00d42aaa@noweto> Message-ID: <20100505174734191506.e3dbb60b@gmail.com> Great! Thank you. Shawn On Wed, 5 May 2010 08:16:37 +0200, Thomas Leitner wrote: > On Tue, 16 Mar 2010 07:28:39 +1000 > Shawn Van Ittersum wrote: > >> Yep, that's it. :) >> >> Shawn >> [sent from mobile phone] >> >> On Mar 16, 2010, at 7:16 AM, Thomas Leitner wrote: >> >>>> The list item is itself a block-level element, and I'm requesting >>>> that * {attribute} and 1. {attribute} become the syntax for >>>> applying attributes to list item elements themselves (not some >>>> other block element inside). >>> >>> Ah... okay! I didn't see "outside the box" ;-) This way it makes >>> much more sense (and should be easier to implement). So the >>> modified syntax would be: >>> >>> A list is started with a list marker (in case of unordered lists >>> one of >>> `+`, `-` or `*` -- you can mix them -- and in case of ordered lists >>> a number followed by a period) followed by one tab or at least one >>> space, >>> optionally followed by an IAL that should be applied to the list >>> item and then the first part of the content of the list item. >>> >>> Does this sound right? The only change to your proposed syntax >>> would be >>> that a real IAL is used instead of the `{.classname}` syntax. > > I have implemented this syntax now and it will be available with the > next release. > > -- Thomas > _______________________________________________ > kramdown-users mailing list > kramdown-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/kramdown-users From t_leitner at gmx.at Wed May 5 05:58:08 2010 From: t_leitner at gmx.at (Thomas Leitner) Date: Wed, 5 May 2010 11:58:08 +0200 Subject: [kramdown-users] TOC In-Reply-To: <20100505174900147103.ce7bb21a@gmail.com> References: <20100425155357139214.3dd0fc8a@gmail.com> <20100425115647.7303ea3f@noeato> <20100504201558.23c40e8c@noweto> <20100505154845225269.9f1e34dd@gmail.com> <20100505092959.289daa44@noweto> <20100505174900147103.ce7bb21a@gmail.com> Message-ID: <20100505115808.03320dcb@noweto> On Wed, 5 May 2010 17:49:00 +1000 Shawn Van Ittersum wrote: > So it will be necessary to supply an empty list to be replaced? > > * > {:toc} > > Or will {:toc} stand on its own? It is implemented in the same way as it is in Maruku (for compatibility), ie. the IAL with the reference has to be applied to a list. -- Thomas From svicalifornia at gmail.com Wed May 5 06:36:08 2010 From: svicalifornia at gmail.com (Shawn Van Ittersum) Date: Wed, 5 May 2010 20:36:08 +1000 Subject: [kramdown-users] TOC In-Reply-To: <20100505115808.03320dcb@noweto> References: <20100425155357139214.3dd0fc8a@gmail.com> <20100425115647.7303ea3f@noeato> <20100504201558.23c40e8c@noweto> <20100505154845225269.9f1e34dd@gmail.com> <20100505092959.289daa44@noweto> <20100505174900147103.ce7bb21a@gmail.com> <20100505115808.03320dcb@noweto> Message-ID: <20100505203608103208.59fb8dd0@gmail.com> OK, got it now. :) Can I do this to create an ordered TOC: 1. Table of Contents {:toc} and have that become: 1. Section a. Subsection b. Subsection 2. Section 3. Section ... Shawn On Wed, 5 May 2010 11:58:08 +0200, Thomas Leitner wrote: > On Wed, 5 May 2010 17:49:00 +1000 > Shawn Van Ittersum wrote: > >> So it will be necessary to supply an empty list to be replaced? >> >> * >> {:toc} >> >> Or will {:toc} stand on its own? > > It is implemented in the same way as it is in Maruku (for > compatibility), ie. the IAL with the reference has to be applied to a > list. > > -- Thomas > _______________________________________________ > kramdown-users mailing list > kramdown-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/kramdown-users From t_leitner at gmx.at Wed May 5 07:01:53 2010 From: t_leitner at gmx.at (Thomas Leitner) Date: Wed, 5 May 2010 13:01:53 +0200 Subject: [kramdown-users] TOC In-Reply-To: <20100505203608103208.59fb8dd0@gmail.com> References: <20100425155357139214.3dd0fc8a@gmail.com> <20100425115647.7303ea3f@noeato> <20100504201558.23c40e8c@noweto> <20100505154845225269.9f1e34dd@gmail.com> <20100505092959.289daa44@noweto> <20100505174900147103.ce7bb21a@gmail.com> <20100505115808.03320dcb@noweto> <20100505203608103208.59fb8dd0@gmail.com> Message-ID: <20100505130153.6937973e@noweto> On Wed, 5 May 2010 20:36:08 +1000 Shawn Van Ittersum wrote: > OK, got it now. :) Can I do this to create an ordered TOC: > > 1. Table of Contents > {:toc} > > and have that become: > > 1. Section > a. Subsection > b. Subsection > 2. Section > 3. Section > ... Currently not, but it is an easy change to allow this... is this an official feature request? ;-) -- Thomas From svicalifornia at gmail.com Wed May 5 08:05:42 2010 From: svicalifornia at gmail.com (Shawn Van Ittersum) Date: Wed, 5 May 2010 22:05:42 +1000 Subject: [kramdown-users] TOC In-Reply-To: <20100505130153.6937973e@noweto> References: <20100425155357139214.3dd0fc8a@gmail.com> <20100425115647.7303ea3f@noeato> <20100504201558.23c40e8c@noweto> <20100505154845225269.9f1e34dd@gmail.com> <20100505092959.289daa44@noweto> <20100505174900147103.ce7bb21a@gmail.com> <20100505115808.03320dcb@noweto> <20100505203608103208.59fb8dd0@gmail.com> <20100505130153.6937973e@noweto> Message-ID: <20100505220542495643.b4d8cda6@gmail.com> Yes, please. :) Shawn On Wed, 5 May 2010 13:01:53 +0200, Thomas Leitner wrote: > On Wed, 5 May 2010 20:36:08 +1000 > Shawn Van Ittersum wrote: > >> OK, got it now. :) Can I do this to create an ordered TOC: >> >> 1. Table of Contents >> {:toc} >> >> and have that become: >> >> 1. Section >> a. Subsection >> b. Subsection >> 2. Section >> 3. Section >> ... > > Currently not, but it is an easy change to allow this... is this an > official feature request? ;-) > > -- Thomas > _______________________________________________ > kramdown-users mailing list > kramdown-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/kramdown-users From t_leitner at gmx.at Wed May 5 11:08:03 2010 From: t_leitner at gmx.at (Thomas Leitner) Date: Wed, 5 May 2010 17:08:03 +0200 Subject: [kramdown-users] Towards the one-oh-oh Message-ID: <20100505170803.29c8e268@noweto> Hi everybody, although the first release of kramdown was just over half a year ago, it grew rather fast and is very mature now. Many bugs in the parser have been fixed with your help and the syntax has been extended to be on par with other Markdown converters. As of 0.7.0 all major syntax extension to Markdown (tables, definition lists, abbreviations, headers IDs, ...) have been added to kramdown. And its extension syntax has been finalized in the last few week. Regarding the converters, the HTML and LaTeX converters are also working well (or the LaTeX converter is not really used ;-) Therefore I think that kramdown 1.0.0 can be released soon and for this I would like to finalize the kramdown syntax and the library API. So I would like to know from you if there is anything missing from kramdown, either syntax-wise or feature-wise, what you would like to see in the 1.0.0 release! As for my plans regarding the 1.0.0 or some later release: * Add a Markdown/kramdown converter * Add a HTML parser based on the parsing functionality of the kramdown parser (this and the former item will allow the (partial) reconstruction of a Markdown/kramdown text from an HTML document) * Add a pure Ruby PDF converter based on Prawn once it has reached its 1.0.0 release (because the API will be stable by then) * Add a converter that takes a kramdown tree and modifies it sothat all HTML elements are converted into native kramdown elements where possible (this should allow better output for non-HTML converters when HTML is used in the source document) Since the above just add functionality, introducing them after 1.0.0 will not break compatibility. Best regards, Thomas From svicalifornia at gmail.com Wed May 5 12:32:50 2010 From: svicalifornia at gmail.com (Shawn Van Ittersum) Date: Thu, 6 May 2010 02:32:50 +1000 Subject: [kramdown-users] Towards the one-oh-oh In-Reply-To: <20100505170803.29c8e268@noweto> References: <20100505170803.29c8e268@noweto> Message-ID: <20100506023250789869.9439048a@gmail.com> Hi Thomas, I wonder if you've had time to consider my request for IAL above a block, so that these two are equivalent: {: .tasks } * Task 1 * Task 2 * Task 3 * Task 1 * Task 2 * Task 3 {: .tasks } As I pointed out in my original request for this, support for the IAL at the top makes for more intuitively placed class and ID attributes, even more so if the modified block contains children or other complicated (lengthy) structure. Please let me know if this can make it into version 0.8 or 1.0. Thanks, Shawn On Wed, 5 May 2010 17:08:03 +0200, Thomas Leitner wrote: > Hi everybody, > > although the first release of kramdown was just over half a year ago, > it grew rather fast and is very mature now. > > Many bugs in the parser have been fixed with your help and the syntax > has been extended to be on par with other Markdown converters. As of > 0.7.0 all major syntax extension to Markdown (tables, definition lists, > abbreviations, headers IDs, ...) have been added to kramdown. And its > extension syntax has been finalized in the last few week. > > Regarding the converters, the HTML and LaTeX converters are also working > well (or the LaTeX converter is not really used ;-) > > Therefore I think that kramdown 1.0.0 can be released soon and for this > I would like to finalize the kramdown syntax and the library API. > > > So I would like to know from you if there is anything missing from > kramdown, either syntax-wise or feature-wise, what you would like to > see in the 1.0.0 release! > > > As for my plans regarding the 1.0.0 or some later release: > > * Add a Markdown/kramdown converter > > * Add a HTML parser based on the parsing functionality of the kramdown > parser (this and the former item will allow the (partial) > reconstruction of a Markdown/kramdown text from an HTML document) > > * Add a pure Ruby PDF converter based on Prawn once it has reached its > 1.0.0 release (because the API will be stable by then) > > * Add a converter that takes a kramdown tree and modifies it sothat all > HTML elements are converted into native kramdown elements where > possible (this should allow better output for non-HTML converters > when HTML is used in the source document) > > Since the above just add functionality, introducing them after 1.0.0 > will not break compatibility. > > Best regards, > Thomas > _______________________________________________ > kramdown-users mailing list > kramdown-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/kramdown-users From svicalifornia at gmail.com Wed May 5 12:35:32 2010 From: svicalifornia at gmail.com (Shawn Van Ittersum) Date: Thu, 6 May 2010 02:35:32 +1000 Subject: [kramdown-users] Towards the one-oh-oh In-Reply-To: <20100505170803.29c8e268@noweto> References: <20100505170803.29c8e268@noweto> Message-ID: <20100506023532125326.a3af7a92@gmail.com> By the way, I've been using a very good HTML-to-PDF library called "dompdf" written in pure PHP. I have been thinking about porting it to Ruby. If anyone is interested in that (as contributor or user), or can suggest alternatives, please let me know. Thanks, Shawn On Wed, 5 May 2010 17:08:03 +0200, Thomas Leitner wrote: > * Add a pure Ruby PDF converter based on Prawn once it has reached its > 1.0.0 release (because the API will be stable by then) From matt at tidbits.com Wed May 5 14:08:28 2010 From: matt at tidbits.com (Matt Neuburg) Date: Wed, 05 May 2010 11:08:28 -0700 Subject: [kramdown-users] Towards the one-oh-oh In-Reply-To: <20100505170803.29c8e268@noweto> Message-ID: On or about 5/5/10 8:08 AM, thus spake "Thomas Leitner" : > So I would like to know from you if there is anything missing from > kramdown, either syntax-wise or feature-wise, what you would like to > see in the 1.0.0 release! I know there isn't much hope, as I got a very chilly reception on the previous occasion, but I will just repeat my requests, one last time: * I'd like to see the SmartyPants functionality (turning straight quotes into curly quotes) optionally separated off (just as Markdown and SmartyPants are two different things). * I'd like a way to tell the parser to stay out of certain constructs that could be easily specified as a regex, such as ERB directives <%...%>. As I explained before, this is because I'm the author of a Web site generation framework (RubyFrontier) that works very differently from webgen. In RubyFrontier, Web page material is processed in a certain order and manner and there are certain moments at which it turns to the user for callbacks. At present I'm using Markdown and SmartyPants in most of my sites, calling each at a certain callback point in the process. It would be nice to be able to replace those calls with kramdown calls (partly out of a desire for pure Ruby, partly because kramdown syntax is so much better than Markdown syntax for certain edge cases like nested lists), but I can't do it unless the above two requests are met. As a compromise, I've introduced an additional callback point in the latest version of RubyFrontier, where kramdown can be called, as is, pretty well; but it doesn't work for all cases. If kramdown behaved as I've requested, I could just switch to it and be in 7th heaven. I feel that I've taken a step towards kramdown and I wish kramdown would take a step towards me. m. -- matt neuburg, phd = matt at tidbits.com, http://www.tidbits.com/matt/ pantes anthropoi tou eidenai oregontai phusei Among the 2007 MacTech Top 25, http://tinyurl.com/2rh4pf AppleScript: the Definitive Guide, 2nd edition http://www.tidbits.com/matt/default.html#applescriptthings Take Control of Exploring & Customizing Snow Leopard http://tinyurl.com/kufyy8 RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html TidBITS, Mac news and reviews since 1990, http://www.tidbits.com From t_leitner at gmx.at Thu May 6 01:19:58 2010 From: t_leitner at gmx.at (Thomas Leitner) Date: Thu, 6 May 2010 07:19:58 +0200 Subject: [kramdown-users] Towards the one-oh-oh In-Reply-To: <20100506023532125326.a3af7a92@gmail.com> References: <20100505170803.29c8e268@noweto> <20100506023532125326.a3af7a92@gmail.com> Message-ID: <20100506071958.3ebe6aac@noweto> > By the way, I've been using a very good HTML-to-PDF library called > "dompdf" written in pure PHP. I have been thinking about porting it > to Ruby. If anyone is interested in that (as contributor or user), > or can suggest alternatives, please let me know. dompdf looks interesting. From what I have seen it uses pdflib or another PDF generation library in the background for actually creating the PDF - this would be the part that prawn is made for. However, what I would like to do in the kramdown-to-PDF conversion is to not take the route over HTML but go straight from the internal tree to a PDF document. Since HTML rendering is *very* hard to get right and for getting good visuals you would basically need an HTML layout engine, I think the best way for converting HTML to PDF is via a library that uses webkit or gecko internally. But this is just my personal opinion... -- Thomas From t_leitner at gmx.at Thu May 6 01:42:39 2010 From: t_leitner at gmx.at (Thomas Leitner) Date: Thu, 6 May 2010 07:42:39 +0200 Subject: [kramdown-users] Towards the one-oh-oh In-Reply-To: References: <20100505170803.29c8e268@noweto> Message-ID: <20100506074239.721fb2aa@noweto> > * I'd like to see the SmartyPants functionality (turning straight > quotes into curly quotes) optionally separated off (just as Markdown > and SmartyPants are two different things). SmartyPants like functionality is implemented via the :smart_quotes and the :typography span parsers. If these two parsers are excluded from the span parsers, no conversion is done. This can currently be achieved by modifying the `SPAN_PARSERS` constant of the Kramdown::Parser::Kramdown class. I will modify this to make including/excluding parsers easier, ie. one then only needs to subclass the parser class and set instance variables. Doing it this way will make the base kramdown parser behave the way it behaves now and it will allow you to customize its parsing functionality in the way you specified above. > * I'd like a way to tell the parser to stay out of certain constructs > that could be easily specified as a regex, such as ERB directives > <%...%>. After I have modified the way the used parsers are set, you can easily write your own parser method which parses `<%...%>` constructs and add it to the list of span parsers (note that you would need to put it at the beginning sothat no other parser method is invoked and potentially interferes). Writing a parser method is easy, for example, this is the complete autolink parser: # Parse the autolink at the current location. def parse_autolink @src.pos += @src.matched_size href = @src[1] href= "mailto:#{href}" if @src[2].nil? el = Element.new(:a, nil, {:attr => {'href' => href}}) add_text(@src[1].sub(/^mailto:/, ''), el) @tree.children << el end define_parser(:autolink, AUTOLINK_START, '<') The AUTOLINK_START is a regexp that matches the whole autolink, in your case it would be something like `/<%.*?%>/`. So as I said before this is a functionality that will not likely make it into the base parser because this is something that should be done by the framework using kramdown (i.e. using ERB before kramdown). However, as explained above you can extend the base parser and use the modified one for parsing documents that also have ERB parts. I will implement the above mentioned changes so that they are available with the next release and so that you can modify the parser. If you need help with the latter, don't hesitate to write on the ML! Is there something else that you would need regarding the use of kramdown in RubyFrontier? -- Thomas From t_leitner at gmx.at Thu May 6 02:36:56 2010 From: t_leitner at gmx.at (Thomas Leitner) Date: Thu, 6 May 2010 08:36:56 +0200 Subject: [kramdown-users] Towards the one-oh-oh In-Reply-To: <20100506023250789869.9439048a@gmail.com> References: <20100505170803.29c8e268@noweto> <20100506023250789869.9439048a@gmail.com> Message-ID: <20100506083656.2089e84a@noweto> > I wonder if you've had time to consider my request for IAL above a > block, so that these two are equivalent: > > {: .tasks } > * Task 1 > * Task 2 > * Task 3 > > * Task 1 > * Task 2 > * Task 3 > {: .tasks } > > As I pointed out in my original request for this, support for the IAL > at the top makes for more intuitively placed class and ID attributes, > even more so if the modified block contains children or other > complicated (lengthy) structure. Please let me know if this can make > it into version 0.8 or 1.0. Basically it is no problem. However, it is a rather invasive change because it affects all block level parsers: each parser has to check if a block IAL has been parsed before and, if it is the case, apply the IAL to the created element. This naturally incurs a small performance penalty... Nonetheless, I have implemented it and it is available with the next release. -- Thomas From svicalifornia at gmail.com Thu May 6 03:32:53 2010 From: svicalifornia at gmail.com (Shawn Van Ittersum) Date: Thu, 6 May 2010 17:32:53 +1000 Subject: [kramdown-users] Towards the one-oh-oh In-Reply-To: <20100506071958.3ebe6aac@noweto> References: <20100505170803.29c8e268@noweto> <20100506023532125326.a3af7a92@gmail.com> <20100506071958.3ebe6aac@noweto> Message-ID: <20100506173253644720.ed66f79d@gmail.com> Yes, agreed. There's no reason for kramdown->PDF to go through HTML. Are you aware of any library that uses WebKit to generate PDFs from HTML? Though not relevant to kramdown, I would to see that for my other uses. Shawn On Thu, 6 May 2010 07:19:58 +0200, Thomas Leitner wrote: >> By the way, I've been using a very good HTML-to-PDF library called >> "dompdf" written in pure PHP. I have been thinking about porting it >> to Ruby. If anyone is interested in that (as contributor or user), >> or can suggest alternatives, please let me know. > > dompdf looks interesting. From what I have seen it uses pdflib or > another PDF generation library in the background for actually creating > the PDF - this would be the part that prawn is made for. > > However, what I would like to do in the kramdown-to-PDF conversion is > to not take the route over HTML but go straight from the internal tree > to a PDF document. Since HTML rendering is *very* hard to get right and > for getting good visuals you would basically need an HTML layout > engine, I think the best way for converting HTML to PDF is via a library > that uses webkit or gecko internally. But this is just my personal > opinion... > > -- Thomas > _______________________________________________ > kramdown-users mailing list > kramdown-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/kramdown-users From svicalifornia at gmail.com Thu May 6 03:34:21 2010 From: svicalifornia at gmail.com (Shawn Van Ittersum) Date: Thu, 6 May 2010 17:34:21 +1000 Subject: [kramdown-users] Towards the one-oh-oh In-Reply-To: <20100506083656.2089e84a@noweto> References: <20100505170803.29c8e268@noweto> <20100506023250789869.9439048a@gmail.com> <20100506083656.2089e84a@noweto> Message-ID: <20100506173421170688.cbfabfae@gmail.com> Thanks, Thomas. :) I'm eager to see how you've implement the parsing for 1.0, because what kramdown does is pretty fantastic. Shawn On Thu, 6 May 2010 08:36:56 +0200, Thomas Leitner wrote: >> I wonder if you've had time to consider my request for IAL above a >> block, so that these two are equivalent: >> >> {: .tasks } >> * Task 1 >> * Task 2 >> * Task 3 >> >> * Task 1 >> * Task 2 >> * Task 3 >> {: .tasks } >> >> As I pointed out in my original request for this, support for the IAL >> at the top makes for more intuitively placed class and ID attributes, >> even more so if the modified block contains children or other >> complicated (lengthy) structure. Please let me know if this can make >> it into version 0.8 or 1.0. > > Basically it is no problem. However, it is a rather invasive change > because it affects all block level parsers: each parser has to check if > a block IAL has been parsed before and, if it is the case, apply the IAL > to the created element. > > This naturally incurs a small performance penalty... > > Nonetheless, I have implemented it and it is available with the next > release. > > -- Thomas > _______________________________________________ > kramdown-users mailing list > kramdown-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/kramdown-users From t_leitner at gmx.at Thu May 6 06:03:59 2010 From: t_leitner at gmx.at (Thomas Leitner) Date: Thu, 6 May 2010 12:03:59 +0200 Subject: [kramdown-users] Towards the one-oh-oh In-Reply-To: <20100506173253644720.ed66f79d@gmail.com> References: <20100505170803.29c8e268@noweto> <20100506023532125326.a3af7a92@gmail.com> <20100506071958.3ebe6aac@noweto> <20100506173253644720.ed66f79d@gmail.com> Message-ID: <20100506120359.0143739e@noweto> On Thu, 6 May 2010 17:32:53 +1000 Shawn Van Ittersum wrote: > Yes, agreed. There's no reason for kramdown->PDF to go through HTML. > > Are you aware of any library that uses WebKit to generate PDFs from > HTML? Though not relevant to kramdown, I would to see that for my > other uses. No, I'm afraid not. -- Thomas From matt at tidbits.com Thu May 6 12:41:24 2010 From: matt at tidbits.com (Matt Neuburg) Date: Thu, 06 May 2010 09:41:24 -0700 Subject: [kramdown-users] Towards the one-oh-oh In-Reply-To: <20100506074239.721fb2aa@noweto> Message-ID: On or about 5/5/10 10:42 PM, thus spake "Thomas Leitner" : > So as I said before this is a functionality that will not likely make > it into the base parser because this is something that should be done > by the framework using kramdown (i.e. using ERB before kramdown). And indeed I did change RubyFrontier so that kramdown *could* be run just after ERB runs. But this might not meet every need. To be brief, the problem is that by that moment in the process the Web page source has been inserted into the template, and there can be good reason to want to run Markdown / kramdown on just the page source alone and not the surrounding template. To be sure, Markdown doesn't understand ERB either; but what it does to ERB expressions is simple and predictable and I can just undo it - basically all it does is to entityize the opening left angle bracket, so I just replace "<%" with "<%" and all is well. But kramdown doesn't realize that ERB tags are tags at all; it reaches right inside them and meddles with their contents: <% @x = "This is code" %>

<% @x = “This is code” %>

Even just being able to turn off the smartypants part of kramdown might be enough to allow me to reverse this in most cases, and then the problem would be no worse than it is with Markdown. But what I'm looking for is something *better* than Markdonw. My approach was always a hack with Markdown; indeed, part of the reason I want to dump Markdown and use kramdown is that I'm always fighting against Markdown, hacking around its bugs and limitations, whereas kramdown (1) is alive and open and under development, and (2) it's Ruby, with all that that implies. Thus, with enough options and Ruby-style customizability built in, kramdown can be a much better choice for me. It sounds like that's the direction things are going, so I'll continue to wait and see how things develop. Thanks for the detailed hints! m. -- matt neuburg, phd = matt at tidbits.com, http://www.tidbits.com/matt/ pantes anthropoi tou eidenai oregontai phusei Among the 2007 MacTech Top 25, http://tinyurl.com/2rh4pf AppleScript: the Definitive Guide, 2nd edition http://www.tidbits.com/matt/default.html#applescriptthings Take Control of Exploring & Customizing Snow Leopard http://tinyurl.com/kufyy8 RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html TidBITS, Mac news and reviews since 1990, http://www.tidbits.com From t_leitner at gmx.at Thu May 6 14:59:44 2010 From: t_leitner at gmx.at (Thomas Leitner) Date: Thu, 6 May 2010 20:59:44 +0200 Subject: [kramdown-users] Towards the one-oh-oh In-Reply-To: References: <20100506074239.721fb2aa@noweto> Message-ID: <20100506205944.1bb7e6ac@noweto> > Even just being able to turn off the smartypants part of kramdown > might be enough to allow me to reverse this in most cases, and then > the problem would be no worse than it is with Markdown. But what I'm > looking for is something *better* than Markdonw. My approach was > always a hack with Markdown; indeed, part of the reason I want to > dump Markdown and use kramdown is that I'm always fighting against > Markdown, hacking around its bugs and limitations, whereas kramdown > (1) is alive and open and under development, and (2) it's Ruby, with > all that that implies. > > Thus, with enough options and Ruby-style customizability built in, > kramdown can be a much better choice for me. It sounds like that's > the direction things are going, so I'll continue to wait and see how > things develop. Thanks for the detailed hints! m. Then you might be interested in the latest commits that I have pushed to github because the API documentation for the Kramdown::Parser::Kramdown class now contains an example on how to create a custom parser based on the kramdown parser, showing how to parse span level ERB tags :-) You can start with the sample code and add the needed block level parser. There is no step 3 ;-) Btw. kramdown 0.7.0 will be released tomorrow... Best regards, Thomas From t_leitner at gmx.at Fri May 7 06:40:20 2010 From: t_leitner at gmx.at (Thomas Leitner) Date: Fri, 7 May 2010 12:40:20 +0200 Subject: [kramdown-users] [ANN] kramdown 0.7.0 released Message-ID: <20100507124020.766d429e@noweto> ## About kramdown kramdown (sic, not Kramdown or KramDown, just 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]. Homepage for installation instructions and documentation: http://kramdown.rubyforge.org ## kramdown 0.7.0 released This release adds syntax support for abbreviations. This means that kramdown is now syntax-wise on par with Maruku and PHP Markdown Extra! Another big change is the extension support: After some discussion on the mailing list (many thanks to Eric Sunshine and Shawn Van Ittersum), the syntax for the extensions has been changed and support for custom extensions will be dropped in a future release. Additionally, the option `auto_ids` has been moved from being interpreted by the parser to being interpreted by the converters. This means that it is not possible anymore to turn automatic header ID generation on or off for parts of a text. The HTML and LaTeX converters also gained the ability to generate a table of contents. Just add the reference name "toc" to an ordered or unordered list and it will be replaced by the ToC (this is "coincidentally" the same syntax that Maruku uses...). ## Changes * Major changes: - Added support for PHP Markdown Extra like abbreviations - Added support for span extensions - New syntax for block/span extensions - Added support for generating a table of contents in the HTML and LaTeX converters * Minor changes: - The option `auto_ids` has been moved from the parser to the converters. - Invalid span IALs are now removed from the output - IALs can now be applied to individual list items by placing the IAL directly after the list item marker - Added an option for prefixing automatically generated IDs with a string - Block IALs can now also be put before a block element * Bug fixes: - Fixed a problem with parsing smart quotes at the beginning of a line (reported by Michael Franzl) * Deprecation notes: - Removed deprecated CLI option `-f` - The old extension syntax and support for custom extensions will be removed in the next release. From svicalifornia at gmail.com Wed May 19 07:23:36 2010 From: svicalifornia at gmail.com (Shawn Van Ittersum) Date: Wed, 19 May 2010 21:23:36 +1000 Subject: [kramdown-users] [ANN] kramdown 0.7.0 released In-Reply-To: <20100507124020.766d429e@noweto> References: <20100507124020.766d429e@noweto> Message-ID: <20100519212336774778.dfe65298@gmail.com> Hi Thomas, Thanks for your work on this release! Sorry I did not respond sooner; some other things came up, and I was not able to test the new kramdown until just now. It seems to be working great! With these most recent changes, how do the speed benchmarks compare to Maruku? Shawn On Fri, 7 May 2010 12:40:20 +0200, Thomas Leitner wrote: > ## About kramdown > > kramdown (sic, not Kramdown or KramDown, just 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]. > Homepage for installation instructions and documentation: > http://kramdown.rubyforge.org > > > ## kramdown 0.7.0 released > > This release adds syntax support for abbreviations. This means that > kramdown is now syntax-wise on par with Maruku and PHP Markdown Extra! > > Another big change is the extension support: After some discussion on > the mailing list (many thanks to Eric Sunshine and Shawn Van Ittersum), > the syntax for the extensions has been changed and support for custom > extensions will be dropped in a future release. > > Additionally, the option `auto_ids` has been moved from being > interpreted by the parser to being interpreted by the converters. This > means that it is not possible anymore to turn automatic header ID > generation on or off for parts of a text. > > The HTML and LaTeX converters also gained the ability to generate a > table of contents. Just add the reference name "toc" to an ordered or > unordered list and it will be replaced by the ToC (this is > "coincidentally" the same syntax that Maruku uses...). > > > ## Changes > > * Major changes: > > - Added support for PHP Markdown Extra like abbreviations > - Added support for span extensions > - New syntax for block/span extensions > - Added support for generating a table of contents in the HTML and > LaTeX converters > > * Minor changes: > > - The option `auto_ids` has been moved from the parser to the > converters. > - Invalid span IALs are now removed from the output > - IALs can now be applied to individual list items by placing the IAL > directly after the list item marker > - Added an option for prefixing automatically generated IDs with a > string > - Block IALs can now also be put before a block element > > * Bug fixes: > > - Fixed a problem with parsing smart quotes at the beginning of a > line (reported by Michael Franzl) > > * Deprecation notes: > > - Removed deprecated CLI option `-f` > - The old extension syntax and support for custom extensions will be > removed in the next release. > _______________________________________________ > kramdown-users mailing list > kramdown-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/kramdown-users From svicalifornia at gmail.com Wed May 19 07:41:43 2010 From: svicalifornia at gmail.com (Shawn Van Ittersum) Date: Wed, 19 May 2010 21:41:43 +1000 Subject: [kramdown-users] [ANN] kramdown 0.7.0 released In-Reply-To: <20100507124020.766d429e@noweto> References: <20100507124020.766d429e@noweto> Message-ID: <20100519214143881040.7de25dc3@gmail.com> First issue: When using the TOC feature, how do I assign a class to the ToC ul? * TOC {:toc .class} doesn't work * TOC {:toc}{.class} doesn't work {.class} * TOC {:toc} doesn't work Is there a way to do it? Shawn On Fri, 7 May 2010 12:40:20 +0200, Thomas Leitner wrote: > ## About kramdown > > kramdown (sic, not Kramdown or KramDown, just 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]. > Homepage for installation instructions and documentation: > http://kramdown.rubyforge.org > > > ## kramdown 0.7.0 released > > This release adds syntax support for abbreviations. This means that > kramdown is now syntax-wise on par with Maruku and PHP Markdown Extra! > > Another big change is the extension support: After some discussion on > the mailing list (many thanks to Eric Sunshine and Shawn Van Ittersum), > the syntax for the extensions has been changed and support for custom > extensions will be dropped in a future release. > > Additionally, the option `auto_ids` has been moved from being > interpreted by the parser to being interpreted by the converters. This > means that it is not possible anymore to turn automatic header ID > generation on or off for parts of a text. > > The HTML and LaTeX converters also gained the ability to generate a > table of contents. Just add the reference name "toc" to an ordered or > unordered list and it will be replaced by the ToC (this is > "coincidentally" the same syntax that Maruku uses...). > > > ## Changes > > * Major changes: > > - Added support for PHP Markdown Extra like abbreviations > - Added support for span extensions > - New syntax for block/span extensions > - Added support for generating a table of contents in the HTML and > LaTeX converters > > * Minor changes: > > - The option `auto_ids` has been moved from the parser to the > converters. > - Invalid span IALs are now removed from the output > - IALs can now be applied to individual list items by placing the IAL > directly after the list item marker > - Added an option for prefixing automatically generated IDs with a > string > - Block IALs can now also be put before a block element > > * Bug fixes: > > - Fixed a problem with parsing smart quotes at the beginning of a > line (reported by Michael Franzl) > > * Deprecation notes: > > - Removed deprecated CLI option `-f` > - The old extension syntax and support for custom extensions will be > removed in the next release. > _______________________________________________ > kramdown-users mailing list > kramdown-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/kramdown-users From svicalifornia at gmail.com Wed May 19 08:08:46 2010 From: svicalifornia at gmail.com (Shawn Van Ittersum) Date: Wed, 19 May 2010 22:08:46 +1000 Subject: [kramdown-users] [ANN] kramdown 0.7.0 released In-Reply-To: <20100507124020.766d429e@noweto> References: <20100507124020.766d429e@noweto> Message-ID: <20100519220846635405.f70ab4f8@gmail.com> Hi Thomas, Since switching to kramdown 0.7, inline links are no longer being generated: [text](target) does not get interpreted. This is obviously a serious issue... Shawn On Fri, 7 May 2010 12:40:20 +0200, Thomas Leitner wrote: > ## About kramdown > > kramdown (sic, not Kramdown or KramDown, just 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]. > Homepage for installation instructions and documentation: > http://kramdown.rubyforge.org > > > ## kramdown 0.7.0 released > > This release adds syntax support for abbreviations. This means that > kramdown is now syntax-wise on par with Maruku and PHP Markdown Extra! > > Another big change is the extension support: After some discussion on > the mailing list (many thanks to Eric Sunshine and Shawn Van Ittersum), > the syntax for the extensions has been changed and support for custom > extensions will be dropped in a future release. > > Additionally, the option `auto_ids` has been moved from being > interpreted by the parser to being interpreted by the converters. This > means that it is not possible anymore to turn automatic header ID > generation on or off for parts of a text. > > The HTML and LaTeX converters also gained the ability to generate a > table of contents. Just add the reference name "toc" to an ordered or > unordered list and it will be replaced by the ToC (this is > "coincidentally" the same syntax that Maruku uses...). > > > ## Changes > > * Major changes: > > - Added support for PHP Markdown Extra like abbreviations > - Added support for span extensions > - New syntax for block/span extensions > - Added support for generating a table of contents in the HTML and > LaTeX converters > > * Minor changes: > > - The option `auto_ids` has been moved from the parser to the > converters. > - Invalid span IALs are now removed from the output > - IALs can now be applied to individual list items by placing the IAL > directly after the list item marker > - Added an option for prefixing automatically generated IDs with a > string > - Block IALs can now also be put before a block element > > * Bug fixes: > > - Fixed a problem with parsing smart quotes at the beginning of a > line (reported by Michael Franzl) > > * Deprecation notes: > > - Removed deprecated CLI option `-f` > - The old extension syntax and support for custom extensions will be > removed in the next release. > _______________________________________________ > kramdown-users mailing list > kramdown-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/kramdown-users From t_leitner at gmx.at Thu May 20 01:22:43 2010 From: t_leitner at gmx.at (Thomas Leitner) Date: Thu, 20 May 2010 07:22:43 +0200 Subject: [kramdown-users] [ANN] kramdown 0.7.0 released In-Reply-To: <20100519212336774778.dfe65298@gmail.com> References: <20100507124020.766d429e@noweto> <20100519212336774778.dfe65298@gmail.com> Message-ID: <20100520072243.14deb96d@noweto> > Thanks for your work on this release! Sorry I did not respond > sooner; some other things came up, and I was not able to test the new > kramdown until just now. It seems to be working great! > > With these most recent changes, how do the speed benchmarks compare > to Maruku? A bit slower than the 0.6.0 release since everytime a new span/block level parser gets added, one more check needs to be performed (not every time)... Nonetheless kramdown is still about 4.2 - 4.6 times faster than Maruku. Since we started out with being about 5 times faster than Maruku, this seems quite okay. -- Thomas From t_leitner at gmx.at Thu May 20 01:24:59 2010 From: t_leitner at gmx.at (Thomas Leitner) Date: Thu, 20 May 2010 07:24:59 +0200 Subject: [kramdown-users] [ANN] kramdown 0.7.0 released In-Reply-To: <20100519214143881040.7de25dc3@gmail.com> References: <20100507124020.766d429e@noweto> <20100519214143881040.7de25dc3@gmail.com> Message-ID: <20100520072459.1ff72ea5@noweto> On Wed, 19 May 2010 21:41:43 +1000 Shawn Van Ittersum wrote: > First issue: > > When using the TOC feature, how do I assign a class to the ToC ul? > > * TOC > {:toc .class} doesn't work > > * TOC > {:toc}{.class} doesn't work > > {.class} > * TOC > {:toc} doesn't work > > Is there a way to do it? No, this is not possible, but I will add support for this. -- Thomas From sunshine at sunshineco.com Thu May 20 03:17:48 2010 From: sunshine at sunshineco.com (Eric Sunshine) Date: Thu, 20 May 2010 03:17:48 -0400 Subject: [kramdown-users] [ANN] kramdown 0.7.0 released In-Reply-To: <20100519220846635405.f70ab4f8@gmail.com> References: <20100507124020.766d429e@noweto> <20100519220846635405.f70ab4f8@gmail.com> Message-ID: <4BF4E21C.2070303@sunshineco.com> On 5/19/2010 8:08 AM, Shawn Van Ittersum wrote: > Since switching to kramdown 0.7, inline links are no longer being generated: > [text](target) > does not get interpreted. This is obviously a serious issue... I do not experience this problem. My site still compiles properly. This small test case: Test [link](http://www.example.com/). is properly compiled by kramdown 0.7.0 to:

Test link.

-- ES From t_leitner at gmx.at Thu May 20 01:34:56 2010 From: t_leitner at gmx.at (Thomas Leitner) Date: Thu, 20 May 2010 07:34:56 +0200 Subject: [kramdown-users] [ANN] kramdown 0.7.0 released In-Reply-To: <20100519220846635405.f70ab4f8@gmail.com> References: <20100507124020.766d429e@noweto> <20100519220846635405.f70ab4f8@gmail.com> Message-ID: <20100520073456.16b5851d@noweto> On Wed, 19 May 2010 22:08:46 +1000 Shawn Van Ittersum wrote: > Hi Thomas, > > Since switching to kramdown 0.7, inline links are no longer being > generated: > > [text](target) > > does not get interpreted. This is obviously a serious issue... I can't reproduce the error with the line given above: $ ruby -Ilib bin/kramdown [text](target)^D

text

So this works. Can you provide a complete example where this doesn't work? -- Thomas From svicalifornia at gmail.com Thu May 20 11:40:36 2010 From: svicalifornia at gmail.com (Shawn Van Ittersum) Date: Fri, 21 May 2010 01:40:36 +1000 Subject: [kramdown-users] [ANN] kramdown 0.7.0 released In-Reply-To: <20100520072243.14deb96d@noweto> References: <20100507124020.766d429e@noweto> <20100519212336774778.dfe65298@gmail.com> <20100520072243.14deb96d@noweto> Message-ID: <20100521014036774827.9a39d310@gmail.com> Excellent! Shawn On Thu, 20 May 2010 07:22:43 +0200, Thomas Leitner wrote: >> Thanks for your work on this release! Sorry I did not respond >> sooner; some other things came up, and I was not able to test the new >> kramdown until just now. It seems to be working great! >> >> With these most recent changes, how do the speed benchmarks compare >> to Maruku? > > A bit slower than the 0.6.0 release since everytime a new span/block > level parser gets added, one more check needs to be performed (not > every time)... > > Nonetheless kramdown is still about 4.2 - 4.6 times faster than Maruku. > Since we started out with being about 5 times faster than Maruku, this > seems quite okay. > > -- Thomas > _______________________________________________ > kramdown-users mailing list > kramdown-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/kramdown-users From svicalifornia at gmail.com Thu May 20 11:41:59 2010 From: svicalifornia at gmail.com (Shawn Van Ittersum) Date: Fri, 21 May 2010 01:41:59 +1000 Subject: [kramdown-users] [ANN] kramdown 0.7.0 released In-Reply-To: <4BF4E21C.2070303@sunshineco.com> References: <20100507124020.766d429e@noweto> <20100519220846635405.f70ab4f8@gmail.com> <4BF4E21C.2070303@sunshineco.com> Message-ID: <20100521014159456555.2d6eeacb@gmail.com> OK, thanks for checking. I'll check it out again over the weekend and try to figure out what went wrong on my end. Shawn On Thu, 20 May 2010 03:17:48 -0400, Eric Sunshine wrote: > On 5/19/2010 8:08 AM, Shawn Van Ittersum wrote: >> Since switching to kramdown 0.7, inline links are no longer being >> generated: >> [text](target) >> does not get interpreted. This is obviously a serious issue... > > I do not experience this problem. My site still compiles properly. > This small test case: > > Test [link](http://www.example.com/). > > is properly compiled by kramdown 0.7.0 to: > >

Test link.

> > -- ES > _______________________________________________ > kramdown-users mailing list > kramdown-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/kramdown-users