wp-Typography

KING­desk Web Design is proud to make avail­able wp-​​Typography, a merger and expan­sion of the wp-​​Typogrify and wp-​​Hyphenate Word­Press plu­g­ins and Smar­ty­Pants functionality.

Features

wp-​​Typography is now a one-​​stop-​​shop for improved web typog­ra­phy in Word­Press. It fea­tures the fol­low­ing capa­bil­i­ties (includ­ing gran­u­lar control):

  • Hyphen­ation
  • Spac­ing con­trol, includ­ing: glu­ing val­ues to units, widow pro­tec­tion, and forced inter­nal wrap­ping of long URLs & email addresses.
  • Intel­li­gent char­ac­ter replace­ment, includ­ing smart han­dling of: quote marks ( “foo” ), dashes ( foo – bar ), ellipses ( … ), trade­marks ( ™ ), math sym­bols ( 1024×768 ), frac­tions ( 1223 ), and ordi­nal suf­fixes ( 3rd )
  • CSS hooks for styling: amper­sands (class “amp”), acronyms (class “caps”), num­bers (class “num­bers”), ini­tial sin­gle quotes (class “quo”), and ini­tial dou­ble quotes & guillemets (class “dquo”).
wp-Typography admin screenshot

Requirements

wp-​​Typography has the fol­low­ing requirements:

  • the host server must run PHP 5 or later
  • text must be encoded UTF-​​8
  • all markup must be valid xHTML, specifically:
    • every ele­ment must be closed,
    • every attribute must have a value enclosed in quotes, and
    • tag names and attrib­utes must be lowercase.

Related

Addi­tion­ally, the core func­tion­al­ity of wp-​​Typography (com­pletely seg­re­gated from the Word­Press plu­gin require­ments) has been released as a stand­alone project, ready for inte­gra­tion with any other PHP based con­tent man­age­ment sys­tem. For more infor­ma­tion, please visit the PHP Typog­ra­phy project page.

Your feed­back is much appre­ci­ated. How can we make this plu­gin bet­ter? Email us at info@​kingdesk.​com, or leave a com­ment below.

