Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.1.3
-
Fix Version/s: 6.2
-
Component/s: Core/Parsing, Viewer RI
-
Labels:None
-
Environment:any
-
ICEsoft Forum Reference:
Description
The community member has had trouble encoding 4-byte character codes in popup annotations. Further debugging on our end has shown the issue is related to how we are encoding the StringObject when we save the changes to file.
We are currently doing dump of the characters as a literal string. In order to handle a wider range of character codes we will need to encode the text values as hex strings. My initial prototype with popup annotations has shown this approach work as expected with all utf-8 values.
We are currently doing dump of the characters as a literal string. In order to handle a wider range of character codes we will need to encode the text values as hex strings. My initial prototype with popup annotations has shown this approach work as expected with all utf-8 values.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Marking as fixed.
Show
Patrick Corless
added a comment - Marking as fixed.
This has been a very interesting exercise as we have now settled on an octal encode string as it more easily encrypted the the a hex string. The Popup annotation box as well as any related annotation param can now use a mixed byte encoding. Further work however is needed to get the input fields working correctly when rendering the content stream, see PDF-1083.