Opened 4 years ago
Last modified 7 weeks ago
#8775 reopened defect (bug)
Numbers in quotation marks get wrong smart quotes
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | Formatting | Version: | 2.8 |
| Severity: | normal | Keywords: | has-patch needs-testing needs-unit-tests |
| Cc: | mdhansen@…, damst |
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 (6)
Change History (31)
comment:4
Denis-de-Bernardy
— 4 years ago
- Keywords needs-testing added
comment:5
mrmist
— 4 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.
comment:6
Denis-de-Bernardy
— 4 years ago
+1
comment:7
follow-up:
↓ 10
Denis-de-Bernardy
— 4 years ago
are there any unit tests on wptexturize?
comment:8
Denis-de-Bernardy
— 4 years ago
or at least, known, funky test cases to watch for?
comment:9
azaozz
— 4 years ago
- Keywords needs-testing added; tested wptexturize formatting curly-quotes numbers commit removed
comment:10
in reply to:
↑ 7
azaozz
— 4 years ago
Replying to Denis-de-Bernardy:
are there any unit tests on wptexturize?
Seems like this needs more testing with non-latin languages.
comment:11
Denis-de-Bernardy
— 4 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.
comment:12
azaozz
— 4 years ago
Also see #3810.
comment:13
Denis-de-Bernardy
— 4 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.
comment:14
Denis-de-Bernardy
— 4 years ago
- Component changed from i18n to Formatting
- Milestone changed from Future Release to 2.9
- Owner nbachiyski deleted
comment:15
janeforshort
— 4 years ago
- Milestone changed from 2.9 to Future Release
Punting b/c no tests done in 6 months and we're in beta.
comment:16
follow-up:
↓ 17
filosofo
— 3 years ago
- Milestone Future Release deleted
- Resolution set to wontfix
- Status changed from new to closed
Let's be realistic.
comment:17
in reply to:
↑ 16
;
follow-up:
↓ 18
Viper007Bond
— 2 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.
comment:18
in reply to:
↑ 17
Denis-de-Bernardy
— 2 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? :-)
comment:19
filosofo
— 2 years ago
We have a patch. It's the prerequisite wptexturize unit tests that are missing.
comment:21
aliso
— 11 months ago
comment:22
MikeHansenMe
— 8 months ago
- Cc mdhansen@… added
aliso's patch works for me. I updated the patch path and included some screenshots of the problem.
comment:23
damst
— 6 months ago
- Cc damst added
comment:24
SergeyBiryukov
— 6 months ago
Related: #22971
comment:25
aliso
— 7 weeks 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?
Probably a dupe see also #7754 #4539 #3810 #4116 #1258
There neeeds to be a big old wp_texturize fix task or something.