Bowerbird@aol.com wrote:
the name _has_to_ reflect the book itself, so there needs to be a _rootname_ that is unique to each book prefixing the filename. that allows different e-texts to live in the same folder, and that can come in handy.
Every OS in use today supports folders, so its best to completely ignore this feature. Lets throw all books into one folder and use the filename to sort them out. This has the added value of making the filename too long for 8.3 machines and ISO-9660. This way users of old machines can't even unpack the files and we won't get complaints that they are too big to view. It's a win-win situation.
since the "rootname" that p.g. has come to decide upon is the e-text-number, use that. so the name for the first scan in #14116 should be something like "14116-001.tif"
Please realize that the etext no. gets assigned immediately before the book is posted. I tried to have this changed, because IMO it is a bad process, but WWers wanted to keep it like it is. In consequence, if you want the etext no. as part of your filename, you'll have to graft it on after the book is posted. Basically your proposal has following advantages over mine: - you have to keep the files on hold, till after the book is posted (use more disk space) - you cannot post book and scans at the same time (more work) - you have to go back to the files some time after you scanned them and rename each one (more errors).
marcello's illustration-file in his djvu has this problem too. he inserted a graphic named "72-image.tif" within the files, but didn't have the corresponding blank-verso file as well.
That file is just a "remake" of the zipped collection of tiffs. I just wanted to test compression, djvu plugin, loading speed, and deep linking features. This file predates my RFC and so cannot be compliant with it.
note that a sort-order rule conflicts with marcello's suggestion that scans of the covers should be named as follows:
c0000.tif = front cover c0002.tif = inside front cover c0003.tif = inside back cover c0004.tif = outside back cover c0005.tif = spine
according to the binding-creates-a-specific-linearity model which we then emulate through judicious naming of the files, names for the back-cover scans should sort to the _bottom_.
Please cite correctly: I said MUST and not should be named, I use djvu files and not tiffs and my front cover is c0001 and not c0000. The reasons why I put them together and in front are: - having 2 different streams for front covers and back covers is overkill - nearer to the paper book experience: first thing you see is the front cover - its easier to print: assuming you want to print the covers at all you'll have to print them on the color printer - if you split the cover page stream where do you put the spine?
in the meantime, _my_ tools will be programmed to do things correctly...
in the *looooooooooooooong* meantime ... -- Marcello Perathoner webmaster@gutenberg.org