Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is there any way to make gedit recognize words with apostrophes when spellchecking? It always tells me that words like didn't and couldn't are misspelled.
Many spellcheckers have a learn feature. If your spellchecker does then you can add the apostrophe words to the dictionary the next time your spellchecker rejects them.
Well, it only checks the part in front of the apostrophe. For example, it says that "can't" isn't misspelled, because "can" is a word. But it says that "didn't" is misspelled, because "didn" isn't a word. I could add "didn" to the dictionary, but it's not a word, and it shouldn't be in the dictionary. Is there a way to make it check the whole word, and not just stop at the apostrophe?
Anyways, I remember my English teacher (not my native language) mentioning years ago that you shouldn't use apostrophes in written word anyways, for example "shouldn't" instead of "should not". I have no idea if that was just her being a know-it-all who doesn't really know-at-all, which was usual from her, or indeed wrong in some degree.
Anyways, I remember my English teacher (not my native language) mentioning years ago that you shouldn't use apostrophes in written word anyways, for example "shouldn't" instead of "should not". I have no idea if that was just her being a know-it-all who doesn't really know-at-all, which was usual from her, or indeed wrong in some degree.
I was also taught the same thing in school in the United States. I ignored the English teachers and have always used contractions in writing. I have never had a spell checker reject a contraction which was spelled correctly.
I think that the rules as taught by English teachers are about a generation behind current English usage. For example when I was in school the English teachers universally condemned the usage of the word "like" as a synonym for the word "as". The English teachers were ignored.
Back around 1900 American English teachers waged a campaign to keep "will" and "shall" as separate words. "will" was becoming used for both "will" and "shall". The English teachers were ignored.
One area where English teachers were successful about 1900 to 1930 was with the word "ain't". "ain't" is the contraction for "am not". At the time there was widespread misusage of "ain't" for all present tense of "to be". "I ain't, you ain't, he she it ain't, we ain't, you ain't, they ain't." The English teachers successfully drove "ain't" out of the English language. Unfortunately they also left us with no contraction for "am not".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.