On Linux Several common compression methods "garbled" or not interesting comparison __linux

The so-called "common" probably can only say that I have seen, tar, GZ, bz2, zip, 7z, jar.
In the title of garbled refers to the LINUX+UTF8 system in the compressed Chinese files in Windows after decompression file name garbled.

Tar is primarily used for archive files and is not responsible for compression itself. GZ and bz2 can only compress a single file, so they are often used in combination with tar, which forms the common tar.gz and tar.bz2. Tar compressed after garbled, tar.gz and tar.bz2 also follow the wrong. Interestingly, bz2 can correctly handle the file file name, but GZ appears garbled.
Zip can be packaged with multiple files, but garbled after compression. Suspected GZ garbled source originated in zip. Jar problem with zip.
In comparison, 7z is a good performance, you can package more than one file, and can be packaged in the correct processing of Chinese file names. One drawback of the discovery is that File-roller cannot compress folders under Gnome. This should be a question of file-roller. Hopefully it will be corrected soon.

Conclusion:
If you use the Linux+utf8 system, it is best to use 7z to compress Chinese files to avoid the normal decompression of Windows. You may have to temporarily use the command line when compressing a folder. PHP code: 7z a dir.7z dir/

Can try xarchive, it can support tar, GZ, bz2, zip, rar, ARJ, Ace, 7z and so on almost all of the compressed file format, itself is a graphical interface of the compression Package Manager, itself can not compress, extract files, by invoking the system in the command-line program to complete, Like File-roler, and can also be extended as needed.
Another xarchiver is ready to be integrated into the Xfce Thunar file Manager, just like Nautilus integrated File-roler, and Xarchive is an independent GTK2 program that is not confusing.

Two Linux and win between not garbled

A file in Chinese file name, copy between win and Linux, file name want not garbled how to do---as long as win and Linux filename encoding the same

Win filename encoding scheme =. But win filename "kanji" =baba,d7d6
Linux filename encoding scheme =utf-8 or GB18030
Conclusion: Linux uses GB18030 encoding to be compatible with win

http://www.linuxsir.org/bbs/showthread.php?t=263669