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

Re: space

From: Geoff Freed <geoff_freed@wgbh.org>
Date: Tue, 02 Dec 2008 18:29:35 -0500
To: John Birch <john.birch@screen.subtitling.com>, public-tt@w3.org
Message-id: <38D1E7C1-36D2-4CE9-BC7B-10BD7107AB94@wgbh.org>


Hi, John:

> I suspect that there will be some time to fill...as I'm proposing that
> dynamic flow is dropped from the spec.

whoa!  well, i suspect we can still fill the time discussing ways to  
perhaps salvage dynamicFlow, or if we want to rework it by adopting  
some other model.  i'll give this some thought.

g.



On Dec 2, 2008, at 3:23 PM, John Birch wrote:

>
> Geoff, all...
>
> I suspect that there will be some time to fill...as I'm proposing that
> dynamic flow is dropped from the spec.
> Everything I was ~promoting~ for dynamic fill can still be achieved by
> 'knife and fork' methods in DFXP...
>
> What dynamic flow was intended as (at least for me :) was as a  
> mechanism
> to move some of the responsibility
> for dynamic display of text over a time period from the author...  
> to the
> display device.
> (Note there is precendence for this as some aspects of EIA608 and 708
> closed captioning have a similar characteristic in that user settings
> impact the display of the captions irrespective of the implied text
> timing from the stream.)
>
> A simplistic dynamic flow example would be some timed text that is
> flowed onto a single line horizontal 'ticker' display.
> Depending on the number of pixels in width (assuming font  
> equivalence),
> different numbers of characters would be simultaneously visible on
> different width displays...I was envisaging a specification that
> encouraged a smart 'dynamic flow'ing display to adjust text 'scroll'
> speeds to ensure that all the text was presented within the time  
> period
> defined by the DFXP document instance.
>
> Still.. a moot point as I now feel certain that dynamic flow cannot be
> done justice within the timeframes - certainly testing and
> representative implementations would be extremely difficult to
> achieve...
>
> Best regards
>
> John Birch
>
> John Birch | Screen Subtitling Systems Ltd | Strategic Partnerships  
> Manager
> Main Line : +44 (0)1473 831700 | Ext : 270 | Office :
> Mobile: +44 (0)7919 558380 | Fax: +44 (0)1473 830078
> john.birch@screen.subtitling.com | www.screen.subtitling.com
> The Old Rectory, Claydon Curch Lane, Claydon,Ipswich,IP6 0EQ,United  
> Kingdom
>
>
> See us at Broadcast Video Expo - February 17th - 19th 2009, Earls  
> Court 2, London, Stand number K56
>
>
> Before Printing, think about the environment
>
> -----Original Message-----
> From: public-tt-request@w3.org [mailto:public-tt-request@w3.org] On
> Behalf Of Geoff Freed
> Sent: 02 December 2008 14:53
> To: public-tt@w3.org
> Subject: xml:space
>
>
>
> can we add a brief discussion of xml:space to the agenda this week?
> i'm confused about what's specified as default behavior in dfxp
> (http://www.w3.org/TR/2006/CR-ttaf1-dfxp-20061116/#content-attribute-
> space) versus what we talked about two weeks ago.
>
> thanks.
> g.
>
>
>
>
> This message may contain confidential and/or privileged  
> information. If you are not the intended recipient you must not  
> use, copy, disclose or take any action based on this message or any  
> information herein. If you have received this message in error,  
> please advise the sender immediately by reply e-mail and delete  
> this message. Thank you for your cooperation. Screen Subtitling  
> Systems Ltd. Registered in England No. 2596832. Registered Office:  
> The Old Rectory, Claydon Church Lane, Claydon, Ipswich, Suffolk,  
> IP6 0EQ
>
Received on Tuesday, 2 December 2008 23:30:25 GMT

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