I think.....
Because is OFFICIALLY UNDOCUMENTED, i dont have a specific url where i
can know how to convert from iso to utf. (<jokemode> Yes im a lammer and
what!... ;-P</jokemode>)
If you convert your database into UTF-8 you dont need to use
upgrade1_5.php script, so you can upgrade 1.5.2 directly from
webbrowser. I dont have any lost information using iconv, but i dont try
it with images on file system, database is a thing, and files into
/image dir other, you know? ;-)
And yes, to pass to 1.5.x is inevitable because is OBLIGATORY. Direct
show problems....
Try to use iconv and upgrade directly like the braves.....send me all
information, please. All information are welcome....
Good Luck, again....
p.d.: At this point im thinking to setup a "fucked by mediawiki software
upgrades" forum....Programmers, dont be furious with me please, you are
make a good work, but do all programmers do, dont document your
programs....When open software will be open software with open
documentation :-S....
Andre Oliveira da Costa escribió:
Hi Christof,
On Tue, 8 Nov 2005 14:49:11 +0100
Christof Damian <christof(a)damian.net> wrote:
On Tue, 08 Nov 2005, Andre Oliveira da Costa
wrote:
Hi,
we are running mediawiki v1.4.0 with a iso-8859-1 DB, and as we
tried to upgrade, locale conversion from iso-8859-1 to UT-8 didn't
work as all latin1 chars like çéõ etc. got replaced by
",". This would be "only" a PITA if we had to manually convert
accented chars by hand, but it turned out that the converstion of
URLs with latin1 chars sent some pages into a blackhole -- they
simply seem to disappear.
I had the same problem, when using the upgrade1_5.php and update.php
scripts. After I put this into my LocalSettings.php it worked though:
$wgLegacyEncoding = 'ISO-8859-1';
Mmmh... this looks promising. But with this setting did you need to run
upgrade1_5.php after all? Or did this simply tell mediawiki to "accept"
iso-8859-1, and you left your DB untouched?
If I were sure this setting is going to be around forever, I would
probably go this way, too. But, I am affraid iso-8859-1 might not be
supported at all in a near future and, in this case we would just be
putting off an inevitable upgrade to UTF-8... Do you know if this
setting is official or is it an "undocumented feature"?
TIA
Andre