MobileRead Forums - View Single Post

Karellen · 11-20-2023, 02:39 PM

Hello @kovidgoyal

Often I find spurious code scattered throughout the ebook and these elements can be overlooked during clean up. Only by stumbling across them by accident, or reading the book in editor view, are you able to find them. For example, finding a single <tt></tt> element in a 150,000 word book will be quite difficult. (assume that you don't know it is there)

The reports component of the Editor is a very useful feature, but I find it a bit lacking and does not provide a complete overview of the coding, so the spurious codes can be overlooked during cleanup. For this reason I would like to request additional reports to give a complete view of the coding in the ebook.

In particular, I am referring to the two reports "Style rules" and "Style classes"

"Style Rules" simply lists the complete css file and applies a usage counter.
I find this misleading because the report is locked to the css file, and if a tag is not in the css file, it is not displayed, yet there could be many instances of its use in the ebook.
This should be renamed to CSS rules to avoid the misinterpretation that it will show all elements.
See image 1

"Style Classes" lists the classes in the css file that are used in the document, which duplicates part of the "Style rules" report. Though, of greater benefit is that it will also list classes used in the ebook that are not in the css file.
This is a very useful report in tracking down some spurious code.
See image 2

What you can see in both images, is that the ebook can be infested with code, yet neither report shows any of it.

What is additionally needed is one report to show all tags in use (image 3) and another report to list inline styling - maybe a report named "Inline styles" or maybe a report showing all attributes in use. This would make it much easier to track down coding that needs attention.

What are your thoughts?

11-20-2023, 02:39 PM	#1
Karellen Wizard Posts: 1,615 Karma: 9500498 Join Date: Sep 2021 Location: Australia Device: Kobo Libra 2	[Request] Additional reports Hello @kovidgoyal Often I find spurious code scattered throughout the ebook and these elements can be overlooked during clean up. Only by stumbling across them by accident, or reading the book in editor view, are you able to find them. For example, finding a single <tt></tt> element in a 150,000 word book will be quite difficult. (assume that you don't know it is there) The reports component of the Editor is a very useful feature, but I find it a bit lacking and does not provide a complete overview of the coding, so the spurious codes can be overlooked during cleanup. For this reason I would like to request additional reports to give a complete view of the coding in the ebook. In particular, I am referring to the two reports "Style rules" and "Style classes" "Style Rules" simply lists the complete css file and applies a usage counter. I find this misleading because the report is locked to the css file, and if a tag is not in the css file, it is not displayed, yet there could be many instances of its use in the ebook. This should be renamed to CSS rules to avoid the misinterpretation that it will show all elements. See image 1 "Style Classes" lists the classes in the css file that are used in the document, which duplicates part of the "Style rules" report. Though, of greater benefit is that it will also list classes used in the ebook that are not in the css file. This is a very useful report in tracking down some spurious code. See image 2 What you can see in both images, is that the ebook can be infested with code, yet neither report shows any of it. What is additionally needed is one report to show all tags in use (image 3) and another report to list inline styling - maybe a report named "Inline styles" or maybe a report showing all attributes in use. This would make it much easier to track down coding that needs attention. What are your thoughts? Attached Thumbnails Last edited by Karellen; 11-20-2023 at 07:55 PM.