Closed Bug 687619 Opened 14 years ago Closed 14 years ago

HTML entities not converted into special characters

Categories

(support.mozilla.org :: Knowledge Base Software, task)

Product:
support.mozilla.org
Component:
Knowledge Base Software
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: thomas.lendo, Unassigned)

References

(
URL
)

Details

HTML entities are not converted into normal characters. E.g. we use – or &hellip in translations (see example URL). Is it possible that Django didn't escape these strings so that they are displayed correctly?
These are in localizations in the templates, not in content. Thomas, is it possible to use the unicode characters instead of the entities? The whole tool chain should support unicode without changes. Otherwise we have to prevent entities from being escaped which adds potential security holes--and will have to happen anywhere one locale wants to use an entity.
Thanks for your answer, James. I now use the unicode characters instead of the entities. I don't want to create security holes in SUMO with that small request. Set as Wontfix.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.