10-17-2015, 10:40 AM | #61 | |
Wizard
Posts: 4,520
Karma: 121692313
Join Date: Oct 2009
Location: Heemskerk, NL
Device: PRS-T1, Kobo Touch, Kobo Aura
|
Quote:
|
|
10-17-2015, 01:17 PM | #62 |
creator of calibre
Posts: 43,778
Karma: 22666666
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
|
@jackie_w Hey, I am delighted by calibre plugins, I have no objections whatsoever to them being made
And I agree with Jellby, this plugin will be useful regardless of what MR decides. |
Advert | |
|
10-17-2015, 01:27 PM | #63 |
eBook Enthusiast
Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
Hi Jackie,
The moderating team has discussed the question you raised, and we're happy to give you the go-ahead for this suggested work, provided that the following conditions are met: 1. All text, table of contents, headings, textual metadata, etc, must be replaced with scrambled text. 2. All images must be replaced with scrambled images or removed. Provided that your suggested plug-in produces output which satisfies these conditions, there would be no problem in uploading such output to MobileRead's forums. One thing to bear in mind with any book is that it might contain embedded fonts that could be protected by copyright. Given that there is no practical method for the tool to know whether or not a font is protected by copyright, and that it could significantly alter the functionality of the book to simply delete the fonts, please make sure that you prominently request users of your tool to ensure that a book contains no copyrighted fonts before uploading it. Please don't hesitate to ask if you have any further questions about this. Last edited by HarryT; 10-17-2015 at 01:30 PM. |
10-17-2015, 02:51 PM | #64 | |
Grand Sorcerer
Posts: 6,171
Karma: 16228536
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
Re: the fonts, I'd already given this some more thought and think it would be safest just to delete all embedded fonts (obfuscated and non-obfuscated) for the Mark I version. Whether it results in a significantly less useful utility in practical terms remains to be seen. I'll post an alpha (non-plugin version) in this thread tomorrow with the hope that some of you will try it out on some of your own books and report back if there are any glaring errors or missed scrambling. ETA: If its possible to 100% reliably determine which fonts are obfuscated perhaps we can leave them in but I'm not familiar enough with the details at the moment. Perhaps Kovid can offer some guidance. Last edited by jackie_w; 10-17-2015 at 02:55 PM. Reason: obfuscated fonts |
|
10-17-2015, 06:12 PM | #65 |
Grand Sorcerer
Posts: 6,171
Karma: 16228536
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
@HarryT,
I do have a another question regarding digits 0-9 contained in the main text content. Originally I left all digits unscrambled. Pros - less confusion when clicking footnote hyperlinks and numeric TOC entries would match their numeric heading/footnote 'other end'. Cons - copyright page would contain unscrambled ISBNs - which may be a dealbreaker If digits need to be scrambled, which of the following would be most acceptable. Replace each digit with:
|
Advert | |
|
10-17-2015, 06:16 PM | #66 |
eBook Enthusiast
Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
I'd go for option 1 personally.
|
10-17-2015, 06:53 PM | #67 |
Grand Sorcerer
Posts: 6,171
Karma: 16228536
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
|
10-17-2015, 08:57 PM | #68 | |
Ex-Helpdesk Junkie
Posts: 19,422
Karma: 85397180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
|
Quote:
I'd just like to say, I am 99% sure I have seen people do this. I may be guilty of exaggerating how often, and I certainly can't bring to mind any instance of a moderator discussing it, truth be told -- so I am probably misremembering something at least. (Perhaps I saw moderators active in the same thread, and mentally associated the two, and don't know the difference now, months or years later?) I still don't see why there should be a problem, though. And even more so why here should be a problem with a book that isn't password-protected, but irreversibly turned into gibberish. EDIT: And I see the decision has been made that gibberish is acceptable. So I suppose it is a good thing we now have a decent alternative. (Because again, I am pretty sure I have seen the password route taken, whether it was condoned/noticed, or not.) Last edited by eschwartz; 10-17-2015 at 09:19 PM. |
|
10-17-2015, 11:08 PM | #69 |
creator of calibre
Posts: 43,778
Karma: 22666666
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
|
@jackie_w: The container object will have an attribute named obfuscated_fonts that will allow you to know which fonts are obfuscated.
|
10-18-2015, 01:54 AM | #70 |
The Grand Mouse 高貴的老鼠
Posts: 71,410
Karma: 305065800
Join Date: Jul 2007
Location: Norfolk, England
Device: Kindle Voyage
|
From a cryptographic point of view, (2) is the worst one. Since then you have some information about the original digit left.
|
10-18-2015, 07:46 AM | #71 | |
Wizard
Posts: 1,528
Karma: 6613969
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
|
Quote:
Last edited by RbnJrg; 10-18-2015 at 07:48 AM. |
|
10-18-2015, 08:32 AM | #72 | |
Grand Sorcerer
Posts: 6,171
Karma: 16228536
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
<a href="...">1</a> it would be easy to do, but if there was lots of rats nesting like this <a href="..."><span...> <sup ...><span ...>1</span> </sup></a> then it would be harder to associate the 1 with the <a> tag rather than the innermost <span>. I'm not saying it's not possible, there's probably a 'parser nesting technique' well known to lxml parsing experts. I just don't know it. Always willing to be educated though |
|
10-18-2015, 09:10 AM | #73 | |
eBook Enthusiast
Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
Quote:
|
|
10-18-2015, 09:12 AM | #74 | |
eBook Enthusiast
Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
Quote:
|
|
10-18-2015, 09:45 AM | #75 | |
Wizard
Posts: 1,528
Karma: 6613969
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
|
Quote:
Code:
<p>something <a epub:type="noteref" href="#fn01">1</a></p> … <aside id="fn01" epub:type="footnote"> Some footnote content </aside> |
|
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Sony ereader troubleshoot | chrisms | Sony Reader | 3 | 10-02-2013 02:08 PM |
Out of copyright ebooks/writers you'd most like to see digitized? | pstjmack | Reading Recommendations | 18 | 09-14-2012 08:46 PM |
whispersync not working: can anyone help me troubleshoot? | rheostaticsfan | Amazon Kindle | 4 | 10-27-2011 08:09 AM |
troubleshoot battery life | kkinser | Amazon Kindle | 2 | 04-18-2011 09:05 PM |
The copyright issues of fan fiction eBooks | Kirok | Lounge | 33 | 12-08-2008 06:54 PM |