I have tried all possible characters. It seems to be working fine now. Thank you for your prompt help a Microsoft customer could only dream of. :-) First I could not read the disc on a Windows machine. Probably, it was formatted in UDF version 2.01, which Windows seems not to support. Even installing Roxio UDF reader did not solve the problem. However, after I had reformatted the disc using cdrwtool, which probably defaults to 1.5, I was able to read the disc without any problems. Even all the diacritics came out perfectly correct. Now all the problems I mentioned in my first posting to this list have been more or less solved. l would also like to try Mt Rainer. I have bought a CD Burner that supports this functionality. However, the most recent patch I have been able to find is: http://www.kernel.org/pub/linux/kernel/people/axboe/patches/v2.4/2.4.19-pre4 /cd-mrw-2.gz which failed to patch my 2.4.20 kernel (and SuSE 2.4.19 kernel) as well. Is there a patch for one of these kernels? Robert Szelepcsenyi -----Original Message----- From: Ben Fennema [mailto:bfennema@attbi.com] Sent: Thursday, January 09, 2003 6:05 AM To: Robert Szelepcsenyi Cc: packet-writing@suse.com Subject: Re: Various problems with packet writing Ok, this should be fixed in CVS.. *crosses fingers* Ben Robert Szelepcsenyi wrote:
This is the only problem I have not been able to make any progress on at all. I resorted to experimenting on a hard disk partition, which I formated using UDF, to make sure it had nothing to do with packet writing (and save my burner and CD-RW media). I did the following test:
I set the samba server to 825 codepage (client side) and ISO-8859-2 charset (server side). I created files with various national characters in their names in my public_html directory. I listed the contents of the directory on my Windows machine, the web browser being set to ISO-8859-2 encoding. All filenames showed correct. In this way I verified that the samba server had done all the translations correctly and that the files had correct names in the ISO-8859-2 encoding.
Next I mounted a UDF volume with iocharset set to ISO-8859-2 and copied the files there. When I listed the contents of the directory, I got back rather different filenames. It seemed to me, that accented characters (that also exist in West European countries) were correct, but most of the other characters were mangled. However, without using the iocharset option I was not able to create some files at all.
Another problem was that I was not able to use UTF-8 and iocharset at the same time.
I would like to know, what takes care for the ISO-8859-x <-> UTF16 transcoding. It seems to me that the system lacks something for ISO-8859-2 and falls back to ISO-8859-1.
Thanks,
Robert Szelepcsenyi