Possible replacement for EPUBCHECK - Page 3

DiapDealer · Yesterday, 02:07 PM

Quote:

Originally Posted by JSWolf

Another bug is with -v. I tried to use it to check what version I have.

Code:

epubveri -v
error: cannot read -v: The system cannot find the file specified. (os error 2)

You really need to learn what "bugs" actually are, Jon. What you're reporting is a feature you expect to be there, but is not.

JSWolf · Yesterday, 02:13 PM

Quote:

Originally Posted by DiapDealer

You really need to learn what "bugs" actually are, Jon. What you're reporting is a feature you expect to be there, but is not.

When the directions say it's there and it's not, it is a bug.

DiapDealer · Yesterday, 02:20 PM

Quote:

Originally Posted by JSWolf

When the directions say it's there and it's not, it is a bug.

The directions DON'T say it's there, Jon. The shortcut for --version is -V (capital) not -v (lowercase). This is clearly displayed if you run epubveri with no arguments (or with epubveri -h). You're clearly out of your depth here. Please refrain from making pointless noise.

JSWolf · Yesterday, 02:52 PM

epubveri should display the version number if you don't give options. and the options should not be case specific.

PeterT · Yesterday, 02:57 PM

Quote:

Originally Posted by JSWolf

Another bug is with -v. I tried to use it to check what version I have.

Code:

epubveri -v
error: cannot read -v: The system cannot find the file specified. (os error 2)

I believe it's either -V (uppercase) or --version

JSWolf · Yesterday, 03:09 PM

Quote:

Originally Posted by PeterT

I believe it's either -V (uppercase) or --version

Yes it is. Most of the time, commands like -V are only case specific if -v is a different command.

DiapDealer · Yesterday, 03:30 PM

Quote:

Originally Posted by JSWolf

epubveri should display the version number if you don't give options. and the options should not be case specific.

This is merely your personal expectation and nothing more. Certainly not a rule, and certainly not a bug. Let. It. Go. You're just making pointless noise.

Kayadelenium · Yesterday, 03:30 PM

Hello everyone,

This falls under both bug and request categories. It's a bug because the program gave an error. Under normal circumstances, it should give a warning for an unrecognized command or missing parameter and suggest using the `-h/--help` command for help.

There's no RFC for command-line flags. There are two texts that are closest, and neither is an RFC: POSIX or GNU Coding Standards. I've started creating common command standards for use in projects like epublift, epubveri, and epubsana, which I started today. After the command standards are finished, I'll make changes to the command usage in epubveri. I have something in mind similar to the UNIX man logic. There's a simple manual page that will show command usage and examples when the user types `epubveri --help`.

-v or -V?
-v is for verbose, -V is for version. git, cargo, ripgrep, curl, ssh, grep, rsync all use it this way.

Finally, I also started the epubsana project to fix the bugs that epubveri found. This project seems like it will take a very long time. Finding and writing each bug, its solution, and its implementation is time-consuming. I spent my whole day on the simplest solution, the 4 ID bug, and released version v0.1.0. If you want to try it, you can check out the webpage.

Source: https://github.com/veripublica/epubsana
Web Demo: https://veripublica.github.io/epubsana/

DiapDealer · Yesterday, 03:39 PM

I certainly wouldn't consider an error being raised whenever an invalid flag is used to be a bug, but it's your show.

JSWolf · Yesterday, 03:56 PM

Quote:

Originally Posted by DiapDealer

This is merely your personal expectation and nothing more. Certainly not a rule, and certainly not a bug. Let. It. Go. You're just making pointless noise.

It's what most command line programs do that I've used that have this sort of option(s).

JSWolf · Yesterday, 03:59 PM

Quote:

Originally Posted by DiapDealer

I certainly wouldn't consider an error being raised whenever an invalid flag is used to be a bug, but it's your show.

But the error message return is not describing that the problem is. It's basally returning a file not found type of error instead of an invalid option error.

DiapDealer · Yesterday, 04:36 PM

I'm done with you, Jon. You don't know the first thing about command-line best practices. You just squawk about things that work differently than you want them too. It's aggravating.

j.p.s · Yesterday, 05:05 PM

Quote:

Originally Posted by DiapDealer

This is merely your personal expectation and nothing more. Certainly not a rule, and certainly not a bug. Let. It. Go. You're just making pointless noise.

It's not pointless. It is very effective at creating counterproductive disruption.

Doitsu · Today, 12:26 AM

@Kayadelenium:

1. Unlike EPUBCheck, epubveri will not flag epub:type attributes in epub2 books
2. Do you plan on adding support for USAGE messages?

