Opened 5 months ago

Last modified 3 months ago

#22823 new defect (bug)

Texturize should handle apostrophes before primes

Reported by: nacin Owned by:
Priority: normal Milestone: Future Release
Component: Formatting Version: 3.4.2
Severity: minor Keywords: has-patch
Cc: brady@…

Description

Not sure if anyone else noticed this, but my recent post on make/core exhibited an odd bug in wptexturize() —

The new target for WordPress 3.5′s release is Monday

Note how that's a prime — ′ — rather than an apostrophe, ’.

Switching the rules seems to work without breaking any unit tests.

Attachments (1)

22823.diff (979 bytes) - added by nacin 5 months ago.

Download all attachments as: .zip

Change History (3)

nacin5 months ago

Initial unit test in [UT1168].

  • Cc brady@… added

This appears to affect more than just this case. Apostrophe characters following numbers that should be converted to single right quotes are instead converted to prime:

'Uno es 1' => ‘Uno es 1′

Even a double quote following a number is converted to a double prime.

"Dos es 2" => “Dos es 2″

The trailing characters in both of those examples aren't quotes (′ and ″). Switching the rules for all those characters would seem to make the prime matching obsolete.

This caused issues for me because the web font I'm using doesn't have support for the prime character and it creates nasty rendering issues. Taking a quick look through the best selling fonts on Fontspring and popular fonts on Font Squirrel, the majority don't appear to have support for prime or double prime built in, either.

Note: See TracTickets for help on using tickets.