View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006624 | mantisbt | localization | public | 2006-01-21 15:54 | 2006-02-04 05:44 |
Reporter | nand | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | duplicate | ||
Product Version | 1.0.0rc5 | ||||
Summary | 0006624: htmlspecialchars: charset `iso-8859-2' not supported | ||||
Description | After selectig polish version in profile the following message appears on every page: SYSTEM WARNING: htmlspecialchars() [function.htmlspecialchars]: charset `iso-8859-2' not supported, assuming iso-8859-1 | ||||
Tags | No tags attached. | ||||
Lovely. Here's a list of all the charsets Mantis languages use: big5 euc-jp euc-kr gbk iso-8859-1 iso-8859-15 iso-8859-2 iso-8859-9 koi8-r shift_jis utf-8 windows-1251 windows-1252 windows-1257 This list was produced with the following command, which is a mess but works: cat lang/*.txt | grep charset | awk '{print $3}' | sed 's/['\''""; ]//g' | tr "[:upper:]" "[:lower:]" | sort | uniq The list of supported charsets for htmlspecialchars() is shown here: http://www.php.net/htmlspecialchars The charsets Mantis uses which are not on that list are as follows: euc-kr gbk iso-8859-2 iso-8859-9 windows-1257 I imagine iso-8859-2, iso-8859-9 and windows-1257 can harmlessly be handled as iso-8859-1 but I have no idea about euc-kr or gbk. |
|
Problem disappear if you translate string_*.txt files with unsupported code pages to UTF-8, and of course set variable "$s_charset" in this files to 'UTF-8'. UTF-8 is supported by htmlspecialchars and contains chars from unsupported code pages like iso-8859-2 for example. |
|
Without a doubt. Conversion of Mantis to UTF-8, however, is a whole 'nother ball game; see 0004084. |
|