Quote:
Originally Posted by jesscat
Yes that works perfectly now!  |
Glad that's fixed it.
Quote:
Originally Posted by jesscat
Now another question... Is there anywhere that the bookmark features for AO3 series bookmarks is retained, since AO3 permits bookmarking of series as well as individual stories? Sometimes I don't bookmark all x stories in a series, but just the series, so it would be nice if I could use this to populate my #my_bookmarks column for anthologies.
Or maybe if not (I'm thinking maybe it's not possible if AO3 is the only archive that has these features?) perhaps is there a way to use the bookmarked status of one of the stories in the anthology to trigger a "bookmarked" status for the entire anthology?
|
Bookmarks on works are on a page we already load. Detecting series bookmarks would require another page we don't already load. I'd prefer not to add that overhead unless there's more than one user wants it--it's a bit esoteric.
Series URLs for anthology epubs are loaded using the generic 'Get Story URLs from Web Page' feature which doesn't parse for site-specific info.
Quote:
Originally Posted by jesscat
I really love the logpage feature in the epubs, but there doesn't seem to be a lot about it in this thread. I've modeled mine after your example, and it works great. But what I'd like to include in my update log is the actual text in the "Comment" field of the log that calibre provides when it does an update and then lets me view the log before making the changes to my library - something like:
...
Is there a metadata field or other way to access this? I don't see one in default.ini.
|
The
logpage feature didn't get a lot of discussion because, until now--to the best of my knowledge--nobody but me used it.
The download 'comment' isn't metadata collected about the book. In fact, it isn't generated until
after the output file has been written. Because if FFF failed to write the output file, that's where it would report it.
If you're interested, here's a snippet from my personal.ini. I use an extra entry to explicitly mark when an epub has been overwritten, plus there's words_added which... may not be documented anywhere.
Spoiler:
Code:
[epub]
include_tocpage: false
include_titlepage: true
include_logpage: smart
logpage_entries: fulldownload,title,storyUrl,series,author,category,genre,rating,warnings,description,dateCreated,datePublished,dateUpdated,numChapters,numWords,words_added,status,version
keep_summary_html:true
make_firstimage_cover:true
# so overwrite downloads have some marker.
add_to_extra_valid_entries:,fulldownload
include_in_fulldownload:title
fulldownload_label:New Download
add_to_replace_metadata:
fulldownload=>^.*$=>Yes