Bookloupe

[windymilla]

Bookloupe (and gutcheck before it) has been a mainstay of PP/PPV checking for a looooooong time.

1. PPers may find it reassuring to continue to have bookloupe available as an explicit tool, rather than combining it with pptxt.
2. At least in my experience, bookloupe was often run near the start of the PPing process, and pptxt near the end, so separate tools would make sense from that point of view too.
3. Consider if there are some bookloupe checks that are out-of-date (like "non-ascii character")

Previously this PR said

Since bookloupe and pptxt have very similar aims, it makes sense to just have the one tool, rather than duplicate features. However, they may be some important checks in bookloupe that are not in pptxt, and could be transferred.

At the very least, it would be good to document here or somewhere else what features of bookloupe are covered by pptxt.

[tangledhelix]

Easy suggestions for checks to drop support for are these two, because utf-8:

• Non-ASCII character
• Non-ISO-8859 character

[tangledhelix]

1. PPers may find it reassuring to continue to have bookloupe available as an explicit tool, rather than combining it with pptxt.
2. At least in my experience, bookloupe was often run near the start of the PPing process, and pptxt near the end, so separate tools would make sense from that point of view too.

My 2¢ on this is that PP'ers have a wide range of workflows and I'd worry that collapsing these into one tool might create friction for people, having to adapt something they've honed over some years...