WebToEpub
WebToEpub copied to clipboard
Option to export only the chapter files as .xhtml files with naming as on web fetch
Is your feature request related to a problem? Please describe.
- No.
Describe the solution you'd like
- An option to export the downloaded chapters as .xhtml files directly (placed in a zip file). If possible .css file too.
- No need for toc, container, content or other files. only the chapter files placed in a zip file.
- The chapters that are exported in this way must have the same name as on the web fetch.
- Without replacing spacing, special characters with underscores.
Describe alternatives you've considered
- None.
Additional context
- Example of the feature request.
- In the first image, the chapter names from the web fetch have spaces, colons, brackets, all that is allowed by the system.
- In the second image, the downloaded epub, has its spaces, colons, etc all replaced by underscores as it is the standard for an epub.
- So, I request an option to be able to export the chapter files as .xhtml and their names same as web fetch without replacement.
An alternative way,
- You could provide an option to export the chapter file names as on web fetch into an epub.
- I think this would be easier than the above mentioned process.
@zeoint
- Are you aware that epubs are also zip files? (Just change the extension from .epub to .zip.)
- This change is not going to happen for WebToEpub. That would complicate WebToEpub, for something that probably only benefits you.
- I'd suggest a better solution is a tool that unpacks an epub, renaming the XHTML files based on the chapter names. That would be (I think) reasonably simple to do. The file toc.ncx gives the file name of each chapter file in the epub, along with the chapter's title.
- I could add the ability to do what you request to the MergeWebToEpub tool. It would probably take less than 2 hours to do so. Now persuade me why I should do this. Basically, why would doing this be useful? Note, if it's useful to you, it might be useful to others. So a better solution would be a Calibre plug-in. Which is a bit outside my area of expertise.
Are you aware that epubs are also zip files? (Just change the extension from .epub to .zip.)
- I knew that. My request is about chapter titles (Keeping the special characters, spacing as on web fetch for supported types).
- Windows doesn't support certain characters for file names to have \ / / : * ? " < > | . But all other characters are supported.
- Currently when epub's are downloaded, if there are special characters in chapter files it will be replaced by underscore.
- For example,
Original Chapter file name on web fetch | Currently | Requested Feature |
---|---|---|
[Auxiliary Chapter] Astor's Book - (1) | Auxiliary_Chapter__Astor_s_Book_-_1 | [Auxiliary Chapter] Astor's Book - (1) |
Entangled! | Entangled_ | Entangled! |
I could add the ability to do what you request to the MergeWebToEpub tool. It would probably take less than 2 hours to do so. Now persuade me why I should do this. Basically, why would doing this be useful? Note, if it's useful to you, it might be useful to others. So a better solution would be a Calibre plug-in. Which is a bit outside my area of expertise.
- I had tried them all, but the problem arises with special characters in chapter titles. Many chapters have these.
- For example, ! , - , ', () , [] , etc.
- I added spacing using a renamer by removing underscore '_'.
- But there is no way to get special characters back once they are replaced.
As to why I need this,
- In an epub reader file names will not be displayed, as the Table of Contents is dependet on toc.ncx, so why would I need this?
- There is an applicaiton that supports this type of file reading without the need for epub format, toc.ncx, content.opf, other files. (In my opinion, one of the best applications if not the best, to read downloaded manga, webtoon, epub, offline).
- The chapter names are used as TOC (side list). So I requested this feature.
An option to export the downloaded chapters as .xhtml files directly (placed in a zip file). If possible .css file too.
Just .xhtml files are sufficient. That reading style has been implemented.
Hello, closing this as its no longer necessary.