LO88259: TEXT PARTS OF MIME MESSAGES WHOSE CONTENT-TYPE HEADERS HAVE NO CHARSET PARAMETER MAY RENDER INCORRECTLY ON TRAVELER DEVICES
Direct links to fixes
Closed as program error.
Character encoding information for a given MIME part of a document is usually listed explicitly in the Content-Type header of the same MIME part via the "charset" parameter. However, some clients may instead choose to transport the charset information inside the corresponding payload itself, in which case the charset parameter will not be specified in the Content-Type header. Traveler's previous handling of this second, less common scenario meant that some content (most often extended-ascii characters) would display incorrectly on Traveler devices, because we would forgo the necessary recording and translation required for these characters to display correctly on devices. With this APAR, MIME content from text parts without explicit charset parameters should display correctly on Traveler devices.
Some MIME Encoded documents may not render correctly on Mobile device if the charset is inline in the message.
This is an unexpected document format. The IBM Traveler server has been updated to handle this correctly.
This fix is included in IBM Traveler 184.108.40.206 and will be included in all future releases. For the latest available maintenance information see this technote: http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
LOTUS NOTES TRA
Fixed component ID
Applicable component levels