Re: [opensuse] should I prefer RAR format for deliverying file to Windows users
----- Original Message ----
From: Zhang Weiwu
Even if Jar works, it still present a problem because the Windows user who received the file and has JRE installed, would trigger JRE to run this jar file... So, thanks for the idea but not exactly solution to my problem. :) On Wed, 2007-03-28 at 07:20 -0700, Simon Roberts wrote:
Have you tried jar? That's the archive format that is used by Java programs. There's a command-line tool that comes with the Java developer's kit (and with the runtime). My understanding is that the format is essentially zip, but modified to use Unicode for the directory information.
BTW, if it works (or not) I'd be pleased to hear about this, as I've been teaching this for a dozen years, and haven't been able to test it myself!
HTH Cheers, Simon
____________________________________________________________________________________ Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/ -- 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
On Wednesday 28 March 2007 16:20, Simon Roberts wrote:
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) ----------------------
Have you tried jar?
WinRAR is even able to handle TAR, GZIP and BZIP2 archives. So give it a try and use the native tools :)
BTW, if it works (or not) I'd be pleased to hear about this,
So am I :)
Ciao,
Daniel
--
J. Daniel Schmidt
On Wed, 2007-03-28 at 16:47 +0200, J. Daniel Schmidt wrote:
On Wednesday 28 March 2007 16:20, Simon Roberts wrote:
Have you tried jar?
WinRAR is even able to handle TAR, GZIP and BZIP2 archives. So give it a try and use the native tools :)
All above 3 had been tried. I also checked briefly their manuals and doesn't seems to be an option for this. Also: CAB format, as it can be opened directly by Windows Me/98/2000/XP could be an alternative, although WinRAR doesn't seem to support it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2007-03-28 at 16:47 +0200, J. Daniel Schmidt wrote:
On Wednesday 28 March 2007 16:20, Simon Roberts wrote:
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) ----------------------
Have you tried jar?
WinRAR is even able to handle TAR, GZIP and BZIP2 archives. So give it a try and use the native tools :)
I receives rar quire often from users: Linux and Windows alike. (So 'native' is a tricky concept.) I have never had the character set problem because I have been lucky. No one is using öäåÖÄÅ in file names. I would be curious for future reference to know if rar does indeed convert character sets in file names. Maybe it is not a rar-specific thing. Maybe it is the specific rar client at either end. It would be interesting to know which they are. -- 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
On Wed, 2007-03-28 at 16:57 +0200, Roger Oberholtzer wrote:
On Wed, 2007-03-28 at 16:47 +0200, J. Daniel Schmidt wrote:
On Wednesday 28 March 2007 16:20, Simon Roberts wrote:
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) ----------------------
Have you tried jar?
WinRAR is even able to handle TAR, GZIP and BZIP2 archives. So give it a try and use the native tools :)
I receives rar quire often from users: Linux and Windows alike. (So 'native' is a tricky concept.) I have never had the character set problem because I have been lucky. No one is using öäåÖÄÅ in file
While having öäåÖÄÅ displayed incorrectly is a bit annoying to most European/American people, having Chinese ideograph displayed incorrectly is pain in the ass for Asian people. Last week I have to send 150 articles to a journalist and they are all saved on my harddisk in Chinese name. After wasted an hour, guess what's the final solution we found? I created her an ISO image file (with -J to mkisofs which store unicode filename). And the really funny things is she opened the ISO image with her WinRAR and all Chinese filenames are correct! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2007-03-28 at 23:13 +0800, Zhang Weiwu wrote:
On Wed, 2007-03-28 at 16:57 +0200, Roger Oberholtzer wrote:
On Wed, 2007-03-28 at 16:47 +0200, J. Daniel Schmidt wrote:
On Wednesday 28 March 2007 16:20, Simon Roberts wrote:
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)
What about the convmv command? I think it supports GB18030 (see man page for charsets). At least this may help convert the names before/after sending. -- 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
Roger Oberholtzer wrote:
Zhang Weiwu wrote:
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)
What about the convmv command? I think it supports GB18030 (see man page for charsets). At least this may help convert the names before/after sending.
Converting the files to GB18030 and then piping them into whatever archiver you prefer seems like the best you are likely to be able to do. RAR is proprietary; there are multiple versions of the file format; there are multiple implementations of the decoder for Linux. It would pay to check exactly what version of all components you are using if you want to pursue that route. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2007-03-28 at 16:47 +0200, J. Daniel Schmidt wrote:
On Wednesday 28 March 2007 16:20, Simon Roberts wrote:
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) ----------------------
Have you tried jar?
WinRAR is even able to handle TAR, GZIP and BZIP2 archives. So give it a try and use the native tools :)
I have tried all of them (creating documents with RAR, gzip, bz2, zip, jar format created by Gnome's file-roller) and all of them opens shows junk file name on Windows (opened by 7-zip running on Windows). However if I receive a document from a Windows user in tar, gzip, bz2, zip format (when testing, created by 7-zip Windows version), all of them opens junk file name on SuSE BUT if a Windows user send me RAR file (made with winRAR), open it in Linux, the file name is CORRECT. So: RAR file made on Linux doesn't contain charset information, RAR files made on Windows contain charset information. The only format acceptable to general Windows user I haven't tried yet is: CAB. This format can be opened by Windows 98/Me/2000/XP. I didn't try it because I cannot find a tool to make such archives. I can only find cabextract in SuSE repository which is used to open CAB format. Still no solution. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2007-03-28 at 23:08 +0800, Zhang Weiwu wrote:
I have tried all of them (creating documents with RAR, gzip, bz2, zip, jar format created by Gnome's file-roller) and all of them opens shows junk file name on Windows (opened by 7-zip running on Windows).
I think you should also try different programs on both ends. It could be an inplementation problem, not an archive format problem (or not only).
However if I receive a document from a Windows user in tar, gzip, bz2, zip format (when testing, created by 7-zip Windows version), all of them opens junk file name on SuSE BUT if a Windows user send me RAR file (made with winRAR), open it in Linux, the file name is CORRECT.
And rar made with 7-zip in windows? If that is also incorrect, then the 7-zip client is the culprit.
So: RAR file made on Linux doesn't contain charset information, RAR files made on Windows contain charset information.
A rar made with gnome roller. Try another tool; but I don't know which, rar is propietary. I wasn't even aware that we could make rars in linux (version 2 rar, I mean).
The only format acceptable to general Windows user I haven't tried yet is: CAB. This format can be opened by Windows 98/Me/2000/XP. I didn't try it because I cannot find a tool to make such archives. I can only find cabextract in SuSE repository which is used to open CAB format.
Posibly propietary.
Still no solution.
A zisofs compressed iso? But it wouldn't "open" on a windows machine, I think. An iso later compressed as zip, that would work (or rzip). Look at Productivity/Archiving/Compression, there are several programs there. You are at a better position to try than many of us are: I can't even test your problem, for instance. I think you have found a problem that should be addressed somehow... - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGCr1etTMYHG2NR9URArsWAJ9u1WIQ41Z05wnUiTHGIs8+tEdAawCfVuhn 4yReFWNQkuLBUizwIGubPys= =GJcL -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed 28 Mar 2007 19:09, Carlos E. R. wrote:
I think you have found a problem that should be addressed somehow...
- excuse me - wondered if UUENCODE might be relevant? friendly greetings -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2007-03-28 at 19:42 -0000, riccardo35@gmail.com wrote:
On Wed 28 Mar 2007 19:09, Carlos E. R. wrote:
I think you have found a problem that should be addressed somehow...
- excuse me - wondered if UUENCODE might be relevant?
I don't think so... - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGCwE8tTMYHG2NR9URAmO/AJ0TxsSGqydeFWhz9hIfxQ6tyo680gCfVpPz Z8FaQYryRm8fQWpZWQ2h7fs= =WTB7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2007-03-28 at 21:09 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Wednesday 2007-03-28 at 23:08 +0800, Zhang Weiwu wrote:
I have tried all of them (creating documents with RAR, gzip, bz2, zip, jar format created by Gnome's file-roller) and all of them opens shows junk file name on Windows (opened by 7-zip running on Windows).
I think you should also try different programs on both ends. It could be an inplementation problem, not an archive format problem (or not only).
However if I receive a document from a Windows user in tar, gzip, bz2, zip format (when testing, created by 7-zip Windows version), all of them opens junk file name on SuSE BUT if a Windows user send me RAR file (made with winRAR), open it in Linux, the file name is CORRECT.
And rar made with 7-zip in windows? If that is also incorrect, then the 7-zip client is the culprit.
7-zip cannot make RAR :~)
So: RAR file made on Linux doesn't contain charset information, RAR files made on Windows contain charset information.
A rar made with gnome roller. Try another tool; but I don't know which, rar is propietary. I wasn't even aware that we could make rars in linux (version 2 rar, I mean).
I am trying: maybe one version of rar have this charset problem solved and I simply didn't create RAR in the right version.
The only format acceptable to general Windows user I haven't tried yet is: CAB. This format can be opened by Windows 98/Me/2000/XP. I didn't try it because I cannot find a tool to make such archives. I can only find cabextract in SuSE repository which is used to open CAB format.
Posibly propietary.
Absolutely proprietary. But first a user (me) have to solve a problem, I can only prefer opensource format AMONG things I have tested works.
Still no solution.
A zisofs compressed iso? But it wouldn't "open" on a windows machine, I think. An iso later compressed as zip, that would work (or rzip).
Look at Productivity/Archiving/Compression, there are several programs there. You are at a better position to try than many of us are: I can't even test your problem, for instance.
I think you have found a problem that should be addressed somehow...
Ah, would appreciate any effort on solving my problem. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu 29 Mar 2007 02:14, Zhang Weiwu wrote:
Ah, would appreciate any effort on solving my problem.
uuencode/uudecode ____ - thank you Carlos - am sure you are right . . . I do recall seeing a few years back, Windows versions of uuencode/uudecode best wishes -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2007-03-29 at 05:56 +0000, riccardo35@gmail.com wrote:
On Thu 29 Mar 2007 02:14, Zhang Weiwu wrote:
Ah, would appreciate any effort on solving my problem.
uuencode/uudecode
Probably I didn't made my point clear but my request seems to have nothing to do with uuencode: As far as I understand uuencode make sure the files are byte-to-byte correct even transferred from/to/between hosts with different charsets. What we want is the file names are ideograph-to-ideograph correct, which means byte-to-byte correct is just what we want not happen, well actually byte number should not be equal, originally 3 bytes (per ideograph) on SuSE, when unpackaged in Windows we want it 2 bytes (per ideograph) only. Because in UTF-8 ideographs are usually 3 bytes each, in GB18030 should be 2 bytes. -- 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 05:56 -0000, riccardo35@gmail.com wrote:
uuencode/uudecode ____
- thank you Carlos - am sure you are right . . . I do recall seeing a few years back, Windows versions of uuencode/uudecode
Yes, me too. But his problem is with filenames, not the contents. uu...
were designed to email files converted into 7 bits text inserted into the
mail body. The filename was not enconded in the conversion, it was just
part of the conversion. The receiver end can use any name, I think:
cer@nimrodel:~> uuencode hola hola.uue
begin 644 hola.uue
M16X@=6X@;'5G87(@9&4@;&$@;6%N8VAA+"!D92!C=7EO(&YO;6)R92!N;R!Q
...
M
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2007-03-29 at 14:54 +0200, Carlos E. R. wrote:
The Thursday 2007-03-29 at 05:56 -0000, riccardo35@ wrote:
uuencode/uudecode
...
cer@nimrodel:~> uuencode hola hola.uue b e g i n 644 hola.uue <=== modified spacing M16X@=6X@;'5G87(@9&4@;&$@;6%N8VAA+"!D92!C=7EO(&YO;6)R92!N;R!Q
It appears that those lines triggered uudecode on servers of people reading the list, which broke - to be expected of a windows product, of course, serves them right :-P See, from "vesbridge-ex01.vesbridge.com": | Antigen for Exchange found Body of Message infected with | CorruptedCompressedUuencodeFile virus. | The file is currently Removed. The message, "Re_ _opensuse_ should I | prefer RAR format for deliverying file | to__ Windows users", was | sent from Carlos E. R. and was discovered in SMTP Messages\Inbound | located at Vesbridge/First Administrative Group/VESBRIDGE-EX01. | and from "DAEMSG03.eur.ad.sag": | Antigen for Exchange found Body of Message infected with | CorruptedCompressedUuencodeFile virus. | The file is currently Removed. The message, "Re: [opensuse] should I | prefer RAR format for deliverying file | | toWindows users", was | sent from Carlos E. R. and was discovered in SMTP Messages\Inbound And Outbound | located at SAG/DE/DAEMSG03B. It triggered both inbound and outbound, and it tells me that the uuencoded file I sent was broken... obviously, it was a partial file, a sample. Good piece of code! :-P - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGDBN/tTMYHG2NR9URAng5AJ9IoncBvUv11Hct1zvkATHBz/39AACeMq8y Zmwk+hHw/sgtMZoAH7Sy888= =h50C -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Carlos E. R. -
Dave Howorth -
J. Daniel Schmidt -
riccardo35＠gmail.com -
Roger Oberholtzer -
Simon Roberts -
Zhang Weiwu