View Single Post
Old 08-18-2024, 06:08 AM   #13
neil_swann80
0000000000101010
neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.
 
neil_swann80's Avatar
 
Posts: 5,893
Karma: 12981955
Join Date: Mar 2023
Location: An island off the coast of Ireland
Device: PB632 [HD3]
Quote:
Originally Posted by EastEriq View Post
Another idea I had is that if there was a small application capable of determining whether the epub is DRMed or not, that one could be set as the default opener, in a script which then calls either eink-reader or koreader depending on the result.
You could try testing for the presence of rights.xml or encryption.xml within the epub container. I think epub3 files are trickier and can contain these files anyway even if there's no DRM.

Quote:
Originally Posted by EastEriq View Post
Still another one is that koreader does detect that an epub is DRMd (because it reports it), so a user patch cold be that it closes itself launching eink-reader instead.
That would require a dedicated koreader plugin, would be plenty of work.

If you make any progress please post it here, I'd be interested to see your approach.
neil_swann80 is online now   Reply With Quote