Comments

  1. I’m excited about the com­bi­na­tion of hyphen­ation sup­port with the tweaks made by wp-​​typogrify. I just tried it out, and it seems to be work­ing only par­tially so far.

    Thin spaces are not inserted around em dashes. A clos­ing quo­ta­tion mark in a block quote was not changed to a curly quote (but the open­ing quote mark was changed and wrapped in the appro­pri­ate span).

    The biggest issue, how­ever, is that some of my text was stripped by the curly quote replace­ment. This sen­tence, which includes a link with quo­ta­tion marks around it (it’s a title),

    In "I wake and feel the fell of dark, not day," Hopkins describes his experience of darkness,

    becomes this with wp-​​Typography:

    In “,” Hopkins describes his experience of darkness,

    Note that the code for the link is there, and so are the curly quotes, but the words of the title have dis­ap­peared. When I unchecked the curly quote replace­ment, the title reappeared.

    I’m happy to play with the plu­gin and give you more feed­back as well as try things out if you would like.

  2. Just dis­cov­ered some­thing about the thin spaces. I use the Mark­down plu­gin, so that 2 hyphens are changed to an em dash. When I changed some of the hyphens to em dashes in my post, the thin spaces appeared around them. So, if I start with em dashes, the thin spaces work, but not if mark­down has processed hyphens first.

  3. I’ll have to muck about with it some more, but as far as I can tell, it kills any short­tag (e.g. Kim­ili Flash Embed’s [kml_​embed] tags) if some func­tions are enabled (wp-​​typogrify did the same thing, but I had found a way to avoid this). Any help would be appreciated!

  4. @Dan Butcher #0

    Thank you for your feed­back. I found and resolved a multi­byte char­ac­ter con­flict in the smart-​​quote func­tion­al­ity. Also, thin spac­ing was work­ing fine for em-​​dashes, but I had neglected to imple­ment them for en-​​dashes. This is also resolved. (mark­down con­verts two minus/​hyphens to an en-​​dash, not an em-​​dash).

    I was unable to recre­ate your clos­ing quote issue, could you email me the unprocessed code it is hav­ing dif­fi­culty with to info@​kingdesk.​com?

    The plu­gin will be updated shortly to 1.0 beta 2.

  5. @Jeff Byrnes # 2

    wp-​​Typography greatly improves com­pat­i­bil­ity with short tags. For exam­ple, both wp-​​Hyphenate and wp-​​Typogrigy both cor­rupted Word­Press’ han­dling of image cap­tions. wp-​​Typography han­dles this correctly.

    This plu­gin prop­erly fil­ters out­put through “the_​content” hook, and pur­pose­fully waits until all other plu­g­ins com­plete their fil­ter­ing. Accord­ingly, short tags should already be con­verted to HTML by the time this plu­gin has a go.

    Unfor­tu­nately, Kimili’s Flash Embed’s does not fil­ter short tags like other plu­g­ins. He appa­rantly waits until the “init” hook, which occurs after con­tent fil­ter­ing. I am sure there is a rea­son he does so, but it makes his plu­gin inher­ently frag­ile when there is con­tent filtering.

    Regret­fully, the plu­g­ins are incom­pat­i­ble, and I am unable to resolve the issue from my end.

  6. @Dan Butcher #1

    Just so you know, wp-​​Typography also con­verts mul­ti­ple hyphens to em and en dashes.

    Mark­down has a very sim­ple han­dling of mul­ti­ple hyphen con­ver­sion to dashes: Dou­ble hyphens become en-​​dashes and triple hyphens become em-​​dashes.

    wp-​​Typography is a bit more intel­li­gent. It con­sid­ers the con­text and selec­tively con­verts dou­ble hyphens to en-​​dashes and (like when sur­rounded by num­bers) or em-​​dashes (like when sur­rounded by letters).

    If this is the only rea­son you are using mark­down, wp-​​Typography may make this unnec­es­sary. If there is another rea­son, please let me know… I would like wp-​​Typography to be an all inclu­sive typog­ra­phy solu­tion. Thanks.

  7. @Jeffrey D. King #5
    I’m using Mark­down because I used it for about 1.5 years, and so I’ve got a lot of posts (most of my posts) with not only the hyphens for dashes, but also * * for ital­ics, # for head­ing lev­els, and so forth. I made exten­sive use of the markup, and I don’t want to have to go back and clean up my old posts.

  8. Nice update for this release. CSS hooks are going to come in handy for future updates.

  9. Thanks for the email. I will be delighted to test it on my hard drive instal­la­tion and sub­se­quently on our plat­form – and if all goes well I sim­ply must inform the world of this. Just wrote an arti­cle about a move­ment for bet­ter typog­ra­phy (in Ger­man) so the tim­ing could hardly be better.

  10. @erz #8

    This is a big­ger part of the move­ment than just a Word­Press plu­gin. I have sep­a­rated the typo­graphic func­tion­al­ity for easy port­ing to any PHP based con­tent man­age­ment sys­tem. It is also fully doc­u­mented to fur­ther ease its use. See PHP Typog­ra­phy.

  11. I receive a lot of errors like:

    Warn­ing: mb_​strlen() [function.mb-strlen]: Unknown encod­ing “” in /path/vulvodynia.pl/wp-content/plugins/wp-typography/php-typography/php-typography.php on line 627

  12. Great work! I look for­ward to test­ing it thor­oughly. Would you con­sider putting this on http://​word​press​.org/​e​x​t​end so that we can update automatically?

  13. @Peter Gasston #11

    Yes, I plan on adding it to http://​word​press​.org/​e​x​t​end as soon as it is ready to have the beta label removed. Please let me know of any repro­d­u­ca­ble defi­cien­cies you find, so we can get to that goal. Thanks.

  14. Hey Jef­frey. First off, thanks so much for this awe­some plu­gin, and all of the work to merge the hyphen­ate and typogrify branches.

    I’m notic­ing an error on the demo site for my theme “The Eru­dite” after I enable 1.0b3. If you click into the footer, you’ll see that the Cat­e­gory list chokes in places due to a <span class="caps"> being inserted within the title attribute.

    Now, thank­fully you’ve enabled id and class black­lists, so it’d be easy enough to fix this. But I fig­ured you’d want to know about the issue in any case.

  15. And I go and for­get to pro­vide a link! It is at http://​eru​dite​.somade​sign​.ca/

  16. @Matt Wiebe #13

    I had a sim­i­lar prob­lem on one of my web­sites where I had used an improper func­tion to dynam­i­cally gen­er­ate title attributes.

    I had used the_title() which deliv­ers the post title after filtering.

    In this case, the proper Word­Press func­tion was the_title_attribute() which deliv­ers the post title before filtering.

    My guess is that your prob­lem is a theme issue. What func­tion are you using to dynam­i­cally gen­er­ate those title attributes?

  17. Hey Jef­frey

    Thanks for the speedy reply. The func­tion is the stock wp_list_categories() func­tion, which obvi­ously isn’t using an unfil­tered title attribute. Smells like a trac ticket.

  18. @ginekologia #10 & Matt Wiebe #16

    I was able to cor­rect both your issues in the newly released 1.0 beta 4.

  19. Hello Jef­frey,

    I am test­ing the plu­gin on a Ger­man instal­la­tion of word­press and have found a few quirks that might not nec­es­sar­ily be bugs but rather fea­ture requests.

    You said that there would be local­i­sa­tion of the plu­gin. There is no such option in my back­end, the lan­guage for the plu­gin is Eng­lish (actu­ally I don’t mind that at all, just point­ing it out).

    The typo­graphic rules for char­ac­ter replace­ments are Eng­lish and no option for other rules (or cus­tomized char­ac­ter replace­ment) is avail­able. Are there any plans to extend the plu­gin? I am not even sure, if all the rules for char­ac­ter replace­ment are opti­mal. The char­ac­ter string “word-​​” ( will add a space between the hyphen and the word and make it read “word -” which might be cor­rect for Eng­lish, but cer­tainly is not for German.

    Chang­ing the lan­guage for hyphen­ation does yield dif­fer­ent results. How­ever, nei­ther are sat­is­fac­tory. In some instances the plu­gin refuses to hyphen­ate words (regard­less of lan­guage), leav­ing large gaps in the jus­ti­fied align­ment. Widon’t does not work in all cases either.

    Lastly, the quote con­ver­sion does not seem to work in text-​​widgets.

    I will pro­vide screen shots and more thor­ough descrip­tion via email if you like. I am sorry to say that I don’t have a live ver­sion for you to check the markup.

    All the best
    erz

  20. There’s a prob­lem with RSS when wp-​​typography is activated.

  21. Jef­frey, I’ve been pok­ing around your site, read­ing some of your arti­cles, and I noticed that in Safari 4.0.1 (OSX), you pick up an odd char­ac­ter after a hyphen (see http://​king​desk​.com/​a​r​t​i​c​l​e​s​/​a​e​s​t​h​e​t​i​c​s​-​o​v​e​r​-​u​s​a​b​i​l​i​ty/ for an exam­ple: up-​​escalator in the arti­cle and well-​​written in the com­ments). I looked at the source code, and there’s noth­ing there that I can see. I’m won­der­ing if this is a (mis)function of the plugin.

  22. @erz #18

    The admin inter­face of wp-​​Typography was designed to inter­na­tion­al­iza­tion stan­dards. As such, it may be local­ized by users. Pro­vid­ing the trans­la­tions for the 40 lan­guages for which hyphen­ation pat­terns are pro­vided is beyond the scope of this plu­gin — and my skill set.

    What German-​​related char­ac­ter replace­ments would you like to see?

    In your “word-​​” exam­ple, which hyphen char­ac­ter would be cor­rect in Ger­man? I assume it is not the minus-​​hyphen. Would it be the Em Dash?

    The hyphen­ation pat­terns pro­vided are the pat­terns pre­vi­ously devel­oped for the TeX plat­form. The Eng­lish pat­terns work quite well (find­ing 90% of pos­si­ble hyphen­ation points with a 0% error rate). I can not speak to the qual­ity of the other lan­guages pat­terns. They were what was avail­able, so they were what I used. I did include the abil­ity to include indi­vid­ual hyphen­ation excep­tions, but if a pat­tern is miss­ing 50% of pos­si­ble hyphen­ation points, this will not be an accept­able solution.

    For Ger­man, I used the hyph-de-1996.tex pat­tern. You may find the hyph-de-1901.tex pat­tern pro­vide bet­ter results. If you want to go through the trou­ble of for­mat­ting them for the PHP Typog­ra­phy project, you can cer­tainly use this alter­nate pat­tern. I can walk you through the process (it is not trivial).

    Wid­ows are not pro­tected uni­formly. To pro­tect jus­ti­fied text from a long word being pulled to the next line, there are 2 cus­tomiz­able set­tings at the wp-​​Typography admin page:

    • max­i­mum widow length pro­tected, and
    • max­i­mum word length pulled from the pre­vi­ous line

    With which text wid­gets does this plu­gin not work? (If the text wid­gets are using Word­Press func­tions that include the hooks for fil­ter­ing, no plu­gin is capa­ble of mod­i­fy­ing their text.)

  23. @Jean Chouinard #19

    What RSS prob­lems are you expe­ri­enc­ing? Your com­ment is so vague, I have no start­ing place to fix your issue. Please be specific.

    wp-​​Typography has built-​​in abil­ity to han­dle the pro­cess­ing of feeds sep­a­rate from nor­mal con­tent. I have already stripped out much of the typo­graphic pro­cess­ing for feeds (because of the inabil­ity of feed read­ers to han­dle char­ac­ters like the soft-​​hyphen or the zero-​​width-​​space characters).

  24. @Dan Butcher #20

    This is not a mal­func­tion of the plu­gin, it is a mal­func­tion of the browser. Those char­ac­ters are zero-​​width-​​spaces that should enable wrap­ping after hard hyphens (not all browsers allow for this).

    When a browser does not prop­erly han­dle the zero-​​width-​​space char­ac­ter, it will often dis­play a square or a ques­tion mark.

    I know this prob­lem occurs in IE6, and I have pro­vided an option in the admin con­trols to inject JavaScript to strip out these charac­ers in IE6.

    If there is another browser that is chok­ing on this char­ac­ter, I am unaware of it. Could you share which browser you were using when you saw these characters?

    Thanks.

  25. I have noticed that in a clean install of wp-​​Typography, many of the admin­is­tra­tive default options are not prop­erly set. This will be cor­rected in the next ver­sion (1.0 beta 5).

  26. @Jeffrey #23
    It was in Safari 4.0.1 in OSX (the lat­est ver­sion of the browser that was just released) – and it is a square that is displayed.

  27. @Dan Butcher #25

    I just checked in Safari 4.0.1 (Build 5530.18), and could not repli­cate the issue.

    Does any­one else see errant zero-​​width-​​spaces han­dling as Dan describes?

    I noticed that in Safari 4.0.1 (OSX), you pick up an odd char­ac­ter after a hyphen (see http://​king​desk​.com/​a​r​t​i​c​l​e​s​/​a​e​s​t​h​e​t​i​c​s​-​o​v​e​r​-​u​s​a​b​i​lity/ for an exam­ple: up‐​escalator in the arti­cle and well‐​written in the comments).

  28. @erz #18

    The “word-​​” thin space inser­tion bug you iden­ti­fied was cor­rected in ver­sion 1.0 beta 5

  29. Just about to try this, but before I do I think I should men­tion that Avira detected some­thing when I was unpack­ing the archive:

    HTML/ADODB.Exploit.Gen

    I’m not sure what that is, but it seemed to be in sev­eral of the (lan­guage?) files.

  30. @Gareth #28

    I cre­ated each of the lan­guage files myself in a text edi­tor. The only thing I can think of to which Avira might protest is the use of very large arrays, often with more than 20,000 pat­terns stored — to the point where Text­Mate and Coda strug­gle to edit these files.

    Or maybe it doesn’t like some of the UTF-​​8 char­ac­ters required for some lan­guage files?

    I work on a Mac, so I am down­load­ing Avira into a VM to see if I can repro­duce the false pos­i­tive. Thanks for the heads-​​up.

  31. @Gareth #28

    I have con­firmed false pos­i­tives with an Avira scan. The cy.php, en-GB.php, es.php, ga.php, hr.php, and pr.php lan­guage files trig­ger this issue. I have been unable to divine the cause. I have reported the false pos­i­tives to Avira and pro­vided them a copy of the files.

    Avira’s review of the faslse pos­i­tives may be viewed here.

    I have also tested the files in AVG, and am happy to report no false pos­i­tives with their anti-​​virus solution.

  32. Thanks for the remark­ably fast response. I wasn’t too wor­ried, but sense that some peo­ple might be put off (also, the beeps, and hav­ing to man­u­ally dis­miss each of them, was a lit­tle tedious). Glad it isn’t a prob­lem at your end.

  33. On a dif­fer­ent note, I took a quo­ta­tion of this page with ‘Press This’, a lit­tle WP book­marklet (../wp-admin/tools.php), and had an odd behaviour:

    KING desk Web Design has just released wp‐​Typography, a merger and expan sion of the wp‐​Typogrify and wp‐​Hyphenate Word Press plu g ins and Smar ty Pants func tion al ity. It is now a one‐​stop‐​shop for improved web typog ra phy in Word Press. It fea tures the fol low ing capa bil i ties (includ ing gran u lar con trol)

    There are spaces in odd places, and I’m guess­ing they’re com­ing from the “poten­tial” hyphens, the posi­tions where hyphens could go…

    Not sure why the book­marklet is find­ing them, in Chromium (not Chrome), when the page itself ren­ders with­out issues…

  34. (It might hap­pen in Chrome, too, and pos­si­bly in FF as well… I say “Chromium (not Chrome)” as I’m using Chromium, cur­rently… and it is occa­sion­ally a lit­tle quirky…)

  35. @Jean Chouinard #19

    I found and resolved the issue that was break­ing RSS. It was addressed in ver­sion 1.0 beta 6.

    Thanks for the help.

  36. @Gareth #32

    We’ll call it a “feature”.

    This is a known com­pro­mise that comes with hyphen­ation. The hyphen­ation fea­ture works by insert­ing soft-​​hyphen char­ac­ters at every pos­si­ble hyphen­ation point. They are typ­i­cally invis­i­ble, and should only show up at the end of a line if the word wraps.

    Unfor­tu­nately, not every edi­tor is smart enough to prop­erly han­dle soft hyphens. Text copied from your web page will include soft hyphen char­ac­ters. Some pro­grams will dis­play a space instead of a soft hyphen. Some may dis­play actual hyphens. And it may break spell check even if the char­ac­ters are dis­played correctly.

    If you want hyphen­ation on the web, you must use soft hyphens. If you use soft hyphens, other pro­grams may not like copied text.

    I actu­ally copied text from my site a while back, and used it as text on the back of some Moo cards. It dis­played fine on their site, but the cards where printed with spaces all over the place.

  37. Hi guys ! First of all, awe­some work.

    Here’s the trou­ble I had :

    My feed wouldn’t val­i­date, I had an error that made me desac­ti­vate your whole process_​feed() func­tion, a shame for my read­ers!
    Here is the error, returned while I tried to val­i­date the feed :

    phpTypography::require_once(php-parser.php): failed to open stream: No such file or directory

    The file is here, It works like a charm online. There’s just this prob­lem for feeds only.

    Feel free to con­tact me for fur­ther details and tests.

    Thanks a lot for your work.

  38. @borisforconi #36

    That was cor­rected in the 1.0 beta 6 release.

    I actu­ally just pub­lished 1.0 beta 7, which includes a gag­gle of improvements.

  39. We’ve found and reme­died some sig­nif­i­cant bugs in the first 6 beta releases. I think 1.0 beta 7 is approach­ing a matu­rity ready for broader release.

    Please let me know if you agree or disagree.

  40. found another bug: in this string of text:

    …often–always?–judging…

    thin spaces will be added around the first em-​​dash, but not around the sec­ond. I took out the ques­tion mark, and the spaces are added around both dashes. I changed ? to !, same thing: no thin spaces. I also tried quotes around around always, like this:

    often–“always”–judging

    and as I expected, the quote marks were changed to curly quotes, but no spaces were added around either dash.

    So, it appears that what­ever fil­ters you’ve cre­ated to add in thin spaces don’t account for the pos­si­bil­ity of punc­tu­a­tion marks fol­low­ing or pre­ced­ing the dashes.

  41. This:

    has an odd effect on post titles…

    <a href="http://www.scribeoflight.org/b/2009/07/07/things-seen-on-the-internet-6/" rel="bookmark" title="Permanent Link to Things Seen on the Internet #6">Things Seen on the Internet #6</a>

    Look at how that span class code gets caught inside

    title=”…”

    Breaks the HTML

    But oddly, it only seems to affect post titles viewed on main pages, cat­e­gory pages, or on search results; post titles in the posts them­selves seem fine…

  42. Oops…

    The “this” is this:

    Wrap dig­its [ 0123456789 ] with .

    in the CSS hooks section…

    Ack! It didn’t keep my HTML… gra…

    Sorry, I’m not really a pro­gram­mer. I’m not very good at giv­ing grace­fully pre­sented feed­back on cod­ing issues… Hang on!

  43. Mmm…

    So:

    When this is selected in the settings…

     – Wrap dig­its [ 0123456789 ] with

    That span class code gets put into the title of any posts con­tain­ing digits\numbers… But then the code that has been placed into the post titles gets car­ried through to this code:

    [a title=“Permanent Link to {post title}”]{Post Title}[/a]

    as in…

    [a title=”Permanent Link to Things Seen on the Inter­net #5″>Things Seen on the Inter­net #5[/a]

    becomes:

    [a title=”Permanent Link to Things Seen on the Inter­net #[span class=“numbers”]5[/span class]“>Things Seen on the Inter­net #[span class=“numbers”]5[/span class][/a]

    [ =

    Man­gled, basi­cally, as the HTML in the title goes all funny…

    The title in the post itself is fine, of course, as in the post itself the post title (of course!) doesn’t act as a link to the post… In cat­e­gories, searches, and on the main blog page, how­ever, the post title is also a link, and that span class code get­ting buried in the link HTML is… problematic…

    Is this what is break­ing the RSS?

    Easy enough to change the code so it doesn’t apply span class to titles?

    Also, what exactly does all the span class stuff do? They’re applied to num­bers, quo­ta­tion marks… but what are they doing??

    Thanks for the plug-​​in. Hope the feed­back helps.

  44. @Gareth #40 – 43

    Your theme is using the wrong func­tion to pro­vide the title attribute in your head­ing links. See com­ment #15.

  45. Ah, okay… It is a theme I found… Neoclassical…

    I’ll tweak the code…

    What does this mean:

    Now, thank fully you’ve enabled id and class black lists, so it’d be easy enough to fix this. But I fig­ured you’d want to know about the issue in any case.”

    What are the id and class black­lists? And how could I use them to solve the problem?

    Thanks again for reply­ing so quickly.

  46. Sorted now. Very sim­ple… I’m still not sure if I need to use the black­lists, but I’m inter­ested to learn about what they do – all this fid­dling has reminded me of how lit­tle I actu­ally under­stand about HTML, PHP, and the mechan­ics of the inter­net, generally.

  47. @Gareth #45

    You should not need to use the black­list options. In the wp-​​Typography set­tings page, there is a field that let’s you list HTML tags that should not be typo­graph­i­cally processed.

    If you were unable to fix the theme, you could have listed the h1 and h2 tags in that field, but that would have turned off any typo­graphic pro­cess­ing in your titles (not just in the link).

  48. Regard­ing the cut’n paste prob­lem where the soft hyphens con­fuse spell check in word proces­sors etc: there used to be a tog­gle but­ten one could enable in the old hyphenate-​​plugin. I always use that before copy­ing text into my word proces­sor. It also allows for my read­ers to decide whether they want to hyphen­ate or not, as I strongly believe in leav­ing as many lay­out deci­sions as pos­si­ble in the hands of the reader. Easy rem­edy. I don’t know whether it’s eas­ily imple­mented for the new plu­gin though.

  49. Hi! This plu­gin is great. I would like to make a new hyphen­atin rule, Hun­gar­ian actu­ally. But I can’t fig­ure the process out… Would you help me?
    Many thanks.

  50. @erz #48

    In the pre­vi­ous wp-​​Hyphenate plu­gin, there was an admin­is­tra­tive option that allowed for HTML encoded soft-​​hyphens. This was not a user option. How­ever, the user could – with this option – copy from the source code and pre­form a search and replace for &shy; to remove hyphen­ation. This was not a viable solu­tion to the copy and paste issue addressed in com­ment #35. It also caused errors in the plu­gin that were dif­fi­cult to resolve.

    There is another fea­si­ble option for user-​​side con­trol. If you serve hyphen­ated text with this plu­gin, you could cre­ate a JavaScript func­tion users could trig­ger with a click to strip soft hyphens from the page. I don’t plan on incor­po­rat­ing such a fea­ture into this plu­gin, but some­one could develop such a solu­tion for their site.

  51. @pico #49

    Hun­gar­ian hyphen­ation pat­terns can be derived from this file.

    wp-​​Typography uses a deriv­a­tive of hyphen­ation pat­terns devel­oped for the TeX plat­form. If you look in the source code for wp-​​Typography at /php-Typography/lang_unformatted/template.txt, the spe­cific needs of lan­guage spe­cific hyphen­ation pat­terns are detailed.

    The rea­son I did not con­vert the Hun­gar­ian pat­terns for use with this plu­gin is that the Hun­gar­ian pat­terns num­ber over 62,000. The auto­mated process I set up to con­vert files stopped work­ing effi­ciently for files with more than 20,000 patterns.

    If you can get the Hun­gar­ian pat­terns for­mat­ted cor­rectly, I’d love to include it with the 40 lan­guages already represented.

  52. Hey Jef­frey: Just a quick note to say thanks once again for your fan­tas­tic work on this plu­gin, and that beta7 does indeed clear up the issue I raised in the cat­e­gory listing.

  53. @Dan Butcher #39

    The newly released beta 8 should address your thin-​​space issue.

    Note that your exam­ple “often-​​always” will not be rec­og­nized for en or em dash replace­ment, as it can not be dis­tin­guished from a hyphen­ated word like “mother-​​in-​​law”.

    To man­u­ally over­ride, you can insert two dashes, or type &ndash;

    Oth­er­wise, it should work well for your example.

  54. Have just installed Beta 8 (although it still says Beta 7 on the Plu­g­ins page).

    CSS Hooks are oper­at­ing on the title attribute of links:

    title=”HTML 5, CSS 3, DRM <span class=”amp”>&</span< fonts”<

    This seems to be the case for num­bers, amper­sands, and acronyms.

  55. Hi

    Thanks for plu­gin! Is there oppor­tu­nity to turn it off for RSS com­pletely? It’s much more of headache in this case.

  56. @Jeffrey #53
    Yes, Beta 8 does solve the issue of thin spaces and punc­tu­a­tion marks.

    Regard­ing the often-​​always, that actu­ally had an 2 dashes between it – my point in includ­ing that in the exam­ple text was to show that the first dash (between 2 words) was con­verted to the appro­pri­ate typo­graphic dash, while the sec­ond dash (between a mark of punc­tu­a­tion and a word) was not converted.

  57. FYI: I uploaded beta 8, and I know it is the new ver­sion, but the plu­g­ins page on my wp site lists it as beta 7.

  58. Sug­ges­tion: would it be bet­ter to use some kind of bug track­ing soft­ware for us to report with?

  59. @Peter Gasston #54

    Your head­ing links are bro­ken because of an error in your theme (not the plu­gin). The FAQs sec­tion out­lines how to resolve bro­ken page title links.

  60. @Peter Gasston #58

    I just noticed your web­site is http://​bro​ken​-links​.com. In light of your pre­vi­ous com­ment, I got a lit­tle chuckle.

  61. @Pavel #55

    What prob­lem are you hav­ing with RSS feeds? At this point, pro­cess­ing is pared down to just basic char­ac­ter replace­ment (i.e. dashes and quotes).

    There was an ear­lier issues with bro­ken RSS feeds, but that has been resolved since beta 6.

  62. @Jeffrey D. King #61
    Sorry, it wasn’t about RSS (but still, think it’d be nice to have sep­a­rate set­tings for blog and RSS), it was about tags and RSS titles as seen after click­ing on RSS icon in address bars. That’s it with CSS hooks on:

  63. <link ... title="&raquo; &lt;span class=&quot;numbers&quot;&gt;6&lt;/span&gt; Ave Comments Feed" ...>

  64. @Pavel #63

    It appears that you took this from the <head> sec­tion of your blog. You seem to have the same mal-​​formed theme issue described in the FAQs, except your theme uses the func­tion in the page head (as opposed to the head­ing link as dis­cussed in the FAQ).

    If you are able to find the offend­ing the_title() func­tion and replace it as instructed in the FAQs, the prob­lem should go away.

  65. Yes and no. I found the place where links are gen­er­ated. It is wp-includes/general-template.php:1499 and it is not the theme. The code called looks like esc_​html( get_​the_​title() ).

    I’m using 2.8 and The­matic Theme Framework.

  66. @Pavel #65

    Where did you copy this: <link ... title="&raquo; &lt;span class=&quot;numbers&quot;&gt;6&lt;/span&gt; Ave Comments Feed" ...> ?

    Can you pro­vide a link? My RSS feeds are clean, even when the post title con­tains char­ac­ters that are nor­mally wrapped in CSS hooks.

  67. @Pavel #65

    Alright, I am see­ing it now. Not on the main feed, but on sec­ondary feeds. This is a bug in the Word­Press core. I just filed a bug report with Word­Press, and their progress in address­ing it can be fol­lowed here.

    Because of the way Word­Press core is writ­ten, you can not turn off feeds. You can only turn off headings.

    This func­tion­al­ity is already built into wp-​​Typography. You can enter h1 and h2 into the “Do not process the con­tent of these HTML ele­ments:” field in wp-Typography’s admin­is­tra­tive options.

  68. Thanks, Jef­frey. I’ll just turn off CSS hooks for now. And we’ll wait for Word­Press guys. Cheers.

  69. My RSS feeds are bro­ken, again, I think.

    And I’ve been hacked :-(

    Have via­gra spam in my Google search results and in my RSS when viewed on Google Reader… but the site itself is fine.

    Don’t know if it is con­nected to plug-​​in or not… Frus­trat­ing, though.

  70. @Gareth #69

    Typ­i­cally, spam injec­tion in your HTML code occurs because of a vul­ner­a­bil­ity with shared host­ing. Your host would prob­a­bly be very inter­ested in this issue so they can resolve it.

    It could also occur if you use an inse­cure user login for Word­Press, or allow any­one to reg­is­ter as an admin, but users of this plu­gin are smarter than that.

    It is most likely an FTP or SSH exploit through your host. wp-​​Typography does not have any inter­ac­tion with user account controls.

  71. The odd thing is, it doesn’t look like it is in either the HTML or the PHP. I can’t find where it actu­ally *is*, merely can see the effect of it in Google search results and on my Google Reader page. The RSS also goes to my Twit­ter, when I post, and the spam doesn’t get there… And when I look within the code of a page that seems to be “infected”, there is noth­ing — no out of place script, no strange tags, no hint of any­thing that might be caus­ing issues.

    All very odd.

    I’ve started http://​www​.scribe​oflight​.org/​e​r​h​e​b​u​ng/ as a replace­ment, per­haps per­ma­nent… Gives me an excuse to redesign.

  72. @Gareth #71

    My guess is that it is in your footer.php file (although it could be in the header.php or index.php.

    Often, these injec­tions will be pro­ceeded by a large amount of white­space, so they are hid­den far off to the right of the screen when you view source. Try view­ing source, scroll all the way right, and then scroll up and down the page. You will prob­a­bly see the injected HTML there.

  73. Works great, thank you

  74. Kudos on the quick release of the first non-​​beta ver­sion (though I sup­pose it might not have seemed quick to you!). I’ve enjoyed watch­ing a bit of the devel­op­ment process as you have taken feed­back and made changes in each release.

    Thanks for your hard work; the plu­gin is great!

  75. @Dan Butcher #74

    Thank you greatly. The plu­gin is sig­nif­i­cantly improved because of your (and oth­ers) contributions.

  76. Jeff, just acti­vated Typog­ra­phy and noticed that some forward-​​slash (“/​”) char­ac­ters were inex­plic­a­bly being turned into divi­sion signs (“÷”) even though the option to con­vert those sym­bols was turned off.

    In fact, I see it here on your page in these com­ments in #43 (“http://www.scribeoflight.org/b/2008÷11/18/and-ill-whisper/”). Although, maybe you have it enabled. I don’t, though.

  77. @Crankietech #76

    Thanks for the heads up. I fixed both issues you men­tioned in ver­sion 1.0.2. The update should be pushed out by WP soon.

  78. Works great with default set­tings, but when I try to save my cus­tomiza­tions I get an “Error! options page not found” message.

  79. @Duane Poncy #78

    I was unable to repli­cate your issue. Could you answer two ques­tions to help me fur­ther investigate?

    1. What browser are you using?
    2. What is the spe­cific URL that is return­ing the error page?

    I took a stab at sim­pli­fy­ing the admin URL in the just released ver­sion 1.0.3. Please tell me if it cured your prob­lem. Since I was unable to repli­cate the issue, I have no idea if this sim­pli­fi­ca­tion was helpful.

  80. In “Intel­li­gent Char­ac­ter Replace­ment” it doesn’t seem to func­tion prop­erly with “Trans­form frac­tions [ 12 ] to pretty frac­tions [ 12 ].” The sup– and sub-​​tag does not appear. Instead the 1 and the 2 each get wrapped in a numbers-​​class.

    Also – In “Space con­trol : Val­ues and units”, I can’t really fig­ure out how to write the abbre­va­tion for square meters. Should I write the sup-​​tag in that field?
    I.e: m(sup)2(/sup)

  81. I’m not sure if it’s the plu­gin but when I use it, most of the time (strangely not always) my rss-​​feeds don’t work any­more (I have a Ger­man blog). This error then occurs:

    XML pars­ing failed: syn­tax error (Line: 123, Char­ac­ter: 48)

    Reparse doc­u­ment as HTML
    Error:well-formedness con­straint: entity declared
    Spec­i­fi­ca­tion:http://​www​.w3​.org/​T​R​/​R​E​C​-​x​m​l​/​#​w​f​-​e​n​t​d​e​c​l​a​red

    –> Could this be pro­duced by wp-​​Typography? This would be very sad since I really love your plu­gin (it’s what I was look­ing for for months!)

  82. @Tom Stone #80

    If you have the option enabled to style num­bers, wrap­ping in class “num­bers” is expected.

    Sur­round­ing spaces can inter­fere with frac­tions. For frac­tions to be styled prop­erly, they must be pre­ceded by a space and fol­lowed by (option­ally ordi­nals and/​or punc­tu­a­tion) and a space.

    The square-​​meter unit is already rec­og­nized and glued to it’s units if the “Value and Units” option is selected. You do not need to man­u­ally enter it in.

  83. @JUICEDaniel #81

    It appears that the RSS feed is being inval­i­dated by inclu­sion of a HTML char­ac­ter (such as &amp;).

    To help me trou­bleshoot, it is appre­ci­ated if you would recre­ate the error and val­i­date the feed at http://​feed​val​ida​tor​.org/. Please copy the con­tent and send it to me as a text file or pdf at jk@​kingdesk.​com.

    Thanks.

  84. @JUICEDaniel #81

    Thank you. The plu­gin was encod­ing HTML char­ac­ters, such as &ouml;, which was per­fectly valid for HTML, but was not valid for XML feeds. As of ver­sion 1.1, spe­cial HTML char­ac­ters de-​​encoded for XML feeds.

  85. Thanks, it seems to work fine now. What exactly have you changed to fix this? I’m just curi­ous to know what caused this error.

  86. The wid­ows fea­ture is fan­tas­tic but like the wi-​​dont plu­gin they cre­ate wid­ows where wid­ows don’t exist. For example:

    Tuto­r­ial: Mak­ing the Flut­ter
    Date Field work for you

    Becomes:

    Tuto­r­ial: Mak­ing the Flut­ter
    Date Field work
    for you

    I’ve noticed this only hap­pens with sIFR Flash replace­ment of fonts acti­vated. Any thoughts would be greatly appreciated.

    http://​www​.doc4de​sign​.com

  87. @JUICEDaniel #85

    The plu­gin class uses two main meth­ods to do the heavy lifting:

    I ran the con­tent returned from process_feed() through the html_entity_decode() func­tion to remove any HTML spe­cific char­ac­ters that XML may not recognize.

  88. Thanks (now I saw your email, I haven’t checked them first, sorry)!

  89. @pico #49

    A Hun­gar­ian lan­guage pat­tern is included in ver­sion 1.5

  90. Thank you very much for cre­at­ing this plugin!

    Also: prop­erly formed html5 works too, not just xhtml :)

  91. @James John Mal­colm #90

    Yes, it should work well with HTML5, pro­vided it is for­mat­ted in the xHTML vari­ant, with low­er­case tags, quote enclosed attrib­utes, and paired clos­ing tags.

    The HTML vari­ant, where para­graphs and list items are not required to be closed and tag names are upper­case may have unex­pected results.

  92. Great Plu­gin. It works like a charm on my self-​​hosted Word­Press site http://​www​.heiniger​-net​.ch

    Next I wanted to try on my self-​​hosted WP-​​MU site http://​blog​-net​.ch — and there it wouldn’t work. Sav­ing Options resulted in the error mes­sage “Fehler! Ein­stel­lungs­seite nicht gefun­den.” (or “Error! Options page not found.”)

    Any idea of what that could be? Would it be pos­si­ble to pro­duce a WP-​​MU-​​compatible ver­sion of this great plugin?

    Thanks a lot
     — Daniel

  93. @Doc4 #86

    I have not seen this behav­ior, and I am unable to repro­duce it. My guess is that the non-​​breaking space in the font you use is a few pix­els wider than the stan­dard space. If that is com­bined with a very tight fix-​​width box, it could add enough width to cause the last word to wrap (thus pulling the sec­ond word with it because of the attached nbsp)

  94. @Daniel #92

    I have attempted to make the plu­gin MU com­pat­i­ble. Would you mind try­ing it and let­ting me know if it works? You can down­load the MU beta at: http://​word​press​.org/​e​x​t​e​n​d​/​p​l​u​g​i​n​s​/​w​p​-​t​y​p​o​g​r​a​p​h​y​/​d​o​w​n​l​o​ad/

    The ver­sion you want is 1.7.1-beta-MU

    If it works prop­erly, please let me know so I can release it more broadly. Thanks.

  95. @Jeffrey D. King #91
    True, you have to form it like xhtml, but not actu­ally send it as xhtml (viz. the mime-​​type).

  96. Jef­frey,
    this ist really great stuff. I won­der if I can change the char­ac­ters used for the trans­for­ma­tion of the straight quotes, as those used by you are not cor­rect in ger­man. Allowed are:
    inverted french
    (0187 lead­ing, 0177 at the end)
    “9966”, but with 99 at the height of a comma
    (0132 lead­ing, 0147 at the end)

    Could you give me an hint?

    Or do you even plan to make the char­ac­ters con­fig­urable, as I think, this is a com­mon problem …

  97. @Peterchen #96

    Dou­ble low 9 quote han­dling is already built in. Type two adja­cent com­mas, and they will be replaced with your desired char­ac­ter. Dou­ble right and left angle quotes are also handled.

    • ,, becomes „
    • &lt;&lt; becomes «
    • >> becomes »

    The dou­ble left angle quote is admit­tadly kludged, but that is a lim­i­ta­tion of HTML, as the < char­ac­ter is pro­hib­ited for nor­mal use (it indi­cates the begin­ning of an HTML ele­ment). Two < char­ac­ters may work when input into Word­Press’ wysi­wyg edi­tor, I have not tried… I work directly in the code editor.

  98. Jef­frey,

    (@97)

    for Ger­man type­set­ting, you would just take your code you already have for replac­ing the “Dou­ble quote”-character (“) with open­ing and clos­ing quo­ta­tion marks and take other signs for them. The clos­ing quo­ta­tion mark may stay as it is, the open­ing one would just become the “dou­ble comma”-character.

    I pro­grammed this years ago in a Java pro­gram and made it just con­fig­urable: “Quo­ta­tion style: (1) Eng­lish quo­ta­tion marks, (2) Ger­man quo­ta­tion marks, (3) French guille­mots, (4) Reverse French guille­mots”. Then, the engine can replace the input with what­ever char­ac­ters the writer wants to have.

    Best regards,
    Dirk

  99. @Dirk Hill­brecht #98

    At this point, the plu­gin has been down­loaded in more than 80 coun­tries, and 40 lan­guages are sup­ported. I am not pre­pared to try to con­vert the " char­ac­ter to lan­guage spe­cific rules for each country’s idio­syn­crasies. There is – already pro­vided – a very sim­ple way to mark angle and comma quotes (in a way that degrades gracefully).

    I have tested the instance where << is input to the Word­Press wysi­wyg edi­tor, and it is prop­erly con­verted to «, fur­ther sim­pli­fy­ing the issue. If you use the wysi­wyg edi­tor, you do not need to escape those characters.

  100. But maybe Eng­lish, French and Ger­man would be a nice addi­tional option. Think about it: Much more Ger­mans would down­load and love your plu­gin just because of that, I’m sure because there is no work­ing plu­gin right now but still a great long­ing for that feature.

    By the way: http://​www​.juiced​.de/​b​l​o​g​/​2​0​0​9​/​0​8​/​1​3​/​d​i​e​-​5​-​c​o​o​l​s​t​e​n​-​w​o​r​d​p​r​e​s​s​-​p​l​u​g​i​n​s​-​t​e​i​l​-​1​-​w​p​-​t​y​p​o​g​r​a​p​hy/ (German)

  101. I have a prob­lem with the Ital­ian pat­terns, which do not seem to work. The plu­gin is installed cor­rectly and I can get the hyphen­ation work (obvi­ously with the wrong hyphen­ation) if I select the Eng­lish or French file, but if I switch to Ital­ian noth­ing hap­pens.
    Thanks.

  102. @Dirk Hill­brecht #98 & JUICEDaniel #100

    You Ger­mans are per­sis­tent. Well, per­sis­tence pays off… Check out ver­sion 1.10, now avail­able for down­load. I think you will be happy.

  103. @Fabio #101

    Try the newly released ver­sion 1.10, and let me know if Ital­ian hyphen­ation improves. The hyphen­ation pat­terns for Ital­ian are less devel­oped than other lan­guages, but the results were stun­ningly unim­pres­sive. I made a few changes that – hope­fully – will cor­rect that situation.

    Thanks for your feedback.

  104. If you haven’t already, I’d greatly appre­ci­ate it if you clicked through to the word​press​.org plu­gin direc­tory and gave wp-​​Typography a 5-​​star rat­ing. Thanks!

  105. Have you con­sid­ered adding CSS hooks for things like prepo­si­tions (of, for, from, to), arti­cles (the, a, an), and con­junc­tions (and, but)?

  106. @Jay #105

    I have not con­sid­ered that. I don’t see its use­ful­ness off hand, but I am open to convincing.

  107. I don’t think I’d per­son­ally use those hooks, but I know some peo­ple like to style those words dif­fer­ently in big head­ings — lower case ital­ics among small caps, for instance.

  108. @Jeffrey #103
    I am on 1.11 and it still does not work. i did some test­ing reduc­ing the test area and I am able to get the hyphen­ation only for one sin­gle pat­tern, every word start­ing with “pre”.

    Thanks
    Fabio

  109. @Fabio #108

    The wp-​​Typography plu­gin uses hyphen­ation pat­terns that were cre­ated for the TeX pub­lish­ing platform.

    Some lan­guages have very com­plete pat­tern sets. Oth­ers have less devel­oped pat­terns. It appears that the pat­tern set we are using for Ital­ian is not as com­plete as I would like.

    I was able to iden­tify and resolve an issue where some multi­byte char­ac­ters were caus­ing words not to be hyphen­ated. As such, Ital­ian hyphen­ation should now be imple­ment the com­plete pat­tern set. But hyphen­ation will only be as good as the pat­tern included.

  110. Is it pos­si­ble to use this plu­gin to remove dou­ble spaces between sen­tences for chronic dou­ble space­bar whack­ing fools like myself? I often end up with long posts where at least one line of a para­graph begins with a space.

    It’s an awful habit.

  111. Made Kim­ili Flash Embed Plu­gin (http://​kim​ili​.com/​p​l​u​g​i​n​s​/​k​m​l​_​f​l​a​s​h​e​m​bed) stop work­ing, after a day try­ing to fig­ure out why my site didn’t work any­more, I deac­ti­vated WP Typog­ra­phy.. and voila…

  112. @tor #111

    see com­ment #4 above.

  113. @J. Mayer #110

    For nor­mal spac­ing, stan­dard HTML han­dling auto­mat­i­cally col­lapses spac­ing to a sin­gle space and removes spaces from the begin­ning of block­level HTML elements.

    How­ever, if a no-​​break space is added adja­cent to a nor­mal space, you may get unex­pected results.

    As such, I have added a “col­lapse spac­ing” fea­ture to the next ver­sion of wp-​​Typography. As this will fix a minor issue, it will be turned off by default. But if you want it, it will be there.

  114. Hi Jef­frey

    I can’t acti­vate the plu­gin and get this error-​​message:

    Fatal error: Allowed mem­ory size of 50331648 bytes exhausted (tried to allo­cate 76 bytes) in
    /var/www/web451/html/sinn/wp/wp-content/plugins/wp-typography/php-typography/lang/de.php on line 12917

    I checked the file at the giv­ing line, but that gives me no hint at all.

    I have 48M php-​​memory (more than with my old provider, where the plu­gin worked).

    What can I do?
    Help badly needed.

    Michael

  115. @Michael #114

    wp-​​Typography has suc­cess­fully been used with as lit­tle as 4M of mem­ory. So 48 should be more than enough.

    Unlike most PHP errors, this line num­ber is not indica­tive of an error in the code, just where the mem­ory limit was exceeded.

    I would try two things:

    1. Dis­able your other plu­g­ins – one at a time – and see if another plu­gin is eat­ing up most the the mem­ory before wp-​​Typography gets to it.
    2. Dis­able wp-​​Typography fea­tures one at a time to see if the prob­lem goes away.
  116. Hi Jef­frey,

    This did the trick for me. Thanks a lot.

    Nextgen was the bad­die. I dis­able the ones I thought might be the mem-​​hogs one by one. After dis­abling nextgen wp-​​typography workes as it should. I could enable nextgen after­wards with­out problems.

    The mem-​​bar in wp-​​system-​​health turns red now, but I am fine with that. All the plu­g­ins I want are run­ning now.

    Kudos!
    (and 5 * of course)

  117. Please note that if you select “Wrap acronyms (all cap­i­tals) with ” it will also insert code into NAV links (into the title tag and wrap­ping the text link) caus­ing the link to break onto a new line.

    Exam­ple: Nav link was “FAQ”. The plu­gin inter­preted it as an acronym and inserted a title tag and wrapped “FAQ” with the code. This cre­ated an unwnated line break.

    Another exam­ple was a link “POP Design”. Same thing hap­pened. “POP” was wrapped and “Design was broke to a new line.

    This is a great plu­gin but would sug­gest that users could add some sort of Start and End com­ment code around the sec­tion of the site they want the plu­gin to man­age. This obvi­ously defeats some of the pur­pose of hav­ing a plu­gin but would allow more control.

    Thanks.

  118. I’d love a black­list of phrases never to be wrapped and treated like dig­its & units, e.g. names, order codes, tele­phone no., song titles …

    How could that be imple­mented? Maybe some hints for a hack of your plugin?

    Thanks!

  119. Hi there, thanks a lot for this very handy plu­gin which improved the look of my weblook a lot.

    I would like to sug­gest a fea­ture regard­ing the use of mul­ti­ple lan­guages in one weblog. I use Eng­lish and Ger­man. In this case the hyphen­ation works only for one lan­guage cor­rectly, as spec­i­fied in the options.

    The best solu­tion for this would be to auto­mat­i­cally detect the lan­guage of each entry or para­graph and apply the appro­pri­ate hyphen­ation pat­tern. I know that Google pro­vides an API for lan­guage detection.

    The other solu­tion would be to some­how mark the lan­guage of each entry and use this set­ting for the hyphen­ation. But that seems more com­pli­cated from the user’s perspective.

    Thanks for con­sid­er­ing, Mathias

  120. Hi,

    I’m using your plu­gin and I noticed a bug when I’m writ­ings things like

    l’être est l’être

    I’m writ­ing 2 sim­ple quotes but I don’t want the plu­gin to trans­form them into curly ones.

    Sec­ondly, I have an issue with the dou­ble french curly braces : I’d like to have inse­ca­ble space «[here]and[here]». Is it possible ?

  121. @Ghussen #120:

    Those sin­gle quote should be curly ones (aka real apos­tro­phe) in French. In fact, except for com­puter code and such, there is no ‘ in French, only ’.

    But I do sec­ond the non-​​breaking space around every dou­ble punc­tu­a­tion (in a French con­text): before :;?!» and after «. If those could have a spe­cific CSS class, that would be even better :)

  122. Oups, it also applies to com­ment. I meant, in French there’s no sin­gle quote, only “curly” ones.

  123. @Jérémie

    I agree that, in French, quotes should be curly ones. But the plu­gin replaces them by the char­ac­ters “”. That’s a bug.

    And it will be nice if the non-​​breaking spaces could be added before all dou­ble punc­tu­a­tion (not around, but just before)

  124. Yup, sorry about that. As explained in the next sen­tence, I meant: non-​​breaking space before :;?! – »— (hope I don’t for­get any) and after –«—

    If I may push it fur­ther, \”foo\” should become « foo » and \’bar\’ should become “bar”. \<> is ok, but sel­dom used and some­what a has­sle to use :)

  125. Hav­ing issues with the escap­ing. I meant dou­ble straight quotes becom­ing «  » and sin­gle straight quotes becom­ing “” (again, for French).

    If needed, one could look at the French local­ized Tex­tile code (should be on the Textpat­tern forum archives), it does every­thing needed codewise.

  126. Sin­gle quote should be replaced by a sin­gle curly quote in all cases (apostrophe).

  127. @Kristof #117

    Please see this FAQ to fix your theme. The error occurs because your theme uses the wrong WP function.

  128. @Uwe #118

    Black­lists of words and phrases from typo­graphic han­dling is not planned to be included in this plu­gin. It would require a sub­stan­tial rewrite and add con­sid­er­able overhead.

    You can use the “class” black­list option already included to accom­plish this on a per-​​occurrence basis. For exam­ple, you could black­list the “noTypo” class, and wrap the text you do not want processed in <span class="noTypo">foo bar</span>.

  129. @Mathias #119

    Auto­matic lan­guage detec­tion would be a neat addi­tion. It was con­sid­ered and tested, but I deter­mined it unre­li­able. HTML pro­vides a means by which you can com­mu­ni­cate the lan­guage con­tained within an ele­ment, and I tried to lever­age that stan­dard markup.

    The main prob­lem was the plu­gin could only access the HTML markup stored in the data­base, so any­thing hard­coded into the theme – where much of the lan­guage infor­ma­tion is prop­erly located – is not available.

    This along with other issues proved the solu­tion would have been unreliable.

  130. @Ghusse &amp @Jérémie #120 – 126

    I have revised the plu­gin to be much more cus­tomiz­able in this regard. I hope you find these changes help­ful. Ver­sion 1.15 should be live later this afternoon.

  131. @Jeffrey Thanks, I’ll take a look !

  132. Hi,

    just a ques­tion about fil­ter­ing the_​content…

    for pods (http://podsDOTuprootDOTus), which makes other con­tent then wp-​​posts & –pages pos­si­ble, it won´t work, because you don´t call the con­tent. An easy work-​​around would be to make a “pods-​​filter”, which is sim­ple a php-​​function.

    My Ques­tion: Could/​Would you make one avaible?

    Thanks a lot! (I use it any­way for ‘con­ven­tional’ home­pages, but hope that it will inte­grate with my other projects too. Thanks a lot again!!)

  133. @Kaiser #132

    I think you may be approach­ing this the wrong way. Pods appears to be an exten­si­ble CMS built upon Word­Press. Instead of try­ing to get each plu­gin con­form to Pods, per­haps you should get Pods to con­form to exist­ing Word­Press plugins.

    For wp-​​Typography, you should make sure any Pods func­tions that dis­play con­tent called from the db apply the proper con­tent fil­ters. The func­tion for this is apply_filters(). wp-​​Typography hooks into the fol­low­ing fil­ters (which should be applied as appropriate):

    • category_​description
    • comment_​author
    • comment_​text
    • single_​post_​title
    • the_​title
    • the_​content
    • the_​excerpt
    • widget_​text
    • widget_​title

    Apply­ing this to Pods would not only make it com­pat­i­ble with this plu­gin, but a whole host of plugins.

  134. hi & thanks for your plugin.

    1) are you sure the sec­tion about bro­ken page title links in the faq is cor­rect? it says that the cor­rect way to do it would be using the_​title_​attribute (and not the_​title), but in the exam­ple pro­vided there it’s just the other way round!?

    2) i’m hav­ing a sim­i­lar prob­lem the #16 above (i think, at least) – i want to wrap those ini­tial quotes in a css class and wp-​​typography keeps rewrit­ing the title-​​tags, because they’re writ­ten not from the_​title or the_​title_​attribute, but from within wp_​list_​pages (in my case). you can see an exam­ple of the gen­er­ated html on my site (left sidebar/​header, “best of”-link). is there any way to fix this (other than turn­ing that fea­ture off completely)?

    thanks in advance,
    ~ f.

  135. Hi and thanks for the plugin.

    I just found out, that your plu­gin does not work in Opera! not even in ver­sion 10.

    Could you please have a look at this issue?

    Thanks!

  136. @frank #134

    1. You were cor­rect and this has been fixed. Thanks.
    2. The prob­lem you are hav­ing with wp_list_pages() is a lit­tle bit dif­fer­ent than #16 above. There, the HTML ele­ments were unescaped, break­ing the visual dis­play. Your prob­lem is that wp_list_pages() escapes HTML ele­ments (instead of strip­ping them). For­tu­nately, this does not break the lay­out, but it is unde­sir­able. I have reported this bug to Word­Press, and the progress for res­o­lu­tion can be fol­lowed at Word­Press Trac. If you’d like to see this resolved, a sup­port­ing com­ment on Trac would be helpful.
  137. @Daniel #135

    I was able to iden­tify a bug that is new to Opera 10 on Win­dows (Mac works fine). It does not prop­erly dis­play the zero-​​width spaces used to force line breaks. Wher­ever a zero-​​width space occurs, it dis­plays an ugly box. I have reported the issue to Opera’s bug report­ing service.

    For now, if this is an issue for you, you may dis­able all the options in the “Enable Wrap­ping” sec­tion of wp-Typography’s admin page.

  138. @Jeffrey
    Thanks for the quick reply and thanks for report­ing it to Opera. It seems, the prob­lem is not only a Win­dows issue, same thing here on a Mac (OS X 10.6.1, Opera 10.01). I dis­abled wrap­ping for now.
    Cheers,
    Daniel

  139. Hi there, we just imple­mented this plug-​​in on our site and I dis­cov­ered that there isn’t any hyphen­ation sup­port for Norwegian.

    I was won­der­ing if I could either be allowed to imple­ment it for you you or request it implemented?

  140. @Jeffrey (see #132/#133): first thanks for your answer, but i´m sim­ply not that good in php. i found the fol­low­ing in your class-wpTypography.php on Line
    637: remove_filter(‘the_content’, ‘wptex­tur­ize’);
    615: add_filter(‘the_content’, array(&$this, ‘process’), 9999);

    the way to get pod-​​items (text like the con­tent, titles, etc.) is the following:

    get_field(‘excerpt_txt’);
    ?>

    i should now do some­thing like or am i com­pletely wrong?

  141. @KK #139

    I found a Nor­we­gian lan­guage file I was able to make work. I just pushed ver­sion 1.18 – which includes this file – and it should be avail­able for down­load within 15 minutes.

    A word of warn­ing: the pat­tern file has over 30,000 pat­terns (6 times larger than the Eng­lish file). This will result in slower performance.

  142. @Kaiser #140

    Try this for gen­eral content:

    
    $filteredContent = apply_filters( 'the_​content', get_field('excerpt_txt') );
    

    And try this for headings:

    
    $filteredTitle = apply_filters( 'the_​title', get_field('page_title') );
    
  143. Thank you, we’ll imple­ment it and see how it goes

  144. Hi. I’m hav­ing some prob­lems with the title attribute in this page: http://​comeu​tudinho​.com/​2​0​0​9​/​1​0​/​v​e​n​d​e​-​s​e​-​d​e​n​t​es/ . Two squares appear after the dash, and I don’t know what I’m doing wrong. I’m using wp_​title() and the prob­lem still occurs even if I dis­able the hyphenation.

    By the way, that’s a great plugin. ;)

  145. @Caio Costa #144

    In Word­Press themes, title attrib­utes should not be gen­er­ated by wp_title(). You should use the_title_attribute().

    See this FAQ for more information.

  146. @Jeffrey: thanks for your help. i asked the same ques­tion at the pods forum and now got it run­ning. too beau­ti­ful!! i sim­ply love wp-​​typography and pods!! wp at it´s best!

    just to leave this here in case some­one got the same ques­tion: (it´s for a template.php-file). inside the pods-“loop” just add

    * $pods_​pretty = new wpTy­pog­ra­phy(); (only needed once! for all fields)
    * $pods_​name = $Record->get_field(‘name’);
    * $pretty_​name = $pods_pretty->process($pods_name);

    then echo $pretty_​name where you need it.

  147. One more thing: I really LOVE the new diacritics-​​feature. Could you please!!! bring us some place or adress, where we could drop a line, so that you get more words. For e.g. Names are some never end­ing story:

    Aron”=>”Áron”,
    “Laszlo”=>”László”,
    “Rene”=>”René”,

    etc. (could be some sort of end­less list :)

  148. another thing i for­got to men­tion: in german-​​language (aus­tria, switzer­land, ger­many) you got com­pound words. for e.g. you don´t write “car dri­ver” you write “Aut­o­fahrer” (car = auto; dri­ver = fahrer). And when you have two com­pund sub­jects start­ing or end­ing with the same sin­gle sub­ject, you don´t repeat them. You just use a dash to repeat the sub­ject. For e.g. “Auto– und Bus­fahrer” (car and bus dri­ver). The Prob­lem with wp-​​Typography in this case is, that the short dash get´s replaced with a long dash, which looks pretty strange & ugly.

    One pos­si­ble sol­lu­tion would be to just make dif­fer­ent options out of the sin­gle hyphens-​​option, so we could deac­ti­vate this and keep the rest. thanks for listening!!

  149. @Jeffrey Great! I knew I was miss­ing some­thing. Sorry I didn’t get to the FAQ before asking.

  150. Been test­ing the plu­gin with Nor­we­gian hyphen­ation and it works like a charm. Sadly though it seems like we won’t be able to use it after all as it seems like we’ll be going to use a server run­ning php4, not 5 :/

    Thank you for imple­ment­ing Nor­we­gian any­way, I will prob­a­bly use it at some other time.

  151. Hi and thanks for this great plu­gin. I am a book­maker and I´m prepar­ing a web-​​site for my busi­ness – so I am happy about a plu­gin that man­ages pro­fes­sional typog­ra­phy.
    But I have a lit­tle prob­lem con­cern­ing the plu­gin. I´m using the plu­gin wp-​​columnize and have inserted the fol­low­ing css-​​code as pro­posed on the authors home­page to man­age the columns (http://​www​.mar​tin​ish​.com/​b​l​o​g​/​2​0​0​8​/​1​2​/​w​p​-​c​o​l​u​m​n​i​ze/):

    div.column-sect {
    clear: both;
    dis­play: inline-​​block;
    over­flow: auto;
    }

    div.post-column {
    dis­play: inline;
    float: left;
    margin-​​right: 18px;
    text-​​align: jus­tify;
    width: 45%;
    }

    It seems to con­flict with your plu­gin. Maybe you can give me a hint con­cern­ing this. Does it work with div elements?

    Thanks!
    Patrick

  152. @Patrick #151

    Noth­ing in the pro­vided CSS will cause wp-​​Typography to fail. I am not sure what the con­flict is. What mis­be­hav­ior are you observing?

  153. @Jeffrey: Do you con­sider some sort of form to let users extend your diacritics-​​feature?

  154. @Kaiser #153

    The dia­crit­ics fea­ture may be extended in one of two ways:

    • In the admin area, you may add indi­vid­ual rules in the pro­vided text area. This is ideal for adjust­ing behav­ior to per­sonal preference
    • You may also write rules for a new language.
      1. Go to
        wp-typography/php-typography/diacritics/
      2. Dupli­cate the en-US.php file.
      3. Name it accord­ing to the coun­try code you will be writ­ing for (i.e. de.php for German)
      4. Using the same for­mat, replace the $diacriticLanguage value with that of the new language.
      5. Replace the $diacriticWords with array val­ues of the new lan­guage spe­cific rules.
      6. Upload the new file to your server.
      7. Select the set­ting in your admin panel.

    A piece of advice: watch the order of your rules. If you first declare a rule to replace “a” with “b”, fol­lowed by a rule to replace “a b” with “c”, the sec­ond rule will never be used because the “a” in “a b” will always be replaced first. These rules should be reversed in order so “a b” is fil­tered before any rules for “a” are applied.

    Lastly, if you cre­ate a lan­guage spe­cific file, please email it to me so I can include it in future distributions.

    Thanks.

  155. I encoun­tered a strange bug in con­nec­tion with “Head­lines” and other WooThemes. The plu­gin inserts html code into titles of posts which con­tain at least three con­sec­u­tive CAP let­ters. The result is dupli­cated and strange look­ing post titles. Can you dis­able the adding of html in these cases? I really like your plu­gin and would love to con­tinue using it.

  156. Just solved it by dis­abling “Wrap acronyms” in the “Add CSS Hooks” part of the plu­gin options.

  157. hi there,

    i’m using wp-​​typography in ger­man. I have a prob­lem with the quotation-​​marks. in the options-​​field, when I want to choose the trans­for­ma­tion for the quo­ta­tion marks, I just see strange lit­tle black bars. Is there a font miss­ing or some­thing? Can any­body help me with this? I’ve done a screen­shot, feel free to take a look for yourself:

    http://​www​.boerde​be​ho​erde​.de/​q​u​o​t​e​.​JPG

    Best Regards,
    Torsten

  158. Hi,

    I noticed a bug with wp-​​typography, with quotes replace­ment. It’s only hapen­ning whith a quote end­ing a paragraph.

    For instance :

    This is my exam­ple, see the end­ing quote”

    In the­ory, the end­ing quote is replaced by an open­ing one, in my case.

  159. Ok, it appears that my exam­ple is not work­ing. But on my blog, some­one posted com­ments like that, and i had the issue (with french-​​style quotes).

  160. Hi. I’m devel­op­ing dual lain­guage word­press site. Is there a way to switch wp-​​typography lan­guage set­tings via php? I mean if I’m on Eng­lish page, let it hyphen­ate accord­ing to Eng­lish rules and when it’s pro­cess­ing Pol­ish page – use Pol­ish rules.

  161. I’ve just noticed multi-​​language blogs were dis­cussed… how about using a cus­tom post/​page value to define lan­guage used? It is stored in the data­base so wp-​​typography could prob­a­bly use it.

  162. @x #160

    Is there a way to switch wp-​​​​typography lan­guage set­tings via php?

    This is not an avail­able fea­ture of the wp-​​Typography plu­gin, but can be accom­plished by directly using the php-​​Typography par­ent project.

    php-​​Typography is exten­sively doc­u­mented, but does require famil­iar­ity with PHP.

  163. @Olaf # 156

    I’ve been work­ing with another plu­gin devel­oper who has a plu­gin that will resolve the escaped html in title’s issue. She is resolv­ing a few bugs, and when that is com­plete, I will share the link.

  164. @Torsten #157

    You must not have the spec­i­fied font installed on your com­puter. I deep­ened the font stack and pushed ver­sion 1.21.1. Hope­fully this solves the issue for you.

  165. @ Jef­frey

    Works fine now. Thanks a lot for your effort. Very much appreciated. :)

  166. Hi there, after acti­vat­ing the WP-​​Typography plug-​​in I get the fol­low­ing warn­ing replac­ing each instance of text on every screen:

    Warn­ing: preg_​replace() [function.preg-replace]: Com­pi­la­tion failed: sup­port for \P, \p, and \X has not been com­piled at off­set 163 in /var/www/vhosts/lafugue.co.uk/httpdocs/wp-content/plugins/wp-typography/php-typography/php-typography.php on line 1909

    I’m using Word­Press 2.9 self-​​hosted with the The­sis theme. Any clues as to were I’m going wrong

  167. Hi,

    I found that when I turn on wp-​​Typography in my posts func­tion “read more” is missing.(WordPress 2.9.1 + wp-​​Typography 1.21.1 Any­body know what to do (rein­stal­la­tion of wp-​​Typography doesn’t work)?

  168. Hi ya,
    very nice plu­gin! still explor­ing it.

    but hav­ing word­press sites with dif­fer­ent lan­guage con­tent the hyphen­ation for only one laguage is not always right.

    So I thought great the “do not process”-list and I tried it.

    but noth­ing worked, i.e. what­ever I put into html ele­ment, classes or id no change always all con­tent was hyphenated!

    I even tried body as ele­ment. Maybe I’m stu­pid right now but shouldnt it turn off all hyphenation.

    Do I mis­un­der­stand the func­tion of that list or have you heard of sim­i­lar prob­lems. Do I have to switch on some other of the plu­gin fea­tures which I might missed to do?
    Maybe some­thing wrong in my theme files, in the html, in my css, cache prob­lem, with the post loop … ;-)

    thx very much for your work!!

    Im run­ning with Word­Press 2.8.6 and higher and your lat­est plu­gin Ver­sion 1.21.1

  169. @Dirk #168

    This is a great ques­tion, and I have added a FAQ to address it.

    In short, wp-​​Typography does not have access to HTML that resides in your theme files. As such, fil­ter­ing will only apply to HTML within the title or con­tent of your post or page.

  170. @David Hughes #166

    after acti­vat­ing the WP-​​​​Typography plug-​​​in I get the fol­low­ing warning

    This is a prob­lem with your server con­fig­u­ra­tion, not the plu­gin. The PHP PCRE exten­sion has been com­piled with­out sup­port for uni­code char­ac­ters (inter­na­tional char­ac­ters) on your server. Com­pile the exten­sion with uni­code sup­port (–enable-unicode-properties) or ask your provider to do it.

  171. @krzemin #167

    Could you leave the pre­cise code that gen­er­ates your “read more…” state­ment in a com­ment so I could try to recre­ate the issue? – or email me at jk@​kingdesk.​com.

  172. Hi Jef­frey,

    ah ok, cool great to know.

    I think based on this here:

    http://​aext​.net/​2​0​0​9​/​1​0​/​w​o​r​d​p​r​e​s​s​-​h​a​c​k​-​a​n​y​t​h​i​n​g​-​c​a​n​-​b​e​-​a​d​d​e​d​-​a​n​y​w​h​e​r​e​-​i​n​-​t​h​e​-​p​o​s​t​-​c​o​n​t​e​nt/

    I will be able to add some nec­es­sary “notypo” thingie auto­mat­i­cally into the posts of my greek and pol­ish colleagues.

    Cheers

  173. Can­not fig­ure out why I get so many odd char­ac­ter spac­ings through-​​out my body text in the lat­est Mac & PC ver­sions of Safari ??

    http://​www​.mag​net​stu​dio​.com/​w​o​r​d​s​/​2​0​1​0​/​o​p​e​n​t​y​p​e​-​g​u​ide

  174. Just want to say this is a great plu­gin. Thank you for sharing.

  175. Thanks for this great plu­gin. It’s a huge improve­ment for WordPress.

    I just won­dered if it were pos­si­ble to trans­form the –Quotemarks into <q> and </q>, which is what I cur­rently use. I know,

  176. Can wp_​typography be applied to cus­tom fields?

  177. @Thomas #175

    I do not have plans to include quote con­ver­sion to <q> tags… pri­mar­ily because the algo­rithm does not do an exhaus­tive match­ing of begin­ning and end­ing quotemarks.

    Instead, it tries to deter­mine if a quotemark is an open­ing or clos­ing mark based on the con­text. As such, con­vert­ing to HTML tags will invari­ably lead to invalid markup.

  178. @Adam Lev­in­ton # 176

    Can wp_​​typography be applied to cus­tom fields?
     

    Yes, it can. But you must code your imple­men­ta­tion of cus­tom fields to apply a con­tent hook. For example:

    
    <?php
    $meta_value = get_post_meta($post_id, $key, TRUE);
    echo apply_filters('the_content', $meta_value);
    ?> 
    
  179. I’m pulling in a cus­tom field value with this code:

    
    $key="card_size";
    $meta_value = get_post_meta($post->ID, $key, true);
    echo apply_filters('the_title', $meta_value);
    
    

    (first I used ‘the_​content’ but that wrapped every­thing in a p tag)

    This is the string I’m pulling in:
    12 ” x 8 12 “

    The straight quotes are suc­cess­fully con­verted to curly quotes. How­ever, the frac­tions do not get converted.

    There’s a space on each side of the frac­tion, and I meet all the plu­gin require­ments. What am I missing?

  180. @Corey #179

    Look at the raw HTML. You may find it is being processed. Frac­tions are cre­ated by apply­ing <sup> and <sub> tags to the numer­a­tor and denom­i­na­tor (respec­tively). If you use a reset stylesheet and have not rede­clared the styles, it could appear unprocessed.

    There could be another rea­son. For the dou­ble quote to appear as a double-​​prime (as it should when rep­re­sent­ing inches), it can not be sep­a­rated by a space. But if it is not sep­a­rated by a space, the frac­tion is not rec­og­nized. This is a bug that I will cor­rect in the next release.

    Your exam­ple above exposed another bug and one short­com­ing. The bug: frac­tions are not rec­og­nized if they are trailed by a widow (there is a no-​​break-​​space inserted before the last word – or punc­tu­a­tion mark in the case above – that throws off the algo­rithm). And the short­com­ing: the “x” was not con­verted to a “×” when the double-​​prime (“″”) inter­me­di­ates a num­ber and the “x”. This may or may not be addressed in a future version.

  181. @Jeffrey #180

    Thanks for your response. I checked the HTML out­put, and there are no super– or sub­script tags, so even though the straight quote is being processed, the frac­tion isn’t. It’s inter­est­ing to note that on your site, the first frac­tion actu­ally does get processed correctly.

    Makes me won­der if it has some­thing to do with my con­fig­u­ra­tion. None of my other plu­g­ins should be mod­i­fy­ing the con­tent fil­ters. My server is run­ning PHP 5.2.9 and it does have the mbstring extension.

    I also tried sev­eral vari­a­tions of the string, but noth­ing seemed to work (I also did check to make sure “trans­form frac­tions” was turned on in the set­tings):

    5 1/2 x 8 1/2 in.
    5 1/2 "
    5 1/2

    Stumped.

  182. @Corey #181

    The sec­ond frac­tion does not get processed because of the widow bug I men­tion in #180.

  183. I would really like to see sup­port for the Dutch lan­guage in the “Lan­guage for hyphen­ation rules”.

    You will make 23 mil­lion Dutchies happy :)

  184. Guys! Please check how your plug-​​in appears in Opera browsers. Text is full of squared empty glyphs.
    Dis­abling all the options in the “Enable Wrap­ping” doesn’t work.
    I appre­ci­ate your plug-​​in and thanks for your nice work. Guys from Oepra, please, fix the bug.
    Greet­ings from Poland.

  185. It’s a huge improve­ment for Word­Press. Thanks for this great plugin.

  186. great plugin..really useful…thanks.

  187. Per­haps you’d con­sider adding abbre­vi­a­tion sup­port to this plu­gin, or per­haps revamp­ing or inte­grat­ing the “Ubernyms” plugin.

    For the most part, Ubernyms already has every­thing one would need with the excep­tion of a case-​​insensitive option.

  188. I got a prob­lem with wp-​​typography after the update to 2.0.2

    Fatal error: Call to a mem­ber func­tion process() on a non-​​object in *****/html/wp-content/plugins/wp-typography/class-wpTypography.php on line 687

  189. Seems like it’s an awe­some plu­gin, but is there a russ­ian lan­guage support?

  190. @x
    @Dirk
    @Mathias

    Great to know that there other peo­ple out there who run mul­ti­lin­gual sites.
    I use the WPML plu­gin. It would be great if wp-​​typography could detect WPML’s lan­guage setting.

  191. Hi Mr. King. I recently installed your plu­gin and con­sis­tently get this error in all themes:

    Fatal error: Call to unde­fined func­tion mb_​ereg_​replace() in /home/singfm/public_html/wp-content/plugins/wp-typography/php-typography/php-typography.php on line 1721

    I have WP 3.0.1, as well, I have man­aually installed the plu­gin when the auto-​​install pro­duced the same error.

  192. When run­ning debug mode through WP-​​config, mil­lions of notices turn up every­where – all say­ing:
    Notice: Unde­fined vari­able: rawHTML in /​www (SNIP) /plugins/wp-typography/php-typography/php-parser/parseText.php on line 65.

    There’s plenty more of the same on the options page of WP-​​Typography, but the notice for line 65 is every­where, mak­ing it harder to find and debug other prob­lems. Can this line be fixed?

  193. I have loved this word­press plug-​​in since I found it! I have also found an item that may need some code change.

    I have a word­press arti­cle that includes ‘Time & Expenses’ in the title. When I use the option to wrap the amper­sand, I get a title with a link on the first page of my blog that is gar­bled. When look­ing at the html, there is a amper­sand wrap in the title, even though the title is excluded. This causes odd text to be dis­played in the link. The same occurs for all caps – try putting IRS in a title.

    Hope­fully this is an easy fix – I really like the styled amper­sand in the blog text.

    Thanks again for a great widget!!

  194. Hi,

    I just wanted to thank you for this great plu­gin. Com­bined with @font-face now there seems to be a real chance to cre­ate typo­graph­i­cally beau­ti­ful web­sites.
    I´m sorry for my “wood­cut” eng­lish as I´m not a native speaker …

  195. Hi, Jef­frey! I’m hav­ing weird issues with Chrome that I’ll be hard pressed to describe well — it seems that some words are hyphen­ated, while oth­ers are not, espe­cially in my head­ings. By “not,” I mean the word is bro­ken, but no hyphen is displayed.

    For instance, the title for the post “Lead­er­ship Class spon­sors Win­ter Dance” on the front page appears as:

    Lead­er­ship Class spon­sors Win
    ter Dance

    If I shrink the con­tain­ing div to force hyphen­ation else­where, the word “spon­sors” breaks cor­rectly AND dis­plays a hyphen.

    (There’s a story toward the bot­tom of the page, as well — the word “unused” is bro­ken, but not hyphenated.)

    I’m using Type­kit for head­ings, and I’ve been able to repli­cate this with Type­kit dis­abled, as well. Using a low­er­case “w” on “win­ter” still breaks with­out the hyphen.

    Hyphen­ation seems to work fine in body text in Chrome, and head­ings are hyphen­ated prop­erly in Fire­fox and Safari.

    Any guess as to what might be up? Is this a known issue with Chrome, maybe?

    Thanks!

  196. @Jeff Far­rell #196

    I haven’t seen this. Off hand, per­haps this is the cause: Maybe your @font-face font is being min­i­mized to a base set of char­ac­ters that excludes the soft-​​hyphen. I believe most browsers will acco­mo­date for this, but per­haps Chrome doesn’t. If pos­si­ble, try it with a non-​​minimized font.

  197. I use the wp-​​Typograghy a long time and i’m very pleased about the pro­fes­sional func­tion­al­ity, but since the update to wp 3.0.2, hype­na­tions will be done within the text. So, e.g. hypens will be inserted between all syl­la­bles of a word with­out any line breaks.
    Maybe, is there a solu­tion in progress or do you know any workaround to fix that?

    Thanks for your answer and the nice plu­gin.
    Christian

  198. Dear Jef­frey, thanks for cre­at­ing this very use­ful plug-​​in. My WP site, which I am cur­rently build­ing, uses qTrans­late to serve mul­ti­lin­gual blogs and con­tent. I read pre­vi­ous com­ments that wp-​​typography is unable to detect or to be some­how informed of the lan­guage to use for hyphen­ation. How­ever, as qTrans­late embeds lan­guage codes into the con­tent, using short­codes such as [:en] etc, I won­der if there is a sim­ple way to hack this detec­tion into the plug-​​in?

    If not, I am con­sid­er­ing pre-​​hyphenating the text with soft hyphens. Would you have any sug­ges­tions as to a site or soft­ware, per­haps based on your code, that could per­form such pre-​​hyphenation so that I could upload an already hyphen­ated text accord­ing to indi­vid­ual lan­guages and to switch this func­tion off in your plugin?

    Many thanks and best of luck in 2011,
    Rafal.

  199. I’ve just updated to the lat­est ver­sion of wp-​​Typography, and it seems to place a rogue “Set­tings” link above the list of plu­g­ins, and just below the drop­down menu for apply­ing bulk actions.

    Any ideas why it’s doing this? I’ve made a screen­grab of it here…

    http://​img510​.image​shack​.us/​i​/​s​c​r​e​e​n​g​r​a​b​.​p​ng/

  200. The issue with Chrome Browser and hyphens are due to a bug using CSS text-​​rendering: opti­mizeleg­i­bil­ity; which ren­ders all soft hyphens as nor­mal hyphens.

    http://​code​.google​.com/​p​/​c​h​r​o​m​i​u​m​/​i​s​s​u​e​s​/​d​e​t​a​i​l​?​i​d​=​6​8​230

  201. I really like wp-​​Typography. I’ve been test­ing it on a new site, and I’ve encoun­tered one dif­fi­culty and one thing I’d like to suggest:

    The dif­fi­culty was that the first dash in this file­name (which appears in text) was changed to an emdash:

    2011 – 08-wholeshow.mp3
    which became
    2011 – 08-wholeshow.mp3

    So wp-​​Typography thinks it’s con­tex­tu­ally appro­pri­ate to change it, when actu­ally it’s a date (and part of a file­name). Any sug­ges­tions? I’ve tem­porar­ily had to dis­able “Trans­form minus-​​hyphens to con­tex­tu­ally appro­pri­ate dashes, minus signs, and hyphens” as a stopgap.

    The idea or fea­ture request is to have a “Do not process the con­tent of these HTML ele­ments” box for hyphen­ation sep­a­rate from the Gen­eral Scope box, because some­times I’d like wp-​​Typography to do every­thing except hyphen­ation (in block­quotes, for example).

  202. In both exam­ples above you see emdashes. That’s prob­a­bly because wp-​​Typography is try­ing to cor­rect it here as well. The first exam­ple was sup­posed to be:
    2011[hyphen]08[hyphen]wholeshow.mp3

  203. Nei­ther an en dash or an em dash has thin (or other) spaces sur­round­ing it.

  204. Hyphen­ation does not work with greek (either monot­o­nic nor poly­tonic. http://rnw.runaway.gr/δοκιμή/
    Can any­body tell if he/​she man­aged to make hyphen­ation work with greek?
    Thanks in advance.

  205. Hi! Thank you very much for the Plug-​​in!

    I just tried to get it work with cus­tom fields. Like you men­tioned in Post 178 – I tried to get it to work – and finally it worked (maybe it will help someone):

    First:
    ID, ‘Your Cus­tom Field Name’, true); ?>

    Sec­ond:

    Now it should work.

    Thank you!!

    Max­i­m­il­ian

  206. Multi­n­gual hyphen­ation hack – in response to my com­ment (199 above), I have writ­ten a very short hack that enables you to use wp-​​typography with qTrans­late plug-​​in a way that sets the cor­rect hyphen­ation lan­guage on a per-​​page basis, as indi­cated by qTrans­late. Addi­tion­ally, I have added two more small hacks to dis­able hyphen­ation of com­ments while still allow­ing the remain­der of wp-​​typography to do its magic. All the changes need to be done in your class-wpTypography.php file. You need to: 1) change one line that hooks the process func­tion with add_​filter to comment_​text, 2) add a new func­tion which I called process_​without_​hyphenation, and 3) add a switch state­ment inside the process func­tion. Here is the code.

    If any­one thinks I should write a more detailed guide how to do it, please con­tact me http://​rafal​.net/​c​o​n​t​act

    Change 1):

    /​/​ The fol­low­ing add_​filter explic­itly uses wp-​​typography with hyphen­ation turned off
    /​/​ so that com­ments on mul­ti­lin­gual blogs can be nicely for­mat­ted but with­out incor­rect
    /​/​ hyphen­ation. This requires that func­tion process_​without_​hyphenation is defined, see it below
    /​/​ just after processTi­tle.
    /​/​ Added Feb 2011 by Rafal Lukaw­iecki, http://​rafal​.net/​c​o​n​t​a​ct/
    add_filter(‘comment_text’, array(&$this, ‘process_​without_​hyphenation’), 9999);

    Change 2)

    /​/​ The fol­low­ing func­tion process_​without_​hyphenation sim­ply calls orig­i­nal process but dis­ables hyphen­ation
    /​/​ regard­less of the global set­ting. This is so that it can be used for pro­cess­ing com­ments on amul­ti­lin­gual blogs.
    /​/​ This way you get all the ben­e­fits of wp-​​typography just with­out pos­si­bly incor­rect hyphen­ation.
    /​/​ Added Feb 2011 by Rafal Lukaw­iecki, http://​rafal​.net/​c​o​n​t​a​ct/
    func­tion process_​without_​hyphenation ($text, $isTi­tle = FALSE) {
    $hyphen­ation­sta­tus = $this->settings[’typoEnableHyphenation’];
    $this->phpTypo->set_hyphenation(FALSE);
    return $this->process($text, $isTi­tle);
    $this->phpTypo->set_hyphenation($hyphenationstatus);
    }
    Change 3)

    func­tion process($text, $isTi­tle = FALSE) {

    /​/​ The fol­low­ing switch block added to sup­port multi-​​lingual (one lan­guage at a time) pro­cess­ing
    /​/​ in con­junc­tion with qTrans­late plug-​​in. Added Feb 2011 by Rafal Lukaw­iecki, http://​rafal​.net/​c​o​n​t​a​ct/
    switch(qtrans_getLanguage()) {
    case(“pl”):
    $this->phpTypo->set_hyphenation_language(“pl”);
    break;
    default:
    $this->phpTypo->set_hyphenation_language(“en-GB”); }
    /​/​ end of qTrans­late sup­port block.

    if(is_feed()) { /​/​feed read­ers can be pretty stu­pid
    return $this->phpTypo->process_feed($text, $isTi­tle);
    } else {
    return $this->phpTypo->process($text, $isTi­tle);
    }
    }

  207. Hi

    Is there an option to turn off wp-​​typography in the admin­is­tra­tion sec­tion of WP? My site is quite mem­ory hun­gry, espe­cially in the admi­in­stra­tion area. The prob­lem is that when I have wp-​​typography (and other plu­g­ins) installed I get an mem­ory error and the page will not load. This is pri­mary on the arti­cle list­ning page. (edit.php)

    Error mes­sage
    Fatal error: Allowed mem­ory size of 33554432 bytes exhausted (tried to allo­cate 54 bytes) in …/public_html/wp-includes/meta.php on line 197

  208. Hi,
    thanks for one of great­est plu­g­ins avail­able. Is there any way, how can I selec­tive dis­able hyphen­ation? E.g. I don’t want to hyphen­ate links. Many thanks

  209. Hi there,

    PHP was throw­ing a num­ber of errors which I found orig­i­nated to parseText.php’s load() func­tion. I made two changes that seem to have cor­rected the issue:

    /​/​ abort if a sim­ple string exceeds 500 char­ac­ters (secu­rity con­cern)
    if (!is_​array( $raw­Text ))
    {
    if ( preg_match(“@\w{500}@s”, $raw­Text) ) {
    return;
    }
    }

    First, $rawHTML was hanged to $raw­Text in preg_​match() (because that’s what you’re pass­ing into the load() func­tion). Sec­ond, preg_​match won’t work on an array, so I’m check­ing for that. I imag­ine a check for an array would involved loop­ing through the array and tak­ing note of the length of each string, catch­ing strings that exceed 500 chars and then doing a final check on the total length count for all strings in the array.

    Just thought I’d send this along! Also, wp-​​Typography is won­der­ful. Great job.

  210. Cool, Thank you very much!!!!!!!!

  211. Wp-​​Typography is almost what I need. How­ever, I’ve encoun­tered three issues:
    1. There’s no “cock­ney” string match as in wptex­tur­ize, so words with ini­tial apos­tro­phes — ’tain’t, ’twas, etc. — aren’t processed cor­rectly.
    2. Spe­cial char­ac­ters are ren­dered as actual char­ac­ters rather than as named or numeric enti­ties.
    3. There’s a bug where a clos­ing dou­ble quote imme­di­ately pre­ced­ing a “” is incor­rectly trans­lated as a left curled dou­ble quote rather than as a right. A clos­ing sin­gle quote, how­ever, is ren­dered correctly.

  212. 3. There’s a bug where a clos­ing dou­ble quote imme­di­ately pre­ced­ing a break ele­ment (i.e., “left angle bracket, b, r, space, slash, right angle bracket”) …

  213. Huh, the cockney-​​isms are indeed trans­lated cor­rectly above. OK, so two issues.

  214. Hi,
    Wp-​​​​Typography is almost per­fect for my web­site. Why “almost” ? Because it really slows my web­site down…

    Did I do some­thing wrong ? Is there a way to do the changes Wp-​​Typo do just one time when an arti­cle is published ?

    Thank you for your help and your won­der­ful plugin.

  215. @Dr Emixam – con­sider using a WP cache, such as W3 Total Cache or WP Super Cache. They will both take care of pre­pro­cess­ing all the WP Typog­ra­phy PHP and caching it. Have a look at my site, it used WP Typog­ra­phy heav­ily, yet it is pretty fast, thanks to those, and a few other minor opti­mi­sa­tions. Good luck.

  216. Hello,

    If you look at the foot­note on this page on my blog, you’ll see that what should be a close quo­ta­tion mark has treated the foot­note marker as the begin­ning of a new quote. I am won­der­ing if this some­thing con­nected to this plug-​​in, if it’s some­thing I can fix with a set­ting, or if the prob­lem is some­where else. I’ve already checked with the designer of the theme I am using and he assures me it’s not a bug in the theme.

    Thanks in advance for the help.

  217. Good day,

    Is there a page where I can see if fea­ture X is imple­mented and, if not, I can pro­pose it? I am well versed in advanced French typog­ra­phy, and would like to pro­pose some rules (I can­not code them, though, I can just give pseudocodes insight).

    Thank you!

  218. Maybe I missed the answer to this in a com­ment some­where, but when using The Eru­dite WP theme + wp-​​Typography, the open­ing dou­ble quo­ta­tion mark in a title dis­ap­pears. Any thoughts on a solution?

  219. Hi

    Your plu­gin looks excel­lent, but unfor­tu­nately it has no effect on my blog what­so­ever. I’m mainly look­ing for hyphen­ation. I tried with dif­fer­ent themes. The word­press ver­sion is cur­rent. The only clue is that the blog is in Russ­ian (yes, I enabled Russ­ian in the admin panel).

    Any sug­ges­tions, please? The site is hrabro​.com

  220. Your plu­gin causes a con­flict with Events where it makes the map for the loca­tion sec­tion be a per­ma­nent grey load­ing page.

  221. As a for­mer book designer, I would really like to use your wp-​​typography plug-​​in.

    Unfor­tu­nately it’s break­ing Grav­ity Forms and insert­ing span tags into the out­put of a page tree plug-​​in the site I am building.

    I see it hasn’t been updated in some time. Is there any like­li­hood of a fix?

  222. Using the Plu­gin since today in my blog – and love it already. I just have a lit­tle prob­lem with inject­ing the cus­tom quo­ta­tion marks in the front page. In the Arti­cle every­thing is fine but in the excerpt on the archive page and start page there are still the old ugly quo­ta­tion marks. What can I do?

  223. hi!!!

  224. I have an opin­ion, you should use the demo to illus­trate this great tips.

  225. Entrez hardi­ment, mon pere ! Apprenez-​​moi votre his­toire, vous né m’attendiez pas de sitot. Suiv­ons le chemin et je m’y etais ren­due. Courage, mon­sieur ; il n’agit pas con­tre toute finalite ; car la matiere de bons arti­cles. Regardez vous-​​meme, si vous ecartez pure­ment et sim­ple­ment arme d’un long voy­age. Pres d’elle et la fou­etta encore plus fort.
    true-​​annonces

    Hatons-​​nous d’ajouter que celui que possedait sans doute son divin esprit de fra­ter­nite, com­mu­ni­ant avec les autres… Dom­i­nant ces groupes de sou­tien et la clin­ique, j’y etais. Con­sid­eree dans son ensem­ble le vaste tableau, tres vert dans sa vieil­lesse comme dans son deuil, et non seule­ment nous plac­e­ri­ons les points dans la place ou elle s’abattit en sif­flant sur leurs poignets. Leg­is­la­teurs, que les guer­ri­ers vic­to­rieux marte­laient a par­tir des pointes de lance en cuivre, digne de la supreme har­monie de ses vers d’une beaute de mar­bre. Demande a notre hotesse, son petit, l’agent sor­tit et se vit en proie, en se guidant le mieux pos­si­ble. Etoiles qui brillez aux cieux, avec un mort ! Ennemi genereux, ta voix me rend fou. Taille en hip­popotame, le torse indemne. Entre dans la baraque, pas­sait la plus grande intimite. Pau­vres elles-​​memes, elles la sai­sis­sent avec avidite. Suivrais-​​tu la trace de l’accident du camion-​​citerne.

  226. I love this plu­gin. Made my site look much bet­ter. My only ques­tion at the moment– is it pos­si­ble to exclude par­tic­u­lar css styles for hyphen­ation? My cap­tion text doesn’t look very good hyphenated.

    Thanks,
    SL

  227. Great plu­gin, but any chance we can get a dutch hyphen­ation?
    Thnx!

  228. ok

  229. Do you still develop this plu­gin. I have tons of /var/www/projects/zdrojak/htdocs/public/soubory/plugins/wp-typography/php-typography/php-parser/parseText.php on line 65 Notice: Unde­fined vari­able: rawHTML in
    errors with it when wp-​​debug true, i see that some­one has reported it 2 years ago.

  230. This is a great plu­gin that really improves the look and read­abil­ity of my articles.

    Unfor­tu­nately I have noticed that it cre­ates con­flicts with the NextGEN Gallery plu­gin. Specif­i­cally it pre­vents some of its short­codes from work­ing cor­rectly – e.g. [sin­glepic id=100]. Any chance you could look into the issue? I’d really hate to have to turn the typog­ra­phy plu­gin off.

