Closed (outdated)
Project:
Typogrify
Version:
5.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
3 Oct 2007 at 02:11 UTC
Updated:
5 May 2020 at 21:18 UTC
Jump to comment: Most recent
Comments
Comment #1
jiangxijay commentedFollow-up. The only refinements that aren't appearing are those generated by SmartyPants; the others (in tags) are fine.
Are there known conflicts with themes or other modules?
Comment #2
jiangxijay commentedSmartyPants/Typogrify convert quotes into curly quotes, but not " into curly quotes.
Can that be changed:? In other words, can SmartyPants (php-typogrify.php or smartypnts.php) be trained to look for the entity?
Comment #3
jiangxijay commentedClarification:
"isn't being translated into curly quotes.Comment #4
jiangxijay commentedAccording to the original developer, support for converting
"entities is in SmartyPants.http://daringfireball.net/projects/smartypants/
Is this not implemented in Typogrify?
Comment #5
jiangxijay commentedIn smartypants.php, a configuration line needs to be edited to include the translation of
"into curly quotes:From this ...
$smartypants_attr = "1"; # Change this to configure.... to this ...
$smartypants_attr = "qDew"; # Change this to configure.However, php-typogrify.php appears to ignore this attribute.
Comment #6
BrightLoudNoise@drupal.org commentedLook for line 82 in smartypants.php, which should look like
$convert_quot = 0; # should we translate " entities into normal quotes?change it to
$convert_quot = q; # should we translate " entities into normal quotes?that took care of it for me.
Comment #7
BrightLoudNoise@drupal.org commentedTo further clarify, you don't need to touch the
$smartypants_attr = "1"; # Change this to configure.line.Comment #8
jiangxijay commentedBingo. Thank you!
Comment #9
BrightLoudNoise@drupal.org commentedComment #10
Tim Gambell commentedI'll add some admin UI for this option. Thanks for tracking it down!
Comment #11
Tim Gambell commentedComment #12
miklComment #13
wim leersIMHO we should close this, because Drupal 5 has not been supported for years.
Comment #14
migmedia commentedYes I second closing this issue.