View Single Post
Old 03-09-2023, 05:19 PM   #3
enuddleyarbl
Guru
enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.
 
enuddleyarbl's Avatar
 
Posts: 786
Karma: 1538394
Join Date: Sep 2013
Device: Kobo Sage
I'd been wondering what those "GBS..." tags were. Yes. A Google Books book. I'll probably just delete the lot of them. But, this happens in quite a few books where they're just trying to put in dead-tree page numbers. I also see them with simple non-page number ids: <a id="frontmatter"> or something. Again, with these GBS ids, I'll probably just trash them. For the others, I try to preserve them. If I'm lucky, I can just do a regex search/replace and move the id into a <section> or <h#> tag. But, sometimes, those already contain another id and I don't know what to do with those.

I can't find anything about anchor elements (<a> tags) having to be enclosed in a block-type tag anywhere. AFAICT, the spec doesn't talk about it and the examples don't indicate one way or another. But, neither Calibre's Check Book tool or EPubCheck have any problem with them that way.

It's just odd that the Beautify tool just seems to do nothing with pages that start out like that if the checking tools don't see anything wrong.
enuddleyarbl is offline   Reply With Quote