Quote:
Originally Posted by BaldTrout
Having a little bit of trouble configuring FimFicFare and am hoping someone may be able to help. I'd like to setup custom columns, or some way to store the Author's URL and Story URL and have that URL be clickable and open up in a web browser.
|
I don't believe it's possible to make a clickable URL column. You'd have to ask about that over in the
Library Management forum.
On the other hand, FanFicFare (not Fim, BTW) already puts the story URL in as an
identifier and sets the author's URL by default. Both of which are clickable links in the Calibre's Book Detail pane (Shft-Alt-D in windows).
Quote:
Originally Posted by BaldTrout
I'm also having some trouble with epub images. I have a few stories that have images with transparency inside their chapters and have set remove_transparency: false in personal.ini like the github wiki suggests to keep the transparency... but it doesn't seem to work. Only no_image_processing:true works to keep the images transparent but I worry that will cause issues down the line. Is there another setting or code line I'm missing?
|
By default, images are resized to something reasonable for an epub reader like a Kindle or Nook. FanFicFare uses the image libraries provided by Calibre. It doesn't surprise me that it doesn't work in all cases.
no_image_processing:true is what I would suggest.
Quote:
Originally Posted by BaldTrout
I seem to have found a parsing bug too. With this story: https://www.fimfiction.net/story/358...ian-fanfiction there's colored text in block quotes. FanFicFare/Calibre can download the story fine, but doesn't write the <span style="color:#[color];"> tag in a way that properly colors the text.
... |
It's technically an HTML standards violation to put <p> tags inside <span> tags. It's meant to be the other way around.
Looking at the first page of that story more closely, the HTML is even more broken with tags interleaving instead of nesting properly. There isn't anything FanFicFare can do about bad input:
The HTML parser, seeing the tags out of order, automatically closes the <span> first. Browsers are more forgiving--and have hugely more complex code to process the HTML with.