Parser RTF
Version 1.29 I-32 Release 2020.1
Memory corruption issues addressed.
Memory leaks addressed.
| I-32 Parser RTF: Aligning text when tab is present |
|---|
|
Summary: Previously, if a tab character was present in a text line in the
source document, the text was added in two parts: one item was an inline field
and the other a text block. This was transparent to the user, but when generated
the alignment of these two items was off.![]() I-32 Parser RTF has been updated so that the presence of a tab character does not affect the alignment of multiple fields in the same row. |
| Implementation Notes:This feature requires an I-32 Parser RTF update. |
| Parser RTF: Right-justified text honored |
|---|
|
Summary: Previously, there were instances in which an original RTF
document was formatted with dot leaders and properly right-justified.![]() When the output to UFF was generated, the text was
unexpectedly wrapped. ![]() |
| Technical: Now, output to UFF formats the right-justified text correctly |
| Implementation Notes: This feature requires a Parser RTF update. |
| RTF Conversion Issue |
|---|
|
| Issue: While converting some RTF files, the RTF parser would generate a memory allocation error. |
| Solution: Updates were made to handle the measuring of a row of content which caused a memory allocation error. |
| Implementation Notes: This feature requires a Parser RTF update. |
Version 1.28 I-32 Release 2019.1
| RTF formatting overlay issue resolved |
|---|
|
| Issue: Previously, when a header had text and a bitmap image, the header was being formatted in a manner that caused the text to display behind the bitmap image. |
| Solution: Now, the RTF Parser correctly positions the various header elements as they appear within the RTF file. |
| Implementation Notes: This feature requires a Parser RTF update. |
| Text is outside the cell/displaying on the boarder and text image |
|---|
|
| Issue: Text inside of the RTF was exceeding the define area for text, this then caused the possibility of other text to not be seen. |
| Solution: Adjustments were made to the way space is calculated and allowed for text to move into the area to the right of the text. |
| Implementation Notes: This feature requires a Parser RTF update. |
| 2nd page created |
|---|
|
| Issue: As part of the RTF Conversion when generating output file, the bottom margin wasn’t considering the height of the footer. This in turn was causing a second page to be generated when not expected. |
| Solution: Updates were made to the calculation of the margin to include the footer height and will no longer create a second page. |
| Implementation Notes: This feature requires a Parser RTF update. |


