W3C home > Mailing lists > Public > public-tt@w3.org > December 2008

Re: new issue? dfxp and language selection

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Fri, 5 Dec 2008 08:06:57 +1100
Message-ID: <2c0e02830812041306k1ead5605j6c4b631a25a0b94b@mail.gmail.com>
To: "John Birch" <john.birch@screen.subtitling.com>
Cc: "Daniel Weck" <daniel.weck@gmail.com>, "Hayes Sean" <Sean.Hayes@microsoft.com>, "Glenn A. Adams" <gadams@xfsi.com>, "Public TTWG List" <public-tt@w3.org>

On Fri, Dec 5, 2008 at 3:45 AM, John Birch
<john.birch@screen.subtitling.com> wrote:
>
> It's a good explanation, but I fear I'm not quite getting my point across.
>
> Two selection scenarios are common in subtitling.
>
> A) target audience language selection. Probably at a level immediately below body level between multiple 'functionally equivalent' yet language differentiated divs.
> B) Removal of inline content because of user preference. For example, in a movie with hard-of-hearing subtitles, a user may wish to turn off the subtitles pertaining to sound effects, but retain those relating to speech. Note: this can be done with current spec using ttm:role attribute.
>
> I agree that DFXP should include a marker that makes an explicit statement about intent.
> E.g. This content is intended for french speakers.
> Or perhaps go further... E.g. This content is intended for french speakers who are also deaf (although this can be finessed using the role attribute).
>
> I agree with Sean that I think that the same type of selection that might be achieved by language matching and switch constructs can be achieved by processing - PROVIDED that sufficient markup exists in the document to identify content with sufficient granularity.
>
> So my suggestion would be
>
>   <sequence ttm:lang="fr" title="Titre en français">
>     <p ttm:role="sound">FANFARE!</p>
>     <p>Ce texte est en français.</p>
>     <p ttm:lang="fr-CA">Ce texte est en québécquois.</p>
>   </sequence>
>
>   <sequence ttm:lang="en" title="Title in English">
>     <p ttm:role="sound">TYRE SCREECH!</p>
>     <p>Quick! Put the body in the boot!</p>
>     <p ttm:lang="en-US">Quick! Put the body in the trunk!</p>
>   </sequence>


How does a processor know to treat this as content selection and not
as text to be displayed sequentially, as the "sequence" tag is
suggesting?

Regards,
Silvia.
Received on Thursday, 4 December 2008 21:07:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 2 November 2009 22:41:39 GMT