Hide Forgot
Help Desk Ticket Reference: https://na7.salesforce.com/500A0000008UApw Workaround Description: 1. Serve the resource as binary 2. Set the default system encoding to ISO-8859-1 project_key: JBEPP Platform issue for GTNPC-78 Text encoding is lost in serveResources
Link: Added: This issue depends GTNPC-78
Tentatively set for 5.2.1
Release Notes Docs Status: Added: Not Yet Documented Release Notes Text: Added: When serving content from a portlet, the encoding of the resource gets rewrote with the default encoding of the running JVM
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Known Issue Release Notes Text: Removed: When serving content from a portlet, the encoding of the resource gets rewrote with the default encoding of the running JVM Added: When serving content from a portlet, resource encoding is being rewritten with the default encoding of the running JVM. To work around the issue, server the resource as a binary, or set the default system encoding to ISO-8859-1.
Issue has now been fixed in EPP svn repository and will appear in the next version. Please note that there are a couple of issues with the example application attached to this jira, so the example application may not work as expected.
Release Notes Docs Status: Removed: Documented as Known Issue Added: Not Yet Documented Release Notes Text: Removed: When serving content from a portlet, resource encoding is being rewritten with the default encoding of the running JVM. To work around the issue, server the resource as a binary, or set the default system encoding to ISO-8859-1. Added: Updated the portlet resource handling to take into consideration the encoding of the mime type when outputting byte array data.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: It was discovered that when content was served from a portlet, the resource encoding was being rewritten with the default encoding of the running JVM. To work around the issue, users had to serve the resource as a binary, or set the system encoding to ISO-8859-1. The fix implements improved resource handling, which honors the mime type encoding when outputting byte array data.