Wendy Reid

Excellent question, we did consider this and ran into issues with how to best address it. I think our hope was that reading applications would have the sense to condense...

We will address this issue in the maintenance group, if still required.

So I've unfortunately found the reason why this was allowed in the first place, and can't make the resolved change without more discussion. We missed the section in the spec...

Thanks @webysther! We'll discuss this in an upcoming meeting. In general, *.lpf is the packaged standard extension, and we've not declared an official extension specifically for audiobooks, but this recommendation...

Draft of the Virtual Locators work: https://docs.google.com/document/d/11GypOjE9xOTaINATl5bxVIA3Mc9jzNBGCr6GT_KNaQ4/edit?pli=1

The EPUB WG's Virtual Locators Taskforce spent a little bit of time trying to figure out the question of page numbering (locators) in digital books. We have a potential solution...

Research to do/Questions to ask: - How do you break things down using the DOM/HTML elements (span, div), particularly non-semantic elements? - What is extracted that is non-textual content? (Alt...

This is directly related to what is proposed in #69 and I wonder if we should just combine these two issues. With "read aloud" are we referring to text-to-speech, screen...

> > With "read aloud" are we referring to text-to-speech, screen reader output, media overlays, or a combination of the three? > > Those are three different domains that cannot...

But @mattgarrish, the document you're referring to explicitly makes the difference between media overlays "Read Aloud" and TTS as separate features. There's a big gulf between the two features, and...