I just tried weird password chars in a stock [EMAIL PROTECTED] client. I set it to:
UploadPassword=*,-#,.a and it worked just like that. I think I had the file authentication.conf saved utf-8 encoded, so that is what seems to be required for weird password chars to work. [EMAIL PROTECTED] client authors, is there a way to check whether it's utf-8 or whether it's something else that needs converting? Perhaps rather than dying if the user has a weird char in his password, you could tell him to save his authentication.conf as utf-8 file if authentication really fails... My perl encoding skills are even worse than the rest of my perl knowledge... Thanks spaetz _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
