While waiting for the ability to search for styles to be implemented, I'm resorting to finding by attribute in one document, to find all text of a specific character style in a copied document, so I can set the style correctly. I'm in the process of making the smaller paperback edition of my book (with a smaller font size throughout). (Incidentally, this task was made harder because the user defined character style information was not copied from one document into the other.) However, finding each use of my user defined character style is made especially tedious because using F&R with specific attributes (font size 10 in my case) in the source document also turns that F&R option on in the F&R panel in the copied document. This means when I search in the copied document for the text I found by attribute in the source document, you can't find it, because the copied document has no text with that attribute, and the F&R panel in the copied document switches mode when you change it in the source document. So you have to: 1) click No Format in the copied doc F&R, 2) enter some of the found text to search for in the copied doc 3) find the text and set the attribute, 4) then go back to the source document and click in its F&R panel 5) clear the text from the Find area because the search in the copied-doc wiped out the text entered in the Find field in the source doc F&R Find field (That 'Find text' can either be no text, which is unreliable; or ".*" and regexp enabled which is less unreliable) 6) click on the Format button in the F&R panel in the source doc and navigate through to choose the format you're after 7) find the next piece of text with that format 8) Repeat steps 1-7 for every piece of text with the user-defined character style in the source document. It's a massive usability failure. Especially because defining and using a character style makes the F&R unreliable. It seems to find random pieces of text with that format, and fail to find others. Nor does the pattern of success and failure to find text by format seem to relate to direct formatting. Not unless DF can creep in via even more operations than I'm aware of. I also note that DF is nowhere fully described or explained in the user guides.
Having problems to follow you. What I get is * Source file with some direct formatting (or character style) (DF/CS) * Copy/paste into target * F&R in the target for the DF/CS formatted text => issue is that DF/CS is not taken into the target Cannot confirm this behavior. Please provide a step-by-step instruction with the minimum required steps.
I just had a quick try to reproduce this, and the behaviour is more complex than I thought. When I reported the bug, it was because it seemed basically like there was only one F&R panel settings shared between the documents: that changing settings in F&R in one doc changed the settings for the F&R in the other. That's how it seemed to be behaving. I have experienced this often enough over the years but it finally became irritating enough to report. But now trying to reproduce with two documents open and opening the F&R panel in each, I can't reproduce it. I have noticed a separate problem while trying: In one F&R I set the Format I was searching for, to Italics. When next I went into Format, the font attribute was not set to Italics, so it's not easy to see what settings you have selected. I then set the font size I was searching for (via Format panel) to 10 pt. When I closed and re-opened the panel (which showed the search now was for italic, 10 pt), and went back into Format, Italics was not shown, but the size (10) was. All the settings chosen should be shown I feel. Anyway, it's strange: the behaviour today is quite different to what I reported it. Oh: I'm now using 7.0.3.1, and the problem I reported was in 7.0.2.2.
(In reply to Luke Kendall from comment #2) > Anyway, it's strange: the behaviour today is quite different to what I > reported it. > Oh: I'm now using 7.0.3.1, and the problem I reported was in 7.0.2.2. Don't think something has changed there. Just reopen if you can reproduce the issue.
(In reply to Heiko Tietze from comment #3) > (In reply to Luke Kendall from comment #2) > > Anyway, it's strange: the behaviour today is quite different to what I > > reported it. > > Oh: I'm now using 7.0.3.1, and the problem I reported was in 7.0.2.2. > > Don't think something has changed there. Just reopen if you can reproduce > the issue. Hmm.. or M. Stahl solved it .. there where some cursor issues, I think. 'speculation' quality.. but doesn't matter anyhow