Multi-reply
Quote:
Originally Posted by ownedbycats
I do have a bit of custom stuff in my personal.ini to add "Oneshot" to my status column. I wonder if that could somehow be tripping up the anthology status code, but I'm not sure how. My anthologies do tend to consist of series of oneshots though.
|
If one of the books in an anthology gets your Oneshot status, the anthology will inherit it.
Quote:
Originally Posted by MarjaE
A couple problems I've encountered.
1. I use 2 tag columns, tags and #notes. Although I've set fanficfare *not* to wipe tags when it writes metadata, it still wipes #notes. Is there a way to get fanficfare to keep existing tags in any tags column?
|
If you use the GUI settings in FFF config under the Custom Columns tab to set #notes, you can also check the 'New only' checkbox. FFF will only write #notes on new downloads.
Or, you can use
custom_columns_settings in personal.ini to set it and change the mode to 'a' to add to existing values. (Must be enabled at the bottom of the Custom Columns tab first.)
From (plugin-)defaults.ini:
Spoiler:
Code:
## (Plugin Only) - You can also populate calibre custom columns with
## the site specific metadata using custom_columns_settings (but only
## if 'Allow custom_columns_settings from personal.ini' is checked in
## the plugin GUI config.) There are three parts, the entry name,
## then the label of the calibre custom column, then (optionally) a
## 'mode'. 'r' to Replace any existing values, 'a' to Add to existing
## value (use with tag-like columns), and 'n' for setting on New books
## only. (Default is 'r'.)
## Literal strings can be set into custom columns using double quotes.
## Each metadata=>column mapping must be on a separate line and each
## needs to have one space at the start of each line.
## 'r_anthaver' and 'n_anthaver' can be used to indicate the same as
## 'r' and 'n' for normal downloads, but to average the metadata for
## the differents story in an anthology before setting in integer and
## float type custom columns. This can be useful for a averrating
## column, for example. Default is to sum the values of all stories,
## and numChapters and numWords are always summed.
#custom_columns_settings:
# cliches=>#acolumn
# themes=>#bcolumn,a
# timeline=>#ccolumn,n
# "FanFiction"=>#collection
# averrating=>#averrating,r_anthaver
Quote:
Originally Posted by ownedbycats
2. I tried to switch from downloading as epubs to downloading as mobis. The resulting mobis crash my preferred reader app on my computer. I haven't tested them on my Kindle. I don't know how these differ from other mobis. Downloading as epub and then converting to mobi still works.
|
FFF's mobi output is ancient and honestly quite bad. It predates me joining the project and it is only still included for the benefit of CLI users who complained when I tried to remove it. I, myself, use Kindles and convert from EPUB on every download.
FAQ:
Why doesn't the MOBI output show chapters markers on the progress bar in Kindle or include images?
Quote:
FanFicFare's MOBI output is less than ideal--it doesn't include chapter markers, nor can it include images. These are complex problems because MOBI is much more difficult to work with than epub.
Given the fact that Kindle has moved on to a newer format (AZW3), it's unlikely FanFicFare's MOBI support is ever going to improve. Unless, of course, somebody who wants it gets involved as a developer and improves it.
Right now, our best suggestion is to download as EPUB and then convert to MOBI.
The Calibre plugin has an option to automatically convert new downloads or updates using Calibre's extremely good Convert feature.
|