Closed hassanakbar4 closed 3 years ago
@rjsparks@nostrum.com edited the issue description
@rjsparks@nostrum.com changed component from ` to
doc/`
@rjsparks@nostrum.com commented
This may still be an issue. Look at clean_whitespace in templatetags/ietffilters
@henrik@levkowetz.com commented
The suggested resolution of collapsing whitespace is probably the right way to go.
@rjsparks@nostrum.com changed priority from n/a
to minor
@peter@akayla.com commented
Perhaps change the return to:
return " ".join(text.split())
@rjsparks@nostrum.com changed status from new
to closed
@rjsparks@nostrum.com changed resolution from ` to
wontfix`
@rjsparks@nostrum.com commented
We haven't been bitten by this in the 13 years that it's been open. I would even argue that if someone made a Subject line that used space inside for effect, that they'd be very confused if those were stripped on the way out.
I'm going to close this as wontfix.
resolution_wontfix
type_cleanup
| by fenner@research.att.comThe cleanup for a subject header coming from a template is currently .replace("\n"," ").strip(). This can leave strings of whitespace in the middle of the string.
One option is to replace \n with "" and make sure to use linear whitespace appropriately inside the template. Another is to collapse multiple spaces and ignore the desire to use space properly (e.g., two spaces after a period in the subject). That latter is probably so rarely required that it might be the right way to go.
Issue migrated from trac:90 at 2021-10-29 15:29:24 +0500