![]() ![]() I also have a file tex_conf and my_spelling in the same directory as my. In this example I'm checking all files in the executed directory with a. ![]() Typically, in my projects I would provision a simple shell script ( check_spellings.sh): #! /bin/bashĪspell -c -t *.tex -conf=./tex_conf -add-extra-dicts=./my_spelling These files are easier to manage and curate for larger projects and can also be version controlled (hopefully with the rest of your project files) and distributed with your content. I'd recommend creating project-level tex_conf and my_spelling files. However, rather than configuring aspell's behaviour at the command line with -add-tex-command=, -rem-tex-command=, etc. (It's trivial to update this: just don't want to pester CRAN.)Īs other users have advised, aspell is a good tool to use for this problem. In the next version, I'll allow any hunspell dictionary. The contents of \input and \include files are checked recursively.ĭue to an oversight, I check against the en_GB dictionary and don't provide the user to select a dictionary. Valid English contractions are not considered spelling errors. The Quebec Xylophone Enterprise Foundation (QXEF) is fictional.Īuthor names in the bibliography are automatically added (with a note). The ability to detect acronyms and add them automatically to the dictionary, so the following will pass. ![]() The ability to fail on certain words, to maintain consistency The ability to add words to the dictionary on a document-by-document basis, by adding You can also add commands whose contents will be ignored. Ignores the contents of commands which don't print, for example the contents of \labels and cite commands, which hunspell spuriously raises as possible spelling errors.The check_spelling command from my R package TeXCheckR is designed to enhance the features in hunspell. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |