This is interesting, at least to me. I've just written a program to pull the italics from the RTF files created by Abbyy. In the book I've been experimenting with, there are 158 lines that have at least one italic word. As I edited that book with the ppe editor, I visually found and marked 65 of them. That's not even close to okay. To fit the editor on a laptop screen, I shrank the image window. A click on it zooms it up, but that is tiresome. Trying to spot italic markup in that too-small and greyscale window is clearly too difficult. One user emailed me that she found the small png window "useless." So I've made a version that has the png window the same size as the edit and analysis pane. That's much better, but now it needs a 1920x1080 display to fit. How many potential users did I just lose? Probably quite a few. I did another version that was two-paned: the image window and the text/analysis window. That fits on everything and allows the user to choose which of the two right panes--edit or analysis--is displayed. Either this or the three-paned version is a big improvement over what I used (and what's at http://etext.ws). The three-paned version is up at http://etext.co. Neither of these are sticky, because I have another project for DPC that I'm overdue to be working on that will consume at least one of those sites for development/testing activities. But back to the size of the png pane. How it's presented doesn't matter for the purpose of getting the italic markup right. I do not believe any process should rely on visual discovery in a markup-free text. Unfortunately, unless it has changed, that's the standard practice at DP. Since proofers are supposed to proof the words, the markup from Abbyy is routinely removed before putting it into the rounds. Then, in the later formatting rounds, the foofers are supposed to catch all of them and put them back in. Well, that doesn't work for me, since I've just demonstrated that I'm not good at spotting italics on a small screen. I'm guessing I'd still miss some even with the three-paned version. So bottom line I'm not going to trust myself and I'll trust Abbyy instead, which is actually very good at spotting and marking italics. The program I wrote is a short edit distance from what guiprep does. Mine is in Python and therefore easy for me to extend to all I would want from guiprep plus some things beyond what guiprep can do. That program, including the part that recognizes and tags italics, is what I'll use to prepare the next book project. --Roger