[wp-trac] [WordPress Trac] #17571: bad double quote replacement in wp_texturize

[WordPress Trac]

#17571: bad double quote replacement  in wp_texturize
------------------------------------------------+--------------------------
 Reporter:  csanquer                            |       Owner:
     Type:  defect (bug)                        |      Status:  new
 Priority:  normal                              |   Milestone:  Future
Component:  Formatting                          |  Release
 Severity:  minor                               |     Version:
 Keywords:  has-patch dev-feedback wptexturize  |  Resolution:
------------------------------------------------+--------------------------
Changes (by nacin):

 * keywords:  has-patch dev-feedback => has-patch dev-feedback wptexturize
 * milestone:  3.4 => Future Release


Comment:

 While it is backed up by unit tests, it is too late to make a change for
 an edge-case issue with texturize.

 I didn't understand the nature of the bug report here originally. The
 issue appears to be that `\"` gets curled in the incorrect manner. When
 are backslashes ever going to be used? If it's ending up in the database,
 we should be looking at storage and retrieval, not texturize. Should the
 quote be curled in this case at all? Should the backslash be quietly
 stripped, or should it be kept? Are there any performance implications of
 the negative lookahead here?

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/17571#comment:13>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software