On 12/10/2010 16:00, Charlie Clark wrote:
Traceback (most recent call last): File "<stdin>", line 1, in<module> UnicodeEncodeError: 'latin-1' codec can't encode character u'\u203a' in position 0: ordinal not in range(256)
ISO-8859-15 is, of course, Latin-1 + the €
Yes, but I don't see why that is being used... Some bits from the error_log entry for this request: HTTP_USER_AGENT 'Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64; Trident/4.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; MDDC; .NET CLR 3.5.30729; .NET CLR 3.0.30729; MS-RTC LM 8; .NET4.0C)' HTTP_ACCEPT '*/*' HTTP_ACCEPT_LANGUAGE 'en-us' So why on earth is iso8859_15 being picked instead of utf-8? Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk