Putting "#" char into book title seems to be a No No.

gkbeer · 10-24-2010, 11:26 PM

I'm up to date with the software as of today. And spent some time messaging the meta-data. I suffixed some titles of a series to include "#1" 2,3,4...

Storm From #1 vs. Storm Front [1]

When I attempted to open one of those books via the content server. There were several python errors. When I tried to open the file directly, the OSX finder complained that the file was not to be found. This despite that I had clicked directly on the icon in the finder.

Obviously the "If it hurts when you do that..." rule seems to apply.

Is this a calibre bug? Or something to do with unix file naming in general?

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
"Settings," then "311" - Int'l Kindle searches for wireless providers in the area	Dr. Drib	Amazon Kindle	2	08-28-2011 10:27 AM
Sony's Response To New Kindle: Not Chasing "Cheapest E-Reader" Title	m-reader	News	74	08-10-2010 03:15 PM
Crash on nonexistent "title" metadata element	Valloric	EPUBReader	3	12-10-2009 01:46 PM
Synchronising "Book" and "Code" views	HarryT	Sigil	2	08-11-2009 07:07 AM
New "E-Book Devices" "Bookeen Opus" forum desired	ericch	Bookeen	3	08-06-2009 06:31 PM

10-24-2010, 11:26 PM	#1
gkbeer Enthusiast Posts: 27 Karma: 30 Join Date: Mar 2006 Device: Kindle, iPod Touch,	Putting "#" char into book title seems to be a No No. I'm up to date with the software as of today. And spent some time messaging the meta-data. I suffixed some titles of a series to include "#1" 2,3,4... Storm From #1 vs. Storm Front [1] When I attempted to open one of those books via the content server. There were several python errors. When I tried to open the file directly, the OSX finder complained that the file was not to be found. This despite that I had clicked directly on the icon in the finder. Obviously the "If it hurts when you do that..." rule seems to apply. Is this a calibre bug? Or something to do with unix file naming in general?