[kramdown-users] Backward incompatible changes in parser/converter

Eric Sunshine sunshine at sunshineco.com
Thu Apr 8 05:21:47 EDT 2010

I was going to make the similar observation that, while XHTML-like 
syntax may be well-known, users of Markdown (with extensions) have also 
already become accustomed to IALs and, by extension, the closely related 
{::foo::} syntax. Thomas, you mentioned the Markdown mailing list. Was 
there relevant discussion there which prompted proposed change?

In any event, if the syntax does change, it probably would be worthwhile 
to continue recognizing the old syntax for some time, and not remove it 
as quickly as some of the other deprecated features have been removed. I 
suggest this since (my impression is that) kramdown has already a wider 
audience than the webgen user base.

-- ES

On 4/7/2010 2:12 PM, Shawn Van Ittersum wrote:
> OK.
> There is something nice about having a uniform syntax to wrap all kramdown "tags."  I can't imagine a suitably concise XHTML representation of IALs, so I'd suggest keeping the extensions in curly-brace format for uniformity.  Wouldn't it be odd to say, "These kramdown tags/directives look like this, but these IAL tags look altogether different..."?
> Juse like all ERB tags have<% %>  wrappers, I think there should be similar consistency in kramdown.
> If you do keep curly braces, I think the directive syntax could be simplified.  Instead of this:
> {::options:: ...}
> why not this:
> {options ...}  or  {kd-options ...}
> Why are all the colons necessary?
> Shawn
> On Wed, 7 Apr 2010 16:40:13 +0200, Thomas Leitner wrote:
>> On Wed, 7 Apr 2010 20:58:03 +1000, Shawn Van Ittersum wrote:
>>> Will this new XHTML options syntax also apply to IALs?  Would you
>>> please send some examples of what that would look like?
>> No, IALs and ALDs will stay the same since they fulfill a completely
>> different purpose. Also, the extensions always stand alone whereas IALs
>> are always applied to an element. Therefore it would not "look"
>> good when using XML tags for this purpose.
>> -- Thomas
>> _______________________________________________
>> kramdown-users mailing list
>> kramdown-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/kramdown-users
> _______________________________________________
> kramdown-users mailing list
> kramdown-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/kramdown-users

More information about the kramdown-users mailing list