lnreader icon indicating copy to clipboard operation
lnreader copied to clipboard

Issue with Epub downloader

Open Shihat007 opened this issue 6 months ago • 2 comments

Steps to reproduce

1.Bookmark and download any novel where their novel title has special character.

2.Try to convert it into epub file.

It won't download if the novel title has any special character(e.g. like : semicolon) or the novel has too many chapters.(E.h. novel like Shadow Slave)

Expected behavior

It should be able to covert to epub regardless of the title of the novel and their chapters.

Actual behavior

I tried to download Epub file of my saved novel then I saw only the novel's which doesn't have special character in their title and doesn't have many chapters (e.g. more than 1500) can be downloaded.

Image

LNReader version

2.0.0

Android version

15

Device

Nothing 2a

Other details

Can the downloader made as such even if there is special character in the novel title we can download the epub file. Thanks..

Acknowledgements

  • [x] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
  • [x] I have written a short but informative title.
  • [x] If this is an issue with a source, I should be opening an issue in the sources repository.
  • [x] I have updated the app to version 2.0.0.
  • [x] I will fill out all of the requested information in this form.

Shihat007 avatar Sep 12 '25 21:09 Shihat007

💔Screenshot_٢٠٢٥١٠٠٤-٠٥٤٨١٥.jpg

Ppoollkkmmnn09 avatar Oct 04 '25 03:10 Ppoollkkmmnn09

Going under the assumption that the error actually is because of characters forbidden in filenames: this problem would be solved if, instead of asking the user to grant permission to a target folder and deciding the filename itself, the exporter used the proper channels for exporting a file and let the user decide where and under which name to save it. If the filename is invalid, the picker would complain, and the user could just choose a different (better) name.

So unless even just calling the file picker with an invalid name throws an error, this would mean there's no need to mess with encoding at all! ...but it would still be nicer if the suggested name for the picker was properly cleaned up before being presented.

ilonachan avatar Oct 15 '25 16:10 ilonachan