Vikas created FOP-2741:

             Summary: Exclamatory (!) symbol not being rendered properly in AFP
                 Key: FOP-2741
             Project: FOP
          Issue Type: Bug
          Components: renderer/afp
    Affects Versions: 2.2, 2.1
         Environment: OS: Windows 7 Enterprise
Java : jdk1.8.0_101
Encoding: ISO-8859-1
            Reporter: Vikas
            Priority: Blocker
         Attachments: C0EX0BG0, Exclamatory.afp,, fopTest.xconf, 

I am not able to render exclamatory (!) symbol in a AFP file. It is rendered as 
a Pipe (|) character instead.

*Below is the test fo file content,*

<fo:root xmlns:fo="";>
        <!-- defines the layout master -->
                <fo:simple-page-master master-name="first" page-height="29.7cm" 
page-width="21cm" margin-top="1cm" margin-bottom="2cm" margin-left="2.5cm" 
                        <fo:region-body margin-top="1cm"/>
                        <fo:region-before extent="1cm"/>
                        <fo:region-after extent="1.5cm"/>

        <!-- starts actual layout -->
        <fo:page-sequence master-reference="first">
                <fo:flow flow-name="xsl-region-body">
                        <fo:block role="p" >
                                <fo:inline font-family="Humnst777 BT">Surprise! 

*Below is the command used to generate afp file,*
  fop -c fopTest.xconf -fo -afp Exclamatory.afp

*Below is the FOP output,*
Sep 25, 2017 3:31:03 PM org.apache.fop.apps.FopConfParser configure
INFO: Default page-height set to: 11.00in
Sep 25, 2017 3:31:03 PM org.apache.fop.apps.FopConfParser configure
INFO: Default page-width set to: 8.50in
Sep 25, 2017 3:31:05 PM processEvent
INFO: Rendered page #1.

*I have tried below options, but could not get it to work*
 1. Tried with different font family (ex: Arial, Helvetica, Symbol)
  2. Used corresponding unicode "&#33;" instead of !

*Please find attached,*
 1. Test fo file
 2. FOP config file
 3. Afp output file
 4. Humnst BT 777 char set file
 5. T1EX0000 codepage

Appreciate your help on this blocking issue.

This message was sent by Atlassian JIRA

Reply via email to