| Summary | character set problems while writing to conf.php |
| Queue | Horde Framework Packages |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | komanek (at) natur (dot) cuni (dot) cz |
| Created | 05/10/2005 (7385 days ago) |
| Due | |
| Updated | 05/12/2005 (7383 days ago) |
| Assigned | |
| Resolved | 05/10/2005 (7385 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
results are unpredictable. The only way this would work is using the
mbstring.script_encoding setting, but that doesn't help at run time.
should be possible to store them in any charset. I have no problems
with utf-8 strings in my own php apps. The only problem I see is to
choose utf-8 for all or to give a user another preference to set for
other charsets. But I think that utf-8 should be fine, because it is
backward compatible with ascii (i.e. iso-8859-1, too) for us-characters.
--David
State ⇒ Not A Bug
are PHP scripts, and PHP scripts need to be in ISO-8859-1 charset.
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ character set problems while writing to conf.php
Queue ⇒ Horde Framework Packages
into this file are forced to be converted to iso-8859-1 charset. This
breaks configurations which contain national characters in various
text strings. Text values on the screen are correct until re-read from
the conf.php file. (Other character conversions like those of
preferences written to the sql backend are correct).
Tested on Horde 3.0.4 with PHP 4.3.11, Apache 2.0.50, problem with
both MSIE and Firefox browsers.