- From: <Johnb@screen.subtitling.com>
- Date: Tue, 29 Mar 2005 09:46:48 +0100
- To: gadams@xfsi.com, russ.wood@softel.co.uk, public-tt@w3.org
- Message-ID: <11E58A66B922D511AFB600A0244A722EE57DAA@NTMAIL>
Glenn, An issue that was discussed recently at the AAF/MXF EBU ad-hoc subtitle commitee.... While the generation of multiple DFXP 'files' for individual languages is an acceptable solution, I feel there may yet be a requirement for a 'lightweight' conditional content mechanism. The specific example I have in mind is to support the concept of viewing 'watersheds' - i.e. content unsuitable for minors. In this case the majority of a subtitle file would be suitable for all viewers - but the odd word or phrase may be 'sanitised' for pre watershed (e.g. 8.00pm) airings of the programme. It would be onerous to require a subtitle archive to retain multiple copies of content to cater for just the alteration of one of two words in a 1300 line subtitle file. Is there any possibility of introducing a conditional content facuility to DFXP that would support this kind of minor use? A second use of this mechanism, which might be a stretch too far, is to support subtitle files that can be used as captions (i.e. near verbatim + sound cues) or as subtitles. In this case the conditional content may be the 'sound cues' and possibly the replacement of some of the subtitle lines with less accurate (but more concise!) translations. best regards John B. -----Original Message----- From: Glenn A. Adams [mailto:gadams@xfsi.com] Sent: 26 March 2005 05:47 To: Russ Wood; public-tt@w3.org Subject: RE: Timed Text Authoring Format - Distribution Format Exchange Profile (DFXP) Streaming DFXP supports general use of xml:lang attribute in order to (1) specify a default language for document instance and (2) to annotation language of nested content. It is up to the author to decide how to use this mechanism. For example, an author could potentially specify different <div/> elements using different languages, or different <p/> elements, etc. Nonetheless, the intention is not to explicitly support in DFXP conditional content selection based on preferred language. In contrast, conditional content selection will be supported in AFXP. The intent with DFXP is to have already made all conditional selections prior to transmitting/exchanging in DFXP format. This means that if an AFXP document supports course granular conditional selection between parallel language representations, then one may produce multiple DFXP document instances from a single AFXP document instance, by enumerating over the condional parameter space (of which each permutation may produce a distinct DFXP document instance). Regards, Glenn _____ From: Russ Wood [mailto:russ.wood@softel.co.uk] Sent: Monday, March 21, 2005 5:36 AM To: public-tt@w3.org Subject: RE: Timed Text Authoring Format - Distribution Format Exchange Pr ofile (DFXP) Streaming 3) I don't see a problem with allowing different languages in the same document but amalgamating different language files at run time is not difficult.
Received on Tuesday, 29 March 2005 08:30:33 UTC