Getting Eclipse CDT to spell check non-source files

Home > e-infrastructure, service-is-configuring-learning-tools, service-is-documenting > Getting Eclipse CDT to spell check non-source files

Getting Eclipse CDT to spell check non-source files

2015/03/02 plagwitz Leave a comment Go to comments

Problem:
1. Using Eclipse Luna CDT, with C/C++ spelling engine, to document C and C++ code in Doxygen (Eclox plugin),
2. Spell check works for inline Doxygen documentation. My API-level code comments in *.[ch](pp)* files gets spell-checked alright (Well…:
  1. I had to download a decent dictionary to avoid recommendation like this one: . I am using the aspell dictionaries from here and here. This is before a restart/recheck:
  2. I still do not know how to teach the C++ spell check engine that a newline does not start a new sentence:
  3. The oft-referred to menu: Edit / Spell check does not show up for me:
3. However, spell check ignores my standalone *.dox files with high-level documentation.
What I have tried:
1. Telling Eclipse about the*.dox file type:
2. Associating *.dox files with the Doxyfile editor: . Fail. This tool from the Eclox plugin seems to help only with the editing of the Doxygen config file.
3. Associating *.dox files with C/C++-editor: Fail: has no effect.
Workaround:
1. Terrible, but since a similar question is still open on stackoverflow): If you can (*.dox requires all comments to be within c-style comments anyway), rename your *.dox files to *.dox.cpp. Terrible, but works:
2. A bit less terrible if you mange to store your standalone *.dox files as *.dox.cpp permanently do this if you get your Doxygen to handle these extensions.
3. What is nice to see is that the spell-checker recognizes Doxygen’s built-in reserved words (as opposed to my custom-defined Doxygen-commands).
Other things to try:
1. I could not get Hunspell4Eclipse to work, despite going to considerable trouble getting the marketplace into my Eclipse installation
2. I have not tried eSpell.