W3C home > Mailing lists > Public > www-international@w3.org > January to March 2015

Re: Selection on text with ruby

From: Shinyu Murakami <murakami@vivliostyle.com>
Date: Wed, 25 Feb 2015 10:11:38 +0900
To: Koji Ishii <kojiishi@gmail.com>
Cc: Xidorn Quan <quanxunzhen@gmail.com>, Bobby Tung <bobbytung@wanderer.tw>, www International <www-international@w3.org>
Message-Id: <20150225101135.F03F.3B6C55AB@vivliostyle.com>
I asked a Japanese TTS and a11y expert, his answer is:
"That's a difficult problem. 
For current TTS, it is better skipping ruby text on copying to plain text.
However, in future, it may be better including ruby text 
if it is standardized how to represent ruby in plain text.
I will confirm it to TTS vendors..."

Shinyu Murakami (ζ‘δΈŠ ηœŸι›„)
CEO & Founder, Vivliostyle Inc.

Koji Ishii <kojiishi@gmail.com> wrote on 2015/02/24 13:31:13
> There was a similar discussion for what Text-to-Speech should read. In
> most cases, people wants TTS to skip <rt>.
> In rare cases, where annotation is really an annotation, not phonetic,
> they want TTS to read them.
> So, probably, should skip by default, and may add something if it
> helps a11y? I'm not following where that discussion went.
> /koji
> On Tue, Feb 24, 2015 at 12:33 PM, Xidorn Quan <quanxunzhen@gmail.com> wrote:
> > On Tue, Feb 24, 2015 at 2:29 PM, Koji Ishii <kojiishi@gmail.com> wrote:
> >>
> >> "Selection" and "copying to plain text" are two different things.
> >>
> >> How to plain-text-ize HTML is not in the scope of the spec as far as I
> >> understand, at least as of today, so it's up to UA to decide what to
> >> do.
> >
> >
> > I realize that. I sent this email because I want to know what would be the
> > most sensible way to handle this.
> >
> > - Xidorn
Received on Wednesday, 25 February 2015 01:12:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:07 UTC