View Single Post
Old 07-11-2015, 07:51 AM   #978
Rev. Bob
Wizard
Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.
 
Rev. Bob's Avatar
 
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
Quote:
Originally Posted by DoctorOhh View Post
Whether the anchors are trash or valuable, it is always nice to have the option to get rid of them.
Aye, there's the rub: "option." Without getting too far into the weeds, here's the situation:

1. All GBS.*.* anchors look alike.
2. Only some of those anchors are used in pagemapping. The rest appear to be garbage except (possibly) in a Google ebook reader app.
3. The GBS-related pagemap appears to be garbage, with the same caveat.
4. My GBS pagemap data comes from a very small sample, from which I am reluctant to generalize.

Thus, it is difficult to separate the pagemapped GBS anchors from the rest, and that may not even be desirable - so, at present, the posted beta routine does not give the option to preserve any GBS anchors. (Well, aside from the "don't use the routine at all" option.)

That is why I'd like to get more feedback on that point before sanctifying this version as a proper release. I'm fine with removing Google app-specific bloat, but not actually useful code.
Rev. Bob is offline   Reply With Quote