-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spell check instructions #61
Comments
I did my spell checking via a very inelegant way that was not described in the lingcod discussion. I converted the compiled pdf to a word document which allowed me to check spelling across text, tables, and figures. The annoying part, of course, was then fixing errors by hand in each of the Rmd files. Not great but it worked for this assessment cycle. |
An option is to open each Rmd file in RStudio and use the spellcheck function under the "Edit" tab. It seems to overlook LaTex stuff, so doesn't get bogged down. Works well in my opinion. |
Thanks for the feedback on your workflow. I will try to document some options. |
@k-doering-NOAA and @iantaylor-NOAA do you have suggestions for how to do spell check on .Rmd files after working with the spell check and packages through nmfs-fish-tools/ghactions4r/issues/36? |
It appears that I have not used {spelling}, directly but am happy to help research this. Also, there's still value in checking the Rd files. I just ran
|
Following the example for
which found a bunch of non-standard words, none of which were actually misspellings. But I think that's because @kellijohnson-NOAA already did some form of spell check on the .tex files.
I think {sa4ss} could have a default WORDLIST that would include many of these things which would then be easy for individual assessment authors to update via |
Note that AFS has a list of individual words used in common and scientific names of fish (not full species names) for addition to spell checkers available from https://fisheries.org/books-journals/writing-tools/fishnames/. |
Bumping this issue in case it's useful for @okenk and @brianlangseth-NOAA. Running
Worked for me to produce a long list of 99% stuff to ignore, but easy enough to skim through to find the useful 1% like Example of the top of the list (I think all these belong as they are):
|
rstudio has a pretty good spell checker built in! (i.e., the typo has a little red underline in the editor) |
Problem
Spell check across multiple .Rmd files is difficult, especially if they include code and LaTex.
Proposal
💡 ?
🥒
More talk on the 2021 lingcod repository in Issue #70.
The text was updated successfully, but these errors were encountered: