Swapnil Khante created FOP-2375:
-----------------------------------

             Summary: Problem while generating ps output in arabic 
                 Key: FOP-2375
                 URL: https://issues.apache.org/jira/browse/FOP-2375
             Project: Fop
          Issue Type: Bug
          Components: ps
    Affects Versions: 1.1
         Environment: Windows 7, 2 GBram
            Reporter: Swapnil Khante
             Fix For: 1.1


We are generation a ps and pdf output using Apache FOP 1.1. We are using .ttf 
fonts for the same. PDF output seems to be fine but we are getting some garbage 
text while generation ps output. As per Apache documentation, ps output format 
only supports type 1 fonts so we have tried using .pfb fonts but problem is not 
resolved. When output is generated text on first page of output is fine but 
from page 2 onward we are getting garbage text. Observation was that if some 
text is outputted on first page and again on next pages it displays fine but if 
some text is first time used on second page or onwards we are facing this 
issue. Below is the entry that we are using in our .xconf file
    <renderer mime="application/postscript">
      <!-- This option forces the PS renderer to rotate landscape pages -->
      <!--auto-rotate-landscape>true</auto-rotate-landscape-->
      
      <!-- This option lets you specify additional options on an XML handler -->
      <!--xml-handler namespace="http://www.w3.org/2000/svg";>
        <stroke-text>false</stroke-text>
      </xml-handler-->
          <filterList>
                        <value>null</value>
                </filterList>
                <filterList type="image">
                        <value>flate</value>
                        <value>ascii-85</value>
                </filterList>
          <fonts>&tripleFilepfb;</fonts>
          <disable-srgb-colorspace>true</disable-srgb-colorspace>
    </renderer>

where tripleFilepfb points refers to .xml file containing .ttf fonts



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to