AniDB

version 0.4.6.194

Titles including special characters leave certain files unusable to emule. Here are some examples:

29.03.2004 17:23:14: Failed to open d:\incoming\anime\Manie-Manie: Meikyu Monogatari - 1 - Movie + external subs [].avi () - No such file or directory
29.03.2004 17:23:14: Failed to open d:\incoming\anime\Manie-Manie: Meikyu Monogatari - 1 - Movie + external subs [].srt () - No such file or directory
29.03.2004 17:23:14: Failed to open I:\Anime\Full Metal Panic 2\\Full Metal Panic Fumoffu - 01 - The Man From The South / Lunch Time that Run Idle [Anime-Keep].avi () - No such file or directory
29.03.2004 17:23:14: Failed to open I:\Anime\Full Metal Panic 2\\Full Metal Panic Fumoffu - 03 - Artistic Hamburger Hill / Stake Out with all of One`s Heart [Anime-Keep].avi () - No such file or directory
29.03.2004 17:23:14: Failed to open I:\Anime\Full Metal Panic 2\\Full Metal Panic Fumoffu - 04 - Fetish That Has Been Touted / Patient Of The Darkness [Anime-Keep].avi () - No such file or directory
29.03.2004 17:23:14: Failed to open I:\Anime\Full Metal Panic 2\\Full Metal Panic Fumoffu - 05 - Pure and Impure Grappler / Trespass with Good Intentions [Anime-Keep].avi () - No such file or directory

It looks like anidb included some characters in the titles that do not suit the windows file naming conventions, and the client does not handle this situation correctly.

It's really an eMule bug, not an AOM bug. If it's an issue either a) report it to eMule team b) don't use special chars.

The file names all follow windows file naming rules, if not it wouldn't be possible to change the names (windows does not allow reserved characters when you rename via MoveFileW).
The : used is the math sign for ratio (unicode $2236), not a real colon (unicode $003A).
The / used is the math sign for division (unicode $2215), not a real slash (unicode $002F).

It looks like anidb included some characters in the titles that do not suit the windows file naming conventions, and the client does not handle this situation correctly.

The client does handle it correctly...Otherwise the files wouldn't be renamed at all.

You guys are really clever.

b) don't use special chars.

I noticed last night it's kinda hard to not use special chars.
Will fix so it's possible to disable them in the next release.

That would be cool. Maybe you could add an option to avoid all special chars, or map them to standard ascii, to stay compatible with ed2k. I noticed something similar in the options dialog. That option had no effect however.

eMule at least is smart enough to realize when ed2k links contain characters it doesn't recognize and replace those with - so there should be no compability problems.
If the autorenamer gives some of your files names that won't work I suggest you don't use it on those files or file a bugreport for eMule / the donkey you use.

The problem seems to be fixed with emule version 0.42.

I don't think so... I use eMule 0.42e and with "special chars" turned on I had a lot of "system cannot find the file specified" errors.