more goofy characters in filenames affecting jobs

[nylonoxygen77]

Hey Mike, I had a file with the trademark (tm) character in the filename. It caused the entire job to error with the message 'Job not submitted. PresSTORE returned error "invalid command name "::xotcl::__#2O"". Exiting' I just happened to notice the tm character when I went to manually restore the files in the PresStore browser, so I figured I would check and see if that was the problem. After removing the line with the tm character from the restore queue file, the job went right through and completed successfully. Not sure exactly how to handle this, that character is one that probably has to be escaped with an ascii code or something.

[szumlins]

Doing some digging, it looks like I'll have to regex the string and replace with the Unicode characters. From what little digging I've done, I found some unicode maps. Probably won't have time to play with this for a bit, but adding them here so I have them for notes.

trademark = ™ = ™ (or ™ ) 
registered trademark = ® = ® 
service mark = &#8480 = ℠ 
copyright = © = © 
sound recording copyright = ℗ = ℗ 

[briansumma]

I'm not sure that the error is actually caused by bad characters (although it doesn't help). Rather I think it happens when you have several files submitted for archive and anyone of them fires back the error "handle could not be resolved: unknown path: ...". For instance, I recently saw the error "invalid command name "::xotcl::__#KJ" on a batch of 14 files that only used alpha numeric characters.

BTW this happens with Mike's script and the awcli.sh script included with PresSTORE at /usr/local/aw/etc.

I think the solution may be to capture the handle given to the file at the time it is archived and save it back into CatDV to use later when you want to restore the file.