This content has been marked as final. Show 4 replies
Are you using Listener 2.0.2? If not, please upgrade, as noted in the release notes , an issue with the handling of multi-byte characters on Windows (or any platform not using UTF-8 as the default character encoding) has been fixed in 2.0.2 (BUG:16715723)1 person found this helpful
I checked the web.xml of the APEX listener and found
Is this the correct indication of the listener version?
Sorry, I should have noticed you are following the old process to add FOP capability to APEX. This process does not involve Listener, you would get a more accurate answer by posting in the APEX forum I've asked an APEX colleague who is more expert on APEX printing to take a look at this thread, hopefully they will be able to point you in the right direction.1 person found this helpful
Listener 2.0.2 includes FOP support out of the box, so you might want to consider upgrading to that.
Thank you very much,
I have re-opened the issue in the Application Express group