[opensuse] [ALMOST SOLVED] how to deliver archive to/from Windows user while ensure filenames in archive not corrupted
I have tested a lot how we can solve this problem: WE cannot avoid it: some day you need to send several files to a Windows user: you use a packing tool either because there are many files or because the file had been too fat and can be compressed. What format to use: most western people I think will choose zip, for me I got a problem: the Chinese file names, after un-packaged on Windows, is junk text because on Linux we all use UTF-8 and Windows Chinese version using different charset (GB18030) And I have tested a lot different formats: Format Created by Opened by Filename readable after unpackaged? zip 7-zip_win32 FileRoller no zip FileRoller 7-zip_win32 no rar WinRAR 3.6 FileRoller yes! rar FileRoller WinRAR 3.6 no iso mkisofs -J WinRAR 3.6 yes! jar FileRoller 7-zip no tar GnuTar WinRAR 3.6 no tar 7-zip GnuTar no cab IExpress cabextract no Note: * WinRAR 3.6 is actually WinRAR 3.60-Beta * 7-zip_win32 is a Windows software, the open-source alternative to WinRAR, can unpackage zip/tar/rar/7z formats and can create zip/tar/7z archives * IExpress is a Microsoft utility pre-installed on most Windows computers. This utility can create CAB format archive * FileRoller is SuSE 10.2's default gnome archive manager * in all above archive formats, TAR and ISO are non-compressing format, e.g. they only archive (collect files into one file). To compress them you can use gzip. So the conclusion is: 1. To send an archive file to other windows user, the only known way that can ensure file names are NOT corrupted due to locale difference is to make the archive with "mkisofs -J", unfortunately no very easy graphical user interface for this purpose. If compression is needed, compress with gzip and Windows user who have WinRAR installed can open it. 2. To send an archive file from Windows to SuSE Linux user, the only known way that can ensure filenames are not corrupted due to locale difference is to make RAR archive with WinRAR (only tested v3.60-beta). 3. Non of known Linux archive formats can handle character-set conversion. "mkisofs -J" is actually using a Microsoft format, and WinRAR is proprietary; 4. 7z format is not tested because most Windows & Linux users cannot directly create/open 7z format archive without install special software so it cannot be used as a general solution. This information might be very useful for asian people on this list. P.S. I have already spent a lot of time getting this partial conclusion, would be very appreciated if someone provide more insightful suggestions or correction! P.S. "mkisofs -J" do not allow file names with more then 64 characters. If you do have such long named files, unfortunately there is no known way you can archive them and deliver to Windows user while ensure the file name not corrupted. -- Zhang Weiwu Real Softservice http://www.realss.com +86 592 2091112 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Forgot to mention: if you don't mind using commandline and you know the character-set of the receipt's Windows system, you can use convmv to pre-convert filenames to that character-set. However this is not my case, when I send a file to a colleague, he might be using company's computer (German Windows) or his notebook (English Windows because too hard to buy notebook with German Windows in China) or his home computer (Chinese Windows because he got a Chinese wife). So I cannot predict what is the character-set of my colleague when he opens the email. My colleague don't get the same pain because he has always been using winRAR: the "standard format" in this international company with employee from many places. My wish is Linux's RAR format support can be better, that the RAR files created by FileRoller would be as feature-rich as archives created with winRAR. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2007-03-29 at 16:50 +0800, Zhang Weiwu wrote:
My wish is Linux's RAR format support can be better, that the RAR files created by FileRoller would be as feature-rich as archives created with winRAR.
I mentioned FileRoller above: actually I don't know what application fileroller called to create rar files, I have tried in SuSE 10.2 both rar 3.60 (Shareware version of Alexander Roshal) and rar 2.71 (Shareware version of Eugene Roshal), both cannot create RAR that contain readable filename on Windows. -- Zhang Weiwu Real Softservice http://www.realss.com +86 592 2091112 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2007-03-29 at 17:01 +0800, Zhang Weiwu wrote:
My wish is Linux's RAR format support can be better, that the RAR files created by FileRoller would be as feature-rich as archives created with winRAR.
I mentioned FileRoller above: actually I don't know what application fileroller called to create rar files, I have tried in SuSE 10.2 both rar 3.60 (Shareware version of Alexander Roshal) and rar 2.71 (Shareware version of Eugene Roshal), both cannot create RAR that contain readable filename on Windows.
So, the only method that works from linux to windows is mkisofs? Too bad. I thought that the shareware version of rar in linux would work. I tried it time ago when I started using linux, back in 1998, but I found it lacking compared to the dos/win version. I hoped it would be better nowdays. There is another option you might try: winrar in linux under wine. If winrar doesn't run, then one of the older dos version, perhaps. Another method: copy file in linux partition to a vfat partition using a windows charset that works, then compress from there. You have to steps to check: first, that when copying to vfat, that the vfat is correctly readable in a windows machine (correct charset, you may have to play with fstab); second the compression step. My hope is that the first step corrects the charset used. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGC6zqtTMYHG2NR9URAmqaAKCTqHE3suwm2FZKnPJSmtSJgdFD+wCeK1B4 VnTCp6Rk0Af/GTpRblyT4+w= =aKUD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2007-03-29 at 14:11 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Thursday 2007-03-29 at 17:01 +0800, Zhang Weiwu wrote:
My wish is Linux's RAR format support can be better, that the RAR files created by FileRoller would be as feature-rich as archives created with winRAR.
I mentioned FileRoller above: actually I don't know what application fileroller called to create rar files, I have tried in SuSE 10.2 both rar 3.60 (Shareware version of Alexander Roshal) and rar 2.71 (Shareware version of Eugene Roshal), both cannot create RAR that contain readable filename on Windows.
So, the only method that works from linux to windows is mkisofs? Too bad.
?? 1. On SUSE, put all the files with UTF-8 (native suse) encoded names in directories as usual. cd to that directory. 2. run: convmv -f UTF-8 -t GB18030 . 3. The names will now all be GB18030. Archive as usual. Do the reverse when files come back. OK. This is how it goes in theory. Anyone tried it? -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Zhang Weiwu wrote:
I have tested a lot different formats:
Excellent list!
P.S. I have already spent a lot of time getting this partial conclusion, would be very appreciated if someone provide more insightful suggestions or correction!
I've asked a friend who may know something but I don't have a reply yet.
P.S. "mkisofs -J" do not allow file names with more then 64 characters. If you do have such long named files, unfortunately there is no known way you can archive them and deliver to Windows user while ensure the file name not corrupted.
Have you tried this option: "-joliet-long Allow Joliet filenames to be up to 103 Unicode characters. This breaks the Joliet specification - but appears to work." Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2007-03-29 at 16:42 +0800, Zhang Weiwu wrote:
I have tested a lot how we can solve this problem: WE cannot avoid it: some day you need to send several files to a Windows user: you use a packing tool either because there are many files or because the file had been too fat and can be compressed.
What format to use: most western people I think will choose zip, for me I got a problem: the Chinese file names, after un-packaged on Windows, is junk text because on Linux we all use UTF-8 and Windows Chinese version using different charset (GB18030)
And I have tested a lot different formats:
Format Created by Opened by Filename readable after unpackaged? zip 7-zip_win32 FileRoller no zip FileRoller 7-zip_win32 no rar WinRAR 3.6 FileRoller yes! rar FileRoller WinRAR 3.6 no iso mkisofs -J WinRAR 3.6 yes!
This only work partially. Although the created ISO image have Joliet extension and all filenames in UTF16LE, winRAR (incorrectly) produce junk text for the first two ideographs, but following ideographs are correct. The same ISO image, once burnt on CDR, works fine (no junk filename) on Windows. Any bug winRAR have (e.g. incorrectly handle first two ideograph in the file name in a .ISO file) is the limitation of Linux, because novice users wouldn't understand this is winRAR's problem, they will only say the file is incorrect can you please send it in the normal way (a.k.a. *.rar)
jar FileRoller 7-zip no tar GnuTar WinRAR 3.6 no tar 7-zip GnuTar no cab IExpress cabextract no
Note: * WinRAR 3.6 is actually WinRAR 3.60-Beta * 7-zip_win32 is a Windows software, the open-source alternative to WinRAR, can unpackage zip/tar/rar/7z formats and can create zip/tar/7z archives * IExpress is a Microsoft utility pre-installed on most Windows computers. This utility can create CAB format archive * FileRoller is SuSE 10.2's default gnome archive manager * in all above archive formats, TAR and ISO are non-compressing format, e.g. they only archive (collect files into one file). To compress them you can use gzip.
So the conclusion is:
1. To send an archive file to other windows user, the only known way that can ensure file names are NOT corrupted due to locale difference is to make the archive with "mkisofs -J", unfortunately no very easy graphical user interface for this purpose. If compression is needed, compress with gzip and Windows user who have WinRAR installed can open it. 2. To send an archive file from Windows to SuSE Linux user, the only known way that can ensure filenames are not corrupted due to locale difference is to make RAR archive with WinRAR (only tested v3.60-beta). 3. Non of known Linux archive formats can handle character-set conversion. "mkisofs -J" is actually using a Microsoft format, and WinRAR is proprietary; 4. 7z format is not tested because most Windows & Linux users cannot directly create/open 7z format archive without install special software so it cannot be used as a general solution.
This information might be very useful for asian people on this list.
P.S. I have already spent a lot of time getting this partial conclusion, would be very appreciated if someone provide more insightful suggestions or correction!
P.S. "mkisofs -J" do not allow file names with more then 64 characters. If you do have such long named files, unfortunately there is no known way you can archive them and deliver to Windows user while ensure the file name not corrupted.
-- Zhang Weiwu Real Softservice http://www.realss.com +86 592 2091112
-- Zhang Weiwu Real Softservice http://www.realss.com +86 592 2091112 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Carlos E. R. -
Dave Howorth -
Roger Oberholtzer -
Zhang Weiwu