- From: Ryo Kuroda <ryo.kuroda@access-company.com>
- Date: Fri, 8 Jan 2021 15:57:01 +0900
- To: Garth Conboy <garth@google.com>
- Cc: Laurent Le Meur <laurent.lemeur@edrlab.org>, W3C EPUB 3 Working Group <public-epub-wg@w3.org>
- Message-ID: <CABb+qRoheBs522VDsQQz+=4N_0eXFSA6BTJ5f6h8U-=eySHwZw@mail.gmail.com>
Hi all, Speaking about our Reading System (PUBLUS Reader for Android/iOS); A. Is your reading system capable of rendering EPUBs that contain HTML > that is not well-formed XML? > Yes. PUBLUS Reader uses Blink (Android) or WkWebKit (iOS). B. Is your reading system capable of ingesting such EPUBs? Does your > toolchain depend on all content documents being well-formed XML? Seems possible. 2020年12月18日(金) 9:00 Garth Conboy <garth@google.com>: > For Play Books. > > * A. Is your reading system capable of rendering EPUBs that contain HTML > that is not well-formed XML? * > > Currently "no" -- epubcheck is part of the ingest pipeline and would fail > such content. XML processing tools are currently used in the ingest > pipeline. > > > * B. Is your reading system capable of ingesting such EPUBs? Does your > toolchain depend on all content documents being well-formed XML? * > > Such content would not currently get past the front door. > > However, if EPUB 3.3 were to add HTML serialization, we would embark on > the (non-trivial) effort to support non-XML content. > > Best, > Garth > > > On Thu, Dec 17, 2020 at 2:33 AM Laurent Le Meur <laurent.lemeur@edrlab.org> > wrote: > >> Hi all, >> >> Speaking about Readium toolkits (Mobile and Desktop) and the desktop >> Thorium Reader app: >> >> A. Is your reading system capable of rendering EPUBs that contain HTML >> that is not well-formed XML? >> >> >> Yes, as all Readium toolkits are based on major web rendering engines. >> They belong to what could be called the "Open Web RS profile". >> >> The Readium Mobile iOS toolkit relies on Webkit (WKWebView). >> The Readium Mobile Android toolkit relies on Chrome (WebView >> <https://developer.android.com/reference/android/webkit/WebView>). >> The Readium Desktop toolkit relies on Chromium (via Electron.js). >> And Thorium Reader relies on Readium Desktop. >> >> B. Is your reading system capable of ingesting such EPUBs? >> >> >> Yes they are. >> >> To be sure, I created a very dirty EPUB from "wasteland" (which contains >> a unique spine item) by replacing the XHTML content by some random HTML tag >> soup. It would be good to have a proper sample, but until then ... it works >> on Thorium like a charm. >> >> Stay safe >> Laurent >> >> >> Le 16 déc. 2020 à 17:03, Dave Cramer <dauwhe@gmail.com> a écrit : >> >> Friday 18 Dec. 2020 >> Time: 10:00 a.m. Boston (60min) >> Local date/time link: >> https://www.timeanddate.com/worldclock/fixedtime.html?msg=EPUBWG+Meeting&iso=20201218T10&p1=43&ah=1 >> >> Connection details at end of note >> >> >> Scribe list: mgarrish, garth, bduga >> >> >> Meeting Chair: Wendy Reid, Dave Cramer (?) >> >> >> Topic (time) >> 1-Homework for forthcoming discussion of HTML Serialization [1] (10 min) >> >> In 2021 we will discuss whether to allow the HTML serialization of >> HTML5 in EPUB. Before having that discussion, we’d like to gather some >> information on how that might impact the existing ecosystem. If you >> have knowledge of any existing EPUB reading system, we’d like to know: >> >> A. Is your reading system capable of rendering EPUBs that contain HTML >> that is not well-formed XML? >> B. Is your reading system capable of ingesting such EPUBs? Does your >> toolchain depend on all content documents being well-formed XML? >> >> 2-Release identifier construction [2] (10 min) >> 3-Non-unique unique identifiers and reading system conformance [3] (10 >> min) >> 4-Clarify language tag values [4] (10 min) >> 5-Missing conformance criteria around item properties? [5] (10 min) >> 6-The default value of rendition:flow [6] (10 min) >> >> Links >> [1] https://github.com/w3c/epub-specs/issues/636 >> [2] https://github.com/w3c/epub-specs/issues/1440 >> [3] https://github.com/w3c/epub-specs/issues/1310 >> [4] https://github.com/w3c/epub-specs/issues/1325 >> [5] https://github.com/w3c/epub-specs/issues/1422 >> [6] https://github.com/w3c/epub-specs/issues/1313 >> >> ======================== >> = issues marked pending close = >> ======================== >> As of the time this email was sent, the following issues were marked >> 'pending close': >> >> Issue 1380: https://github.com/w3c/publ-epub-revision/issues/1380 >> Issue 1389: https://github.com/w3c/publ-epub-revision/issues/1389 >> >> >> For an up to date list of the current set of 'pending close' issues, >> please see: >> >> https://github.com/w3c/publ-epub-revision/issues?q=is%3Aopen+is%3Aissue+label%3AStatus-ProposeClosing >> >> ================= >> = Connection details = >> ================= >> Text Chat: http://irc.w3.org/?channels=epub >> IRC://irc.w3.org:6665/#epub >> >> Meeting link for Zoom in archive: >> https://lists.w3.org/Archives/Member/member-epub-wg/2020Aug/0000.html >> >> >> ================= >> The EPUBWG relies on IRC in our weekly call to encourage meeting >> participation, document our discussions, vote on resolutions and manage the >> speaker queue, etc. For more information about IRC in w3.org, please >> review https://www.w3.org/wiki/IRC >> >> >> -- ————————————————————— 株式会社ACCESS 電子出版事業本部 開発部開発課 黒田 涼 (Ryo Kuroda) Mail: Ryo.Kuroda@access-company.com ————————————————————— -- ..
Received on Friday, 8 January 2021 07:09:34 UTC