![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Changes between Version 3 and Version 4 of Ticket #43810, comment 9
- Timestamp:
- 06/23/2026 01:14:36 PM (2 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #43810, comment 9
v3 v4 8 8 - `I<strong>'ve been</strong>` → `I<strong>‘ve been</strong>` (wrong) 9 9 10 wptexturizeloses the preceding `I` (it's in a separate token) and opens a quote. The realistic case is bolding a contraction. It can be fixed the same narrow way as #18549 — but it needs a check so a genuine opening quote like <em>'Hello'</em> is ignored. (Only treat the ' as an apostrophe when the text before the tag ends in a letter or number.)10 `wptexturize` loses the preceding `I` (it's in a separate token) and opens a quote. The realistic case is bolding a contraction. It can be fixed the same narrow way as #18549 — but it needs a check so a genuine opening quote like <em>'Hello'</em> is ignored. (Only treat the ' as an apostrophe when the text before the tag ends in a letter or number.) 11 11 12 On the `I'v'e' 'b'e'en'` example specifically: comparing plain vs bolded, the *only* apostrophe that changes is the first one — `I’v’e’…` (plain) vs `I‘v’e’…` (bold) — which is exactly the case above. Every other apostrophe is identical with and without the bold, so the rest isn't a tag bug. (The `'` that opens a quote after a space, ` 'b`, does that in plain text too — that's wptexturize's normal handling of an apostrophe after whitespace.)12 **On the `I'v'e' 'b'e'en'` example specifically:** comparing plain vs bold text, the *only* apostrophe that changes is the first one — `I’v’e’…` (plain) vs `I‘v’e’…` (bold) — which is exactly the case above. Every other apostrophe is identical with and without the bold, so the rest isn't a tag bug. (The `'` that opens a quote after a space, ` 'b`, does that in plain text too — that's `wptexturize`'s normal handling of an apostrophe after whitespace.)
