Opened 11 years ago
Closed 11 years ago
#27588 closed defect (bug) (fixed)
Shortcodes and nbsp
Reported by: | miqrogroove | Owned by: | DrewAPicture |
---|---|---|---|
Milestone: | 4.0 | Priority: | normal |
Severity: | normal | Version: | 3.8 |
Component: | Formatting | Keywords: | has-patch 4.0-early |
Focuses: | docs | Cc: |
Attachments (3)
Change History (15)
#6
follow-up:
↓ 7
@
11 years ago
- Milestone changed from Awaiting Review to 4.0
Seems like the use case would be to change the regex, unless I'm missing something, currently it includes "spaces include new lines, tabs, nbsp entities, and the UTF-8 nbsp".
Happy to write the hook docs if ya'll come to a consensus on whether to keep the filter.
#7
in reply to:
↑ 6
@
11 years ago
Replying to DrewAPicture:
Seems like the use case would be to change the regex, unless I'm missing something, currently it includes "spaces include new lines, tabs, nbsp entities, and the UTF-8 nbsp".
Yeah, I mean, is there a need for this regex to be filterable?
#8
in reply to:
↑ 4
@
11 years ago
Replying to SergeyBiryukov:
What would be a use case for the
wp_spaces_regexp
filter?
Primarily for anyone not using UTF-8. NBSP has alternative encodings.
Note: See
TracTickets for help on using
tickets.
In 28708: