View Single Post
Old 09-02-2012, 05:02 AM   #10
unboggling
Wizard
unboggling ought to be getting tired of karma fortunes by now.unboggling ought to be getting tired of karma fortunes by now.unboggling ought to be getting tired of karma fortunes by now.unboggling ought to be getting tired of karma fortunes by now.unboggling ought to be getting tired of karma fortunes by now.unboggling ought to be getting tired of karma fortunes by now.unboggling ought to be getting tired of karma fortunes by now.unboggling ought to be getting tired of karma fortunes by now.unboggling ought to be getting tired of karma fortunes by now.unboggling ought to be getting tired of karma fortunes by now.unboggling ought to be getting tired of karma fortunes by now.
 
Posts: 1,065
Karma: 858115
Join Date: Jan 2011
Device: Kobo Clara, Kindle Paperwhite 10
Quote:
Originally Posted by travger View Post
OK, I have some thoughts:

'Assessing Formats' - Bulk Convert to Preferred Format.
Seems a bit pointless to me. Pros - makes nice uniform library.
Cons - 1. Book that I fix today and feel happy about coloring headings purple may seem rather ghastly few years hence.
2. Any conversion may lose or add something (I'm presently reading a mobi book where there's no blank lines for the scene breakes, I doubt that they will appear after conversion. This particular book has such a twisted css that I must uglify very nice ePub in order to replace some code especially for the conversion to mobi. In this case I'll keep both nice formats).
3. When I don't read the book immediately, leaving original format be saves lot of time - just quick quality check is all.
4. By the time I get around to reading it, several things may have happened: I may have found better quality/preferred format; I may have gotten new reading device; my html skills will definitely increase.
5. Maybe next book in the series has different but nicer formatting, then I can change first one more easily, having an example.

Fixing Formats - Convert to Editable Format
IMHO converting anything html to word and back is not good practice. Editing for example ePub in Sigil is much more under control, it won't accept mistakes, and you can see right away the change (and maybe undo it).

Editing Metadata - Title
I prefer shorter title. Probably it's subconcious answer to Windows path length limit. A friend gave me his zipped library, and many books there were unextractable because the title was too long.

Maintenance -
Maybe warning about not to mess around directly in the Calibre folders should be capitalized?
@travger. Thank you for the feedback. It helps me. A lot.

Assessing Formats - Bulk Convert.
I will clarify what options I use in conversion. The issues of bulk convert and deleting original format both need careful reconsideration. I'll at least add some discussion of pros/cons for each of those issues, both of which I've seen discussed here more than a few times. I vaguely recall we also talked about some of this last year, and revisiting these issues now from the perspective of a year's additional experience will be good.

Fixing Formats - Convert to Editable Format
I agree, that needs some clarification and rethinking too. I've been learning HTML, CSS, and Sigil gradually and am probably to the point where I should ditch fixing in Word, OpenOffice, or LibreOffice in favor of preferably fixing in Sigil in my real-life workflow. In the workflow document I was thinking of changing the simple fix example from Word back to OpenOffice, but first I need time to figure out and test how to anchor graphics to paragraphs in OpenOffice. I wanted to use a simple example. And I wish I'd started learning ins and outs of Sigil sooner. I'll rewrite this section into at least 2 fix subsections, one for Sigil fix, one for OO fix.

Editing Metadata - Title & filename lengths
Yeah, Windows filenames does throw a wrinkle into long titles. And I suppose also long series names, when those are included in saves/sends. It's been years since I used Windows and I simply forgot…. Now you pointed it out and I read this Naming Files, Paths, and Namespaces, (Windows Dev Center) I realize I should change how I deal with title addendums and long series names such as with hierarchical series subgroups, since we all might as well try to be interoperable as possible with filenames, for principle's sake if nothing else. For Title, off the top of my head: only append very short items such as " - 3 Ed" or " - ARC" to make title more unique for editions. And put any omnibus elements into their own empty book wishlist record, rather than appended to title. And put long title addendums in custom column Note. For Series, I need to think about it some more, and test some templates for truncating and abbreviating - - and I can probably use or adapt one of chaley's examples from calibre user manual section on Template Language. This issue is probably why he used that particular example in the first place.

Maintenance - Calibre Library Folders
Done. Made entire paragraph bold - at least until I think of some other way to emphasize it significantly but more subtly (if that's even possible….)

It may take a few days to a week before any of these other changes (and subsequent dependent changes) go into effect in the document. My general rule is that any changes in the document get tested and worked into my real-life workflow first. Though to my regret and later rework, on some occasions I screwed up by including something I hadn't tested sufficiently. Such as un-KISS series numbering for Complex Series (in Edit Metadata section), that I'd tested with insufficient number of cases when overly tired. Which I just somewhat fixed, and probably still needs more work along with the other series conventions toward being simpler. (The more specific I get, the more I get in trouble….)

travger, thanks again for the feedback.

@all, you're welcome to chime in with discussion, comment, feedback.



Edit: So what is a good compromise on title or series name length, taking into account the whole path with filename needs to fit into what, 260 char? - Would you say 40 char for title? Seems too short…. Oops, let's see. Would also need path including title + series + series_index. So series name saved or sent by template needs to be a very short abbreviation derived from longer string in Series column.

Last edited by unboggling; 09-02-2012 at 07:28 AM. Reason: minor corrections & last question
unboggling is offline   Reply With Quote