W3C home > Mailing lists > Public > public-tt@w3.org > August 2012

Re: quick questions

From: Kouichi Uchimura <Kouichi.Uchimura@jp.sony.com>
Date: Fri, 24 Aug 2012 10:23:00 +0900
To: Glenn Adams <glenn@skynav.com>, "public-tt@w3.org" <public-tt@w3.org>
Cc: Kouichi.Uchimura@jp.sony.com
Message-Id: <20120824102300.619F.187D7024@jp.sony.com>
Forgive my longer reply.

> Section 9.3.3 step 5 [1] maps tt:region to fo:block-container for the purpose of defining presentation semantics. Although it isn't made explicit by step 5, the intent is that the style properties of the latter are populated by using the computed style set associated with the tt:region. As such, the tts:visibility property would map to the associated XSL-FO visibility attribute on the resultant fo:block-container producing the effect I stated above.
> 
> I will file an action to add text to make the style mapping explicit, such as is found in steps 6, 8, etc.
Thank you. I really appriciate your effort!

> Keep in mind that "applies to" is related to semantic application and not presence or use of a style property.
> This attribute may be specified by any element type that permits use of attributes in the TT Style Namespace; however, this attribute applies as a style property only to those element types indicated in the following table.
My understanding of the text "This attriubte may be..." is
 "though this attribute can be specified on any elements, 
 but finally only appried to the limited(on the table) elements."
My understanding this is just explaining of schema structure.
And it is too difficult to realize "applies to"
 is not related presence or use of style prop even if intended by this
text.
 -- but can realize the other part e.g. 8.4.4.2

> [2] http://www.w3.org/TR/ttaf1-dfxp/#style-attribute-fontSize
I re-confirm this but cannot find correspond text... 

> What this means is that, for the purpose of style inheritance, tts:fontSize can appear on any tt: element that permits tts:* attributes, and furthermore, when determining the computed style set on leaf elements, i.e., as described by step 5 of [3].
Yes. I can understand your comment., that is the answer I was looking
for.
And can agree to you.
Processers will have such values internally 
 if implementers understand this correctly.
I was not sure that 
 whether the internal values can be used to Computed Style Set
Processing
  -- Thus % of fontSize can have meaning --

Thank you again!

best regards,
Uchimura

On Thu, 23 Aug 2012 18:32:53 +0900
Glenn Adams <glenn@skynav.com> wrote:

