GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
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.
Hi, I try my best to use the right context on forums and stuff... However my first question is on continous sentences (Like the one I just did) do I capitalize the H? And is there a set number of commas I can not exceed in a sentence, and is it ok to ask another question in a sentence(Like I just did)? And lastly, is it ok to end your post without a period? For example, like this
Luckily English is a very vesatile language (the shortest proper sentence is "I am."). The first letter of a sentence should be capitalised. I treat commas as pauses for breaths in a conversation - read it back and imagine you are saying the sentence, the commas and full stops (periods) should fall into place naturally.
Best rule - use words, proper words, never use AOLspeak, you don't speak that way (except ironically/sarcastically) so don't write that way. Using full words also helps our non-native English speaking members.
I have no problem with multiple questions in a sentence, as long as question markes break them up. The exception to this, in my view, is where the questions are totally seperate from each other and should then be given there own sentences.
in my opinion you can use as much commas as you think is possible without making the sentence impossible to understand. questions and other stuff is just the same: use whatever you wish and come up with, as long as the text can be understood without any mathematical application suite or a genius
and then these "shortcuts" like imo or imho and so on - I'd like people to give up using them since they only make the text slower to read and understand ("imo u r newb 4real, r u or not?" is like hell...and this is only a _small_ example).
anyway, I'd say write what and how you like as long as you can be sure that it is understood it helps everybody read it quicker and answer better...if I bump into a text that I cannot understand without reading it 10 times letter by letter, I let it be and don't care no matter what the problem is it is describing. it's just that I can use my time better by answering to questions I can read normally....
of course, I'm just me - everybody has their own opinions about this
A good rule of thumb is to use short sentences. Is these situations it helps keep things clear. Basic punctuation like the period is also a good idea.
Long sentences, although perfectly clear when constructed correctly, can become difficult to comprehend if there are several thoughts or concepts contained withing the same sentence and this can confuse the reader and reduce the chances of getting an answer to a technical question which was already probably quite confusing.
Obviously posts like this are typed in a big hurry. I type dozens every night, so you have to expect a lot of mistakes. If you keep your post as clear as possible it will help get an answer.
Capitals come at the beginings of sentences. The number of commas will depend on the structure of the sentence. There are no set minimum or maximum limits.
I have a habit of using a lot of dots....I visualize it as two separate, yet related, sentences. I don't believe it's proper, but at the same time I don't think it is any more difficult to understand than a semicolon. The truth of the matter is I don't think semicolons are appropriate in prose....they should be left for coding as far as I'm concerned.
Spoken english is constantly evolving, and I believe written English would naturally follow. The exception is when it becomes ridiculously difficult to understand, as mentioned above. It's fine, however, to add your own flavor to your writing as long as it's legible.
Heheh - that reminds me of our old CEO who would send out his regular email to the staff filled with ... , as in:
"I was in Japan ... met with heads of trade ... very impressed with all we are doing .... have to remember that cost efficiency is needed ... met with the President ...." and so on. Really used to both wind me up and make me laugh - this man earned millions but couldn't put a proper sentence together.
... is used when paraphrasing and reducing - esp. when two thoughts from 2 sentences could be used as one sentence, as in "Spoken english is constantly evolving, ... It's fine, however, to add your own flavor to your writing as long as it's legible." you see? (not a perfect example).
The guy who first measured longitude accurately (Harrison the watch/clock maker) wrote an opening sentence in one of his books which was 24 pages long. Otherwise, writers tend to go for short, snappy sentences: "He shot him through the room." and suchlike.
"Spoken english is constantly evolving, and I believe written English would naturally follow."
The English alphabet does a poor job of representing spoken English. For example, the alphabet does not reproduce voice inflection. Punctuation makes a few pathetic attempts to reproduce inflection with ? and !. The Internet has invented emoticons which help some but there are still occasional flames over misunderstood voice inflections in written posts.
Many languages have much better alphabets. As an example I once listened to a Thai read a newspaper article to me about the Americans landing on the moon. The article was in Thai and the reader did not speak a word of English. Yet he pronounced the English words "Neil Armstrong", "rocket ship", and "Houston" perfectly with a Texas accent.
So I agree that both spoken and written English evolve but I think that there will always be a difference between spoken and written English in order to make up for the deficiencies of the English alphabet.