Comments on: WordPress Plugin - Textile 2.0

By: Simon Wakeman » Making the move to Wordpress

Simon Wakeman » Making the move to Wordpress — Tue, 25 Jul 2006 05:34:24 +0000

[...] Migrating content over from Textpattern was as simple as running a built-in script, which moved the content without any errors. The template migration was quite straightforward – I merged the XHTML/CSS from my old Textpattern templates with code taken from the great Minimalist Sandbox template. I then went through all my old content and removed the Textile (although had I wanted to continue with Textile there’s a plug-in available to run Textile in Wordpress). [...]

By: Jaykul

Jaykul — Sun, 26 Mar 2006 21:31:20 +0000

I see what you mean … I think you will find that none of the attributes work on links in Textile at all (test here). Which is to say: this is not a problem with my plugin, which is merely a wrapper, it’s the way the Textile parser works. I am not usually prepared to alter the parser, since IMHO, these pseudo-markup languages are only useful when they work the same way everywhere…

PLEASE feel free to file bug reports:
http://www.textism.com/tools/textile/index.php

By: Jon Zuck

Jon Zuck — Sun, 26 Mar 2006 19:29:22 +0000

Jaykul, Tom is right. The plugin is not parsing class attributes correctly. “link text(oop)” would give a TITLE attribute of “oops.” Parentheses coming before the text should give a CLASS of “oops.”

I assign an “ext” class to all my external links. The parser bug is most frustrating.

By: Jaykul

Jaykul — Thu, 23 Mar 2006 02:42:38 +0000

I think you mean to put “link text(oops)” which works like: link text

By: Tom

Tom — Mon, 20 Mar 2006 12:47:19 +0000

There seems to be a bug with parsing link attributes. In this example, the link should have ‘oops’ as a class attribute. Instead, the parenthesised ‘oops’ appears as part of the link text.

link attribute test: (oops)link text

By: Compositio Hodierna » Test du plugin Textile

Compositio Hodierna » Test du plugin Textile — Wed, 01 Mar 2006 13:14:42 +0000

[...] Il est disponible sur Site Textile [...]

By: mileandra » Kommentarvorschau fur Wordpress

mileandra » Kommentarvorschau fur Wordpress — Sun, 26 Feb 2006 23:36:21 +0000

[...] Achtung: das Preview-Template gibt den Inhalt mit der Funktion ‚textile()‘ aus. Wenn ihr das Textile-Plugin nicht installiert habt, entfernt die Funktion bitte aus dem Template, bevor ihr dieses einsetzt. [...]

By: Axodys » Blog Archive » New Years Upgrade

Axodys » Blog Archive » New Years Upgrade — Sun, 01 Jan 2006 23:55:40 +0000

[...] On the individual post formatting front I’m also leaning towards standardizing on markdown rather than textile, but I will need to do some further investigatiion on the relevant post pluginformatting issues that WordPress 2.0 may have introduced. It looks like the Text Control plugin will allow me to switch between Textile and Markdown formatting relatively painlessly, but [Smarty Pants][] character encoding doesn’t seem to work properly at the moment. I’d investigate further, but it lets me set Textile as my default for all my old posts and specify Markdown on an individual post basis and that’s all I really need. [...]

By: Technosailor » Textpattern to WordPress Import Script

Technosailor » Textpattern to WordPress Import Script — Tue, 29 Nov 2005 21:16:12 +0000

[...] Also, since you’re coming from Textpattern, you probably have been using Textile to format your comments and posts. If this is the case, we recommend downloading and installing Textile for WordPress. Trust me… You’ll want it. [...]

By: Technosailor » Friday Poll and Another Migration

Technosailor » Friday Poll and Another Migration — Sat, 26 Nov 2005 04:39:37 +0000

[...] One thing I do have to say is that I have grown attached to Textile which was built into Textpattern. Same maker. So I added Textile for WordPress 2.6 to my plugin list allowing me to continue to post entries using it. [...]