Just a couiple of guesses. Word 2003 could be trying to cope with the
possibility that some fields (particularly INCLUDETEXT and AUTOTEXT) might
insert a section break and the \sectd is there to try to re-impose the
section formatting that existed prior to the field. Or it may be something
to do with the possibility that a MERGEFIELD might insert RTL text into an
otherwise LTR paragraph (or vice versa).
I have to say I've only looked at the RTF encoding to try to understand or
solve very specific problems so do not have good instincts as to why you
might need a \sectd.
--
Peter Jamieson
http://tips.pjmsn.me.uk
"Amdious" wrote in message
...
Hello,
I'm trying to figure out why something changed from Word 97 to Word 2003.
I'm inserting a basic MergeField into a Word .doc file contained within a
formatted line.
ie.
Why does MergeField «TEST» Kill the tab in WordPad
I have a left indent before the "Why" so I get a \li720 for the format of
"Why does..." and when I insert the «TEST» mergefield in appends a \sectd
to
the end of the field keyword section that terminates the formatting and if
I
open the file in WordPad the left indent is removed.
ie.
Why does MergeField «TEST» Kill the tab in WordPad
It's simple enough to reproduce by creating a new file, move the left
indent
margin to the right, write some words, insert the MergeField write more
words, then save the file as RTF. Open the file in WordPad and the \liN
will
not be recognized. I tried the same thing in Word 97 and the \sectd is
NOT
applied to the end of the MergeField. I believe Office 2000 will not
apply
the \sectd either. The file looks fine in Word, but not in WordPad. I'm
guessing the \sectd was applied on purpose, but I need to know why and how
to
have it removed such that I can retain the line formatting.
Thank you in advance.