From: Andreas R. <and...@gm...> - 2012-01-22 21:15:45
|
Dear all, while testing Ardour's (www.ardour.org) TOC file generation routines, I found that while cdrdao uses the backslash in TOC files for escaping double quotes and allowing for octal notation of characters it *does not* allow the backslash itself to be escaped. To avoid any trouble a program generating a toc file will have to write a normal backslash in octal notation. Which is fine, but probably should be documented. No what I have trouble with is that cdrdao does not do that itself when writing a toc file while reading a CD. Example: Use any toc/wav image with CD text you have around, change the CD title to: TITLE "MyTestDisc\134" The \134 will be correctly interpreted as backslash and written as such onto your CD. Now when you rip the same CD with cdrdao, the resulting toc has: TITLE "MyTestDisc\" which, when fed to cdrdao will break the toc parser. Is there any specific reason of this behaviour? Are any programs using cdrdao relying on this behaviour? And if not, what's the best place to upload a patch? Best regards Andreas |