You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a growing interest in multilingual R packages, and this relates to recent rOpenSci work.
Would it be possible to add the ability to spellcheck a package with multiple languages? To address, e.g., the case when documentation or a README is provided in two languages (real-life example). I understand that this might then miss some typos because they are a valid word in the other languages.
From a quick glance, it looks like this might require a change to the hunspell (this change? ropensci/hunspell#37) so feel free to move there if you believe that's more appropriate.
The text was updated successfully, but these errors were encountered:
I'm not a linguist but I think the concept of "multiple languages" is a ambiguous. Would you expect it to be able to check sentences using a mix of languages and accept e.g. a spanish word pluralized with english grammar rules? What about chineese and english?
I think if you want to mix languages we probably need some way you can mark a specific section or file with a given language and we can check it in that language. But I generally feel it is a bad idea to randomly mix languages in a document...
Yes, I think you make a good point about using multiple languages in a single document. But let's say I want to use different languages in two different vignettes. How would you go with using spelling in this situation?
There is a growing interest in multilingual R packages, and this relates to recent rOpenSci work.
Would it be possible to add the ability to spellcheck a package with multiple languages? To address, e.g., the case when documentation or a README is provided in two languages (real-life example). I understand that this might then miss some typos because they are a valid word in the other languages.
From a quick glance, it looks like this might require a change to the hunspell (this change? ropensci/hunspell#37) so feel free to move there if you believe that's more appropriate.
The text was updated successfully, but these errors were encountered: