I'm studying up on CCS and ePub for now.
Just one more question,
Suppose I would put a link in the header and/or footer of every chapter, linking to the next and previous chapter. Is there a way to create a single line in CCS, or should I manually create the link in every chapter, in the HTML code?
CCS Seems to me some kind of code where you can specify the overall text, so you won't have to re-specify this same information within every HTML chapter of the epub.
Now most ebook readers I have, have internal fonts, and internally regulate fontsize, and neither do I find it necessary to specify external websites within an epub, as the devices don't connect to the web anyway, so I don't need to specify all those parameters in CSS, and can just get rid of them.
In fact, leaving it with a clean, stripped to the core, HTML might even be better.
For that reason I was thinking of not using CCS at all, removing any line of code that was not vital to a reading device.
Previously I even removed lines like the one I mentioned above, to save on HTML complexity, but I recoded my files with bookdesigner, and I don't know how BD modified the source HTML (perhaps added that info again when encoding to LRF files without my knowledge).
So, unless if I can use CSS to create some kind of code that will save me time in HTML code, and keeps the overall ePub file clean, I am thinking of getting rid of CSS altogether!
As far as removing the lines of code:
Code:
<?xml version="1.0" encoding="UTF-8" ?>
<container version="1.0"
Tell me, is there any other container version out there?
Any reading device I know automatically selects UTF-8 when not specified (even in HTML), and since there is only one container version, I presume each reading device presumes you're using this container version. None of the reading devices is equipped to read version 2.0, so to me it's like a useless line of code; as the device probably will automatically assume it's container version 1, and even if not, it will handle it as one; but further testing on that soon, once I've been able to create a basic ePub file.
I still have an Astak reader Pro, and Ectaco Jetbook Color to test my epub files on (unfortunately I switched my regular Jetbook for a Jetbook Color, so I no longer have that device for testing).
As far as replacing files in an existing epub, so far it has worked, just as long as I manually update the internal files, mentioning any change in chapters, titles, and file names and so on...