epub 120 (MO) about epub-testsuite

[OriIdan]

On Thu, Mar 13, 2014 at 10:28 PM, Marisa DeMeglio
[email protected]:

user feedback:

EPUBTEST-0120

1. mo-basic-040: Volume Control: it is not clear to me if you mean
   that the RS should have its own volume control (independent from, e.g.
   the OS volume control), or just having a way of controlling the volume
   (e.g., the OS volume control) is ok.

I don't think we need such a test. I don't remember any part of the spec.
talking about volume.

2. Skippability and Escapability sections: change the wording of "the
   following highlighted fragment" to something like "the following
   green-backround fragment" to avoid confusion with the MO "highlighted
   (active) fragment".

3. Clip Times: clip_times_tests.smil references 3 different audio
   files. In this way, a RS that correctly handles the missing
   clipBegin/clipEnd attributes, but it does not handle multiple audio
   references in the SMIL file, does not pass the test.
   (This observation might apply to other tests.). Moreover, in the
   clip_times_tests.smil I got, clipBegin/clipEnd are not actually
   missing from any element, so mo-audio-010 and mo-audio-020 are
   not actually checked (or I am missing something).

Reply to this email directly or view it on GitHubhttps://github.com//issues/52
.

Ori Idan CEO Helicon Books
http://www.heliconbooks.com

[marisademeglio]

I'm changing mo-basic-040 to read as follows:

"If you can adjust the MO volume independently of the device volume (for example, as a standalone MO-specific option or via overall Reading System volume), then the Reading System supports volume control."

[marisademeglio]

I have replaced skippable and escapable test descriptions of "highlighted" with color-specific descriptions.

The affected tests are:
mo-skip-010
mo-skip-020
mo-esc-010
mo-esc-020
mo-esc-030

[OriIdan]

On Sat, May 3, 2014 at 12:38 AM, Marisa DeMeglio
[email protected]:

I'm changing mo-basic-040 to read as follows:

"If you can adjust the MO volume independently of the device volume (for
example, as a standalone MO-specific option or via overall Reading System
volume), then the Reading System supports volume control."

I think saying "overall Reading System volume" may confuse people with
device volume buttons and that is not what we want.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/52#issuecomment-42081774
.

[marisademeglio]

@OriIdan could you propose alternate wording?

[marisademeglio]

Clip times tests have been fixed. The affected tests are:

mo-audio-010
mo-audio-020
mo-audio-030

(Btw the clip times tests do require that a RS support multiple audio files in one SMIL file)

[OriIdan]

I suggest the following sentence, it is the same as you proposed but
without the examples that in my opinion may lead users to think we are also
talking on hardware volume control.

"If you can adjust the MO volume independently of the device volume, then
the Reading System supports volume control."

Ori Idan

On Wed, May 7, 2014 at 2:32 AM, Marisa DeMeglio [email protected]:

@OriIdan https://github.com/OriIdan could you propose alternate wording?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/52#issuecomment-42372819
.

[marisademeglio]

Thanks! It's been updated.