search

dipu-bd / lightnovel-crawler

Generate and download e-books from online sources.
https://pypi.org/project/lightnovel-crawler/
GNU General Public License v3.0
1.48k stars 291 forks source link

code from sekindo #58

Closed SirGryphin closed 5 years ago

SirGryphin commented 5 years ago

I've noticed it before but thought it was a one off. Sometimes I get this kind of error/message in my books.

This is a sentence in the book. "Hello, I'm a example." said Me. code from sekindo - Readlightnovel.org In-article - outstream code from sekindo /339474670/ReadLightNovel/InStory_1 This is a sentence in the book. "Hello, I'm a example." said Me.

As you can see I get this weird message and duplicate sentences, there's also others through out as well at random points, I've listed them below.

/339474670/ReadLightNovel/InStory_3
/339474670/ReadLightNovel/InStory_2
/339474670/ReadLightNovel/BottomStory

I don't know what causes it, I was downloading this novel https://www.readlightnovel.org/mo-tian-ji If you need anymore info let me know and I will try and provide it.

yudilee commented 5 years ago

Have you check the novel source, for example if you found duplicate/weird text in chapter 9 you should check via web browser in that chapter. This program flow is first you give toc link url and then the crawler check and save all chapter url and the access each chapter to get the text. then bind it into e book format. Can you give detail chapter in which problem occured. and also you may choose other source. My recommendation is novel planet, it has many novel maybe even more than novel in readlightnovel

dipu-bd commented 5 years ago

Can you tell us the chapter number where you found code from sekindo?

It is hard to process all the junk texts inside. Some sites have more junks than the others. You can try other available sources to download the novel. They might have more clear and neat content.

For example, check these sources:

dipu-bd commented 5 years ago

I found the issue. Those texts are actually from comments which is not ignored. In the next release this issue will be fixed.