when I burn files with names containing German Umlauts (for example "pelzmärtl.jpg"), the burned names are:
1.) displayed wrong in Windows Explorer;
2.) cannot be found by links anymore;
3.) raise an error message in cdrtfe, when "verify" is enabled.
Point 2.) is such a big disadvantage for me, that I sadly have to go back to Sonic and Nero (they do it right). I regret this, because I wanted to go away from Nero and Sonic and go to cdrtfe, because I like cdrtfe very much.
Point 3.) is listed in the help file as "known bug"
Details:
Using: Windows XP Home and cdrtfe 1.3.1.0.
ä is changed to o-with-tilde.
I tried different settings in "Extras" > "Einstellungen" > "cdrecord" > mkisofs, for example: -input-charset cp850 -output-charset cp850, without success.
Best regards,
Axel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
3.) (English) Settings: Dialog 'Filesystem'(?) -> 'General'(?) -> 'Codepage'(?):
leave 'Input Charset' blank, and set 'Output Charset' to cp850. (?) means,
this is how I translated the German words; I don't know, if cdrtfe uses these
words.
For me on a German Windows XP the following settings work:
Dialog 'Dateisystem' -> 'Zeichensatz': leave 'Input Charset' blank, and set 'Output Charset' to cp850. With this settings all German special characters (äöüÄÖÜß) were displayed correctly within the Joliet, UDF and ISO9660:1990 (ISO-Level 4) file system. Verified with ISOBuster.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I leave 'Input Charset' blank but set 'Output Charset', my cdrtfe doesn't burn anything. :(
Error messages from console window:
...
/cygdrive/C/Programme/cdrtfe/tools/cdrtools/mkisofs: Iconv based locales may change file name length.
/cygdrive/C/Programme/cdrtfe/tools/cdrtools/mkisofs: Cannot yet have different -input-charset/-output-charset.
...
Waiting for reader process to fill input buffer ... /cygdrive/C/Programme/cdrtfe/tools/cdrtools/cdrecord: Premature EOF on stdin.
/cygdrive/C/Programme/cdrtfe/tools/cdrtools/cdrecord: Input buffer error, aborting.
...
mkisofs -version is: 2.01.01a38
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have no idea why mkisofs behaves differently on your system. Are you using the binaries included in the cdrtfe installer or portable version? Or do you have any special settings regarding Windows?
My system: German Windows XP pro, ansi codepage 1252, oem codepage 850
Which file system settings are you using to create the discs?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I installed cdrtfe with the installer (filename: cdrtfe-1.3.1.exe), it's the non-portable version.
Windows is German XP home, unfortunately I couldn't find the informations regarding ansi-codepage and oem-codepage...Where can I find this?
I never changed the codepages.
File System:
General tab: Joliet, 103, nothing else;
ISO9660 tab: iso-level 4, nothing else;
Special tab: nothing;
At first I burned to DVD+R and now, for testing, I burn to DVD+RW. ;)
BTW, I'm using the cygwin.dll which comes with cdrtfe-1.3.1.
-- Axel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Open a DOS-Box and run the command chcp. The active oem codepage will be displayed.
I ran some tests (on a newly installed Windows XP pro under VMWare) and I had no problems using different codepages with mkisofs as long as no iconv functions were used. For my system the right settings were cp1250 as input and cp850 as output charset. Without input charset it worked, too. When a CD has a ISO9660:1990 file system Windows seems to use the active oem codepage.
Unfortunately, I have no idea why mkisofs doesn't want to convert between codepages in your case. Perhaps you could try other binaries or an older version of mkisofs before the icons support was introduced (mkisofs 2.01.01a27).
Regards,
Oliver
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you! This shows codepage: 850. Seems to be OK.
With a Ruby-script, I could get, that my system default codepage is 1252. (I couldn't get the oem, so chcp was what I still needed.)
So, my codepages seem to be the same as yours.
> mkisofs 2.01.01a27
I've difficulties to find precompiled binaries for this.
Could you send me your mkisofs.exe and the files from your folder: ...\cdrtfe\tools\cygwin\ ?
Or, maybe, everything of your ...\cdrtfe\ folder? (Excuse me, if it's a littlebit unhumble.)
I could try, if it works on my system and maybe I could find out, which part makes the difficulties.
Regards,
Axel
axel ? friedrich_smail @ gmx ? de
use '.' instead of ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you! This shows codepage: 850. Seems to be OK.
With a Ruby-script, I could get, that my system default codepage is 1252. (I couldn't get the oem, so chcp was what I still needed.)
So, my codepages seem to be the same as yours.
> mkisofs 2.01.01a27
I've difficulties to find precompiled binaries for this.
Could you send me your mkisofs.exe and the files from your folder: ...\cdrtfe\tools\cygwin\ ?
Or, maybe, everything of your ...\cdrtfe\ folder? (Excuse me, if it's a littlebit unhumble.)
I could try, if it works on my system and maybe I could find out, which part makes the difficulties.
Regards,
Axel
axel ? friedrich_smail @ gmx ? de
use '.' instead of ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
when I burn files with names containing German Umlauts (for example "pelzmärtl.jpg"), the burned names are:
1.) displayed wrong in Windows Explorer;
2.) cannot be found by links anymore;
3.) raise an error message in cdrtfe, when "verify" is enabled.
Point 2.) is such a big disadvantage for me, that I sadly have to go back to Sonic and Nero (they do it right). I regret this, because I wanted to go away from Nero and Sonic and go to cdrtfe, because I like cdrtfe very much.
Point 3.) is listed in the help file as "known bug"
Details:
Using: Windows XP Home and cdrtfe 1.3.1.0.
ä is changed to o-with-tilde.
I tried different settings in "Extras" > "Einstellungen" > "cdrecord" > mkisofs, for example: -input-charset cp850 -output-charset cp850, without success.
Best regards,
Axel
With the help of Oliver, we could find a way to solve the problem ("burning
files with names containing German Umlauts").
What works, at least for me:
1.) Installing cdrtfe 1.3.1 (the newest one available today)
2.) Replace
3.) (Deutsch) Settings: Dialog 'Dateisystem' -> 'Allgemein' -> 'Zeichensatz':
'Input' leer lassen, 'Output': cp850.
3.) (English) Settings: Dialog 'Filesystem'(?) -> 'General'(?) -> 'Codepage'(?):
leave 'Input Charset' blank, and set 'Output Charset' to cp850. (?) means,
this is how I translated the German words; I don't know, if cdrtfe uses these
words.
Other settings I use are:
File System:
General tab: Joliet, 103, Output: cp850, nothing else;
ISO9660 tab: iso-level 4, 31 characters, nothing else;
Special tab: nothing;
Windows is German XP home;
Axel
For me on a German Windows XP the following settings work:
Dialog 'Dateisystem' -> 'Zeichensatz': leave 'Input Charset' blank, and set 'Output Charset' to cp850. With this settings all German special characters (äöüÄÖÜß) were displayed correctly within the Joliet, UDF and ISO9660:1990 (ISO-Level 4) file system. Verified with ISOBuster.
When I leave 'Input Charset' blank but set 'Output Charset', my cdrtfe doesn't burn anything. :(
Error messages from console window:
...
/cygdrive/C/Programme/cdrtfe/tools/cdrtools/mkisofs: Iconv based locales may change file name length.
/cygdrive/C/Programme/cdrtfe/tools/cdrtools/mkisofs: Cannot yet have different -input-charset/-output-charset.
...
Waiting for reader process to fill input buffer ... /cygdrive/C/Programme/cdrtfe/tools/cdrtools/cdrecord: Premature EOF on stdin.
/cygdrive/C/Programme/cdrtfe/tools/cdrtools/cdrecord: Input buffer error, aborting.
...
mkisofs -version is: 2.01.01a38
I have no idea why mkisofs behaves differently on your system. Are you using the binaries included in the cdrtfe installer or portable version? Or do you have any special settings regarding Windows?
My system: German Windows XP pro, ansi codepage 1252, oem codepage 850
Which file system settings are you using to create the discs?
First of all, thank you very much for your help.
I installed cdrtfe with the installer (filename: cdrtfe-1.3.1.exe), it's the non-portable version.
Windows is German XP home, unfortunately I couldn't find the informations regarding ansi-codepage and oem-codepage...Where can I find this?
I never changed the codepages.
File System:
General tab: Joliet, 103, nothing else;
ISO9660 tab: iso-level 4, nothing else;
Special tab: nothing;
At first I burned to DVD+R and now, for testing, I burn to DVD+RW. ;)
BTW, I'm using the cygwin.dll which comes with cdrtfe-1.3.1.
-- Axel
> Where can I find this?
Open a DOS-Box and run the command chcp. The active oem codepage will be displayed.
I ran some tests (on a newly installed Windows XP pro under VMWare) and I had no problems using different codepages with mkisofs as long as no iconv functions were used. For my system the right settings were cp1250 as input and cp850 as output charset. Without input charset it worked, too. When a CD has a ISO9660:1990 file system Windows seems to use the active oem codepage.
Unfortunately, I have no idea why mkisofs doesn't want to convert between codepages in your case. Perhaps you could try other binaries or an older version of mkisofs before the icons support was introduced (mkisofs 2.01.01a27).
Regards,
Oliver
> chcp
Thank you! This shows codepage: 850. Seems to be OK.
With a Ruby-script, I could get, that my system default codepage is 1252. (I couldn't get the oem, so chcp was what I still needed.)
So, my codepages seem to be the same as yours.
> mkisofs 2.01.01a27
I've difficulties to find precompiled binaries for this.
Could you send me your mkisofs.exe and the files from your folder: ...\cdrtfe\tools\cygwin\ ?
Or, maybe, everything of your ...\cdrtfe\ folder? (Excuse me, if it's a littlebit unhumble.)
I could try, if it works on my system and maybe I could find out, which part makes the difficulties.
Regards,
Axel
axel ? friedrich_smail @ gmx ? de
use '.' instead of ?
> chcp
Thank you! This shows codepage: 850. Seems to be OK.
With a Ruby-script, I could get, that my system default codepage is 1252. (I couldn't get the oem, so chcp was what I still needed.)
So, my codepages seem to be the same as yours.
> mkisofs 2.01.01a27
I've difficulties to find precompiled binaries for this.
Could you send me your mkisofs.exe and the files from your folder: ...\cdrtfe\tools\cygwin\ ?
Or, maybe, everything of your ...\cdrtfe\ folder? (Excuse me, if it's a littlebit unhumble.)
I could try, if it works on my system and maybe I could find out, which part makes the difficulties.
Regards,
Axel
axel ? friedrich_smail @ gmx ? de
use '.' instead of ?
OK, one step ahead:
"ISO-Level-3" -> works
while
"ISO-Level-4" -> wrong
Other settings unchanged:
singlesession
onthefly
DAO
Joliet (103)
Rockridge OFF
UDF OFF
cdrtfe 1.3.1.0, without changes.
Regards,
Axel