[GUI Plugin] FanFicFare

[darth1]

Calibre 3.14 running ffd latest -3.25

and it wasn't doin this until I updated, but im runnin win7 home premuim

[JimmXinu]

Originally Posted by darth1

Calibre 3.14 running ffd latest -3.25

and it wasn't doin this until I updated, but im runnin win7 home premuim

Try the test version I just mentioned above. Link in my sig. It works in v2.85.1, so it should be fine in v3.14.

I generally only test against old versions when I have reason to believe there's an issue; and then only against the last of each major, so v2.85.1, v3.48 & v4.23.

[darth1]

Well that worked, Thanks Jim and such prompt reply too

I'm waiting for the newer cards to come down in price before I get a new PC this one has done what I've needed of it for 12-13 years so far, it was decently top tier when I bought It but the parents went cheap when thay got their own two years after and within 5 years I was obselte completely

[MerlinMama]

could you add squidgeworld.org? As far as I can tell, it is the old squidge.org/Peja WWOMB. I just received my email invite yesterday.

[JimmXinu]

That's.... AO3's software running on another site? Is that a thing? I didn't know that, but sure enough, there it is. How did I not know that before?

I'll definitely be looking into that, if for no other reason than to support fanfic sites using OTW; since eFiction is basically in zombie mode right now.

[JimmXinu]

New Test Version Posted

2020-11-14
- New Site: squidgeworld.org - shares code with AO3.

I don't have an account on squidgeworld.org, so I haven't tested login. FYI.

[Skittles8705]

Hi! i use Fanficfare to make mobis to send to my kindle fire but recently after the latest updates, none of the mobis i've recently made are being accepted by amazon through my devices email. Its always worked before. Is this a known issue? i've tried to re-install the plugin and then remake a mobi to send and I'm still getting an error saying amazon cant accept the type of files i'm sending.

[John Maverick]

Originally Posted by JimmXinu

New Test Version Posted
- adapter_scribblehubcom: Accept chapter URLs.
- adapter_wwwnovelallcom: Accept chapter URLs, must change to true storyId/URL after.

I only tested the scribblehub and novelall changes with a few example URLs--I don't read those sites, so I don't know what's common.

