#16957 closed defect (bug) (duplicate)
wptexturize - problem with numbers and non-breaking spaces
Reported by: | pavelevap | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.1 |
Component: | Formatting | Keywords: | needs-patch wptexturize needs-unit-tests |
Focuses: | Cc: |
Description
1) Insert following code into HTML editor and publish.
New <strong>Year "2011" will be</strong> fantastic.
Then look at website:
<p>New <strong>Year ”2011″ will be</strong> fantastic.</p>
You can see wrong html quotes.
2) I also worked with TinyMCE editor (only writing simple text, paragraphs, strong, moving some parts of text by CTRL+C and CTRL+V). But after publishing, there were hidden non-breaking spaces in text. There were on different places, for example before "(" and after characters ".", "í", "é", etc. But they were random. I am not sure how it can be caused? Non-breaking strings were not visible and also not transformed into HTML entity on website. I noticed them only in HEX editor, when examining HTML source code (C2 A0).
Of course, when these non-breaking spaces were before (or after) quotes, then quotes were not recognized regurarly by wpuntexturize, example:
Nemám žádné "úžasné" schopnosti.
Is transformed by wpuntexturize into:
<p>Nemám žádné ”úžasné” schopnosti</p>.
You can see wrong open quote:
instead of “ there is ”
But only when hidden non-breaking space (C2 A0) is between žádné a "úžasné".
Attachments (1)
Change History (13)
#5
@
11 years ago
Likely from this plugin - http://wordpress.org/plugins/wpuntexturize/
#7
@
11 years ago
- Summary changed from wpuntexturize - problem with numbers and non-breaking spaces to wptexturize - problem with numbers and non-breaking spaces
#8
@
11 years ago
I have a patch for your second issue at #22692.
If this ticket is duplicating other tickets now, I suggest we close it.
#10
@
11 years ago
- Keywords needs-unit-tests added
- Milestone changed from Awaiting Review to Future Release
Part 1 of this ticket is the same bug referenced in #8775. I just submitted a patch for it.