Replies: 10 comments 9 replies
-
do you mean the chapter file name? actually this chapter files name are not the final audiobook, they are just used |
Beta Was this translation helpful? Give feedback.
-
the A.I. speaker will say 1 intro etc.. that's it. and the final file will be 1 file only containing all your book text, chapters included. |
Beta Was this translation helpful? Give feedback.
-
ok, tell me how to manage millions of ebook with their own chapters classification, own language? do you know there is absolutely no standard rules to guess what is a chapter in an ebook? would you like I show you 10 ebooks from 10 different languages and so make a code guessing what is a chapter... then I will be happy to integrate it in eb2ab. |
Beta Was this translation helpful? Give feedback.
-
that said, now if you have a way to guess what is a chapter for at least 80% of the whole ebooks in the world. I would be very happy to know it. |
Beta Was this translation helpful? Give feedback.
-
it's not worth to copy paste chatGPT.... metadata is already in eb2ab, thing you still don't catch is WITHOUT standards, it's IMPOSSIBLE to guess the part/poem/chapter/psalm/whatever title starting with the word itself splitting the text in chapters. some books have ther chapter called 1., 2. ,3. ,4. etc... or A. B.C. without or without title. now how you make your script differs from this and legends, exceptions, nomenclatures, preface etc...? and multiply this by +1100 languages... your function will work for some books, until it will break on other books.... that's why it's better you make your own function for your own books, on our side we cannot satisfy everybody with a so simple function. as I said, you need an A.I. which is greater than the whole TTS models together.... |
Beta Was this translation helpful? Give feedback.
-
Now, there is an option as the project become popular, we can create ourselves a STANDARD for all languages. To define the exact chapters you wish with its own title into the audiobook chapter indices, you must:
we can even create a STANDARD that define the start and the end of the book like this: this way, people will have choice to not care or use our standards.... and it will be much more easy for everyone. |
Beta Was this translation helpful? Give feedback.
-
calibre does not do anything about how an ebook is structured. it shows only the metadata the author/editor put in and the xhtml pages, images and special pages that are in. no standards or "guess" calibre is doing to check if it's a chapter or else. there is NO chapter tags at all because there is NO standards. do you understand? if there is a chapter tag in an ebook, it's a personal and not standard reason why it is existing. with xhtml you can create any kind of TAGS. you cannot reinvent the wheel when there is NO WHEEL. I'm not sure you catch it still. |
Beta Was this translation helpful? Give feedback.
-
and what are you doing on ebooks without TOC? again you insist on the ebook you have on your hands and your language, and apparently you don't care of others. |
Beta Was this translation helpful? Give feedback.
-
what I can do is at least check if there is a TOC then parse it in dict() object, After that the trick would be to check which info we can find in every section that point to a page/text to the ebook and check where it is in the DOC provided. but even with TOC we must know what is a chapter in +1100 languages... |
Beta Was this translation helpful? Give feedback.
-
could you try this script under python_env and tell me if it works for you (provide the epub_file variable path file):
|
Beta Was this translation helpful? Give feedback.
-
The resulting audio files would be more user-friendly if they kept the chapter names instead of numbering them.
I'm aware it's a bit tricky because epub has nested chapters like a book, but audio files just support flat chapter structures.
I'm leaving the suggestion here so that it doesn't get forgotten.
Beta Was this translation helpful? Give feedback.
All reactions