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

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):

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

where defaultWebEncoder is an object with org.owasp.esapi.Encoder class

Should we use a different approach? Ideas?

Jacopo


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

Hello Devs

In Accounting -> Reports PDF is not rendering properly for numeric value. For ex - It printed it like - $116.85
        I have verified it for Income Statement and Trial Balance.

Thanks And Regards
Sumit Pandit

Reply via email to