- From: Yuki Sekiguchi <yuki.sekiguchi@access-company.com>
- Date: Tue, 6 Oct 2020 18:05:16 +0900
- To: public-epub-wg@w3.org
- Message-ID: <CADxFA+S3i0gVG_V7gn2+W4T+VQdQH5zdshfM18UcXiZGqjaATw@mail.gmail.com>
Hi, EPUB 3.0 defines -epub-text-combine [1] as an alias of text-combine [2] whose Inherited is no. IIUC, EPUB 3.0.1 defines -epub-text-combine [3] as an alias of text-combine-horizontal [4] whose Inherited is yes. The latest EPUB 3.3 [5] is mostly the same as EPUB 3.0.1 except an alias of text-combine-upright [6] instead of text-combine-horizontal. Is this intentional incompatibility? There is an EBPAJ's sample EPUB file [7]. Although it just checks how a reading system renders an EPUB and doesn't check conformance, it is famous in Japan and most publishers use it to check reading systems. The EBPAJ's sample has a content to check this "Inherited" behaviour. Then, our customer asked us to fix EPUB 3.0's "Inherited: no". [1]: http://idpf.org/epub/30/spec/epub30-contentdocs-20111011.html#sec-css-writing-modes [2]: https://www.w3.org/TR/2011/WD-css3-writing-modes-20110428/#text-combine [3]: http://idpf.org/epub/301/spec/epub-contentdocs-20140626.html#sec-css-writing-modes [4]: https://www.w3.org/TR/2012/WD-css3-writing-modes-20121115/#text-combine-horizontal0 [5]: https://w3c.github.io/publ-epub-revision/epub33/core/#sec-css-prefixed-writing-modes [6]: https://www.w3.org/TR/2012/WD-css3-writing-modes-20121115/#text-combine-horizontal0 [7]: http://ebpaj.jp/counsel/guide Best regards Yuki Sekiguchi -- .
Received on Tuesday, 6 October 2020 09:06:09 UTC