> we heavily use the import feature of version 1.9.4. Maybe have a look at the changelog of the latest version.
I remember I have looked at that problem in general, but I am not sure whether I could fix / have fixed that in 1.9.x. > Whenever I try to import a page with a German > Umlaut in it's name, I get the following error message: > > UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 5: > ordinal not in range(128) It's non-trivial to find the console/commandline encoding in a platform-independant way. > Is there any other workaround available, besides importing the page with non > umlaut characters (i.e. > ue, oe, ae), renaming the page afterwards in the filesystem? Instead of calling that script on the console, you could have some python code that reads the pagenames from a file with known encoding and proceeds similar as the code for the script command does. ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ Moin-user mailing list Moin-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/moin-user
