Uploaded image for project: 'FOP'
  1. FOP
  2. FOP-1705

added regression to font-shorthand-test.fo that shows bug

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Resolution: Duplicate
    • 0.95
    • None
    • fo/unqualified
    • None
    • Operating System: Windows XP
      Platform: PC
    • 47859

    Description

      I added a regression to font-shorthand-test.fo that shows a bug in font shorthand capability.

      We apparently have trouble handling the case where a quoted font follows an unquoted font in the comma separated list of fonts.

      Here is the case that fails:

      <fo:block font="xx-large/1.4 Arial, 'Times New Roman', sans-serif">
      <test:assert property="font-family" expected="[Arial, Times New Roman, sans-serif]"/>
      <test:assert property="font-size" expected="20736mpt"/>
      <test:assert property="font-weight" expected="400" />
      <test:assert property="font-style" expected="NORMAL" />
      <test:assert property="line-height.optimum" expected="29030mpt" />
      <test:assert property="font-variant" expected="NORMAL" />
      Test font shorthand
      </fo:block>

      The error message is the following:

      file:/C:/perforce/Users/levinson/fop-trunk/test/fotree/testcases/font-shorthand-test.fo Property 'font-family' expected to evaluate to '[Arial, Times New Roman, sans-serif]' but got '[sans-serif, Symbol, ZapfDingbats]' (test:assert in fo:block at line #72, column #94)

      I add a patch file.

      Attachments

        1. font-shorthand-test.patch
          2 kB
          Jonathan Levinson
        2. FontShortHandProperty.patch
          2 kB
          Jonathan Levinson

        Issue Links

          Activity

            People

              fop-dev@xmlgraphics.apache.org fop-dev
              levinson@intersystems.com Jonathan Levinson
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: