PowerArchiver 9.2 added yEnc support in May 2005.Īs with uuencoding, despite its flaws, yEnc remains active and effective on Usenet. Stuffit Deluxe added yEnc support with version 8.0 in 2003. Moreover, some article transports may, on the grounds of enforcing compliance with the Internet message format standard, automatically convert any message using 8-bit characters to either Base64 or quoted-printable, entirely nullifying the overhead advantage. It works poorly with the increasingly popular UTF-8 character set, for instance. yEnc can also be mangled by different character sets. Not all transports can handle the 8-bit characters employed by yEnc, which may cause data corruption. NUL is also escaped because of problems handling null characters in common code, although as an optimization yEnc adds 42 to every source byte so that data with large stretches of 0x00 values does not require a lot of escaping. = is the escape character, so it itself is escaped. LF and CR are escaped because the RFCs that define Internet messages still require that carriage returns and line feeds have special meaning in a mail message. Therefore 252 of the 256 possible bytes are passed through unencoded as a single byte, whether that result is a printable ASCII character or not. YEnc assumes that binary data mostly can be transmitted through Usenet and email. An additional advantage of yEnc over previous encoding methods, such as uuencode and Base64, is the inclusion of a CRC checksum to verify that the decoded file has been delivered intact.

Stuffit deluxe thunderbird email