> The basic problem is that Windows differentiates between text files > (translate between \n and \r\n) and binary files, whereas UNIX doesn't. So > "text mode" works just fine on binary files in UNIX, but breaks horribly > under Windows (anything resembling \r\n gets mangled on read, and all \n > gets mangled on write). Perl uses text mode by default, which is fine for > UNIX, but breaks on Windows when you manipulate binary files. Ok, but does forcing binary mode, as my patch does, break under UNIX? Besides, for crossfire.[01] containing the whole PNGs, it's just weird to use TEXT mode, and not binary mode, even if it happens to work under UNIX :) > T Nicolas 'Ryo' _______________________________________________ crossfire-devel mailing list crossfire-devel at lists.real-time.com https://mailman.real-time.com/mailman/listinfo/crossfire-devel