[GUI Plugin] FanFicFare

[JimmXinu]

What he said.

Unrelated: Has anyone seen that problem with TtH updates lately?

[MGSaintz]

Originally Posted by JimmXinu

What he said.

Unrelated: Has anyone seen that problem with TtH updates lately?

Yes, usually if you follow the update link on your browser and then have FFF update it will go through as normal.

[JimmXinu]

Originally Posted by MGSaintz

Yes, usually if you follow the update link on your browser and then have FFF update it will go through as normal.

Ugh. From the silence I had hoped it had gone away.

Has anyone captured a debug log from the test version when a TtH update fails?

[firefoxxy]

Originally Posted by davidfor

For the word count and description, have a look at ...

Thank you david and Jim! I'll have a look into that thread.

[readerboy7]

I am experiencing a bug with FFF version 2.2.17, using calibre 2.48, shown below. Note that the example and explanation is a bit long-winded, sorry. I couldn't figure out how to effectively reduce the example.
[Edit:]: I re-downloaded the whole fic using most recent calibre (2.50.1), and problem still persists.[/Edit]
Here is a section from the fic The Scaly Raptor, from spacebattles. Note that I'm not using a quote box, due to formatting.

The scream woke the four recovering raptors downstairs, though only Blue could move as the other three were too injured to do so and laid in their "nests", frightened for their Alpha. Nonetheless, the raptor beta rushed up the stairs until she reached the room claimed by her Alpha and looked in to see a large, male raptor staring at something. Growling, Blue strode in as she guessed what had happened. "<Get away from Alpha, now...>"

Much to her surprise, the raptor turned and stared at her before it spoke in Owen's voice. "B-Blue? Did you just talk?"

Confused, Blue walked more into the room and tilted her head. "<Why do you sound like Alpha and make not-prey sounds?>"

The raptor then tapped himself on the chest. "Blue, it's me! I... I have no idea what happened, but I got turned into a raptor..."

Here is the same section, but from the epub copy I got using FFF.

The scream woke the four recovering raptors downstairs, though only Blue could move as the other three were too injured to do so and laid in their "nests", frightened for their Alpha. Nonetheless, the raptor beta rushed up the stairs until she reached the room claimed by her Alpha and looked in to see a large, male raptor staring at something. Growling, Blue strode in as she guessed what had happened. "<Get away from Alpha, now...>"

<Much to her surprise, the raptor turned and stared at her before it spoke in Owen's voice. "B-Blue? Did you just talk?"

<Confused, Blue walked more into the room and tilted her head. "<Why do you sound like Alpha and make not-prey sounds?>"

<<The raptor then tapped himself on the chest. "Blue, it's me! I... I have no idea what happened, but I got turned into a raptor..."

The italics persists throughout the rest of the chapter, before ceasing at the beginning of the next chapter. The number of '<' signs at the end of each line increases every time a '<' appears in the chapter. The '<' count also resets at the end of each chapter.
How might this problem be fixed?

[JimmXinu]

Originally Posted by readerboy7

I am experiencing a bug with FFF version 2.2.17, using calibre 2.48, shown below. Note that the example and explanation is a bit long-winded, sorry. I couldn't figure out how to effectively reduce it.
Here is a section from the fic The Scaly Raptor, from spacebattles. Note that I'm not using a quote box, due to formatting.

...

The italics persists throughout the rest of the chapter, before ceasing at the beginning of the next chapter. The number of '<' signs at the end of each line increases every time a '<' appears in the chapter. The '<' count also resets at the end of each chapter.
How might this problem be fixed?

I just downloaded it with default settings and I didn't see that problem. However, with replace_br_with_p: true in personal.ini, I do see that happen.

Unfortunately, I didn't write that feature and I frankly don't understand how it works. I'll send an email to the original developer of that feature, but I don't think I've heard anything from them in the last year.

In the meantime, you can remove/comment out replace_br_with_p: true or add replace_br_with_p:false to [forums.spacebattles.com].

You could also download the story from ffnet instead. It's not as far along, but it is being updated regularly.

[readerboy7]

Originally Posted by JimmXinu

I just downloaded it with default settings and I didn't see that problem. However, with replace_br_with_p: true in personal.ini, I do see that happen.

