I have been monitoring this problem for a little while now and it hasn't
yet disappeared.

This is what I have done and currently know:

I used the advanced find to locate all instances of double words and then
removed all of the existing double words at that point (about 2 weeks ago).
There were LOTS scattered through 300 pages of content. At a guess it could
be more than one per A4 page equivalent.

After removing the double words I have been frequently performing the
advanced find and replace to determine if they were randomly generated in
the document. No new double words were found in areas of the document that
hadn't been touched.

Double words were still created though. The only new cases of double words
have been in active areas of the document (i.e. in specific LyX file/child
that I have been working in and in the specific section).

At one point I believe that I pressed the space bar and I'm pretty sure it
created a double word on the key press (not 100% sure though).

e.g. I typed "The implications of rigid" with keystrokes like this:
"The<spacebar>implications<spacebar>of<spacebar>rigid<*spacebar*>"
And after the last <spacebar> following the word "rigid" a second rigid was
duplicated to give this:
"The implications of rigid rigid"

I didn't see the duplicate word happen, but I had stopped typing after the
word 'rigid' as turned a page. I looked back only to see the last word
duplicated.

It is still very frustrating, but at least knowing that it is occurring as
a result of keystrokes is a step forward. And with the advanced search and
find they are at least easy to remove.

FIND AND REPLACE QUESTION:
What would I need to put in the "Replace with:" section to delete a
duplicate word once found? Can it be done? Where would I have to look to
find out about the syntax for writing my own expressions?

I did try to create a user defined regular expression but because I really
have no idea about the syntax required, it just resulted in replacing the
duplicate word with the literal  expression plus with  \endregexp{} tacked
on the end.

Cheers
James

Reply via email to