Quote:
Originally Posted by DLSieving
I'm avoiding the use of numbered sections and chapters so that no conversion algorithm for any publishing platform going forward will be able to easily figure out what I'm trying to do and impose its own structuring.
<SNIP
I'm afraid you've got the wrong end of the stick on this point. I learned from Guy Kawasaki (APE author) to polish my use of styles in the source document before proceeding to the publishing tools, which is what I did.
|
I've read Kawasaki, and I've seen (and used for experimentation purposes) his templates, for Word
and for INDD. Now, I'm going to say this and then shut up, as you seem to think that anything I say to you that conflicts with what you've inferred, is wrong, but there's absolutely no "platform-structuring" that will be "imposed" by some retailer. NONE OF THEM do that. The only thing that I know of that does some type of "auto-structuring" is Calibre,
which isn't a platform. Neither Amazon, iBooks, B&N, or any other retailer, impose structure, or do anything based on what headers you do or don't use. That's why everyone here--with probably, I dunno, 10,000 total books under their collective belts--are fuddled by your process. Because it seems to be designed to get around a system that is not only non-existent now, but has no implementation in the foreseeable future.
Quote:
|
Wrong again, I'm afraid. I'm finding the best long-term solution to each problem as I encounter it. Covering my tracks where automated conversion tools might otherwise intrude is an example of this. I like the results and it will save me a lot of work down the road.
|
OK. Well, obviously, I'm not going to be useful to you. If you're going to talk about CALIBRE, as an "automated conversion tool," that's one thing. But that has NOTHING to do with the platforms. And frankly, 5 minutes of regex would resolve any Calibre-imposed structure, and lastly, even THEN, it doesn't impose it unless you don't bother to spend an hour or so learning it.
Done now. BTW, font foundries don't really make a distinction between an "ebook license" and "redistribution." You want to subset the font, fine, but you may wish to be aware that foundries don't have text in their licensing requirements exempting licensing
if the font is obfuscated.
I'll leave the folks in the Workshop to it.
Hitch