FileZilla-Log-Analyzer icon indicating copy to clipboard operation
FileZilla-Log-Analyzer copied to clipboard
verified publisher icon Stunner

Updates for FileZilla_Server-0_9_54

Open stehpancar opened this issue 9 years ago • 2 comments

fixed: No successful transfers were found as the text returned by FileZilla server changed for the "226" status code. (was "Transfer OK" now is "Successfully transferred") fixed: By now FileZilla_Server (0_9_54) produces utf-8 log files. Decoding

stehpancar avatar Jan 14 '16 13:01 stehpancar

Thanks for the pull request! I am wondering if opening the log files with utf-8 encoding will work for log files generated by older versions of FileZilla Server.

Stunner avatar Jan 14 '16 21:01 Stunner

This depends on the encoding FileZilla Server used back then. If it used plain US-ASCII for storing assuming utf-8 when opening should work. I believe the same is true for latin1 (aka "ISO 8859-1"). https://en.wikipedia.org/wiki/ISO/IEC_8859-1

If it used the system encoding of windows. Things will be tricky. https://en.wikipedia.org/wiki/Mojibake I think there is no simple solution. A work around would be to add a command line switch that a user can use to specify the encoding that was used when the file was stored. Guessing would always be problematic.

stehpancar avatar Feb 04 '16 21:02 stehpancar