SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

Special-Characters-Handling

#1

Hi there,

sorry me again :slight_smile:
got SongKong running on my Server (Debian) and am happy about nice folders and filenames i have now. But I have a problem in combination with windows-hosts in my network.
Just a little example:
i got a file named:

001 - Would I Lie to You?.mp3
002 - There Must Be an Angel (Playing With My Heart) (Ft. Stevie Wonder).mp3
003 - I Love You Like a Ball and Chain.mp3
004 - Sisters Are Doin' It for Themselves.mp3
005 - Conditioned Soul.mp3
006 - Adrian (Ft. Elvis Costello).mp3
007 - It's Alright (Baby's Coming Back).mp3
008 - Here Comes That Sinking Feeling.mp3
009 - Better to Have Lost in Love (Than Never to Have Loved at All).mp3

Displaying, playing, editing, copying, … on th server is no problem (even if i was surprised that the questionmark is allowed at all). But a large number of clients in my network are windows hosts (xp to 8.1) that access the library via SMB. Those are not able to handle those characters in filename.
That results in a directorylisting like that:

0GW63I~Y.MP3
002 - There Must Be an Angel (Playing With My Heart) (Ft. Stevie Wonder).mp3
003 - I Love You Like a Ball and Chain.mp3
004 - Sisters Are Doin' It for Themselves.mp3
005 - Conditioned Soul.mp3
006 - Adrian (Ft. Elvis Costello).mp3
007 - It's Alright (Baby's Coming Back).mp3
008 - Here Comes That Sinking Feeling.mp3
009 - Better to Have Lost in Love (Than Never to Have Loved at All).mp3

I allready saw those folders some times before and not thought a lot about that. I just thought maybe SK had issues renaming the file, and renamed them manually with the help of the id3-Tag. But today i analyzed it a bit more and found out, that SK did rename them realy fine, but windows does the crap (or maybe the samba-implementation).

Well i don’t know how SK would be behave when directly running on a windows host, maybe someone could test that with a track that has those characters in name.

My question is now, how can I avoid that? i already have character-simplification turned on. Without any success. In the help you say “? will be replaced with <” i am sure, that would fail on a windows-host, too, exactly like “:”. I tried to rename a file on windows and it tells me, the following characters are definitely not allowed (dunno if that are realy all forbidden, or if they only think no one would use any others )

Could you offer an option to replace/delete those characters, or a substitution-table (maybe allready filled with some characters) to make it fully compatible for those poor guys hanging on the M$-Operating System? :slight_smile:

Thanks and regards

PS: i am currently working on a clean translation of the german-languish-file, but i think i will still need some days/weeks as it is realy A LOT of text :slight_smile:

#2

I think the problem is that you are running SongKong on Linux so when renaming files it complies with Linux filenaming restrictions, but then you are accessing the files via WIndows and some of the filenames are not compatible with Windows.

If you ran SongKong from Windows and renamed the files hosted on Linux via Windows then it would comply with Windows renaming restrictions. The Simplify non-standard chars is intended to use simpler more compatible characters where possible (i.e removing accents where possible) but it doesnt consider the differences between different Operating systems, it consider this or we could have a substitution-table (like we do in Jaikoz)

Ive raised:
http://jthink.net:8081/browse/SONGKONG-756

I’m still a bit surprised though that your Windows client does not handle linux filenames that are invalid for Windows though, you might be able to fix this by using a different Windows client.

#3

Hi Paul,

the problem is, that my “client” is the standard-Explorer and also other file-commanders is connect to the host to.

Also when i access via ftp i can’t copy the files, as the ftp-client tells me, that those filenames can not be stored.

I have licensed both (SongKong and Jaikoz) but switched for the most work to SK. as configuration of jaikoz was bit too complex for me in the beginnig and my fear to retag-destroy my library because of a bad configuration in jaikoz was too big :slight_smile:

also i switched to the linux-server as tagging-machine because I had stability-issues on windows-hosts, the tagger just closed after some hours of work and i was not able to find out why. the most simple solution was to switch over to a stable OS and et voila it runs rockstable under debian :slight_smile:

thanks Thomas