Re: [Phpwiki-talk] Ampersand

[Jeff D. <da...@da...>]

On Fri, 21 Feb 2003 21:33:51 +0100
"Klaus - Guenter Leiss" <Le...@we...> wrote:

> There had been users
> with different computerplatforms and different local charsets
> and the charcaters above 127 were different. I assume that
> is a problem of the browser.

Yes, that's probably right.  For phpwiki output, the character
set is specified in the Content-Type: HTTP header.  Browsers
are supposed to respect that.

For form input, (like when editing a page) phpwiki sets
the accept-charset attribute of the <form> tag.  This should
make browsers submit the form input in the proper character set.

(Probably there are some forms that phpwiki generates which
don't have the proper accept-charset attribute.  That's a phpwiki
bug...  Report those if you find them.)




> I think if you wanted to
> discuss music or language you would need many characters
> that are not in ISO-8859-1.

... or math...  But then that requires things not even in UTF.


> > (Searches for "H=E4schen" won't find the text "H&auml;schen".)
> This could mean that entities have to be allowed also in searches.

The real solution to that is to switch to using UTF-8 internally,
so that we can store all those nice characters in a uniform manner.
The problem is that MySQL and PHP support for this is not
(last I checked) good (or universal) enough to do this.

Or, as a hack, I guess we could store everything in US-ASCII,
with all characters above 127 converted to some canonical entity.
(i.e. =DC always needs to be stored the same way: either &Uuml;
or &#220; )

Another option would be to internally use UTF-8 (in PHP), but
(assuming enough people have UTF-8 enabled PHP's) and convert=20
to US-ASCII as described above in the backend for those database
who don't support unicode.

Just thinking aloud... or visibly, rather...



As for replying to the list or to the sender (or both): I say do
whatever you think appropriate for the message.

My MUA (sylpheed) seems to reply to the list by default.
It must be picking the address from the List-Post: header, since
there doesn't seem to be a Reply-To:, and From: lists the sender,
not the list.