Scheider, Hendrik schrieb:
> I am having trouble with a special character in my page sources: the Euro
> currency sign, though directly input as character in the edit form (my
> keyboard has it as key), is converted to € in the page source (with
> the ampersand then escaped as entity for output).
Only the server-defined charset is possible. (mostly iso-8859-1)
otherwise the connection from the client to the server and the
connection from the server to the database will be undefined.
> I found some ancient discussion on the accent/umlaut issue on the list
> here http://sourceforge.net/mailarchive/message.php?msg_id=3872323
> and here http://sourceforge.net/mailarchive/message.php?msg_id=494295
>
> but don't know the actual state. At least German umlaute and Roman language
> accents work fine even as wiki links (url_encoded in the URL, but unescaped
> for output). Furthermore I am totally inexperienced in the field of charset
> encodings.
The actual state is a bit better now (see the problems jeff talks about
in the first link)
Special &#<num>; encodings are now (since a few days in CVS only)
allowed, which are displayed asis. This is problematic for searches e.g.
Markup_isonumchars in InlineParser.
regex: "\&\#\d{2,5};"
e.g. …
> I am using php 4.3.10 on apache 1.3.33 and mysql 4.1
> with
> extension=php_mbstring.dll
> turned on in PHP.
Aha. That makes a difference. I wouldn't turn that on unless you use
japanese charsets.
mbstring does charset conversion also, which is independent of phpwiki.
--
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/
|
