Summary | htmlspecialchars and other encodings |
Queue | Horde Framework Packages |
Type | Enhancement |
State | Rejected |
Priority | 1. Low |
Owners | |
Requester | vilius (at) lnk (dot) lt |
Created | 04/27/2004 (7753 days ago) |
Due | |
Updated | 05/07/2004 (7743 days ago) |
Assigned | |
Resolved | 05/07/2004 (7743 days ago) |
Milestone | |
Patch | No |
State ⇒ Rejected
raw email body. It already now produces a huge overhead but taking
charsets into account would need to completely parse every single
message with the MIME framework. That would actually take as long as
watching every single message in a mailbox.
convert each tooltip text from email message encoding to
NLS::getCharset(). I would submit a patch if only knew how to write it
:)
p.s. you should change ticker type to BUG.
to find out if the needed charset is currently supported by
htmlspecialchar(), we would have to use this workaround for *every*
htmlspecialchar() call, degrading the perfomance massively.
I don't consider this whole thing a huge problem though, because UTF-8
is supported and OSes not supporting UTF-8 will disappear soon anyway.
http://www.mail-archive.com/php-i18n@lists.php.net/msg00272.html
State ⇒ New
Priority ⇒ 1. Low
Type ⇒ Enhancement
Queue ⇒ Horde Framework Packages
support more encodings than native php's htmlspecialchars() has
(http://www.php.net/manual/en/function.htmlspecialchars.php table no.1).
For now, I'm using windows-1257 encoding, and i'm getting broken HTML
if tooltip preview is turned on (see attachment). It confuses some
older browsers, and i can't get into my inbox at all.