Re: [gpsd-dev] [AIS] HTML testsuite report

[Eric S. Raymond]

Christian Gagneraud <address@hidden>:
> I have two goals, but I'm not sure exactly where to add these
> generated documentations bits:
> - Gives a clear and detailed picture of what is decoded and what has
> been checked against known good decodings

That's already described, in a format easier for humans to handle, early in
AIVDM.txt.  And I'd prefer to have just one of truth about that.

> - Show example of AIVDM sentences vs scaled/unscaled JSON.

Logically that should go in AIVDM.txt somewhere.

> The first point could be included somewhere in the beginning of the
> document to show GPSD's AIS decoding status
> 
> The other ones could be included after each message description
> table for example.

One of my design goals for AIVDM.txt, though, is not to have it be too
specific to GPSD's decoding implementation.  I've accepted having the 
JSON member names in the tables because all the alternatives are too
difficult to maintain, but I'd really prefer that other stuff specific
to JSON be confined to the document appendix dedicated to that.

I suggest you drop your conversion script in devtools (with an explanation
in the README there).  We can work on it there and think about how to 
apply it.
-- 
                <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>