[Zope] Character-set woes (possibly OT)

[Chris Withers]

Mark Barratt wrote:
> Chris Withers wrote:
> 
>>> Pragmatic solution: define the character-set as iso-8859-1 in the 
>>> page containing the form which in turn contains the rich-text-editing 
>>> widget, 
>>
>> Well, every HTML page should specify the character set it's encoded 
>> with or it's not valid HTML <0.5 wink>
>>
> Instead of UTF-8 definition, rather than instead of nothing.

Ah, well, is the stuff you're chucking out UTF-8 or iso-8859-1?
what do you want to be chucking out? ;-)

>> That seems like it should always happen. What happens on non-windows 
>> clients?
>>
> Currently, I don't care so haven't tested - user group is closed and all 
> use some variety of Windows/Word. Will get round to testing from Mac 
> clients one day and will report back.

:-)

>> What are the MySQL issues? What appear to be the Zope issues?
> 
> Hard to disentangle. MySQL explicitly doesn't support any encoding of 
> Unicode except in latest (4.1?) versions - and then you need to define 
> tables as UTF-8 at creation. 4.1 is not stable. 

:-(

> In older versions the 
> theory is that you can define fields as BLOBs but haven't tried that. In 
> text fields only standard entity references work, (though they shouldn't).

Best not to rely on that then...

What would you like to have happen in what you're doing?

cheers,

Chris