FlashFXP Forums - View Single Post

Yil · 06-02-2007, 09:29 PM

Unicode for files in ioFTPD is a long ways off. Just too many places that the code would need work to get it to handle 16 bit chars if the whole code base was compiled for wchar's and doing just parts of it would probably be worse...

TCL is entirely a different issue. It's possible that if you grab the lib/encoding directory from a standard tcl distribution that might solve some of your problems. I removed it from the 6.x releases since the 5.x releases didn't have it and people came to rely on exporting .NFO files with 8bit graphics which totally confused the utf-8 encodings... It seemed most people were happy with the old "broken" style as it kept script compatibility. You may find that replacing the encodings will work for your personal scripts using utf-8 though... If that helps let me know, and I'll see if I can add a new iputs option that operates in a raw style mode so you can also use 8bit graphics.

06-02-2007, 09:29 PM
Yil Too much time... Join Date: May 2005 Posts: 1,194	utf-8 Unicode for files in ioFTPD is a long ways off. Just too many places that the code would need work to get it to handle 16 bit chars if the whole code base was compiled for wchar's and doing just parts of it would probably be worse... TCL is entirely a different issue. It's possible that if you grab the lib/encoding directory from a standard tcl distribution that might solve some of your problems. I removed it from the 6.x releases since the 5.x releases didn't have it and people came to rely on exporting .NFO files with 8bit graphics which totally confused the utf-8 encodings... It seemed most people were happy with the old "broken" style as it kept script compatibility. You may find that replacing the encodings will work for your personal scripts using utf-8 though... If that helps let me know, and I'll see if I can add a new iputs option that operates in a raw style mode so you can also use 8bit graphics.