Though we’ve already mentioned it this morning, consider this the
official announcement of RedCloth 4.0.0. It’s available on RubyForge,
so all you have to do to get it is gem install RedCloth (don’t forget
to make it CamelCase). Also, when I did a gem update RedCloth, I got
an error, probably because we’ve never had to pick the platform
before. A gem install RedCloth worked just fine for updating, though.
I’d like to thank _why for starting the rewrite and then so freely
giving up the reigns. It’s surely not as good of code as if he’d
written it all himself, but there it is, functional and built on the
foundation of his solid work and that of Adrian Thurston, Dean Allen,
and many others.
We could’ve put out testing gems forever, but at some point you have
to release and see how it does in the wild. One bug has already been
reported that I think warrants a 4.0.1, but I’d like to wait at least
a week and deliver several bug fixes at once.
Thanks for your patience during the rewrite and your input along the
way!
Upwards,
Jason
Hello,
Congratulations to the RedCloth 4.0.0 release and thanks for the
outstanding work and all your efforts.
I’ve upgraded the slideshow (S9) gem that lets you author
slides/presentations in Textile to use RedCloth 4.0.0 to test out the
new machinery. (You can find some samples @
http://slideshow.rubyforge.org/svn/samples )
All works great except for one slide in the Merb deck. The slide title
reads:
h1. -vendor/plugins- gems
Before 4.0.0 that would translate to:
vendor/plugins gem
But now no longer honors the deletetion modifier and just ends up as:
-vendor/plugins- gem
Anyways, thanks again for the outstanding work and all your efforts
to make the RedCloth 4.0.0 release happen.
Cheers.
Gerald, I’ve filed your bug report as a ticket here:
http://jgarber.lighthouseapp.com/projects/13054-redcloth/tickets/20-
strikethrough-in-h1-not-working
Thanks for reporting it!
Hello,
Gerald, I’ve filed your bug report as a ticket here:
Lighthouse - Beautifully Simple Issue Tracking
Thanks for adding the ticket and looking into it. Just a little
addition. I did some more testing and found the strikethrough won’t
get honored only if it starts out e.g.:
h1. -vendor/plugins- gems
-vendor/plugins- gems
Won’t work. But:
h1. yada yada -vendor/plugins- gems
yada yada -vendor/plugins- gems
Will work.
In the ticket you write: “You can use square brackets to force a
strikethrough.”
I’d appreciate if you can give an example as I am unclear how to
force a strikethrough (e.g. do you mean using just html e.g. h1.
vendor/plugins).
Again thanks for your efforts in getting RedCloth 4.0.0 out the door.
Cheers.
Hey, Gerald. I should have provided an example. Sorry about that.
Let me give a little explanation for everyone’s benefit:
All the inline modifiers can be made a little more explicit by
surrounding them with square brackets. So, if you want to make a link
to a “Wikipedia article about
Textile”:Textile (markup language) - Wikipedia
, you can’t get the last character of the link because how would
RedCloth know if the link ended with a parenthesis or you just
surrounded a link in parentheses (like “this”:http://redcloth.org/)?
Square brackets to the rescue: [“Wikipedia article about
Textile”:Textile (markup language) - Wikipedia
] works perfectly.
Same with your strikethrough: surrounding the strikethrough with
square brackets makes it work:
$ redcloth
h1. [-vendor/plugins-] gems
outputs:
vendor/plugins gems
Yes, it’s annoying and it doesn’t conform to Textile 2, but it saves a
lot of frustration over things being accidentally struck through,
which happened a lot with the old version. Try this with RedCloth 3.x:
If I use dashes–like this–to make my statement, it used to get
struck through.
and you’ll get
If I use dashes-like this-to make my statement, it used
to get struck through.
As I said in the ticket, if someone can come up with a patch that
doesn’t sabotage normal text-with-hyphens, I’d be glad to accept it!
Thanks,
Jason