Hello, I'd like to submit a feature request. Currently, it appears you can run Spell Checker on only one file at a time. It would be nice to be able to run Spell Checker on multiple files in one operation: - Run Spell Checker on all files found inside a DITA Map - Run Spell Checker on all files in a Project Thanks very much! Seraphim
Hello, Now spell checking is applied only to the current file opened in an editor panel and the errors are corrected in interactive mode: mark an unknown word by selecting it in the editor panel and ignore or replace it with a suggestion from the spell dictionary, mark the next unknown word, etc. Running the spell checker in non-interactive mode (on a set of files specified in a project or a DITA map) implies a change in the mechanism for reporting and correcting the errors (for example to display a list with all errors in a panel at the bottom of the Oxygen window as in the case of the Find/Replace dialog vs. the Find All action) and also implies adapting the spell checking implementation to files not opened in an editor panel which is not trivial. Anyway we will consider your request for a future version of Oxygen. Thank you, Sorin Seraphim Larsen wrote:
Hello,
I'd like to submit a feature request. Currently, it appears you can run Spell Checker on only one file at a time.
It would be nice to be able to run Spell Checker on multiple files in one operation:
* Run Spell Checker on all files found inside a DITA Map * Run Spell Checker on all files in a Project
Thanks very much! Seraphim
I would suggest that it work something like this: - In the Map Editor, or in the Project View, select a new command: Check Spelling - If you were in Map Editor, it would start going through all the topic files referenced by topicref - If you were in Project View, it would go through all the files currently visible in the filter, or currently selected - It would scan each file for spelling problems. - If it doesn't find any (in any of the files), it would report that. - But if it does find any errors, it would open that topic file in the editor, and then kick off the normal file-based spell checker. - When that file-based process is done, ideally it would continue with the map/project-based process. - But even if it stopped after checking all the errors in that single file, and you had to manually re-start the map/project spell check, it would be a lot easier than what we have now. So, this might be easier than what you describe. I don't think it's necessary to generate a report in the error panel at the bottom of the screen, as for error checking. That would be cool, but not necessary. All it would really need to do is find each file, open it in the background, run a check; if spelling errors found, open the file, and start the usual spell-check process; if not, close the file and move on to the next. What do you think? Thanks! Seraphim On Wed, Jul 16, 2008 at 8:01 AM, Sorin Ristache <sorin@oxygenxml.com> wrote:
Hello,
Now spell checking is applied only to the current file opened in an editor panel and the errors are corrected in interactive mode: mark an unknown word by selecting it in the editor panel and ignore or replace it with a suggestion from the spell dictionary, mark the next unknown word, etc. Running the spell checker in non-interactive mode (on a set of files specified in a project or a DITA map) implies a change in the mechanism for reporting and correcting the errors (for example to display a list with all errors in a panel at the bottom of the Oxygen window as in the case of the Find/Replace dialog vs. the Find All action) and also implies adapting the spell checking implementation to files not opened in an editor panel which is not trivial. Anyway we will consider your request for a future version of Oxygen.
Thank you, Sorin
Seraphim Larsen wrote:
Hello,
I'd like to submit a feature request. Currently, it appears you can run Spell Checker on only one file at a time.
It would be nice to be able to run Spell Checker on multiple files in one operation:
* Run Spell Checker on all files found inside a DITA Map * Run Spell Checker on all files in a Project
Thanks very much! Seraphim
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Seraphim Larsen wrote:
o But if it does find any errors, it would open that topic file in the editor, and then kick off the normal file-based spell checker. * When that file-based process is done, ideally it would continue with the map/project-based process.
How could the process be stopped in this case? Would a Cancel button just skip the rest of the current file and start checking the next file or stop the whole process? A button Cancel and another one like "Cancel project level checking" just complicate the interaction of the user with the dialog for spell checking in the current file. I think it is more straightforward to show a progress dialog with a Cancel button and to update dynamically on screen a list of errors as they are found by a non interactive spell checking process.
* But even if it stopped after checking all the errors in that single file, and you had to manually re-start the map/project spell check, it would be a lot easier than what we have now.
If the operation stops after spell checking the first file in interactive mode does the user conclude that there are no more errors in the whole project or that only the first file was checked? I think users don't like ambiguities in a graphical interface. I think an action for spell checking the whole project/DITA map is expected to go through all the files of the project. If the action must be re-launched on the same project after finishing with the first file then it is not an action with project scope as the action name implies so it sounds like an incomplete implementation. Regards, Sorin
participants (2)
-
Seraphim Larsen -
Sorin Ristache