Details
Bug
Major
Description
This bug was span from PDF-783, the file in question uses mixed byte encoding on the T value of the text field dictionary. The problem here is the mixed byte format is non-standard and is making annotation edits incorrect.
When we do an edit we relay on the T value to get the actual text value of the annotation. When the annotation is rendered the first time the format is defined by the annotations content stream and drawn as a shapes. When we do an edit we need to decode the T value to get the original text value independent of the content stream. At this point the T value encoding issue shows up and we we get a lot of ? and or Unicode characters mixed with the correct content.
When we do an edit we relay on the T value to get the actual text value of the annotation. When the annotation is rendered the first time the format is defined by the annotations content stream and drawn as a shapes. When we do an edit we need to decode the T value to get the original text value independent of the content stream. At this point the T value encoding issue shows up and we we get a lot of ? and or Unicode characters mixed with the correct content.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 5.2.1 [ 12071 ] |
| Fix Version/s | 6.1 [ 12070 ] | |
| Fix Version/s | 6.0.1 [ 12071 ] |
| Fix Version/s | 6.2 [ 12974 ] | |
| Fix Version/s | 6.1 [ 12070 ] |
| Summary | Forms | Forms multi byte encoding issue |