Nathan Hamblen wrote: They are used in many thousands of articles. Bots can't edit the page history. Bots can't fix user names, comments, and page titles. -- brion vibber (brion @ pobox.com)

On Monday 14 June 2004 09:20, Brion Vibber wrote: Couldn't the database be converted online? I am thinking about a script which would be doing something like this: for cur_id=1 to x Protect page cur_id Convert page cur_id and its edit history to UTF-8 Write cur_id to "ConversionStatus.php" Unprotect page cur_id next and then, I'm not sure where, probably in Article.php, $wgOutputEncoding could be set to UTF-8 if cur_id of the displayed article < one in ConversionStatus.php and left ISO-8859-1 if it's not. (Of course, the script would have to check if the article was already protected and not unprotect it in that case but I didn't want to complicate the pseudocode.)

Brion Vibber wrote: I suppose most of the time will be taken to convert old. Shouldn't be possible to convert only cur while either leave old unconvert or mark each entrey in old as unconverted/still in iso-8859-1 and convert these entries when they are needed or by a very low priority job? (of course the soft will need to handle the conversion flag when viewing on old version of an article, doing a diff, ...) Is this doable or still too complex? -- Looxix