Re: EPUBCheck v4.2.2 (maintenance release) is available

I made a misleading explanation.

> a file that occured error at v4.2.1
This "error" means,following;
https://github.com/w3c/epubcheck/issues/1036

-------------------------------------------------
株式会社ボイジャー 小池利明
koike@voyager.co.jp
Toshiaki Koike (Voyager Japan, Inc.)
-------------------------------------------------
On 7月 19 2019, at 8:34 午後, Toshiaki Koike <koike@voyager.co.jp> wrote:
> Hi Romain,
>
> Thank you for the releace EPUBCheck v4.2.2 !
> I think the results are expected.
>
> I tried to check a file that occured error at v4.2.1, then I confirmed the errors to warnings.
> at v4.2.1,
> -------------------------
> Validating using EPUB version 3.2 rules.
> ERROR(NAV-011): /home/koike/LocalDocs/checkfile/001.epub/OEBPS/toc.xhtml(20,51): 'toc' nav must be in reading order; link target 'OEBPS/text/1101028739_jp_0001_0004.xhtml' is before the previous link's target in spine order.
> ....(omission)
>
> Check finished with errors
> Messages: 0 fatals / 4 errors / 0 warnings / 0 infos
>
> EPUBCheck completed
> -------------------------
>
> at v4.2.2,
> -------------------------
> Validating using EPUB version 3.2 rules.
> WARNING(NAV-011): /home/koike/LocalDocs/checkfile/001.epub/OEBPS/toc.xhtml(20,51): 'toc' nav must be in reading order; link target 'OEBPS/text/1101028739_jp_0001_0004.xhtml' is before the previous link's target in spine order.
> INFO(INF-001): /home/koike/LocalDocs/checkfile/001.epub/OEBPS/toc.xhtml(20,51): The previous rule is under review and its severity may change in a future release. See the discussion at https://github.com/w3c/publ-epub-revision/issues/1283
> ....(omission)
>
> Check finished with warnings
> Messages: 0 fatals / 0 errors / 4 warnings / 4 infos
>
> EPUBCheck completed
> -------------------------
>
> with command line option "-e -q", the result is expected!
>
> And I checked a file that no error / warnings at v4.2.1, I confirmed the same result(no error / warnings)
> at v4.2.1,
> -----
> Validating using EPUB version 3.2 rules.
> No errors or warnings detected.
> Messages: 0 fatals / 0 errors / 0 warnings / 0 infos
>
> EPUBCheck completed
> -----
>
> at v4.2.2,
> -----
> Validating using EPUB version 3.2 rules.
> No errors or warnings detected.
> Messages: 0 fatals / 0 errors / 0 warnings / 0 infos
>
> EPUBCheck completed
> -----
>
> If I'll find the problem from now on, then I'll feedback.
> Thanls a lot.
>
> -------------------------------------------------
> 株式会社ボイジャー 小池利明
> koike@voyager.co.jp
> Toshiaki Koike (Voyager Japan, Inc.)
> -------------------------------------------------
>
> On Jul 19 2019, at 5:47 pm, Romain <rdeltour@gmail.com> wrote:
> > Hi everyone,
> >
> > EPUBCheck v4.2.2 is now available at the following page:
> > https://github.com/w3c/epubcheck/releases/tag/v4.2.2
> > This is a small maintenance release of EPUBCheck:
> > - reverts the rule about nav toc and page-list being in spine order to a WARNING (following the recent EPUB CG discussion, see the minutes at https://www.w3.org/2019/07/11-epub3cg-minutes.html).
> > - includes the complete translation of output messages to Traditional Chines (contributed by David Lee, thanks!).
> >
> > EPUBCheck v4.2.2 supersedes v4.2.1 as the latest production-ready release of EPUBCheck.
> > As usual, feedback or bug reports are always welcome! via replies to this email or directly to our issue tracker on GitHub:
> > https://github.com/w3c/epubcheck/issues
> > Best,
> > Romain.
> >
> > --
> > Romain Deltour – @rdeltour
> > Software and standards development
> > The DAISY Consortium
> > http://www.daisy.org
> >
>
>