[pLog-svn] Encoding Titles
oscar at renalias.net
Sun Nov 11 06:56:32 EST 2007
Yes, I don't think we should spend any more time with this considering
that LT 2.0 will be 100% UTF-8.
On 10 Nov 2007, at 21:09, Reto Hugi wrote:
> I think I now understand the issue:
> If the page is, say, iso-8859-1 encoded (due to the definition in the
> locale), and we want to add categories with umlauts or other non-ascii
> chars through AJAX on the new post page, that screws up. We need utf-8
> encoding on the website for this to work.
> As utf8 is already default for the trunk I think this is an issue we
> won't fix.
> On 11/04/2007 11:04 PM, Reto Hugi wrote:
>> I'm not sure if it's just me or anybody else could reproduce this
>> Umlauts or other chars not within ASCII range get lost if used
>> everywhere but the article text-body if WYSIWYG editor is activated
>> because that one converts the chars to html entities.
>> DB Collation: UTF8
>> LT DB-Config: UTF8
>> Languagefile (and therefore XHTML Charset: iso-8859-1
>> I can't see where they get lost, but they are still in the getter
>> that supplies the value to the global add method. But the view
>> has get data with those chars filtered out (they are not there
>> So I thought it must be my db setup. But as it's utf8 I'm wondering
>> I'm doing wrong...
>> Maybe some of you encoding experts can enlighten me :)
>> thanks and cheers,
>> pLog-svn mailing list
>> pLog-svn at devel.lifetype.net
> pLog-svn mailing list
> pLog-svn at devel.lifetype.net
More information about the pLog-svn