View Single Post
Old 02-04-2024, 10:39 AM   #9264
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
JimmXinu's Avatar
 
Posts: 7,025
Karma: 4604635
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
Quote:
Originally Posted by jessbbaby34 View Post
...
I saw once you said you didn't want public links to adult sites so I can DM specific examples if you want them.
...
It's less me and more MobileRead wants to stay family friendly. DM'ing me NSFW links is fine.

Quote:
Originally Posted by jessbbaby34 View Post
Huh, interesting idea about the author page. Is there a way to skip the checking for an author page?
I didn't write that adapter, but it looks like the only reason the author page is read is to get the story's category.

Most of the time, I don't like trying to code around site errors. In practice, I clicked to a dozen authors and didn't see a single story that wasn't category 'Bondage' on that site--the site's dedicated subject.

Plus the home page says it's a static copy of the site since Feb 22.

So I would not be hugely opposed to removing the author page fetch if you (meaning anyone who reads the site) will testify that they haven't seen other category values.

Quote:
Originally Posted by culytera View Post
Under what circumstances does ${origchapter} actually retain the original value instead of having the same value as ${chapter} since the latter is affected by chapter_title_x_pattern?
New chapter markings. Specifically, that's used to remove new chapter markings without needing to read the site again to get the chapter titles.

From defaults.ini:
Spoiler:
Code:
## If true, when updating an epub that already has old chapters, new
## chapters will be marked in the TOC and chapter header by using
## chapter_title_new_pattern and chapter_title_addnew_pattern to set
## the chapter title.
## If set to latestonly, only new chapters downloaded this time will
## be marked (new) and existing chapters will have any (new) marks
## removed.
##
## mark_new_chapters can be true, false or latestonly
mark_new_chapters:false

## chapter title patterns use python template substitution.  The
## ${number} is the 'chapter' number and ${title} is the chapter
## title, after applying chapter_title_strip_pattern.  ${index04} is
## chapter number padded with leading zeros (mostly for internal use)
## such as 0001.  ${index} == ${number} for backward compatibility.  A
## few site adapters add additional chapter metadata.

## The basic pattern used when not using add_chapter_numbers or
## mark_new_chapters
chapter_title_def_pattern:${title}

## Pattern used with add_chapter_numbers, but not mark_new_chapters
chapter_title_add_pattern:${number}. ${title}

## Pattern used with mark_new_chapters, but not add_chapter_numbers
## (new) is just text and can be changed.
chapter_title_new_pattern:(new) ${title}

## Pattern used with add_chapter_numbers and mark_new_chapters
## (new) is just text and can be changed.
chapter_title_addnew_pattern:${number}. (new) ${title}
JimmXinu is offline   Reply With Quote