Classification: NOT PROTECTIVELY MARKED
I don't know if this is a bug but I can't find anything about it
anywhere else.
I have a number of docs with text insets. When I do an update, an extra
carriage return is added at the end of the inset which duplicates the
paratag of the first line of
Hi Cynthia
I don't know if this will help or not...I ran into something many years ago,
only it was an autonumbered paragraph not a page break. After much futzing,
fiddling and testing, I came up with something that works.
1. Make sure the end-of-file marker is immediately after the last
Milton, Cynthia wrote:
I have a number of docs with text insets. When I do an update, an
extra
carriage return is added at the end of the inset which duplicates the
paratag of the first line of the inset. The first paratag is a section
head with a page break, so this also is duplicated. The
Hi Cynthia
I don't know if this will help or not...I ran into something many years ago,
only it was an autonumbered paragraph not a page break. After much futzing,
fiddling and testing, I came up with something that works.
1. Make sure the end-of-file marker is immediately after the last
Milton, Cynthia wrote:
> I have a number of docs with text insets. When I do an update, an
extra
> carriage return is added at the end of the inset which duplicates the
> paratag of the first line of the inset. The first paratag is a section
> head with a page break, so this also is duplicated.
Classification: NOT PROTECTIVELY MARKED
I don't know if this is a bug but I can't find anything about it
anywhere else.
I have a number of docs with text insets. When I do an update, an extra
carriage return is added at the end of the inset which duplicates the
paratag of the first line of
