View Issue Details

IDProjectCategoryView StatusLast Update
0015362phplist applicationInternationalization (l18n)public17-05-11 14:50
ReporterEdgarWahn 
PrioritynormalSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
Product Version2.10.10 
Target Version4.0.xFixed in Version2.11.6 
Summary0015362: overall handling of charsets
DescriptionYou can enter bits of text at several locations, ranging from config file (plain text email user name) to configuration (database). At no point (it seems) the charset of user input is been checked or converted to UTF-8. You might end up with a mixture of Charsets, depending on the browser settings of the PHPList users.
Additionally PHPList does not send an content-type HTTP header containing charset information, which will produce bad output depending on the users browser settings. You really should send something like "content-type: text/plain; charset=utf-8".
Additional Information* check & convert every single bit of input by utilizing mb_detect_encoding or equivalent
* generate content-type HTTP header containing a fixed charset (utf-8 preferred)
* adapt the i18n language files (as they contain an charset header as well, they need to be converted to utf-8 (which could be done automatically as you know the sites charset and the translations charset => iconv))
TagsNo tags attached.

Relationships

related to 0001644 resolvedmichiel Subject error with UTF-8 encode in Traditional Chinese 

Activities

There are no notes attached to this issue.