-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
parsed-literal blocks shouldn't be processed by SmartyPants #647
Comments
From tpowers on 2011-02-24 23:38:08+00:00 Ooops. Above suggestion doesn't work since it also blocks smartypants processing on other nodes that happen to do substitutions. Instead you might have to add an self.in_literalblock flag to keep track of when you are processing a literal block? |
From tpowers on 2011-02-25 00:08:44+00:00 Here's a fix that seems to work: in writers\html.py:
}}} |
From tpowers on 2011-03-02 16:38:17+00:00 Hmmm. Looks like that last "fix" also doesn't work correctly. It turns off SmartyPants processing for more than just literal_blocks for some reason. Some number of paragraphs after the parsed-literal are also not processed by SmartyPants? |
From Daniele Varrazzo on 2011-05-07 13:14:18+00:00 Bugged by the bug too. The attached patch (against 1.0.7) works for me. |
From Georg Brandl on 2011-05-15 11:52:58+00:00 Closes #647: Do not apply SmartyPants in parsed-literal blocks. → <> |
From Georg Brandl on 2011-09-22 10:14:48+00:00 Removing milestone: 1.0 (automated comment) |
From Georg Brandl on 2014-10-18 07:32:19+00:00 Removing version: 1.0.7 (automated comment) |
In writers\html.py the following is done:
therefore I'm pretty sure that:
should be changed to:
given that:
or something similar to prevent SmartyPants processing from being done on parsed-literal blocks.
Otherwise "normal" quote characters get converted to smart quotes which, for example, doesn't work when documenting command lines that need to be copied & pasted.
The text was updated successfully, but these errors were encountered: