Quote:
Originally Posted by Zerubel
My second question - is it possible to tell Fanficfare to put tags like characters and pairings into custom columns and not add them to the epubs main tags? I've managed to do it with ao3's "genre" (aka freeform madness) into a text-only column, but if possible i'd still like to collect that data to browse characters and pairings without adding to the main clutter.
|
Yes. There's the GUI Custom Columns tab and the personal.ini
custom_columns_settings setting.
For historical reasons, the personal.ini setting that controls what goes into Calibre's Tags column is
include_subject_tags. Some sites also use
extra_subject_tags to add to it (from before we had
add_to_*).
Quote:
Originally Posted by Zu'l
I'm having same problem when trying to download fic from Royal Road (link https://www.royalroad.com/fiction/24709), how do you tell which chapter(s) are causing the 'maximum recursion depth exceeded' issue?
|
Run in debug mode and look at the log, or set
continue_on_chapter_error:true and look to see which chapter is marked ERROR in the ebook..
Quote:
Originally Posted by ackomb
The reason I don't want to check "New Only" is because I still want it to add newly added tags, I just don't want it to remove the ones I've added when I update a story. Since I'm assuming "New Only" applies to a new story and not a new tag.
|
You can use a
custom_columns_settings line with the
a flag set. From defaults.ini:
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