#1459 closed defect (bug) (worksforme)
texturize: characters that are substituted with entities adjacent to parentheses render malformed xhtml
Reported by: | tjaard | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 1.5.1 |
Component: | General | Keywords: | xhtml wellformedness texturize |
Focuses: | Cc: |
Description
I made a post on my blog today, which contained the string ("word"). It after being texturized I got an xml parsing error (I serve my blog as xhtml+xml) because the result was malformed. The character entities for the quotes weren't properly delimited by a semicolon. Placing the (numerical) entities instead of the " character made no difference.
Change History (3)
#1
@
19 years ago
- Milestone set to 1.5.1
- Summary changed from texturize: certain parethesis + quotes combinations give malformed xhtml to texturize: characters that are substituted with entities adjacent to parentheses render malformed xhtml
#2
@
18 years ago
- Milestone 1.5.1 deleted
- Resolution set to worksforme
- Severity changed from critical to normal
- Status changed from new to closed
No update in a year. WordPress' editor has undergone many revisions, no longer does "texturized". Marking works for me.
This ticket was mentioned in Slack in #forums by yui. View the logs.
2 years ago
Note: See
TracTickets for help on using
tickets.
Just found out that a sequence like (oh yeah...) gives problems too. Seems that it is a general problem that a character entity (or something that is replaced with one) adjacent to a parenthesis results in malformed xhtml.