When giving adapter_wwwnovelallcom a chapter URL, it can't find the storyUrl until after it's downloaded that chapter page. There are a few other adapters that change the storyId and storyUrl like that, but they are rare. (I vaguely recall that it can sometimes cause some weirdness, but I don't remember what exactly.)

I tested with the stories updates received in my email and FFF accepted chapters urls for scribblehub and novelall. At least with the stories I folllow.

Again a lots of thanks for your hard work!!!

[JimmXinu]

Originally Posted by Skittles8705

Hi! i use Fanficfare to make mobis to send to my kindle fire but recently after the latest updates, none of the mobis i've recently made are being accepted by amazon through my devices email. Its always worked before. Is this a known issue? i've tried to re-install the plugin and then remake a mobi to send and I'm still getting an error saying amazon cant accept the type of files i'm sending.

FanFicFare's mobi output is very poor and I don't recommend using it, there's an FAQ about it. I, personally, download to epub and convert everything to azw3 to read on Kindle.

That said, I'm not aware of any difference in FFF's mobi output recently. The code was changed to be py2/py3 compatible back in April. It is possible that Calibre running on python3 now has introduced some subtle change.

However, I think it's equally like that Amazon has just randomly decided you can't do that anymore. What Amazon does and doesn't allow is not publicly defined and I have had the exact files pass through and be rejected at different times.

Short answer: I don't know anything that could help, sorry. I use epub->azw3 and USB side-load.

[ownedbycats]

Does FFF not use ebook-convert itself for mobi output? I guess changing it up would require some work though.

[JimmXinu]

New Test Version Posted

2020-11-15
- Add (optional, default on) convert support for data:image in-line <img>s.
- Add pass-through support for data:image in-line <img>s.
- Set default cover_min_size: 10,10 to avoid spacer images as covers.
- XenForo: Fixes for extra /s in some normalized post URLs.

This one is more 'test' than usual; especially for XenForo sites. You might want to save your previous installed version.

HTML can include images 'in-line', where the image data is encoded and included directly in the HTML. In past, FFF has handled this case... poorly.

Now, if it can, FFF will convert the in-line images to file images so that FFF's image processing can be applied and duplicate images shared. Since the first example given was a case of a 1x1 'spacer' image, I also set cover_min_size to default 10,10 now.

(This change was inspired by #596, but doesn't directly address the issue raised.)

While 'on' by default, it can be turned off--and in-line images will only be converted if base64 encoded. If you have examples of other encodings used 'in the wild', please let me know.

## In-line images (<img src="data:image/...;base64,...") are converted
## to files so the normal image processing can be applied, but only if
## base64 encoded.  Note that in-line images are also removed when
## include_images:false.  Also allows for in-line image to be cover.
## If set false, in-line images will be kept as-is.
convert_inline_images:true

Note that there isn't an option to go back to the old behavior; it was that broken. However, if enough people desire it, I could add a "don't include in-line images at all" option, which would be roughly equivalent.

[John Maverick]

Originally Posted by JimmXinu

New Test Version Posted

2020-11-12
- adapter_wuxiaworldco: added status #592 from Rikkitp
- Don't use polyglot, not included until Calibre3. Remove some debug output.
- adapter_scribblehubcom: Accept chapter URLs.
- adapter_wwwnovelallcom: Accept chapter URLs, must change to true storyId/URL after.

I only tested the scribblehub and novelall changes with a few example URLs--I don't read those sites, so I don't know what's common.

When giving adapter_wwwnovelallcom a chapter URL, it can't find the storyUrl until after it's downloaded that chapter page. There are a few other adapters that change the storyId and storyUrl like that, but they are rare. (I vaguely recall that it can sometimes cause some weirdness, but I don't remember what exactly.)

With adapter_wwwnovelallcom when downloading urls of different chapters of the same novel, FFF tries to update the novel multiple times. I didn't see the novels updates corrupted or anything for updating the same ebook multiple times, but it make the update take longer. Wich is a little annoying with longer novels, but nothing with I can't live.

It's possible that the checks that make sure the urls are unique are made on the chapters urls, instead of the deduced novel url.

I think this happens with any novel of novelallcom, but here is a example:

Novel url:

https://www.novelall.com/novel/Monster-Factory.html

Chaptes url of that novel:

https://www.novelall.com/chapter/Monster-Factory-Chapter-393/2003975/
https://www.novelall.com/chapter/Monster-Factory-Chapter-394/2003976/
https://www.novelall.com/chapter/Monster-Factory-Chapter-395/2004515/
https://www.novelall.com/chapter/Monster-Factory-Chapter-396/2005058/
https://www.novelall.com/chapter/Monster-Factory-Chapter-397/2005059/

If I try to paste these chapters url to FFF, or are taken by by FFF from my email, FFF will try to update, or download the novel 5 times.

But this don't happen with adapter_scribblehubcom.

My setup is the following:
OS: Linux Mint 19.3 Tricia x86_64
Calibre versión: 5.5
FanFicFare version: 3.25.5

If by any case this can't be easy solved, I don't mind it leave this behaviour, just so FFF can accept chapters urls.

Like always thanks in advance.

[JimmXinu]

Originally Posted by John Maverick

With adapter_wwwnovelallcom when downloading urls of different chapters of the same novel, FFF tries to update the novel multiple times. I didn't see the novels updates corrupted or anything for updating the same ebook multiple times, but it make the update take longer. Wich is a little annoying with longer novels, but nothing with I can't live.
...

You believe you already quoted the answer, it was just a bit vague :

Originally Posted by JimmXinu

- adapter_wwwnovelallcom: Accept chapter URLs, must change to true storyId/URL after.

When giving adapter_wwwnovelallcom a chapter URL, it can't find the storyUrl until after it's downloaded that chapter page. There are a few other adapters that change the storyId and storyUrl like that, but they are rare. (I vaguely recall that it can sometimes cause some weirdness, but I don't remember what exactly.)

Because the site doesn't include the storyId in the chapter URLs (it's common for the author to, but no guaranteed) FFF doesn't know the storyUrl until after fetching metadata and the plugin is currently coded to detect the duplicates before metadata fetch, but not after.

I know that there were reasons why FFF doesn't re-check, but I don't remember them off hand. I'll look into it, but I don't want to rush because the whole plugin-update edifice is a bit fragile.

[youonlyliveonce]

Has anyone failed to download from Wattpad? I have tried it many times but it failed. I copied the url from the address bar and pasted it into fff but always reported bad url

[JimmXinu]

It was also reported by a user on GitHub(#599).

However, because I don't see it, I believe it's Wattpad implementing a blocking mechanism of some kind. Whether that's for specific users who download 'too much', or 'badlist' IP ranges or what, I don't know.

I don't believe there's anything wrong with FFF, though.