Unfortunately, I didn't write that feature and I frankly don't understand how it works. I'll send an email to the original developer of that feature, but I don't think I've heard anything from them in the last year.

In the meantime, you can remove/comment out replace_br_with_p: true or add replace_br_with_p:false to [forums.spacebattles.com].

You could also download the story from ffnet instead. It's not as far along, but it is being updated regularly.

So it's not a problem with default FFF (mostly) but that a fix for one rare issue (old fics) causes a break with a different rare issue (the '<' symbol appearing in fics). That's interesting, and I'm re-downloading the fic now.
Sorry for the noob question, but how do I look at the source code, specifically for that feature and the sections of the code it interacts with? I couldn't find it in the github page.
Edit: found what I think might be the specific page (def replace_br_with_p(body) on htmlheuristics.py), and I can see why you have difficulty with it. Ouch.

[Feynor]

Odd that I haven't seen this error before. I'll look at the heuristics now.

P.S.: I'd have loved to have had a slightly shorter story to test this on :P

That said, I get &lt; and &gt; into my heuristics code, and somewhere along the processing they get turned into < and >, now I just have to figure out where, because it's not something I intended.

Addition: The culprit seems to be Beautiful Soup. From the looks of it BS is not so beautiful after all, as it decodes the html entities, including &lt; and &gt;

[Feynor]

I just sent a fix to Jim.

[JimmXinu]

New test version posted (direct link).

Thanks Feynor!

2016-02-02
Add code for lazyload images in base_xenforoforum.
Correct outdated ini comment re *_filename.
Fix for replace_br_with_p(htmlheuristics) when author includes <>, thanks Feynor!
Update translations.

[fearofshorts]

Hey, every time I try to download or update a story hosted on fimfiction.net I get an "IncompleteRead" error, is there a fix for this? Maybe it's a case of the sites server derping up though...

Anyway, thanks very much for your continued work on this awesome program/plugin.

[JimmXinu]

Originally Posted by fearofshorts

Hey, every time I try to download or update a story hosted on fimfiction.net I get an "IncompleteRead" error, is there a fix for this? Maybe it's a case of the sites server derping up though...

I tried a story from the front page of the site and it worked fine for me. If it's still happening for you, please post a few problem story URLs.

It would also be helpful to see a debug log. Restart calibre in debug (under the calibre Preferences drop down), try the download, then quit calibre and it will give you the debug text you can post.

[saluli]

I was reading the topic and saw somebody using the plugin not only to assign a specific cover to each fandom, but also create a cover based by ship.

So, I am curious. It is possible to mix this? Like, use this cover on all Doctor Who fics, but if the ship is 10/Rose use this one? And how it would react if the fanfiction has more then one ship?

[JimmXinu]

generate_cover_settings lets you choose both a template of what metadata to use and the regex to compare to. And the first entry that has a regex that matches it's template is the one that will be used. So put more specific above less specific.

## If you have the Generate Cover plugin installed, you can use the
## generate_cover_settings parameter to intelligently decide which GC
## setting to run.  There are three parts 1) a template of which
## metadata part(s) to look at, 2) a regular expression to match the
## template, and 3) the name of the GC setting to use, which must
## match exactly.  Use this parameter in [defaults], or by site eg,
## [ficwad.com]
## Make sure to keep at least one space at the start of each line and
## to escape % to %%, if used.
## template => regexp to match => GC Setting to use.
## To use this, make sure you go to the Generate Cover tab in FanFicFare
## config and check 'Allow generate_cover_settings from personal.ini
## to override'
## You can check for an existing cover image in the metadata
## cover_image.  cover_image can be:
## specific -- The site has an image that is specifically this story's cover
## first -- The first image in the story or story desc is used as cover
## default -- A default_cover_image was used
## old -- There was already a cover image in the epub.
## This is useful because GC plugin can use the existing image.

# This is a bit simplified, but gets the point across.  
generate_cover_settings:
 ${category},${ships} => Doctor Who,.*Rose/10 => DrWhoRose10Cover
 ${category} => Doctor Who => DrWhoCover

[saluli]

Thanks, this was a very helpful explanation. It will really help not to do this case by case.