[abcde] Re: Bug#69411: abcde: Certain CDDB entries cause an mp3 file save error

[Robert Woodcock <rcw@debian.org>]

On Sat, Aug 19, 2000 at 03:41:47AM -0500, Peter Samuelson wrote:
> When you have two TITLE0 fields it is equivalent to a single TITLE0 two 
> lines long.  This should be supported.  (Not that I've checked.)

Yes, it is.

> > and I removed all colon (:) characters from the file (Does FAT
> > support (:) in a filename? I doubt). Then, it worked.
> 
> No, FAT doesn't.  Unix filesystems allow all characters except '\0' and
> '/' but of course the innovative Microsoft filesystems do not.  I think
> it's reasonable for a program to assume that a filesystem is sane,
> i.e. every program out there shouldn't have to have a fallback for when
> open() fails due to illegal characters like ':'.
> 
> In other words, if you "fix" abcde to mangle your filenames to fit with
> weird limitations like those Microsoft imposes, should you also fix the
> other 4999 Debian packages to do the same?
> 
> A better solution is to mount your FAT32 partition as UMSDOS.  That way
> "illegal" filenames are mangled automatically.

Ugh.

I knew :'s wreaked havoc on Windows when being shared through Samba, but I
didn't know they couldn't be created on FAT at all. That's disturbing :)

As a workaround you can redefine mungefilenames() to eat colons or translate
them to something else.

Perhaps abcde should translate colons by default (but to what?) - especially
since very few of those other 4999 Debian packages like to automagically
generate colons in filenames on a constant basis.
-- 
Robert Woodcock - rcw@debian.org
"Napster? What's Napster?" -- Lars Ulrich

To unsubscribe: echo unsubscribe | mail abcde-request@whimsica.lly.org