<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Huddled Masses - Latest Comments in WordPress Plugin - Textile 2.0</title><link>http://huddledmasses.disqus.com/</link><description>Joel Bennett's development blog...</description><language>en</language><lastBuildDate>Sun, 26 Mar 2006 16:31:20 -0000</lastBuildDate><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582525</link><description>I see what you mean ... I think you will find that none of the attributes work on links in Textile at all (test "here":http://www.textism.com/tools/textile/index.php). 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...&lt;br&gt;&lt;br&gt;PLEASE feel free to file bug reports:&lt;br&gt;&lt;a href="http://www.textism.com/tools/textile/index.php" rel="nofollow"&gt;http://www.textism.com/tools/textile/index.php&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaykul</dc:creator><pubDate>Sun, 26 Mar 2006 16:31:20 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582524</link><description>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."&lt;br&gt;&lt;br&gt;I assign an "ext" class to all my external links. The parser bug is most frustrating.  :-(</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jon Zuck</dc:creator><pubDate>Sun, 26 Mar 2006 14:29:22 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582523</link><description>I think you mean to put "link text(oops)" which works like: "link text(oops)":http://www.huddledmasses.org/</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaykul</dc:creator><pubDate>Wed, 22 Mar 2006 21:42:38 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582522</link><description>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.&lt;br&gt;&lt;br&gt;link attribute test: "(oops)link text":/url</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tom</dc:creator><pubDate>Mon, 20 Mar 2006 07:47:19 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582521</link><description>If you use the "For Beautifiers" version, and set the priority of Geshi *higher* than that of Textile, you shouldn't have any problems, although I seem to be getting an extra &lt; br /&gt;. Of course, only I can get &lt; code &gt; (or anything else that looks like HTML) into these pages, so let me show by example:&lt;br&gt;&lt;br&gt;h6. Perl:&lt;br&gt;&lt;br&gt;&lt;code lang="perl"&gt;$foo = $_;&lt;br&gt;print $foo;&lt;/code&gt;&lt;br&gt;&lt;br&gt;h6.  Html&lt;br&gt;&lt;br&gt;&lt;code lang="html"&gt;&amp;lt;div class="somesillytestcode"&amp;gt;&lt;br&gt;&lt;p&gt;This is a paragraph with a &lt;b&gt;bold&lt;/b&gt; word in it.&lt;/p&gt;&lt;br&gt;&lt;p&gt;This is another paragraph with an &lt;em&gt;emphasized&lt;/em&gt; word in it.&lt;/p&gt;&lt;br&gt;&amp;lt;/div&amp;gt;&lt;/code&gt;&lt;/code&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaykul</dc:creator><pubDate>Tue, 18 Oct 2005 00:25:52 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582520</link><description>I have the same problem as you James, from what i can guess the Textile plugin is getting the html after the GeSHi plugin colours it, then Textile converts the html into entities.&lt;br&gt;&lt;br&gt;i tried using a Textile plugin that skipped over pre tags (what i was using to contain the source code) but it was just messing it up even more (wrapping the pre tags in another set of pre tags, then just generally messing with the html)&lt;br&gt;&lt;br&gt;at the moment i have just disabled the source highlighting until i can find a working configuration.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">The_Decryptor</dc:creator><pubDate>Mon, 17 Oct 2005 07:45:04 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582519</link><description>I've installed your Textile 2.6 plugin and also the GeSHi plugin.  For some reason when I write:&lt;br&gt;&lt;br&gt;&lt;br&gt;print ("Hello World");&lt;br&gt;&lt;br&gt;&lt;br&gt;I see the pure HTML tags for the syntax highlighting.  WordPress is not rendering the HTML for some reason.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">James</dc:creator><pubDate>Wed, 12 Oct 2005 22:32:20 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582515</link><description>Looks like the @==@ notextile @==@ stuff is acting like his @code@ blocks used to. *Ugh.*  You think he'd take my fixes if I could figure this out?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaykul</dc:creator><pubDate>Wed, 05 Oct 2005 22:59:35 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582518</link><description>To show what I mean, type the following into the Textile generator:&lt;br&gt;&lt;br&gt;==&lt;b&gt;inside a &lt;b&gt; tag&lt;/b&gt;==&lt;br&gt;&lt;br&gt;==&lt;br&gt;lots of code ought to be able to go here&lt;br&gt;&lt;em&gt;emphasized&lt;/em&gt; and &lt;strong&gt;strong&lt;/strong&gt;, and all sorts of stuff.&lt;br&gt;The idea is that *stars* should stay *stars* and _underscores_ too!&lt;br&gt;==&lt;br&gt;&lt;br&gt;%==Hypothetically, this ought to be in a span tag.==%&lt;br&gt;&lt;br&gt;I've sent a bug report from that page to Dean Allen.&lt;/b&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dutch Gecko</dc:creator><pubDate>Tue, 04 Oct 2005 18:11:47 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582517</link><description>Thanks for the reply Jaykul.&lt;br&gt;&lt;br&gt;I just updated to 2.6 and I'm making some progress: now if I use the notextile tag the whole ==== part appears, but textile is still doing something since it's changing the  to HTML chracters (of the &amp;amp; number ; type). I can understand your plugin isn't at fault, it appears to be a problem with the generator code, but it's a little frustrating. Feel free to email me if you rather wouldn't post a huge discussion in your comments page :)&lt;br&gt;&lt;br&gt;Once again, thanks for your help so far.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dutch Gecko</dc:creator><pubDate>Tue, 04 Oct 2005 17:55:45 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582516</link><description>To reply to the question about math: - and + work fine, as long as there's a space on either side of them. You could turn that feature off fairly simply: edit the file, go to the "fSpan" function and remove the line(s) defining them: @'-'  =&amp;gt; 'del',@ and @'+'  =&amp;gt; 'ins',@&lt;br&gt;&lt;br&gt;About the block quote, I'm not sure why it doesn't work in that spot, but I have no intentions of adding features to Dean's Textile parser, I want to keep them the same so that people can trust his documentation.  The best bet is to raise this question on "his blog":http://www.textism.com/ or "textpattern support forums":http://forum.textpattern.com/&lt;br&gt;&lt;br&gt;The @&amp;lt; notextile &amp;gt;@ blocks, and double = blocks work now, too (in 2.6) so I think most of the problems have been cleaned up.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaykul</dc:creator><pubDate>Mon, 03 Oct 2005 21:42:12 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582514</link><description>You mean one of &amp;lt; &amp;nbsp;!-- these -- &amp;gt;, but, _as far as I know_ (and this is being parsed by Textile, as you can tell), there's nothing preventing you from putting &amp;lt;!-- comment one --&amp;gt; *comments* &amp;lt;!-- comment two --&amp;gt; in your page. &lt;br&gt;&lt;br&gt;Try viewing the source of this page. There should be two comments, one on either side of the bold "comments" above.  You can also look at the post I made for the recent "Textile 2.6 release":http://www.huddledmasses.org/2005/10/03/textile-plugin-26-released/, there's a comment right in the main post that says "there's a Jaykul comment here" so I'm sure it's not Textile stripping it out...&lt;br&gt;&lt;br&gt;Which version did you grab?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaykul</dc:creator><pubDate>Mon, 03 Oct 2005 20:18:52 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582513</link><description>It appears that came out hopelessly wrong. You know what I mean with an HTML comment right? TIA.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dutch Gecko</dc:creator><pubDate>Mon, 03 Oct 2005 16:12:44 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582512</link><description>I'd like to congratulate you on a fantastic plugin for WordPress. I'm still very new to WP but this plugin makes it a lot easier to use.&lt;br&gt;However, I'm having some extreme difficulty with escaping. I use the "AdSense Deluxe":http://www.acmetech.com/blog/2005/07/26/adsense-deluxe-wordpress-plugin/ plugin, and this uses tags in the form of an HTML comment (&amp;lt; !&amp;ndash;- comment --&amp;gt;) to insert a block of code (usually adsense code). For some reason though, no matter how I try to escape this small block, it will be textiled. If I leave out the escape characters then the first four characters vanish (the left tag, exclam. mark and the two dashes). If I surround it with escapes then I get @@ tags instead, with the whole comment showing. Neither shows an advert :)&lt;br&gt;&lt;br&gt;This didn't happen in Textile1, but I need 2's functionality because 1 was being a pain wrapping p tags around everything. Can anybody help?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dutch Gecko</dc:creator><pubDate>Mon, 03 Oct 2005 16:11:10 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582511</link><description>I've _finally_ gotten around to adding a "download" link to my source script.  All of my plugins should be simple and easy to download now, just click through to the source and hit the download link.&lt;br&gt;&lt;br&gt;Hopefully that will solve all the download problems people have had.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jaykul</dc:creator><pubDate>Fri, 23 Sep 2005 17:33:05 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582510</link><description>Well, the plugin is great, but using "-" to designate deleted text (the strike tag i.e.) messed up my import from blogger. Every post that had a minus in it was suddenly striked through, you can imagine my surprise when I first noticed it. ;-)&lt;br&gt;Anyway, is it possible to turn that one feature off (possibly "+", too, because I might want to use a + in my texts sooner or later...&lt;br&gt;Which leads me to the question: If I use Textile, I can't post mathematical content, right?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Grendel</dc:creator><pubDate>Fri, 02 Sep 2005 12:36:05 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582509</link><description>Hmm, I'm not so sure I'm right about what's causing the blockquote to fail.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">eas</dc:creator><pubDate>Tue, 16 Aug 2005 22:50:51 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582508</link><description>Thanks for writing this plugin.  I'm writing to note an issue i'm seeing with text I marked up with Textile for use in my MT blog which I'm importing into Wordpress.&lt;br&gt;&lt;br&gt;It seems that the Textile2.5 plugin fails to create a block quote when the first thing following it is a textile encoded link:&lt;br&gt;&lt;br&gt;==&lt;br&gt;bq. "Wordpress":http://www.wordpress.org&lt;br&gt;==&lt;br&gt;&lt;br&gt;Also appearantly the MT plugin has some innovations like extended blocks, that I found really handy.  I could enter ===bq..=== and it would blockquote everything until the next block idenfitier (usually a ==p.==).  It would be very cool to be able to use this in Wordpress too.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">eas</dc:creator><pubDate>Tue, 16 Aug 2005 22:33:55 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582507</link><description>Whoops, better comment on the updated entrya??</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andr</dc:creator><pubDate>Fri, 12 Aug 2005 13:48:47 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582506</link><description>Sorry, another thing: Could it be that your span, code etc. functions basically ignore the notextile blocks? I mean, if you do something like &lt;br&gt;&lt;br&gt;==&lt;br&gt;*hello*&lt;br&gt;==&lt;br&gt;&lt;br&gt;"hello" is still strong :(</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Horst</dc:creator><pubDate>Wed, 03 Aug 2005 12:26:15 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582505</link><description>Hi :) First of all: Thanks for taking the effort of making this plugin :)&lt;br&gt;&lt;br&gt;I just played around with it a little bit (after I've become used to Textile thanks to instiki) and found a small problem with it. In the block function when you try to determine if the current line starts a pre-block or not, you only accept pres without arguments.&lt;br&gt;&lt;br&gt;@@ -437,7 +437,7 @@&lt;br&gt;         array_push($text, " ");&lt;br&gt;&lt;br&gt;         foreach($text as $line) {&lt;br&gt;-            if (preg_match('//i', $line)) {&lt;br&gt;+            if (preg_match('//i', $line)) {&lt;br&gt;                 $pre = true;&lt;br&gt;             }</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Horst</dc:creator><pubDate>Wed, 03 Aug 2005 11:52:08 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582504</link><description>I tried Textile plugin 2.5 beta, and it works quite well.  But I see this plugin alters HTML tags severly:&lt;br&gt;&lt;br&gt;For example, a href="test__program_screenshots.jpg" is translated a href="_programscreenshots.jpg ('em' tags in attributes! :( )&lt;br&gt;&lt;br&gt;I hope this issue is fixed soon.&lt;br&gt;&lt;br&gt;Thanks.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Trustin Lee</dc:creator><pubDate>Wed, 03 Aug 2005 11:21:25 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582503</link><description>Oh! And the 1.0 Version link above just goes to the 2.5 file</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex</dc:creator><pubDate>Fri, 15 Jul 2005 11:56:06 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582502</link><description>OH MY GOD!&lt;br&gt;I spent like 30 mins trying to figure out why the plugins wouldn't work (since I couldn't find them at the textile SITE! I found them here... only to discover that the files are all formatted in HTML!!!! WHYYYYYYYY&lt;br&gt;&lt;br&gt;So I copied the code from the rendered html into a text file and now it should work fine :)&lt;br&gt;Just thought you should either provide a raw text version, and/or point out the fact that these files are not just plain ol' php files... (i just "save file to disk"ed them...)&lt;br&gt;Thanks for providing the files though!&lt;br&gt;Cheers :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex Yule</dc:creator><pubDate>Fri, 15 Jul 2005 11:50:57 -0000</pubDate></item><item><title>Re: WordPress Plugin - Textile 2.0</title><link>http://HuddledMasses.org/wordpress-plugin-textile-20/#comment-2582501</link><description>In the previous comment, "tag handling" should be "image handling" and "s*" should be backslash-ess-star.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Caleb Epstein</dc:creator><pubDate>Fri, 10 Jun 2005 09:24:52 -0000</pubDate></item></channel></rss>