You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are you using the CLI, web service or calibre plugin?
CLI and web service
What is the story URL?
http://archiveofourown.org/works/41844
What is the output format you used?
html, epub, mobi
What steps will reproduce the problem?
simply typing in the url and downloading
What is the expected output? What do you see instead?
I want to keep the <hr>, or at least have some space between text and summary
(especially chapter summaries), but there is none. I tried using replace_hr:
false or even replace_hr: true, but it doesn't work, and I don't have the
python knowledge to know what to do. Couldn't find it in FAQ. Is the output
supposed to be without any horizontal line?
What version of the product are you using? On what operating system?
fanficdownloader-4.4.28 , ubuntu 12.04
Thank you.
Original issue reported on code.google.com by amelie...@web.de on 13 Oct 2012 at 4:41
The text was updated successfully, but these errors were encountered:
FFDL does preserve <hr> tags in the story text. That's literally why I first
got involved with the project--to keep the <hr> tags.
If you're talking about the line under the 'Summary:' and 'Notes:' titles on
AO3, those are style "border-bottom: 1px solid;". Styles are, for the most
part, stripped for consistency between stories, sites and eReaders.
The leading and trailing chapter and author notes from AO3 are blockquote tags.
You can use output_css parameter in personal.ini to add style to blockquote if
you want borders or additional space.
Original comment by retiefj...@gmail.com on 13 Oct 2012 at 6:09
Yes, I meant the line under "Summary" and "Notes". I blindly assumed those were
<hr> as well. My bad.
I'll do what you suggested and change blockquote style. I hadn't thought of
that. I was thinking I'd probably have to add margin for <div> and <table>.
Thank you!
Original comment by amelie...@web.de on 13 Oct 2012 at 6:38
Original issue reported on code.google.com by
amelie...@web.de
on 13 Oct 2012 at 4:41The text was updated successfully, but these errors were encountered: