bugzilla | 1 Apr 2013 05:50
Picon

[Bug 21456] New: Flash crash ssl

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21456

            Bug ID: 21456
           Summary: Flash crash ssl
    Classification: Unclassified
           Product: XSLFO
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSL-FO Requirements
          Assignee: xsl-editors <at> w3.org
          Reporter: Kathysoto411a <at> gmail.com
        QA Contact: xsl-editors <at> w3.org

--

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.

srinivasarao vegunta | 12 Feb 2013 13:06
Picon
Favicon

<none>

    Hi!
Glenn Adams | 21 Apr 2012 18:12
Gravatar

5.10.4 from-page-master-region discrepancy?

In XSL-FO 1.1, 5.10.4, appears:


"If this function is used in an expression on a formatting object, F, that is a descendant of an fo:page-sequence, then the computed value is taken from the region specification that was used to generate the nearest ancestor region reference area which has as its descendants the areas returned by F."

However, this is followed by an example where "this function" (from-page-master-region) is used on fo:page-sequence, and not a descendant of fo:page-sequence!

<fo:page-sequence master-name="default-sequence" writing-mode="from-page-master-region()">

How is this example to be reconciled with the normative language cited above about being "used in an expression ... that is a descendant of an fo:page-sequence"?

Regards,
Glenn

Adrian Stadelmann | 22 Mar 2012 16:31
Picon

7.22.2 overflow: :request to support of text-overflow

Hi,
It whould be very helpful to use a text-overflow as in
http://www.w3.org/TR/css3-ui/#text-overflow0

why:
the overflow="hidden" is not very useful for a print media in case of text, because it may cut a letter.

Doing this outside of the FO namespace is also a bad solution because it requires font size/style calculation.

see also my http://stackoverflow.com/questions/9807926/add-suspensive-dots-at-end-of-a-text-in-case-of-overflow-hidden question.

other ideas?

Adrian





John Obri | 15 Mar 2012 15:48
Picon

Permission Request for 'Transformations XSL (XSLT...'

Hello,

I've known you website for ages! And I found interesting your  
publication "Transformations XSL (XSLT)" which I googled on  
http://xmlfr.org/w3c/TR/xslt/ ! I'd love to use it in a project I'm  
involved with called "Geek Science", so I'm seeking your permission for  
translation to Macedonian language. "Geek Science" is a freemium-model  
non-English language orientated startup with collection of scientific  
articles, personal notes etc. in several languages that is collaboratively  
edited by volunteers from around the world since 1999. Young and old,  
students and professors - even your neighbor could be a volunteer member.

If you agree, we will credit you for your work in the resulting  
translation's references by stating that it was based on your work and is  
used with your permission, and by mentioning the name of my project "Geek  
Science" back to:
http://xmlfr.org/w3c/TR/xslt/

Thank you for your time and patience.
I look forward to your response next week.

---
Best wishes,
John Obri
Tirana, Albania
(GMT +1)
Translation for Education FAQ - http://goo.gl/q9Oq9

bugzilla | 18 Aug 2011 16:47
Picon

[Bug 13828] New: ICC reference may be out of date

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13828

           Summary: ICC reference may be out of date
           Product: XSLFO
           Version: 2.0 Working Draft
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P2
         Component: XSL-FO
        AssignedTo: tgraham <at> mentea.net
        ReportedBy: tgraham <at> mentea.net
         QAContact: xsl-editors <at> w3.org

SVG Color 1.2 uses:

[ICC42]
    International Color Consortium. Specification ICC.1:2004-10 (Profile
version 4.2.0.0) Image technology colour management — Architecture, profile
format, and data structure.
    Available at http://www.color.org/ICC1V42.pdf

--

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

bugzilla | 18 Aug 2011 16:33
Picon

[Bug 13827] New: Do cie-lab-color() and cie-lchab-color() need optional white point?

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13827

           Summary: Do cie-lab-color() and cie-lchab-color() need optional
                    white point?
           Product: XSLFO
           Version: 2.0 Working Draft
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSL-FO
        AssignedTo: tgraham <at> mentea.net
        ReportedBy: tgraham <at> mentea.net
         QAContact: xsl-editors <at> w3.org

XSL FO 2.0's cie-lab-color() and cie-lchab-color() [1] are meant to be
compatible with what can be expressed in SVG Color 1.2 [2].

The cielab() and cielchab() functions in SVG Color 1.2 both have an option
white point parameter.

Should XSL FO 2.0 have this parameter in its functions?

Regards,

Tony Graham.

[1] http://www.w3.org/Style/XSL/Group/2009/03/xslfo20.html#d2e7142
[2] http://dev.w3.org/SVG/modules/color/master/SVGColor.html

--

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

bugzilla | 17 Aug 2011 13:05
Picon

[Bug 13804] New: Is normative rgb-icc() prototype wrong?

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13804

           Summary: Is normative rgb-icc() prototype wrong?
           Product: XSLFO
           Version: 1.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSL-FO
        AssignedTo: tgraham <at> mentea.net
        ReportedBy: tgraham <at> mentea.net
         QAContact: xsl-editors <at> w3.org

The rgb-icc() prototype [1] in the normative HTML for XSL 1.1 is:

color rgb-icc(numeric, numeric, numeric, NCName, numeric, numeric)

However, the non-normative XML source [2] for XSL 1.1 contains:

<proto name="rgb-icc" return-type="color"><arg type="numeric"/><arg
type="numeric"/>
<arg type="numeric"/><arg type="NCName"/><arg type="numeric"/><arg
type="numeric" occur="rep"/></proto>

I.e., the 'occur="rep"' on the last <arg> does not make it any different from
an <arg> without it.

In contrast 'occur="opt"' adds a "?" after the argument in the rendered
prototype.  E.g., in 'system-font()'.

Was 'occur="rep"' supposed to add a "+" after the argument name in the rendered
prototype?

Regards,

Tony Graham                                   tgraham <at> mentea.net
Consultant                                 http://www.mentea.net
Mentea       13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland
 --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --
    XML, XSL FO and XSLT consulting, training and programming

[1] http://www.w3.org/TR/xsl11/#expr-color-functions
[2] http://www.w3.org/TR/2006/REC-xsl11-20061205/xslspec.xml

--

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

bugzilla | 28 Jul 2011 14:26
Picon

[Bug 13406] New: "caption-side" should be "Extended" conformance level

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13406

           Summary: "caption-side" should be "Extended" conformance level
           Product: XSLFO
           Version: 1.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P2
         Component: XSL-FO
        AssignedTo: tgraham <at> mentea.net
        ReportedBy: tgraham <at> mentea.net
         QAContact: xsl-editors <at> w3.org

The "caption-side" property [1] is listed in section B.3 [2], Property Table:
Part II, as having "Complete" conformance level.  It should be "Extended"
conformance level.

"caption-side" applies only to fo:table-and-caption [3], where it "specifies
the position of the caption box with respect to the table box."  The "caption
box" is the optional fo:table-caption [4] child of fo:table-and-caption.

fo:table-and-caption has "Basic" conformance level [5], and fo:table-caption
has "Extended" conformance level [5], but there's little point implementing
fo:table-caption without implementing "caption-side", since that is a major
part of the correct implementation of fo:table-caption.

Furthermore, "Extended" conformance [6] is defined as "includes everything
else, except for shorthands", and "Complete" conformance is defined as
"includes everything".  "caption-side" is not a shorthand, so it better fits
the definition of "Extended" conformance rather than "Complete".

Actually, defining fo:table-and-caption as "Basic" and fo:table-caption" as
"Extended" is odd in itself, since there's very little point in using a
fo:table-and-caption that doesn't have a fo:table-caption.  It would be better
to also make fo:table-caption have "Basic" conformance and move the fallback
currently defined for fo:table-caption to be the fallback for "caption-side".

Regards,

Tony Graham.

[1] http://www.w3.org/TR/xsl11/#caption-side
[2] http://www.w3.org/TR/xsl11/#prtab2
[3] http://www.w3.org/TR/xsl11/#fo_table-and-caption
[4] http://www.w3.org/TR/xsl11/#fo_table-caption
[5] http://www.w3.org/TR/xsl11/#d0e36675
[6] http://www.w3.org/TR/xsl11/#conform

--

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Julian Reschke | 13 May 2011 14:03
Picon
Picon

is there a media type for XSL-FO?

Hi there,

see the subject line -- is there a media type for XSL-FO documents? (I 
did check the XSL 1.1 spec, plus the IANA registry, but couldn't find 
anything...)

Best regards, Julian

bugzilla | 23 Mar 2011 13:32
Picon

[Bug 12369] New: Reference-orientation and writing-mode on page-master and regions

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12369

           Summary: Reference-orientation and writing-mode on page-master
                    and regions
           Product: XSLFO
           Version: 1.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSL-FO
        AssignedTo: Tony.Graham <at> MenteithConsulting.com
        ReportedBy: vhennebert <at> gmail.com
         QAContact: xsl-editors <at> w3.org

There seems to be ambiguities in the way the reference-orientation and
writing-mode properties should be handled on side regions.

fo:simple-page-master is used to generate a page-viewport-area/
page-reference-area pair. The reference-orientation of the page-viewport-area
is set to 0. In the description of Section 6.4.13, “fo:simple-page-master”,
there is the following:
• a note saying “For example, if the writing-mode of the fo:simple-page-master
is ‘lr-tb’, then these regions correspond to the body of a document, the
header, the footer, the left sidebar, and the right sidebar.”
• this sentence: “The ‘writing-mode’ of the page is used to determine the
placement of the five regions on the master.”

That seems to indicate that the value of the “writing-mode” property set on the
fo:simple-page-master is used to determine the placement of the regions.

• but further below there is this: “The reference-orientation of the
page-reference-area and writing-mode of the page-viewport-area are determined
by the formatting object that generates the area (see 6.4.5 fo:page-sequence).”

In Section 6.4.15, “fo:region-before”, there is this: “This region specifies a
viewport/reference pair that is located on the ‘before’ side of the
page-reference-area.”

So, if the fo:simple-page-master has a “reference-orientation” of 0 and the
fo:page-sequence a “reference-orientation” of 90, what prevails?

The existence of the from-page-master-region() function leaves to think that
the third point above should prevail. If that function is used, then the
reference-orientation and writing-mode properties set on fo:simple-page-master
would be used, otherwise this is the value of those properties as specified on
the fo:page-sequence element that would count. However, in Section 5.10.4 no
mention is being made of the fo:simple-page-master element. Only the regions
are mentioned.

If we assume that the from-page-master-region() function actually also applies
to fo:simple-page-master, and given the following XSL-FO document:

<?xml version="1.0" standalone="no"?>
<fo:root xmlns:fo="http://www.w3.org/1999/xsl/format">

  <fo:layout-master-set>
    <fo:simple-page-master master-name="page"
      page-width="21cm" page-height="29.7cm" reference-orientation="90">
      <fo:region-body margin-top="15pt" reference-orientation="90"/>
      <fo:region-before extent="10pt"/>
    </fo:simple-page-master>
  </fo:layout-master-set>

  <fo:page-sequence master-reference="page"
    reference-orientation="from-page-master-region()">
    <fo:static-content flow-name="xsl-region-before" font-size="8pt">
      <fo:block>xsl-region-before</fo:block>
    </fo:static-content>
    <fo:flow flow-name="xsl-region-body">
      <fo:block>lorem ipsum dolor sit amet, consectetur adipiscing elit.
        vestibulum arcu felis, gravida vitae laoreet in, molestie nec
        libero. mauris non enim diam. pellentesque nisl diam, aliquet
        nec euismod vitae, convallis nec massa. mauris gravida arcu ac
        erat euismod molestie. maecenas eget neque in sem aliquam
        viverra. vivamus dictum lobortis scelerisque.</fo:block>
    </fo:flow>
  </fo:page-sequence>

</fo:root>

Because the from-page-master-region() function is used, the
“reference-orientation” property specified on the fo:simple-page-master and the
regions would be used to determine their orientations.

So the content-rectangle of the page-reference-area would be like this:

    ___________________________
    |          end            |
    |                         |
    |                         |
    |                         |
    |                         |
    |                         |
    |before                   |after
    |                         |
    |                         |
    |                         |
    |                         |
    |                         |
    |                         |
    |_________________________|
              start

While the content-rectangle of the region-viewport-area for the region-before
is supposed to be like this:

     after
     ____
     |  |
     |  |
     |  |
     |  |
     |  |
  end|  |start
     |  |
     |  |
     |  |
     |  |
     |  |
     |__|
    before

which seems to be inconsistent with the description of fo:region-before:
    “The before-edge of the content-rectangle of this region-viewport-area is
positioned coincident with the before-edge of the content-rectangle of the
page-reference-area generated using the parent fo:simple-page-master. The
block-progression-dimension of the region-viewport-area is determined by the
extent trait on the fo:region-before formatting object.”

The inconsistency could be resolved by replacing content-rectangle with
border-rectangle in the excerpt above. Because, as explained in Section 4.2.3,
“Geometric Definitions”, the definition of the before/after/start/end-edges of
the content-rectangle of an area uses the inline/block-progression-direction of
that area; Whereas the border/padding/allocation-rectangles use the directions
of the parent area.

Thanks,
Vincent

--

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


Gmane