Quote:
Originally Posted by Rev. Bob
BR:
Before I make changes, I have to properly diagnose the problem. That's why I explained the distinction between the two types of issues and requested clarification.
If it's an actual bug, that's a very serious matter and I need to see why the program isn't working properly. That is - and must be - my top priority.
If it's just a quibble about the output message, then that's an entirely different story. I don't worry about polishing that chrome until I'm sure the engine's running properly; there's no point.
If this is really such an unimaginably vital issue - if the people in this development forum are truly incapable of testing a beta without reading "Stripped spans in X" and understanding that it means "The stripspans routine made changes to X" - then I don't know what to say. For now, wording tweaks are the least of my worries; proper handling of the EPUB does and must take precedence over what the log message says.
|
I use the output of the plugin for testing. I use it to check if the spans have been stripped properly. So if the plugin says that the spans have been stripped and which files, I can pick some of the files to have a look at to make sure the spans were correctly removed. But when I go into the files and find there never were any spans removed, it's wasting my time as I look at the original code and the new code to make sure things worked. So what I am doing is comparing the code to check the spans when there's no reason to do so.