sgbotsford at gmail.com
Wed Mar 24 14:20:26 EDT 2010
Given the paucity of ETS editors, viewers, enabled browsers however, I'm
afraid that I will insist on keeping my horse, at least until there is more
than two roads in town. My horse will eat hay. And who knows where the
next gas station is.
The bowerbird is half right. Elastic tab stops are worthy of implementing.
But to keep the transition cost minimal the older way has to be supported
I can see merit in having MD understand elastic tab stops as part of it's
goal toward minimalist markup.
It certainly would make simple tables easy to do.
Sherwood of Sherwood's Forests
Sherwood's Forests -- http://Sherwoods-Forests.com
50042 Range Rd 31
Warburg, Alberta T0C 2T0
On Wed, Mar 24, 2010 at 12:11 PM, david parsons <orc at pell.chi.il.us> wrote:
> In article <1ffdc.6466484d.38dbaac4 at aol.com>,
> <markdown-discuss at six.pairlist.net> wrote:
> >Content-Type: multipart/alternative;
> > boundary="part1_1ffdc.6466484d.38dbaac4_boundary"
> >Content-Type: text/plain; charset="US-ASCII"
> >Content-Transfer-Encoding: 7bit
> >sherwood said:
> >> I don't understand.
> >what's to understand? :+)
> >> Are you saying that MD should recognize elastic tab stops
> >> in a file and convert that to a html table?
> >yes, that's what i'm saying, or at least part of it.
> And this would convert markdown from a general-purpose writers tool
> into some sort of boutique plugin. I can't really see that this
> would count as an advantage to _anyone_ who currently uses markdown.
> -david parsons
> Markdown-Discuss mailing list
> Markdown-Discuss at six.pairlist.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Markdown-Discuss