> 
> On Tue, Aug 21, 2012 at 5:15 PM, Kouichi Uchimura <Kouichi.Uchimura@jp.sony.com<mailto:Kouichi.Uchimura@jp.sony.com>> wrote:
> Thank you  for your reply.
> 
> (a) is fine. Thank you.
>  I appliciate if you indicate corresponding specification.
> 
> Section 9.3.3 step 5 [1] maps tt:region to fo:block-container for the purpose of defining presentation semantics. Although it isn't made explicit by step 5, the intent is that the style properties of the latter are populated by using the computed style set associated with the tt:region. As such, the tts:visibility property would map to the associated XSL-FO visibility attribute on the resultant fo:block-container producing the effect I stated above.
> 
> I will file an action to add text to make the style mapping explicit, such as is found in steps 6, 8, etc.
> 
> [1] http://www.w3.org/TR/ttaf1-dfxp/#semantics-region-layout-step-1
> 
> 
> (b):
> tts:fontSize is applied to span element.
> And not applied to region element...
> 
> Keep in mind that "applies to" is related to semantic application and not presence or use of a style property. More specifically, see the language at [2].
> 
> This attribute may be specified by any element type that permits use of attributes in the TT Style Namespace; however, this attribute applies as a style property only to those element types indicated in the following table.
> 
> [2] http://www.w3.org/TR/ttaf1-dfxp/#style-attribute-fontSize
> 
> What this means is that, for the purpose of style inheritance, tts:fontSize can appear on any tt: element that permits tts:* attributes, and furthermore, when determining the computed style set on leaf elements, i.e., as described by step 5 of [3].
> 
> [3] http://www.w3.org/TR/ttaf1-dfxp/#semantics-style-resolution-processing-sss
> 
> 
> best regards,
> Uchimura
> 
> On Sat, 18 Aug 2012 11:56:06 +0900
> Glenn Adams <glenn@skynav.com<mailto:glenn@skynav.com>> wrote:
> 
> >
> > On Fri, Aug 17, 2012 at 2:24 PM, Kouichi Uchimura <Kouichi.Uchimura@jp.sony.com<mailto:Kouichi.Uchimura@jp.sony.com><mailto:Kouichi.Uchimura@jp.sony.com<mailto:Kouichi.Uchimura@jp.sony.com>>> wrote:
> > Hi
> >
> > I have 2 more questions. Sorry for send many questions...
> >
> > (a) tts:visibility
> >  tts:visibility specifies visibility of the elemnet.
> >  What is expected if visibility is set to hidden to region elemet?
> >   (1) the region and its descendant elements are hidden
> >   (2) the region is hidden but decendant elements are visible if any
> >  I guess (1) is correct understanding but this takes me another question.
> >
> > (1) is correct, in the sense that any content targeted to the region is no displayed
> >
> >
> >  What is expected in next case
> >   <region xml:id="r1" and set it to visible!>
> >   ...
> >   <p region="r1" tts:visibility="hidden" begin="0s" "1s">
> >     textA
> >     <span tts:visibility="visible">
> >       textB
> >     </span>
> >   </p>
> >
> > In first question, my expectation is
> >  if an element is invisible then its descendant elements are invisible.
> >
> > none of <p> or its descendants are visible
> >
> > If this is true, textB above is also invisibile???
> >
> > children of a hidden element are hidden regardless of their visibility setting
> >
> > If not, it means (2) is correct but
> >  where content is drawn if region is hidden?
> >
> > (b) "em" relative unit of length
> > How can I specify the region extent and origin to use "em" unit?
> > What fontSize is applied to compute the relative value?
> >
> > font size is always well defined in the sense that if it is not specified on region or otherwise referenced then the initial value '1c' applies; if ttp:cellResolution is not specified, then 32 15 applies, so fontSize (in vertical dimension) would be heightOfRootContainer/32
> >
> > I guess "em" can be used to specify fontSize property only and
> > not for extent/origin.
> >
> > the only place where the value of <length> is restricted, is when tts:extent is specified on the root element tt:tt, in which case it must be pixels; see the text under [1]
> >
> > If tts:extent is specified on the ttelement, then the width and height must be expressed in terms of two <length><http://www.w3.org/TR/ttaf1-dfxp/#style-value-length> specifications, and these specifications must be expressed as non-percentage, definite lengths using pixel units.
> >
> > [1] http://www.w3.org/TR/ttaf1-dfxp/#style-attribute-extent
> >
> >
> > best regards,
> > Uchimura
> >
> > --
> > Consumer Products & Services Group
> > Home Entertainment Business Group
> > Home Entertainment Development Div.
> > Section1 Dept.7
> > Sony Corp.(Japan)
> > Kouichi Uchimura <Kouichi.Uchimura@jp.sony.com<mailto:Kouichi.Uchimura@jp.sony.com><mailto:Kouichi.Uchimura@jp.sony.com<mailto:Kouichi.Uchimura@jp.sony.com>>>
> >
> >
> >
> >
> 
> --
> Consumer Products & Services Group
> Home Entertainment Business Group
> Home Entertainment Development Div.
> Section1 Dept.7
> Sony Corp.(Japan)
> Kouichi Uchimura <Kouichi.Uchimura@jp.sony.com<mailto:Kouichi.Uchimura@jp.sony.com>>
> 
> 

-- 
Consumer Products & Services Group
Home Entertainment Business Group 
Home Entertainment Development Div.
Section1 Dept.7 
Sony Corp.(Japan)
Kouichi Uchimura <Kouichi.Uchimura@jp.sony.com>
Received on Friday, 24 August 2012 01:24:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 24 August 2012 01:24:04 GMT