I use the same style sheet for all books, but actually copy it to each ebook's directory, so there are currently around 850 copies of the same style sheet. But it is trivial to update them all from the master.
That seems like a horrible waste of inodes. I feel this pain, because I ran out of inodes on one of my arrays working on some PG works, even though I had 50GiB of space free on the drive. I had to reformat with more inodes to work around the problem.
It still uses more space, but the alternative, having all the html files link to a single css doesn't allow for zipping and downloading.
Here's an easy solution: In each .zip, you include a copy of the stylesheet, the same stylesheet you include with every copy... except, when you unzip the works, they go into a structure like this: Gutenberg/ |-- books | |-- Book_One.xml | `-- Book_Two.xml `-- styles `-- Gutenberg.css Every .zip that you unzip into there, will overwrite Gutenberg.css with the copy that you duplicate inside each .zip file, and the .xml (or .html or text or whatever) versions of the books go into a separate subdir. In your .xml files, you use the standard <base url="..."> clause or simply point your style declaration to ../styles/Gutenberg.css. This is exactly how it works on the Web in general, for very similar projects. Did that make sense? David A. Desrosiers desrod@gnu-designs.com http://gnu-designs.com