Notes/Domino Fix List
 |  |
| SPR # AANA647HE7 | Fixed in 6.5.5 release | Regression in 6.0.3 |
Product Area: Client Technical Area: Editor Platform: Cross Platform
Lotus Customer Support APAR: LO03882
SPR# AANA647HE7 - Beginning in V6.5.5, the Notes Client Import and Export of RTF will be capable of using either the current V605/6.5.4 RTF conversion code or the new much improved RTF conversion code. By default V606/6.5.5 will run the new code. The user can make it run the old V605 code by adding "UseOlderRTFImportExport=1" to Notes.ini. Release 6.x, from 6.5.5 on, will have this dual RTF converter capability. Starting with 7.0, only the new RTF conversion code will be present. This regression was introduced in 6.0.3.
Technote Number: 1156923
Problem:
These issues were reported to Quality Engineering in a number of software
problem reports (SPRs):
-- The hang/crash issue was fixed in Notes 6.5.2/6.0.4 (SPR# MGAN5URTV8). This
fix affected consecutive end-of-table tags which were introduced by the use of
nested tables.
-- SPR# KMCL5Y4SWX: Further improvements related to formatting as well as to
the hang/crash were made in Notes/Domino 6.0.5 / 6.5.4.
Excerpt from the Lotus Notes and Domino Release 6.0.5 / 6.5.4 MR fix list
(available at http://www.ibm.com/developerworks/lotus):
Editor
SPR# KMCL5Y4SWX - Exporting to RTF results in error messages and badly
formatted Word documents. We fixed a problem that resulted in begin/end table
mismatched tags - and error messages in Word. We also improved the general
look/pagination of the exported document by 80-90% for low to medium complexity
mail messages. Problems relating to formatted tables will be fixed in another
release.
-- SPR# AANA647HE7: Used to track additional formatting issues including some
table formatting issues; fixed in Notes/Domino 6.5.5.
Excerpt from the Lotus Notes and Domino Release 6.5.5 MR fix list (available at
http://www.ibm.com/developerworks/lotus):
Editor
SPR# AANA647HE7 - Beginning in V6.5.5, the Notes import and export of .rtf will
be capable of using either the current V605/6.5.4 .RTF conversion code or the
new, much improved rtf conversion code. By default, V606/6.5.5 will run the new
code. The user can make it run the old V605 code by adding
"UseOlderRTFImportExport=1" to the notes.ini file. Releases 6 from 6.5.5 on
will have this .dual rtf converter capability. Starting with 7.0, only the new
rtf conversion code will be present. This regression was introduced in 6.0.3.
-- SPR# AMOR66JJ3Q: Used to track additional formatting issues observed when
the document contains an attachment.
Excerpt from the Lotus Notes and Domino Release 6.5.5 MR fix list (available at
http://www.ibm.com/developerworks/lotus):
Editor
SPR# AMOR66JJ3Q - When a rich text file containing tables was exported, the
letters appear unreadable and displayed vertically and the margins were
incorrect. This problem has been fixed in 6.5.5 and was a regression introduced
in 6.0.
-- SPR# RCHN667PD2: being used to track additional formatting issues observed
when the document contains an embedded object.
-- SPR# COY3N5QT8: introduced an enhancement to the export filters made in
Notes 6.0.1, that tracks additional functionality that included header
information during export.
Workaround:
If you haven't yet upgraded, create a form that doesn't use tables and/or
formulas, and then use View --> Switch Form to use the new form to display the
document while exporting.
Refer to the Upgrade Central site for details on upgrading Notes/Domino. More >
Last Modified on 12/03/2013
Go back
|