#8775 closed defect (bug) (fixed)
Numbers in quotation marks get wrong smart quotes
Reported by: | filosofo | Owned by: | wonderboymusic |
---|---|---|---|
Milestone: | 4.0 | Priority: | normal |
Severity: | normal | Version: | 2.8 |
Component: | Formatting | Keywords: | has-patch needs-testing wptexturize |
Focuses: | Cc: |
Description
Have a number in quotation marks, such as "12345"
or '12345'
and wptexturize
converts the right quotation mark to double-prime and prime marks, respectively.
Patch fixes.
Attachments (7)
Change History (49)
#5
@
16 years ago
- Keywords tested commit added; needs-testing removed
Updated patch. Tested with numbers and single/double quotes. Seems to work. doesn't appear to break anything else, so marking as tested. Comitting would seem the fastest way of geting more test exposure.
#9
@
16 years ago
- Keywords needs-testing added; tested wptexturize formatting curly-quotes numbers commit removed
#10
in reply to:
↑ 7
@
16 years ago
Replying to Denis-de-Bernardy:
are there any unit tests on wptexturize?
Seems like this needs more testing with non-latin languages.
#11
@
16 years ago
- Component changed from Formatting to i18n
- Owner set to nbachiyski
k... moving this over to i18n then. I wouldn't know what to test on this front. :-)
D.
#13
@
16 years ago
- Keywords needs-unit-tests added
- Milestone changed from 2.8 to Future Release
punting pending unit tests... even though, like the one wpautop one I just punted, I think this should get committed outright.
#14
@
16 years ago
- Component changed from i18n to Formatting
- Milestone changed from Future Release to 2.9
- Owner nbachiyski deleted
#15
@
15 years ago
- Milestone changed from 2.9 to Future Release
Punting b/c no tests done in 6 months and we're in beta.
#16
follow-up:
↓ 17
@
15 years ago
- Milestone Future Release deleted
- Resolution set to wontfix
- Status changed from new to closed
Let's be realistic.
#17
in reply to:
↑ 16
;
follow-up:
↓ 18
@
14 years ago
- Milestone set to Future Release
- Resolution wontfix deleted
- Status changed from closed to reopened
It's still a valid issue. Just because progress isn't being made isn't reason enough to close the ticket.
#18
in reply to:
↑ 17
@
14 years ago
Replying to Viper007Bond:
It's still a valid issue. Just because progress isn't being made isn't reason enough to close the ticket.
Any chances you've got a patch? :-)
#22
@
12 years ago
- Cc mdhansen@… added
aliso's patch works for me. I updated the patch path and included some screenshots of the problem.
#25
@
12 years ago
Any idea when this fix can make it into core? The unit tests should be the same as in http://unit-tests.trac.wordpress.org/changeset/757, right?
#27
@
11 years ago
What is this intended output for these examples?
I need 4 x 20'=80' of trim.
The best year "was that time in 2012" when everyone partied, he said.
#28
@
11 years ago
I recommend narrowing the focus of this patch so that it will not affect text other than numbers surrounded by quotes preceded by spaces. Examples:
"2004"
'27'
The answer is "42".
Numbers at the beginning or ending of quoted phrases have ambiguous meaning if we want to keep using the primes logic.
#31
@
11 years ago
- Keywords needs-unit-tests removed
New patch against trunk should be much closer to what we need. In miqro-8775.patch:
- Quoted numbers preceded by spaces get curly quotes.
- So, "123" works, but"123"blah does not work.
- Trailing space not required. Will this break things like '99's?
- Decimals and commas are allowed after the first digit.
- nbsp works as whitespace.
- Regexp will search for quotes first for optimum performance.
- Unit tests updated to match.
#32
@
11 years ago
This will also break the assertion for 'Class of '99', but that is highly ambiguous.
#33
@
11 years ago
- Owner set to wonderboymusic
- Resolution set to fixed
- Status changed from reopened to closed
In 28721:
#34
@
11 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
Reopen to discuss and update the broken unit test for
Class of '99's
See also #26850.
The main question is which patterns should have priority when an apostrophe preceeds exactly two digits.
#38
@
10 years ago
Was there a regression for this (possibly related to #26850)? This is still an issue on trunk and wordpress.com, as seen here:
http://variety.com/2014/film/news/how-to-train-your-dragon-2-tops-foreign-box-office-after-china-debut-1201284893/
http://variety.com/2014/digital/news/expendables-3-illegally-downloaded-5-million-times-but-still-isnt-top-hit-for-pirates-1201285179/
http://coreygilmore.wordpress.com/2014/08/18/expendables-3-illegally-downloaded-5-million-times-but-still-isnt-top-hit-for-pirates/
#39
@
10 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
Reopening for investigation.
#40
@
10 years ago
coreygilmore: You are seeing the prime and double-prime logic there. It hasn't changed.
#41
@
10 years ago
- Resolution set to fixed
- Status changed from reopened to closed
Apparently this was for numbers-only within quotes.
#42
@
10 years ago
Same situation as https://core.trac.wordpress.org/ticket/4539#comment:57
Several different bugs were brought up in comments but never really had a whole ticket just for "Primes vs. Quotes Ending With Digits". That is its own can of worms.
Make a new ticket if desired.
Probably a dupe see also #7754 #4539 #3810 #4116 #1258
There neeeds to be a big old wp_texturize fix task or something.