Kayadelenium · Today, 05:35 PM

@Doitsu Thanks, both are good questions.

1. epub:type in EPUB2 — you're right, this is a real gap on my side. EPUB2's content model shouldn't accept the OPS namespace at all, so epub:type should be flagged there. I've confirmed the cause in the code; I want to match exactly what epubcheck reports (message ID + severity) before I ship the fix, so I won't rush it.

2. USAGE messages — yes, on the roadmap. Right now those findings exist but are folded under INFO. The plan is to split out a proper USAGE level and suppress it by default with an opt-in flag, the same way epubcheck does. Not done yet.

I'm looking into both. I'll post here with the concrete details — what will change and what won't — once I've worked through it. A fairly large piece of work has landed on my plate, so please bear with the timing.

Yesterday, 03:39 PM	#39
DiapDealer Grand Sorcerer Posts: 29,571 Karma: 212177564 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	I certainly wouldn't consider an error being raised whenever an invalid flag is used to be a bug, but it's your show. Last edited by DiapDealer; Yesterday at 03:54 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
EPUBCheck v4.2.6	jhowell	ePub	0	06-30-2021 03:49 PM
EPUBCheck v4.2.5	jhowell	ePub	0	03-23-2021 09:45 AM
EPUBCheck v4.2.4	jhowell	ePub	3	06-24-2020 09:51 AM
EPUBCheck v4.1.1	Doitsu	ePub	2	03-18-2019 10:39 AM
Web-based epubcheck upgraded to epubcheck 1.0.5	kjk	ePub	4	02-09-2010 09:53 PM

Yesterday, 02:52 PM	#34
JSWolf Resident Curmudgeon Posts: 84,093 Karma: 153695583 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	epubveri should display the version number if you don't give options. and the options should not be case specific.

Yesterday, 03:30 PM	#38
Kayadelenium Junior Member Posts: 4 Karma: 10 Join Date: Jul 2026 Location: Planet Earth Device: Kobo Forma	Hello everyone, This falls under both bug and request categories. It's a bug because the program gave an error. Under normal circumstances, it should give a warning for an unrecognized command or missing parameter and suggest using the `-h/--help` command for help. There's no RFC for command-line flags. There are two texts that are closest, and neither is an RFC: POSIX or GNU Coding Standards. I've started creating common command standards for use in projects like epublift, epubveri, and epubsana, which I started today. After the command standards are finished, I'll make changes to the command usage in epubveri. I have something in mind similar to the UNIX man logic. There's a simple manual page that will show command usage and examples when the user types `epubveri --help`. -v or -V? -v is for verbose, -V is for version. git, cargo, ripgrep, curl, ssh, grep, rsync all use it this way. Finally, I also started the epubsana project to fix the bugs that epubveri found. This project seems like it will take a very long time. Finding and writing each bug, its solution, and its implementation is time-consuming. I spent my whole day on the simplest solution, the 4 ID bug, and released version v0.1.0. If you want to try it, you can check out the webpage. Source: https://github.com/veripublica/epubsana Web Demo: https://veripublica.github.io/epubsana/

Yesterday, 04:36 PM	#42
DiapDealer Grand Sorcerer Posts: 29,571 Karma: 212177564 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	I'm done with you, Jon. You don't know the first thing about command-line best practices. You just squawk about things that work differently than you want them too. It's aggravating.

Today, 12:26 AM	#44
Doitsu Grand Sorcerer Posts: 5,835 Karma: 24222221 Join Date: Dec 2010 Device: Kindle PW2	@Kayadelenium: 1. Unlike EPUBCheck, epubveri will not flag epub:type attributes in epub2 books 2. Do you plan on adding support for USAGE messages?

Today, 05:35 PM	#45
Kayadelenium Junior Member Posts: 4 Karma: 10 Join Date: Jul 2026 Location: Planet Earth Device: Kobo Forma	@Doitsu Thanks, both are good questions. 1. epub:type in EPUB2 — you're right, this is a real gap on my side. EPUB2's content model shouldn't accept the OPS namespace at all, so epub:type should be flagged there. I've confirmed the cause in the code; I want to match exactly what epubcheck reports (message ID + severity) before I ship the fix, so I won't rush it. 2. USAGE messages — yes, on the roadmap. Right now those findings exist but are folded under INFO. The plan is to split out a proper USAGE level and suppress it by default with an opt-in flag, the same way epubcheck does. Not done yet. I'm looking into both. I'll post here with the concrete details — what will change and what won't — once I've worked through it. A fairly large piece of work has landed on my plate, so please bear with the timing.