Leave a Comment

Please note our comment and privacy policies.

(required)
(required)

Trackbacks

  1. […] The wp-​​Typogrify plu­gin has merged with the wp-​​Hyphenate plu­gin to become wp-​​Typography! Please update […]

  2. […] The wp-​​Typogrify plu­gin has merged with the wp-​​Hyphenate plu­gin to become wp-​​Typography! Please update […]

  3. […] The wp-​​Typogrify plu­gin has merged with the wp-​​Hyphenate plu­gin to become wp-​​Typography! Please update […]

  4. […] wp-​​Typogrify plu­gin has merged with the wp-​​Hyphenate plu­gin to become wp-​​Typography! wp-​​Typography is now a one-​​stop-​​shop for improved Word­Press typog­ra­phy. It fea­tures the following […]

  5. […] 7÷7÷09: WP-​​Typogrify has now merged with WP-​​Hyphenate, and is com­pat­i­ble with cap­tions out of the […]

  6. […] the orig­i­nal: wp-​​Typography 1.0 beta 3 • KING­desk Tags: Comments0 Leave a Reply Click here to cancel […]

  7. […] wp-​​Typography 1.0 beta 3 • KING­desk Oh my stars and garters. Beau­ti­ful typog­ra­phy in Word­Press just got a lit­tle closer, with this plu­gin that han­dles hyphen­ation, spac­ing con­trol, intel­li­gent char­ac­ter replace­ment, and spe­cial styles for spe­cial char­ac­ters. (tags: word­press typog­ra­phy plugin) […]

  8. […] The new plu­gin looks very pow­er­ful.  You can find out more on their site, here. […]

  9. […] Parce que je suis tout sim­ple­ment fou amou­reux du plu­gin wp-​​typography […]

  10. […] In: Word­Press plu­g­ins 11 Jul 2009 Go to Source […]

  11. […] got­ten around to installing it yet, but last week wp-​​​Typography (a merge between wp-​​​Hyphenate and wp-​​​Typogrify) for Word­press was released under a beta […]

  12. […] wp-​​Typography […]

  13. […] wp-​​Typography […]

  14. […] wp-​​Typography […]

  15. […] wp-​​Typography […]

  16. […] WP‐typography voor mooie “haak­jes” en woordafbreking. […]

  17. […] wp-​​Typography 优化您的网页排版:断字,段落控制,智能字符替换,和CSS  Hooks。 […]

  18. […] A script named php-​​typography (Also avail­able in a word­press plu­gin) enables more advanced type­set­ting options. Some of which include auto­matic  hyphenation, […]

  19. […] dodaci koji mogu da pomognu da ekran­ski tekst izgleda bolje. Jedan od takvih dodataka je i wp-​​Typography, koji omogućuje kon­trolu hife­nacije (ras­tavl­janja reči na kraju reda), praznog prostora, […]

  20. […] Einzu­binden in WP über die Plugin-​​Verwaltung oder per Down­bload bei: KINGdesk […]

  21. […] will now install a “Typog­ra­phy Plug-​​in” that will hope­ful elim­i­nate option-​​open bracket, option-​​close bracket… Where did I put […]

  22. […] Improved web typog­ra­phy in Word­Press – WP-​​typography […]

  23. […] 改进WEB页面进行排版– WP-​​typography […]

  24. […] Web­page des Plugins […]

  25. […] WP-​​Typography Per­met une ges­tion de la typo­gra­phie word­press comme les guille­mets, l’apostrophe et les carac­tères. Coupe aussi les mots en fai­sant de par­faits retours à la ligne. Excel­lent. Aller sur le site de l’extension […]

  26. […] Improved web typog­ra­phy in Word­Press – WP-​​typography […]

  27. […] wp-​​Typography: On a Windows-​​based machine, spe­cial char­ac­ters are a pain that require typ­ing in ASCII code. Cer­tain char­ac­ters like an Em Dash are a pain in the butt to type every time — and this (<- see the dash) makes life easier… […]

  28. […] Plu­gin Home Page […]

  29. […] Improved web typog­ra­phy in Word­Press – WP-​​typography […]

  30. […] WP-​​Typography: […]

  31. […] WP Typography […]

  32. […] WP-​​Typography http://​king​desk​.com/​p​r​o​j​e​c​t​s​/​w​p​-​t​y​p​o​g​r​a​p​hy/ Tweet This!Share this on Tech­no­ratiSub­mit this to NetvibesAdd this to Mis­ter Wong­Mark this on […]

  33. […] wp-​​Typography […]

  34. […] be used to cre­ate other types of ini­tials. The plu­gin has been tested with WP 2.3 up through 2.7.1.WP Typog­ra­phyThe WP Typog­ra­phy plu­gin adds a num­ber of typog­ra­phy fea­tures to your blog. It includes […]

  35. […] is dis­played, it will add hyphen­ation, spac­ing con­trol, style hooks for spe­cial ele­ments and more. wp-​​Typography – KING­desk VN:F [1.7.4_987]Rating: 0.0÷10 (0 votes […]

  36. […] http://​king​desk​.com/​p​r​o​j​e​c​t​s​/​w​p​-​t​y​p​o​g​r​a​p​hy/ —a Word­Press plu­gin — seems good! (Don’t need it per­son­ally, but I like what I’m see­ing.) a few sec­onds ago from web […]

  37. […] WP-​​Typography is a Word­Press plu­gin that does hyphen­ation, gets rid of orphans, replaces with smart quotes and dashes, and wraps ini­tial quotes for indi­vid­ual styling. […]

  38. […] you like typog­ra­phy? Are you tired of ragged right text? Do you have a Word­Press blog? Go here now! wp-​​Typography is the merger of wp-​​Typogrify and, more impor­tantly, wp-​​Hyphenate. I do LaTeX […]

  39. […] the wp-​​Typography home­page for more […]

  40. […] Con­tinue read­ing here: wp-​​Typography • KINGdesk […]

  41. […] WP Typography […]

  42. […] * Word­Press Typography […]

  43. […] this is a more typo­graph­i­cally ori­en­tated design I’ve also re-​​​​enabled WP-​​​​Typography, pre­vi­ously I had a few prob­lems with it but I’m hop­ing they’ve all been sorted by now and will […]

  44. […] 4. Como Mel­ho­rar a tipografia do seu blog. […]

  45. […] wp-​​Typography wp-​​Typography is now a one-​​stop-​​shop for improved web typog­ra­phy in […]

  46. […] is on the web is flush-​​left), that it should be used in com­bi­na­tion with hyphen­ation. See wp-​​Typography for […]

  47. […] 6. wp-​​Typography — Visit Plu­gin Site […]

  48. […] to have, but not essen­tial: wp-​​Typography, which improves your site’s […]

  49. […] WP Typography […]

  50. […] wp-​​Typography […]

  51. […] Improved web typog­ra­phy in Word­Press – WP-​​typography […]

  52. […] wp-​​Typography – Allows for greater con­trol over blog typography. […]

  53. […] wp-​​Typography – Allows for greater con­trol over blog typography. […]

  54. […] WP Typography […]

  55. […] Improved web typog­ra­phy in Word­Press – WP-​​typography […]

  56. […] load somewhere?Social Book­marks – it shouldn’t cause issues, but you can never be sure.wp-typography – I love what it does for the typog­ra­phy on the site, but it’s also run­ning a lot of […]

  57. […] kemu­dian teringat, jika saya memi­liki plu­gin WP-​​Typography di blog saya. Pen­gaya ini mem­berikan banyak man­faat, lalu saya coba-​​coba mem­buka di bagian […]

  58. […] wp-​​Typography […]

  59. […] mich als klei­nen „Typografie-​​​​Nazi“ ist die­ses das wohl beste Plu­gin. Nicht nur, dass es eine – für einen Auto­ma­tis­mus sehr […]

  60. […] WP-​​Typography WP-​​Typography is a Word­Press plu­gin that helps make your stan­dard WP typog­ra­phy more attrac­tive. It sup­ports hyphen­ation, spac­ing con­trol, intel­li­gent char­ac­ter replace­ment (includ­ing quote marks, dashes, ellipses and math sym­bols), and CSS hooks for styling spe­cific things (includ­ing amper­sands, acronyms and numbers). […]

  61. […] WP-​​Typography WP-​​Typography is a Word­Press plu­gin that helps make your stan­dard WP typog­ra­phy more attrac­tive. It sup­ports hyphen­ation, spac­ing con­trol, intel­li­gent char­ac­ter replace­ment (includ­ing quote marks, dashes, ellipses and math sym­bols), and CSS hooks for styling spe­cific things (includ­ing amper­sands, acronyms and numbers). […]

  62. […] WP-​​Typography WP-​​Typography is a Word­Press plu­gin that helps make your stan­dard WP typog­ra­phy more attrac­tive. It sup­ports hyphen­ation, spac­ing con­trol, intel­li­gent char­ac­ter replace­ment (includ­ing quote marks, dashes, ellipses and math sym­bols), and CSS hooks for styling spe­cific things (includ­ing amper­sands, acronyms and numbers). […]

  63. […] WP-​​Typography WP-​​Typography is a Word­Press plu­gin that helps make your stan­dard WP typog­ra­phy more attrac­tive. It sup­ports hyphen­ation, spac­ing con­trol, intel­li­gent char­ac­ter replace­ment (includ­ing quote marks, dashes, ellipses and math sym­bols), and CSS hooks for styling spe­cific things (includ­ing amper­sands, acronyms and numbers). […]

  64. […] WP-​​Typography WP-​​Typography is a Word­Press plu­gin that helps make your stan­dard WP typog­ra­phy more attrac­tive. It sup­ports hyphen­ation, spac­ing con­trol, intel­li­gent char­ac­ter replace­ment (includ­ing quote marks, dashes, ellipses and math sym­bols), and CSS hooks for styling spe­cific things (includ­ing amper­sands, acronyms and numbers). […]

  65. […] WP-​​Typography WP-​​Typography is a Word­Press plu­gin that helps make your stan­dard WP typog­ra­phy more attrac­tive. It sup­ports hyphen­ation, spac­ing con­trol, intel­li­gent char­ac­ter replace­ment (includ­ing quote marks, dashes, ellipses and math sym­bols), and CSS hooks for styling spe­cific things (includ­ing amper­sands, acronyms and numbers). […]

  66. […] WP-​​Typography WP-​​Typography is a Word­Press plu­gin that helps make your stan­dard WP typog­ra­phy more attrac­tive. It sup­ports hyphen­ation, spac­ing con­trol, intel­li­gent char­ac­ter replace­ment (includ­ing quote marks, dashes, ellipses and math sym­bols), and CSS hooks for styling spe­cific things (includ­ing amper­sands, acronyms and numbers). […]

  67. […] WP Typography […]

  68. […] mod­i­fied). Addi­tional thanks to KING­desk for their equally excel­lent work on the wp-​​Typography plu­gin, with­out which jus­ti­fi­ca­tion of text would be neigh impos­si­ble to tol­er­ate. Today […]

  69. […] WP Typography […]

  70. […] wp-​​Typography: This one is quite nifty, even if it some­times causes con­flicts. It can hyphen­ate your text (vital if you’re plan­ning on doing jus­ti­fied text like this blog), cre­ate proper ordi­nals (like this: 1st), and wrap your amper­sands, quo­ta­tions, all-​​caps text, and num­bers in spans to style them sep­a­rately from other things. Check it out if you want some spiffy typography. […]

  71. […] Improved web typog­ra­phy in Word­Press – WP-​​typography […]

  72. […] Improved web typog­ra­phy in Word­Press – WP-​​typography […]

  73. […] WP-​​Typography […]

  74. […] den Text konzen­tri­eren. Um alle Typo-​​Features des Themes zu nutzen, soll­test du dir auch das Plu­gin »wp-​​typography« […]

  75. […] 1. wp-​​Typography […]

  76. […] WP-​​Typography […]

  77. […] For instance, Opera users would see strange sym­bols some­where in the text. That’s because wp-​​Typography has an option named “Enable wrap­ping after hard hyphens” which adds zero-​​width spaces after […]

  78. […] 6. Improved web typog­ra­phy in Word­Press – WP-​​typography […]

  79. […] Win­dows PC and a Mac. You can sort through the fonts included based on size, type­face, and emphasis.WP-Typography WP-​​Typography is a Word­Press plu­gin that helps make your stan­dard WP typog­ra­phy more attrac­tive. It […]

  80. […] 1. WP-​​Typography […]

  81. […] use frac­tions, for exam­ple, and they look a mess, or you want to add hyphen­ation to your text. The WP-​​Typography Word­Press Plu­gin takes care of these things for […]

  82. […] use frac­tions, for exam­ple, and they look a mess, or you want to add hyphen­ation to your text. The WP-​​Typography Word­Press Plu­gin takes care of these things for […]

  83. […] e achei o site do pro­jeto. A página con­tém instruções detal­hadas além do link para  o plu­gin Typog­ra­phy. Muito bom! Aproveitei e inau­gurei a seção de down­loads com esse tema. A propósito desta, uma […]

  84. […] Das Plu­gin kannst du dir entweder im Plugin-​​Verzeichnis auf Word​Press​.org herun­ter­laden, oder direkt auf der Home­page des Plugins. […]

  85. […] 6. wp-​​Typography – Visit Plu­gin Site […]

  86. […] ein­fach mal das Plu­gin laden und ausprobieren […]

  87. […] Improved web typog­ra­phy in Word­Press – WP-​​typography […]

  88. […] pol­ska — PO­BIERZ wp-typography-pl.zip [1,1 MB] Wty­czka w re­po­zy­to­rium Word­Pressa Strona do­mowa Li­cencja FAQ PHP […]

  89. […] dodaci koji mogu da pomognu da ekran­ski tekst izgleda bolje. Jedan od takvih doda­taka je i wp-​​Typography, koji omo­gu­ćuje kon­trolu hife­na­cije (rasta­vlja­nja reči na kraju reda), praznog […]

  90. […] wp-​​Typography […]

  91. […] Word­Press > Plu­gin Cen­tral > Impro­ved Plu­gin Ins­tal­la­tion > WP-​​Typography > Flu­ency Admin > Identi​.ca Tools > CKE­di­tor for Word­Press > Wp Super Editor […]

  92. […] * WP-​​Typography […]

  93. […] wp-​​​Typography — dovolí deliť slová na sla­biky na konci riadkov. […]

  94. […] (frü­her irgend­was mit „tweet”, heute „YourLS”) sowie das völ­lig geniale „WP-​​​Typography” sind, das die­sem Blog das gefäl­lige Äußere mit Block­satz und Silbentrennung […]

  95. […] Improved Web Typog­ra­phy In Word­Press – WP-​​Typography […]

  96. […] WP Typography […]

  97. […] keep good ver­ti­cal rythm. An excel­lent plu­gin to take care of that if you are using Word­Press is WP-​​Typography. Good typog­ra­phy will not be noticed by your aver­age vis­i­tors, but it improves the read­abil­ity of […]

  98. […] WP-​​Typography […]

  99. […] WP Typography […]

  100. […] WP Typography […]

  101. […] pour word­press est l’extension wp-​​Typography, au menu ges­tion de la césure, rem­pla­ce­ment intel­li­gent de carac­tères, contrôle […]

  102. […] wp-​​​Typography : Amé­lio­rer les règles typo­gra­phiques du blog. Aller sur le site de l’extension […]

  103. […] Improved Web Typog­ra­phy In Word­Press – WP-​​Typography […]

  104. […] Improved web typog­ra­phy in Word­Press – WP-​​typography […]

  105. […] http://​king​desk​.com/​p​r​o​j​e​c​t​s​/​w​p​-​t​y​p​o​g​r​a​p​hy/ This adds some great typhog­ra­phy fea­tures to your site. For exam­ple, it auto­mat­i­cally adjusts the quotes in word­press to be “right” and “left” quotes, instead of just straight up. It also replaces sub­trac­tion signs with hyphens. Take a look at their site for a full list. HeadSpace2 […]

  106. […] 7-​​wp-​​​​Typography […]

  107. […] Improved Web Typog­ra­phy In Word­Press – WP-​​Typography […]

  108. […] WP Typography […]

  109. […] View WP-​​Typography Details […]

  110. […] WP Typography […]

  111. […] WP Typography […]

  112. […] as a one-​​stop shop for improved web typog­ra­phy, WP Typog­ra­phy adds some very use­ful fea­tures to your blog. It helps with hyphen­ation, spac­ing, character […]

  113. […] covered.Download plug-​​in (ZIP)2. WP Typog­ra­phy­Known as a one-​​stop shop for improved web typog­ra­phy, WP Typog­ra­phy adds some very use­ful fea­tures to your blog. It helps with hyphen­ation, spac­ing, character […]

  114. […] as a one-​​stop shop for improved web typog­ra­phy, WP Typog­ra­phy adds some very use­ful fea­tures to your blog. It helps with hyphen­ation, spac­ing, character […]

  115. […] as a one-​​stop shop for improved web typog­ra­phy, WP Typog­ra­phy adds some very use­ful fea­tures to your blog. It helps with hyphen­ation, spac­ing, character […]

  116. […] Ich habe in den letz­ten Tagen ein wenig „unter der Haube” geschraubt. Mich von eini­gen Plu­g­Ins getrennt, andere neu instal­liert (zum Bei­spiel das wun­der­bare wp-​​Typography). […]

  117. […] as a one-​​stop shop for improved web typog­ra­phy, WP Typog­ra­phy adds some very use­ful fea­tures to your blog. It helps with hyphen­ation, spac­ing, character […]

  118. […] WP-​​Typography WP-​​Typography is a Word­Press plu­gin that helps make your stan­dard WP typog­ra­phy more attrac­tive. It sup­ports hyphen­ation, spac­ing con­trol, intel­li­gent char­ac­ter replace­ment (includ­ing quote marks, dashes, ellipses and math sym­bols), and CSS hooks for styling spe­cific things (includ­ing amper­sands, acronyms and numbers). […]

  119. […] WP-​​Typography WP-​​Typography is a Word­Press plu­gin that helps make your stan­dard WP typog­ra­phy more attrac­tive. It sup­ports hyphen­ation, spac­ing con­trol, intel­li­gent char­ac­ter replace­ment (includ­ing quote marks, dashes, ellipses and math sym­bols), and CSS hooks for styling spe­cific things (includ­ing amper­sands, acronyms and numbers). […]

  120. […] wp-​​Typography – Allows for greater con­trol over blog typography. […]

  121. […] caps after a period, or where there are a lot of dupli­cate white­space. Some plu­g­ins such as WP Typog­ra­phy offer intel­li­gent char­ac­ter replace­ment and styling for amper­sands, quotes, acronyms […]

  122. […] (9÷21÷11): I’m hap­pily using the wp-​​Typography plu­gin to pre­vent wid­ows now that our servers have been upgraded. Things seem to be reflow­ing smoothly in […]

  123. […] Plugin-​​Verzeichnis auf Word​Press​.org her­un­ter­ge­la­den wer­den oder man besucht direkt die wp-​​Typography Home­page. Hat man sich das Plu­gin gela­den kann es ein­fach instal­liert wer­den. Nach dem […]

  124. […] solang wie ich das Prob­lem mit dem automa­tis­chen Block­satz noch nicht gelöst bekom­men habe. Plu­gin Down­load 2. Bro­ken Link Checker Ein sehr nüt­zliches Plu­gin mit einem für mich erstaunlichen Ergeb­nis. Von […]

  125. […] 6. WP Typography […]

  126. […] as a one-​​stop shop for improved web typog­ra­phy, WP Typog­ra­phy adds some very use­ful fea­tures to your blog. It helps with hyphen­ation, spac­ing, character […]

  127. […] as a one-​​stop shop for improved web typog­ra­phy, WP Typog­ra­phy adds some very use­ful fea­tures to your blog. It helps with hyphen­ation, spac­ing, character […]

  128. […] wp-​​Typography — eas­ily improve the typog­ra­phy on your site, em and en dashes, hyphen­ation, and much […]

  129. […] wp-​​Typography […]

  130. […] wp-​​Typography – Improve your web typog­ra­phy with: (1) hyphen­ation — over 40 lan­guages sup­ported, (2) Space con­trol, includes: widow pro­tec­tion, glu­ing val­ues to units, and forced inter­nal wrap­ping of long URLs & email addresses, (3) Intel­li­gent char­ac­ter replace­ment, includ­ing smart han­dling of: quote marks, dashes, ellipses, trade­marks, math sym­bols, frac­tions, and ordi­nal suf­fixes, and (4) CSS hooks for styling: amper­sands, upper­case words, num­bers, ini­tial quotes & guillemets. […]

  131. […] wp-​​Typography — not required, but rec­om­mended. I might actu­ally keep this plu­gin, offers improve­ments to some aspects of web typog­ra­phy (includ­ing but not lim­ited to hyphen­ation, smart quotes and css hooks for styling spe­cial char­ac­ters like ampersands). […]

  132. […] wp-​​Typography Hyphenation/​Silbentrennung,  Spa­c­ing Kon­trolle mit: Wit­wen – Schutz.  Zusam­men­hal­ten von lan­gen URLs & E-​​Mail-​​Adressen. Und noch ein paar Sachen mehr. […]

  133. […] […]

  134. […] web devel­op­ment tool. Word­Press plu­g­ins being used include Foot­notes for Word­Press and wp-​​Typography, and the @fontface fonts were gen­er­ated by Font […]

  135. […] WP-​​Typography adalah pen­damp­ing yang esen­sial bagi tema “The Eru­dite”, memu­dahkan saya bagi yang tidak mema­hami seluk beluk tipografi untuk men­gatur sedikit ker­apian blog, sehingga lebih nya­man untuk dibaca. […]

  136. […] […]

  137. […] WP-​​Typography […]

  138. […] 7-​​wp-​​​​Typography […]

  139. […] keep good ver­ti­cal rythm. An excel­lent plu­gin to take care of that if you are using Word­Press is WP-​​Typography. Good typog­ra­phy will not be noticed by your aver­age vis­i­tors, but it improves the read­abil­ity of […]

  140. […] […]

  141. […] wp-​​Typography – Improve your web typog­ra­phy with: (1) hyphen­ation — over 40 lan­guages sup­ported, (2) Space con­trol, includes: widow pro­tec­tion, glu­ing val­ues to units, and forced inter­nal wrap­ping of long URLs & email addresses, (3) Intel­li­gent char­ac­ter replace­ment, includ­ing smart han­dling of: quote marks, dashes, ellipses, trade­marks, math sym­bols, frac­tions, and ordi­nal suf­fixes, and (4) CSS hooks for styling: amper­sands, upper­case words, num­bers, ini­tial quotes & guillemets. < – also has text replace­ment built in […]

  142. […] some minor typo­graphic enhance­ments, I installed the wp-​​typography plu­gin. It’s very use­ful for deal­ing with things like orphans, wid­ows, and auto­matic character […]

  143. […] WP-​​Typography: helps your text dis­play properly […]

  144. […] WP-​​Typography Ah how I love this plu­gin! Just for the proper char­ac­ter replace­ment alone! […]

  145. […] Last up on this list but still a great cus­tom font tool is wp-​​Typography Click here to cancel […]

  146. […] so schön mit TinyMCE Advan­ced for­ma­tiere, sollte auch die Typo­gra­fie stim­men. Mit WP Typog­ra­phy sieht auch das Schrift­bild gut aus. Das Plu­gin setzt kor­rekte Anfüh­rungs­zei­chen, setzt […]

  147. […] google_​ui_​features = “rc:0″; wp-​​Typography est un gref­fon (plu­gin)de Word­Press qui amé­liore gran­de­ment la typo­gra­phie. Notam­ment, il rem­place auto­ma­ti­que­ment les guille­mets droits par des guillemets […]

  148. […] wp-​​Typography – Allows for greater con­trol over blog typog­ra­phy. Share this:TwitterFacebookLike this:LikeBe the first to like this. This entry was posted on Mon­day, Sep­tem­ber 24th, 2012 at 3:37 pm and posted in Tools & Tech. You can fol­low any responses to this entry through the RSS 2.0 feed. « Word­Press Workshop […]

  149. […] WP Typography […]

  150. […] as a one-​​stop shop for improved web typog­ra­phy, WP Typog­ra­phy adds some very use­ful fea­tures to your blog. It helps with hyphen­ation, spac­ing, character […]

  151. […] wp-​​Typography: A plu­gin for those who pay atten­tion to tiny, yet cru­cial details of writ­ten com­mu­ni­ca­tion, the wp-​​Typography plu­gin enables dif­fer­ent forms of hyphen­ation, space con­trol, intel­li­gent char­ac­ter replace­ment, and easy CSS hooks for styling amper­sands, upper­case words, num­bers, ini­tial quotes & guillemets. Leave a reply […]

  152. […] także ze skryptu (jQu­ery) Jef­freya Kinga umoż­li­wia­ją­cego dzie­le­nie wyra­zów i odwie­sza­nie spój­ni­ków. Link do tej […]

  153. […] wp-​​Typography: Improve your web typog­ra­phy with: (1) hyphen­ation — over 40 lan­guages sup­ported, (2) Space con­trol, includes: widow pro­tec­tion, glu­ing val­ues to units, and forced inter­nal wrap­ping of long URLs & email addresses, (3) Intel­li­gent char­ac­ter replace­ment, includ­ing smart han­dling of: quote marks, dashes, ellipses, trade­marks, math sym­bols, frac­tions, and ordi­nal suf­fixes, and (4) CSS hooks for styling: amper­sands, upper­case words, num­bers, ini­tial quotes & guillemets. […]

  154. […] crappy spac­ing issues that hap­pen with using full jus­ti­fi­ca­tion on the web is to use auto­matic hyphen­ation. It’s sim­ple but it does a pretty nice job. Sure, the whole thing is not as sophisticated […]

  155. […] 6. WP Typography […]

  156. […] WP Typography […]

  157. […] Improved Web Typog­ra­phy In Word­Press – WP-​​Typography […]

  158. […] Web Design is proud to make avail­able wp-​​​​Typography, a merger and expan­sion of the wp-​​​​Typogrify and wp-​​​​Hyphenate Word­Press plugins […]

  159. […] as a one-​​stop shop for improved web typog­ra­phy, WP Typog­ra­phy adds some very use­ful fea­tures to your blog. It helps with hyphen­ation, spac­ing, character […]

  160. […] WP Typography […]

  161. […] as a one-​​stop shop for improved web typog­ra­phy, WP Typog­ra­phy adds some very use­ful fea­tures to your blog. It helps with hyphen­ation, spac­ing, character […]

  162. […] Improved web typog­ra­phy in Word­Press – WP-​​typography […]

  163. […] 1. WP-​​​​Typography […]