Re: PDF is not rendering properly.

[Scott Gray]

Hi Jacopo,




Regards
Scott

On 13/08/2009, at 10:07 PM, Jacopo Cappellato wrote:

I was a bit curious so I took a look, the problem was that the $ sign was being encoded twice, both by easpi and by freemarker so when fop came to decode it, it was going from &#36: to $

This is caused by the encoder used for special characters not working properly with our FOP framework. We can fix this by commenting out the following line in widget.properties:

screenfop.encoder=xml





   public static class XmlEncoder implements SimpleEncoder {
       public String encode(String original) {
           return StringUtil.defaultWebEncoder.encodeForXML(original);
       }
   }



Should we use a different approach? Ideas?

Jacopo


On Aug 13, 2009, at 9:03 AM, Sumit Pandit wrote:

but I am worried because we will then have issues with some special characters breaking the XML syntax of FO. The encoder that we are using for FOP (with screenfop.encoder=xml ) is (see StringUtil class): where defaultWebEncoder is an object with org.owasp.esapi.Encoder class

Hello Devs


        I have verified it for Income Statement and Trial Balance.

Thanks And Regards
Sumit Pandit

In Accounting -> Reports PDF is not rendering properly for numeric value. For ex - It printed it like - $116.85

smime.p7s
Description: S/MIME cryptographic signature