B
Bas van der Doorn
Hello,
I am trying to use the RTF code from a RTF2 1.8 control in a Word document
after exporting it through an Access report and clearing the RTF header and
other Access export garbage with a script. The issues below are not caused
by this however, as they can be reproduced by copying the RTF code in the
Access table to a textfile and renaming it to RTF. Word has one problem
reading bulleted lists created by RTF2 version 1.8:
- The biggest problem with a bulleted list is that it is closed by
\line\pard\par, which WordPad can read correctly, but Word XP cannot. The
solution I have found to this probem is using \line\par\pard, which
interchanges \par and \pard. Now both Word and Wordpad can read it
correctly.
The next 'problem' is a result of my usage of the RTF2 control. I hope it
will be acknowledged however.
The last item of the bulleted list is closed with \line\pard\par (or
\line\par\pard after fix) and immediately (without whitespace) followed by
the next textline (I know that there is a newline character in between when
RTF2 saves it). This happens not when copying the RTF text, but only when
exporting it through an Access report, which unfortunatly deletes the
end-of-line character when exporting the RTF code. This results in the first
word of the following sentence not being displayed properly in word.
Inserting one space character after each \pard (if fix above is applied)
would also solve this problem for me. Since the space character would be
between the markup code, it should not have any impact on compatibility or
the displayed text at all. I fully understand if this white space is not
welcome and will not be implemented though. I can always expand my own
script to search for \pard (or \par) and insert one space character behind
it.
Could mister Lebans please shed some light on this situation and hopefully
come up with a fix for at least the first problem above?
Thank you very much,
Bas
I am trying to use the RTF code from a RTF2 1.8 control in a Word document
after exporting it through an Access report and clearing the RTF header and
other Access export garbage with a script. The issues below are not caused
by this however, as they can be reproduced by copying the RTF code in the
Access table to a textfile and renaming it to RTF. Word has one problem
reading bulleted lists created by RTF2 version 1.8:
- The biggest problem with a bulleted list is that it is closed by
\line\pard\par, which WordPad can read correctly, but Word XP cannot. The
solution I have found to this probem is using \line\par\pard, which
interchanges \par and \pard. Now both Word and Wordpad can read it
correctly.
The next 'problem' is a result of my usage of the RTF2 control. I hope it
will be acknowledged however.
The last item of the bulleted list is closed with \line\pard\par (or
\line\par\pard after fix) and immediately (without whitespace) followed by
the next textline (I know that there is a newline character in between when
RTF2 saves it). This happens not when copying the RTF text, but only when
exporting it through an Access report, which unfortunatly deletes the
end-of-line character when exporting the RTF code. This results in the first
word of the following sentence not being displayed properly in word.
Inserting one space character after each \pard (if fix above is applied)
would also solve this problem for me. Since the space character would be
between the markup code, it should not have any impact on compatibility or
the displayed text at all. I fully understand if this white space is not
welcome and will not be implemented though. I can always expand my own
script to search for \pard (or \par) and insert one space character behind
it.
Could mister Lebans please shed some light on this situation and hopefully
come up with a fix for at least the first problem above?
Thank you very much,
Bas
