Re: Incompatibility of -epub-text-combine's "Inherited" between EPUB 3.0 and 3.0.1

Hi Xu-san,

Long time no see!

I'm talking about incompatibility between "text-combine" and
"text-combine-upright".

Since text-combine is defined by the working draft spec, CSS WG can change
it to text-combine-upright without considering compatibility. However,
since -epub-text-combine is defined by the EPUB 3.0 recommended spec, EPUB
spec should consider compatibility.

I don't see any specific place in epub 3.3 to define inherit value for
> text-combine-upright tho. But yeah, I think the inherited value is
> depending on CSS definition.

Yeah. EPUB 3.3 defines an alias of value and, IIUC, doesn't define an alias
of property. However, I guess text-combine is an alias
of text-combine-upright. Then, "Inherited" should be the same, and we must
consider them as the identical property during the cascading process.

Best regards
Yuki Sekiguchi


On Tue, Oct 6, 2020 at 8:19 PM Xu, Jeff <zheng.xu@rakuten.com> wrote:

> Hi Sekiguchi-san
>
> Long time no see.
> I think text-combine-upright replacing text-combine-horizontal is to keep
> alignment with CSS update.
> In terms of incompatibility between text-combine-upright vs
> text-combine-horizontal you can check out with Koji or CSS WG.
>
> I don't see any specific place in epub 3.3 to define inherit value for
> text-combine-upright tho. But yeah, I think the inherited value is
> depending on CSS definition.
>
> EBPAJ content guideline is old and outdated. There is something else such
> as text decoration also needs to be fixed in my opinion.
>
> Cheers,
>
> Zheng(Jeff) Xu
>
> Senior Mobile Application Engineer
>
> Toronto, Canada (GMT-5)
>
>
> www.kobo.com
>
>
>
>
>
>
> ------------------------------
> *From:* Yuki Sekiguchi <yuki.sekiguchi@access-company.com>
> *Sent:* Tuesday, October 6, 2020 5:05 AM
> *To:* public-epub-wg@w3.org <public-epub-wg@w3.org>
> *Subject:* Incompatibility of -epub-text-combine's "Inherited" between
> EPUB 3.0 and 3.0.1
>
> 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
>
> .
>

-- 
.