the hamstu

Thanks for this. I was about to write this port myself.

I’m looking forward to testing it out on some of my Wordpress installs.

Will do.

Great work first of all.

Secondly, I believe I found a bug. When the plugin adds spans for all-caps and other characters, it does so to all of the title, including the title attribute of the post’s link.

To explain that better, on my blog I have the title surrounded by a link (a). On that link I have a title attribute that repeats the title of the post ; for instance, my title attribute might generate “Permalink for This Post” in which This Post is the name of the post.

The bug comes when a span is inserted into the title attribute. Understand?

This looks good, one question though - does it deal with blogs that already have the PHP smartypants module installed? Thanks!

great that you’ve ported it to php. Great job. I’m now off to try it out. Would be interesting to see if we could get some “ligature” support in there!

I could cry. Thanks so much for this.

Please ignore my previous comment. It’s working perfectly (unlike my eyes).

I’m so impressed with it, that I’ll be writing about it on iLT. Thanks again for porting this to PHP.

Thanks, Hamish.
It doesn’t fix the example I showed you. IS it possible to “typogify” within a link?

Hamish
Yes, I use wp-cache, but had cleared it before checking. I edited the post and saved, but I’m still seeing that widow. I’ve found another too — in the Chocolate post, where it says, “Clever isn’t it”. Strange.

You are a star. Works perfectly. Really appreciate you taking a look and fixing. Great plugin. I can now review it on iLT.

I’m really looking forward to seeing your version of the Fontometer. I can’t wait!

Great work. Thanks. I was searching for such information.

Red hot and totally awesome! Thanks!

I found one issue: if the span class=caps option is enabled, there’s one situation I’ve found so far that’s broken:

If a post has an acronym in the title of it (such as my Leopard GM post: http://blog.christopherbowns.com/2007/10/25/leopard-gm-released-early-to-journalists-not-developers/), wp-typogrify inserts the span in the Permalink’s title attribute, and since you can’t “nest” double-quotes, this does quite a number on the page’s content, shifting the remainder of the title attribute into the link’s text. I’ll leave span caps enabled so you can see what the HTML looks like.

In addition, I have Markdown with SmartyPants installed on the blog, but upon enabling, I had no SmartyPants-styled quotes until I enabled it in the options panel.

Thanks for the plugin. One question though: How would/could I port this for Expression Engine?

Small bug: In the widont() function, the regex pattern includes ‘accronym’ bu this should be ‘acronym’.

I think this should be just a little bit smarter. It assumes that you write your blog entry within the admin area. I’m probably not alone in that I write my entries in OpenOffice so I can spell-check, save half-written entries, etc.

Usually when you copy/paste from a word processor you will get characters that already appear as desired but are not represented by HTML entities. Checking for them and converting them into the proper HTML entities seems like it would be safer and more consistent.

For example, if the word processor screws up somewhere and curls the quotes in the wrong direction, they get copied over and wp-typogrify just trusts that they’re correct, making the user wonder why these quotes should be any different from quotes they type in.

You get a similar problem with em/en dashes. If they’re already proper dashes when they’re copied over, thin spaces won’t be applied around them.

I love that this plugin exists at all… I was just surprised to find that it corrected almost nothing when I wrote postings my usual way. Just thought you’d like another use case.

Oh, and did not know about it. Thanks for the information …

Thanks for this terrific plugin. I definitely started using it right after it was plugged on the iLT blog.

Sadly I’m one of those guys that doesn’t get around to saying “thanks” until he has an issue to go with it. I ran into a problem with widow protection that is likely very rare, but a problem nonetheless. I have a poem which has a last line of one word (see it), which gets an nbsp entity prepended to it. This causes it to indent, which is not desirable behavior.

It doesn’t bother me that much, but maybe a switch could be added on a post-by-post basis (like <!--no-typogrify-->) to revert to texturize rather than typogrify behavior?

In reference to Christopher Bowns issue, I’m continuing to experience this issue, even though all of the blog’s “the_title()” bits say “echo wp_specialchars(get_the_title(), 1)” (which they always have been, by the by.) Anyway, I still experience the issue; you can see it in action at http://www.marcusrezak.com/

@Alenônimo
The ligatures thing is interesting. However, it wouldn’t look good for all typefaces. For example, if your tesxt is set in Georgia, Georgia doesn’t have an st ligature, so you’d get the standard ‘unicode’ one.

Re the CSS options you could change the ampersand (&) for a pretty one (e.g. Hoefler Text). so, where you have:

&

just use the following CSS rule:

.amp {
font-family: ‘Hoefler Text’;
font-style: italic;
}

The italic ampersand in Hoefler Text is gorgeous!

Hello there,

Thanks for the amazing plugin, it really saves me a lot of time and worry and I install it on every site I have running and those that are in progress.

I did however, notice that if you install it on a site that you have previously manually inserted non-breaking spaces at the end of paragraphs, that it adds yet another one prior to them. This results in three words wrapping to a new line rather than two. Is there anything I can do to remedy the problem without manually removing all of the existing non-breaking spaces?