Re: Border- and padding-conditionality and fences

Re: lengths and percentages

Column´s Size

HI, 

I´m with a big problem. 
I have two files with the same hierarchy. 
In the first one, I set the column´s size with 30px. In the another one a
make the same, but on IE it shows different. One with 15mm and the other
with 5mm. But when i use Firefox, it shows fine.Both with 5mm.
Someone has an idea about this?

Thanks

Alexandre
--

-- 
View this message in context: http://www.nabble.com/Column%C2%B4s-Size-tf4061422.html#a11538725
Sent from the w3.org - xsl-editors mailing list archive at Nabble.com.

RE: Column´s Size

This list is for raising comments on the W3C specifications.

For advice in using the various technologies, there are other lists
available, for example the xsl-list at mulberrytech.com. If you post your
question there, and give rather more detail about what you are doing, I'm
sure someone will be able to help you.

Michael Kay

> -----Original Message-----
> From: xsl-editors-request <at> w3.org 
> [mailto:xsl-editors-request <at> w3.org] On Behalf Of axdmoraes
> Sent: 11 July 2007 13:24
> To: xsl-editors <at> w3.org
> Subject: Column´s Size
> 
> 
> HI, 
> 
> I´m with a big problem. 
> I have two files with the same hierarchy. 
> In the first one, I set the column´s size with 30px. In the 
> another one a make the same, but on IE it shows different. 
> One with 15mm and the other with 5mm. But when i use Firefox, 
> it shows fine.Both with 5mm.
> Someone has an idea about this?
> 
> Thanks
> 
> Alexandre
> --
> View this message in context: 
> http://www.nabble.com/Column%C2%B4s-Size-tf4061422.html#a11538725
> Sent from the w3.org - xsl-editors mailing list archive at Nabble.com.
> 
> 
> 

Re: ipd/bpd percentage base

RE: lengths and percentages

Hi Anders and Editors:

I agree that this will be a great improvement. Thank you.

Victor Mote 

> -----Original Message-----
> From: Anders Berglund [mailto:alrb <at> us.ibm.com] 
> Sent: Tuesday, July 10, 2007 3:02 PM
> To: xsl-editors <at> w3.org; Victor Mote
> Subject: Re: lengths and percentages 
> 
> 
> Thank-you for your comment on XSL 1.1. The XSL SG has 
> revieved your comment and is proposing the following 
> clarification of the XSL Spec: 
> 
> Normative text for 5.11, replacing the "Note": 
> 
>   If a property allows <percentage> values, then it may be 
> used in a short
>   form. In properties which do not otherwise specify the 
> semantics of a
>   <percentage> value in the property definition, the resolved 
> value of the
>   <percentage>, a <length>, is applied to the <length> 
> components and the
>   initial value to all the non-<length> components of the
>   compound property as above. 
> 
> Description of <percentage> value in 7.12.5, 7.12.6: remove 
> (handled by the normative text above). 
> 
> Anders Berglund, Editor XSL                                      

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.476 / Virus Database: 269.10.8/906 - Release Date: 7/17/2007
6:30 PM

RE: ipd/bpd percentage base

Hi Anders and Editors:

Your proposed changes clarify this nicely. Thank you.

Victor Mote 

> -----Original Message-----
> From: xsl-editors-request <at> w3.org 
> [mailto:xsl-editors-request <at> w3.org] On Behalf Of Anders Berglund
> Sent: Wednesday, July 18, 2007 8:44 AM
> To: xsl-editors <at> w3.org
> Subject: Re: ipd/bpd percentage base
> 
> 
> Thank-you for your comment on XSL 1.1 in
> http://lists.w3.org/Archives/Public/xsl-editors/2007AprJun/0004
> The XSL SG has revieved your comment and is proposing the 
> following changes to the XSL Spec: 
> 
> ipd/bpd percentatge base: 
> 
> in 7.15.3 and 7.15.7 add to the end of the sentence 
> 
> The percentage is calculated with respect to the 
> corresponding dimension of the closest area ancestor that was 
> generated by a block-level formatting object. 
> 
> the text: 
> 
> , or if there is no such area ancestor the closest area 
> ancestor that is a reference area. 
> 
> in 6.2 change the sentence: 
> 
> The parameter entity, "%block;" 
> in the content models below, contains the following 
> formatting objects: 
> 
> to 
> 
> The parameter entity, "%block;" 
> , defining the block-level formatting objects, 
> in the content models below, contains the following 
> formatting objects:   
> 
> 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.476 / Virus Database: 269.10.8/906 - Release 
> Date: 7/17/2007 6:30 PM
> 
> 
> 

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.476 / Virus Database: 269.10.8/906 - Release Date: 7/17/2007
6:30 PM

fo:folio-prefix (and other) content

Dear Editors:

This question applies at least to fo:folio-prefix, fo:folio-suffix, but also
seems to apply to fo:index-page-number-prefix, fo:index-page-number-suffix,
fo:index-page-citation-list-separator, and
fo:index-page-citation-range-separator.

Each of these objects has the following content model:
    (#PCDATA | %inline;)*.

The question: From whom do the child objects inherit properties? The use of
the term "static" for some of these seems to imply that they inherit
normally, that is, by reference to their ancestors in the tree. However,
that seems unlikely. It is easy, for example, to imagine an
fo:page-number-citation with a 12-point "Glossary-" prefix surrounded by
10-point text in a footnote. Am I correct to assume that instead this
content should be "grafted" in a manner similar to the way that fo:marker
content inherits from the fo:retrieve-marker that it replaces? Or would the
fo:page-number-citation need to explicitly set the font-size to the correct
value?

In any case, I think an explicit statement in the Recommendation addressing
this issue for each of these objects would be helpful.

Thank you in advance for your help.

Victor Mote
The FOray Project www.foray.org

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.476 / Virus Database: 269.10.10/908 - Release Date: 7/19/2007
6:10 PM

fo:page-sequence properties

Dear Editors:

There is a minor editorial glitch in the documentation for fo:page-sequence.
The object definition references the properties "country" and "language".
However, Appendix B-4 (in the PDF version at least) does not list
"fo:page-sequence" as applying to these properties. I believe that the
object definition is correct, as these properties are part of the
"conversion properties" listed at 6.6.10, which must be available from the
"reference-page-sequence" addressed there.

Victor Mote

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.476 / Virus Database: 269.10.16/914 - Release Date: 7/23/2007
7:45 PM

Re: page-sequence properties