Opened 12 years ago
Closed 12 years ago
#27588 closed defect (bug) (fixed)
Shortcodes and nbsp
| Reported by: | miqrogroove | Owned by: | DrewAPicture |
|---|---|---|---|
| Priority: | normal | Milestone: | 4.0 |
| Component: | Formatting | Version: | 3.8 |
| Severity: | normal | Keywords: | has-patch 4.0-early |
| Cc: | Focuses: | docs |
Attachments (3)
Change History (15)
#6
follow-up:
↓ 7
@
12 years ago
- Milestone Awaiting Review → 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
@
12 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
@
12 years ago
Replying to SergeyBiryukov:
What would be a use case for the
wp_spaces_regexpfilter?
Primarily for anyone not using UTF-8. NBSP has alternative encodings.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
In 28708: