"Check Spelling in Files..." ignores Author Review PIs

[Frank Ralf]

Hi,

When spell checking a document in Author mode, oXygen takes the Author Review processing instructions into account and recognizes the following "describes" as spelled correctly:

Code: Select all

This document des<?oxy_delete author="frank" timestamp="20150428T144021+0200" content="k"?><?oxy_insert_start author="frank" timestamp="20150428T144022+0200"?>c<?oxy_insert_end?>ribes the support and setup.

However, when running the spell check from the Project View via Check Spelling in Files..., oXygen complains:

Code: Select all

Mispelled word "des", ...

Mispelled word "ribes", ...   

This creates a lot of false positives when spell checking a lot of files that have already been reviewed and corrected with active Author Review feature. Could that be amended?

Kind regards,
Frank

[Radu]

Hi Frank,

I understand, we have the same issue with using Find/Replace in Files to find content which might span over change tracking areas.
So right now both the Find/Replace in Files and Spell Check in Files work directly over the XML text content with problems like the ones you mentioned.
For Oxygen 17.1 (Autumn this year) we plan to allocate some time to make the find/replace in files work also over content as if it would be opened in the Author visual editing mode. If we manage to do this, we'll have the capability to also try this for the spell check in files.
So I will update this thread if we manage to fix this.

One thing you could try as a workaround would be to open the DITA Map in the DITA Maps Manager and use the "Open Map in Editor with resolved topics" action to open the DITA Map in the Author visual editing mode with all topics expanded in place as read-only content. This might take some time. Then you can press F7 to show the manual spell check dialog. Whenever you want to make a modification you can right click and choose Edit Reference to open and edit that particular topic.


Regards,
Radu

[Frank Ralf]

Hi Radu,

Thanks for your quick reply and the explanation. I had suspected something like that. Good to know that this problem is on your radar and will hopefully be solved in oXygen 17.1

Kind regards,
Frank