Well, this was inevitable.
You are here: dive into mark → Archives → March 2003 → PyTextile
I am no longer accepting public comments on this post, but you can use this form to contact me privately. (Your message will not be published.)
| Recent Stuff | For You, Special Price | Stay Here |
|---|---|---|
|
|
||
| Good Stuff | Buy The Cow | Go Away |
|
|
||
| Powered by Google | Drink The Milk | Don't Steal |
| posts / comments | © 2001-8 Mark Pilgrim |
Wow, and I was going to finish my python port this morning. Thanks for saving me the time.
Comment by John Beimler — Wednesday, March 19, 2003 @ 7:03 am
Cool, I was just working on this a couple of days ago but I’m glad someone else beat me to it. :) I think I’ll offer it as a text formatting option in the next release of my multiprotocol Python XML-RPC blog client/library…
Comment by Rob Tillotson — Wednesday, March 19, 2003 @ 7:25 am
Excellent!
Now I guess it’s just a matter of Gruber making an Applescript version and the Narrator doing it up in Java und Textile vill rule ze vorlt.
Haha!
(Whoops, war on)
Comment by Dean Allen — Wednesday, March 19, 2003 @ 8:19 am
Anyone know whether someone has written a side-by-side or feature-by-feature comparison of Textile with reStructured Text? And/or with the “HTML-Lite” that Radio UserLand implements?
reStructured Text is described in these two spots:
http://docutils.sourceforge.net/spec/rst/introduction.html
http://docutils.sourceforge.net/docs/rst/quickref.html
Comment by Doug L. — Wednesday, March 19, 2003 @ 12:49 pm
Quickly:
reStructuredText is designed to be output-format-agnostic; Textile is specifically designed for web display.
reStructuredText has many options that Textile lacks, such as field lists, definition lists, nested blockquotes, simple tables, and grid tables.
Textile has several options that reStructuredText lacks, such as inline shorthand for CODE, CITE, and SUP. Also, its ability to auto-map high-bit ASCII characters to HTML numeric entities (making it possible to cut-and-paste smart quotes without breaking validation).
reStructuredText is designed for a particular style of formal document: it has a system of cataloging footnotes, bibliographic citations, and hyperlinks. Textile is designed for shorter, more informal documents like blog posts and comments.
Comment by Mark — Wednesday, March 19, 2003 @ 1:44 pm
Is this doable in JavaScript? I’d like to see this without a screen refresh.
Comment by pb — Wednesday, March 19, 2003 @ 3:04 pm
I don’t see why not. Javascript has regular expressions.
Comment by Mark — Wednesday, March 19, 2003 @ 3:12 pm
So Dean … are you giving me your permission?
Comment by The Narrator — Wednesday, March 19, 2003 @ 4:30 pm
Permission granted, Dan. Encouraged, cheered on, supported, cheer-led, voted for, acknowledged, endorsed, sanctioned (whups), say hey, and fire up a Cohiba.
Comment by Dean Allen — Wednesday, March 19, 2003 @ 6:14 pm
So it’s time, then, for textile() to have a plain-language spec: doctypes for which it intends validity and what it generally aims to be. Again (I keep saying this), a description of what it isn’t probably does the job best.
What is it? Structurally-aware UBBcode with an addiction to Proust, validating to XHTML 1.1 Trans. The earth will shift under its feet, though. To live un-Balkanized, it must define itself.
Nobody commenting where would implement a half-Textile, a sorta-Textile — but others might. While it sill can, I think Textile should announce its goals, benefits and understood limitations [somewhat] more formally.
My Mom will like Txl because it’s intuitive, but in two years when she wants a PDA version of her etchings she’ll thank me because it delivered valid, transformable structure without her knowing it. These are its twin gifts.
Comment by Lou Quillio — Wednesday, March 19, 2003 @ 7:07 pm
Mozilla and IE now feature API’s for rich text editing. It would be pretty fly if you integrated PyTextile with that.
-Ken
Comment by Ken Kinder — Wednesday, March 19, 2003 @ 8:40 pm
Ken: Do you know any more info on that? It sounds like a fun project to work on.
pb: If you’re going to work on that, please let me know; I’d love to participate.
Mark: see pb’s comment — you should probably have code to convert an (obvious) email address into the mailto: link instead of a broken http:// one. I can help with this if you don’t have time.
Comment by Joe Grossberg — Thursday, March 20, 2003 @ 1:52 pm
Um, the box is clearly labeled “Home page”. I don’t want to be responsible for anyone’s email address.
Comment by Mark — Thursday, March 20, 2003 @ 2:49 pm
Mark: OK, fair enough. But, as you know, people don’t always read directions, much less follow them. :)
Comment by Joe Grossberg — Thursday, March 20, 2003 @ 3:06 pm
Hmm, something goes wrong with consecutive lists. For example, try:
* one
* two
* three
* four
* five
This should yield two separate lists, but instead PyTextile creates one list. Using a *-list directly after a #-list doesn’t work well either.
Comment by Hans — Sunday, March 23, 2003 @ 6:35 pm
1.04 is up and should fix the problem with consecutive lists.
Comment by Mark — Sunday, March 23, 2003 @ 9:41 pm
Nice work! One more contraction for you, that I’d added in my local copy (in addition to ‘ve): ‘re (as in “they’re”; that may be the only instance in English).
Comment by Chris Lawrence — Monday, March 24, 2003 @ 12:27 am
It doesn’t seem to have appeared so far, so here’s a Java version (with free bugs!)
http://pipthepixie.tripod.com/code/jtextile.html
Comment by Phil Wilson — Wednesday, April 23, 2003 @ 7:08 am