[Scummvm-devel] Wiki update coming up

[Max Horn]

Hi Darkstar, all,

the issue has been fixed, I just had to turn "MySQL 5" mode "off",  
which had been turned on by accident by the transition. Unfortunately,  
some pages had already been changed for intl fixes, so I had to  
rollback those.

Right now, our DB uses latin1 collation on all tables, while MediaWiki  
uses the "backward-compatible UTF-8" mode (whatever that means  
exactly, they only mention this name on their Wiki but seem not to  
explain it anywhere).

For now, this works. It might be useful to convert the DB to UTF-8 at  
some point, but for it works and I am hesitant to spend more effort on  
this issue than required. Esp. since it seems to be rather  
underdocumented :/.

Cheers,
Max

Am 27.01.2009 um 12:31 schrieb <darkstar at drueing.de> <darkstar at drueing.de 
 >:

> Hi,
>
> I had the same problems while updating a personal wiki of my own  
> some time
> ago. It seems that newer mysql databases use UTF-8 encodings while  
> the older
> db used latin1.
> I fixed it by piping the mysql dump through recode ("recode  
> latin1..utf-8 <
> db.dump > db2.dump")
>
> It might be a similar issue that you're facing...
>
> *returns to lurk mode*
>
> -Darkstar
>
>> -----Original Message-----
>> From: Max Horn [mailto:max at quendi.de]
>> Sent: Tuesday, January 27, 2009 4:56 PM
>> Cc: scummvm-devel.lists.sourceforge.net devel
>> Subject: Re: [Scummvm-devel] Wiki update coming up
>>
>> Hi,
>>
>> Am 27.01.2009 um 10:35 schrieb Jordi Vilalta:
>>
>>> 2009/1/27 Max Horn <max at quendi.de>:
>>>> it seems the upgrade went fine and we are now at MediaWiki version
>>>> 1.13.3
>>>
>>> Great. It's been noted on IRC that there are issues with pages
>>> containing non-ascii characters (it's been noticed first on
>> the Touché
>>> page:
>> http://wiki.scummvm.org/index.php/Touch%C3%83%C2%A9:_The_Adven
> tures_of_the_Fifth_Musketeer
>>> ; the page about international game titles is another clear example:
>>> http://wiki.scummvm.org/index.php/International_Game_Titles ).
>>>
>>> I remember something like this happened some time ago (I don't
>>> remember if it was on another update or what). Is it just a
>>> configuration issue or should we start modifying the pages by hand?
>>> (IIRC this was last time's solution)
>>
>> Thanks for pointing this out. Please do *not* attempt to fix
>> the issue
>> via edits. I'll look into the issue now.
>>
>> Bye,
>> Max
>> --------------------------------------------------------------
>> ----------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
>> _______________________________________________
>> Scummvm-devel mailing list
>> Scummvm-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/scummvm-devel
>
>