Next Question
RSS
Darned if I know. I've gotten on rolls where the result ended up being one sentence per paragraph, and it was all grammatically correct.
It wasn't such a problem until one day I got the idea to learn the Blackfoot language. It's every interesting, because they don't have "words" per say... rather, they phonemes and morpheme, which by themselves don't express a pure concept, such that you have to string at least two of them together to get what we'd all a rod.
The closest example I can think of in English would be "ing". By itself "ing" doesn't mean anything. You have to say "running" for it to have meaning.
Well, they have a language where it's *all* pieces of phoneme, and they literally construct words on the fly from the phonemes, such that two different Blackfoot speakers can come up with two different words for the same concept... sort of like how in English Ox and Bull both mean a male cow, but in English those are both valid words.
In Blackfoot, they do to the phonemes of words like we can do to words in a sentence, where "She ran", and "Ran she did" mean the same thing even though the words are in different order... it's like to them, running and ingrun are both valid for the same concept.
Consequently, the really good Blackfoot speakers can string together phonemes like beads on a chain to have it where one word says what a whole sentence would in English... and I think that in German they sort of agglutinate phonemes that way, although I doubt to the same extent... but it's why native Blackfoot speakers used to have such a hugh regard for what they called their "Great Speakers". With Blackfoot, if they had a great speaker, they'd love to sit around the campfire and hear the speaker tell a story with a whole new freshly minted agglutinated phonetic set of words that nobody had ever heard said that way before.
I knew a guy... Dr. Don Frantz, who's goal was to make a Blackfoot-English Dictionary, and he nearly lost his mind. It ended up being a funny sort of lookup-grid to show combination's of phonemes that would make different words that would mean the same things, and even then there were old-time native speakers who were telling him he wasn't quite covering it all.
The point is... ever since I studied Blackfoot, it mangled my ordinary sense for where sentences should begin and end, and it turned me into a guy who would hyphenate twelve words into one supercalifragilisticexbialodocious word if the spell-check software would let him get away with it.
Which means, I have to remember a rule of thumb, and for English, the rule of thumb for when to drop a period is this: One sentence equals one complete thought.
Which means, technically speaking, if a paragraphs length sentence is expressing one single complete thought with all its nuances, then by the rules of grammar it's a valid sentance, which means, it boils down to a question of style.
For that, I use a second rule of thumb taught to me by the great Gudrend Hess, niece of the German writer Herman Hess.
She told me that in German, sentences could become very run-on, and that one had to choose to draw an arbitrary line, and that when she was writing for a north American audience, she would punctuate her sentences with periods when she though it would break it into pieces that would be a complete thought to a twelve year old.
I asked her why a twelve year old, and she said because that was the average level of literacy in America, and as a writer, she wanted to reach the maximum audience to within one standard deviation of the literacy level of the average.
So... according to my Linguistics prof Gudrend Hess... break your sentences into bite-size pieces where each one represents a complete thought comprehensible to a mentally sound graduate of the sixth grade.
Permalink | Report
To get rid of the run on sentence, read it in parts. Look at the overall sentence and determine how many individual pieces you have in the sentence. Are you combining multiple ideas into one? For each sentence determine if you can break it into more than one without making it choppy.
As you practice doing this in edit mode, you will become more in tune with how the sentences you end with are flowing and should be able to work that style into the original written text in the future.
Tags: editing, grammar, writing
Helpful Answer?
(3)
(0)
Permalink |
Report
I've only been publishing online for going on three years, and when I look back on some of my old stuff, I can see how I've improved. So hang in there, it's a learning process!
Tags: editing, writing
Helpful Answer?
(2)
(0)
Permalink |
Report
Maybe I can help you a little. Let's look at your opening sentence:
"Upon deciding recently to become a writer, I have been practicing my style, and it has come to my attention that one of my major flaws is that I use a lot of run-on sentences."
Now lets see if we can pare it down a bit.
"Soon after I decided to become a writer, I discovered a major flaw while practicing my style. I use a lot of run-on sentences."
Notice that I kept the last eight words of your sentence exactly as they are, only changed to a simple declarative statement. You correctly identified and placed that thought as the pivot to your next topic; "what will I do to improve"?
Write your first draft however you like, then edit. Try to limit yourself to one comma per sentence at the beginning, just as an exercise. It will become easier with practice. Try to identify the important thoughts, and separate them from those that could be eliminated or combined. Look for words you can do without, like "and", "that", and "which". You may try making a numbered list of your thoughts. Looking at them in that format may help you to prioritize them, group them or eliminate those that may duplicate or seem unnecessary.
I commend you for attempting to begin reaching one of the primary accomplishments of writing, "economy of expression". Edgar Allan Poe became so skilled that many of his short stories can almost be read as poems. Ezra Pound was another famous proponent. "The young Pound shared Edgar Allan Poe's conviction that any word unessential to a work should vacate the premises."
http://www.hanknuwer.com/ezra.html
See if this sentence and it's edit make sense to you:
"I am like you in that I like to write, and there is almost nothing I would like to do better, because it makes me feel good to get my thoughts on paper."
OR
"I, like you, am fond of writing. Nothing makes me feel better than capturing my thoughts on paper."
It is probably worth your time to brush up on different types of sentences, so that by varying them, you will be able to create the effect you are seeking. You will come to know why you are choosing a conpound-complex sentence and or why you are choosing a simple declarative statement.
You are not at the mercy of your sentences, you are their God. You can create them and annihilate them as you wish! Rule them wisely!
Disclaimer: I may be totally wrong.
http://www.youtube.com/watch?v=BgkzMKlXFdI&feature=fvw
Helpful Answer?
(8)
(0)
Permalink |
Report
---quote---
The easiest way to avoid run on sentences is to scan the sentences you have written when you do your proofreading. Look for subjects and verbs. Determine if you have written two sentences. If you have, be sure you have joined them in one of the following ways.
----end of quote--
Tips on avoiding run on sentences.
1. Join sentences with junction to coordinate them.
2. Use a semicolon to join sentences.
3. Use therefore, however, nevertheless, consequently, etc.
Source(s):
http://www.authorsden.com/visit/viewarticle.asp?id=19869
Permalink | Report
Also, I don't recommend relying on software for grammar checking. My experience has been that MS Word, for example, simply does not like long sentences, even when they are grammatically correct and express a complete, albeit complex, thought.
Sentence length and complexity is often a matter of personal choice. Long-winded sentences and run-on sentences are not the same entity. I tend to favor long, unwieldy sentences, and I've noticed that some of my proofreaders prefer them shorter while others are perfectly fine with them as they stand. Sometimes it's worth breaking up longer sentences for clarity, but other times I prefer to keep them on the rationale that the thought they express is suffers from being divided.
Permalink | Report
It would probably stunt your stream of conscience to be constantly thinking about things as you write. You need to concentrate on the story, get the ideas down and then worry about the details later.
So, like you suggested, wait until you are editing and re-reading what you write to worry about it. If something reads weird it probably is weird.
Of course you could always set up a macro that will mark repetitive use of joining words as a spelling error. :)
Permalink | Report
I tend to have both run ons and sentence fragments when I first write things out, especially in a forum like MA where it is more like a conversation. For that, it is not so important to catch them, but since I also design websites, and do Mahalo pages, it IS important to be clear and catch these things.
What *I* do to catch them is read my work over before submitting... if it seems odd but I just don't see what the problem is, I read it out loud.
You would be surprised what you will find reading your work out loud. This is especially true if you've read and re-read your work many times, as I do on websites, or for research projects I've done.
Since I know what I am saying, I tend to fill in the correct info when reading it silently. But reading out loud makes me change all kinds of things. I choose better words, tenses, change punctuation, and catch any sentence fragments or run ons that would have been there.
I find that my finished work is much more polished than it otherwise would have been...
and a final tip... if it is something important... especially if you will not be able to edit it, (if time allows) walk away from it and come back at another time.
a fresh set of eyes catches things that otherwise might have been missed.
=)
Source(s):
personal experience and my 2 cents...
Tags: proofreading, grammar, runon, english
Helpful Answer?
(1)
(0)
Permalink |
Report
First: See if anything after a conjunction (such as "and") can be formulated into a new sentence.
Second, a tip from my high school English teacher: When you write a rough draft for a piece wait 24 hours before you revise it. That allows you to clear your head a bit and come back to revise the contents.
Third: If you have a friend or family member who doesn't mind looking over the writing for you, by all means ask, even pay them a small commission when it sells.
Good luck with your writing adventures.
Permalink | Report
1. Microsoft provides a grammar checker on your computer that will highlight the errors which can be accessed by opening up Microsoft word and clicking on the button in the top right hand corner, there you will see a box in the lower right hand corner "word options", click on it and then click on proofing.
You will need to check the following boxes:
a. ignore words in uppercase
b. ignore words that contain numbers
c. ignore internet and file addresses
d. flag repeated words
e. check spelling as you type
f. use contextual spelling
g. mark grammar error as you type
h. check grammar with spelling
2. There is another spell checker right when you open microsoft work, located in the upper right hand corner " spelling and grammar checker"
3. Free grammar checkers on the web.
•Spellchecker.net
•Grammar Slammer
www.whitesmoke.com
Permalink | Report
(This sentence is a run on because there is not a comma in front of the short conjunction that joins the two sentences.)
2. It is possible you might accidentally use "only" a comma to join two sentences which creates a comma splice, and a run-on sentence. For example: The current was swift, he could not swim to shore.
(This sentence is a run on because you cannot join two complete sentences with just a comma.)
3. Sometimes you might join two complete sentences without any punctuation at all. For example:
The current was swift he could not swim to shore.
(This sentence is a run on because there is no punctuation or conjunction between the two complete sentences.
The easiest way to avoid run on sentences is to scan the sentences you have written when you do your proofreading. Look for subjects and verbs. Determine if you have written two sentences. If you have, be sure you have joined them in one of the following ways.
(1)You can join two sentences with a coordinating conjunction:
,and ,for
,but ,nor
,or ,yet
(Be absolutely sure you place a comma in front of these short conjunctions.) For example:
The current was swift, and he could not swim to shore.
(2) You can join two sentences with a semicolon (;)
(Be sure the sentences are fairly short and closely related.
The current was swift; he could not swim to shore.
(3)You can join two sentences with a longer conjunction such as therefore, moreover, nevertheless, consequently, etc. If you use a longer conjunction, you must place a semicolon in front of it and a comma after it.
For example: The current was swift; consequently, he could not swim to shore.
If you are careful to determine that you have written two sentences, and then join them together with the proper punctuation, the problem of using run-on sentences in your writing will disappear
Permalink | Report
Answered Question
M$3.23
November 02, 2009 06:16 AM
How to avoid run-on sentences?
Attention: Writers!
Upon deciding recently to become a writer, I have been practicing my style, and it has come to my attention that one of my major flaws is that I use alot of run-on sentences.
I tend to be overly descriptive and long winded. Is there a way that I can avoid the run-on sentence, or should I leave it to the editing? I find that sometimes I have an idea that starts out clearly, but the more I mull it over, the more details come to mind, and by the time I get it on paper my main ideas are being lost in an abundance of information.
Is this a problem that other people have? How do you avoid it?
Upon deciding recently to become a writer, I have been practicing my style, and it has come to my attention that one of my major flaws is that I use alot of run-on sentences.
I tend to be overly descriptive and long winded. Is there a way that I can avoid the run-on sentence, or should I leave it to the editing? I find that sometimes I have an idea that starts out clearly, but the more I mull it over, the more details come to mind, and by the time I get it on paper my main ideas are being lost in an abundance of information.
Is this a problem that other people have? How do you avoid it?
- In Books & Authors |
- Tags: on, run, description, structure, sentence |
- |
- Report |
-
Share
RSS
Best Answer Decided by Votes
| November 02, 2009 11:33 AM |
It wasn't such a problem until one day I got the idea to learn the Blackfoot language. It's every interesting, because they don't have "words" per say... rather, they phonemes and morpheme, which by themselves don't express a pure concept, such that you have to string at least two of them together to get what we'd all a rod.
The closest example I can think of in English would be "ing". By itself "ing" doesn't mean anything. You have to say "running" for it to have meaning.
Well, they have a language where it's *all* pieces of phoneme, and they literally construct words on the fly from the phonemes, such that two different Blackfoot speakers can come up with two different words for the same concept... sort of like how in English Ox and Bull both mean a male cow, but in English those are both valid words.
In Blackfoot, they do to the phonemes of words like we can do to words in a sentence, where "She ran", and "Ran she did" mean the same thing even though the words are in different order... it's like to them, running and ingrun are both valid for the same concept.
Consequently, the really good Blackfoot speakers can string together phonemes like beads on a chain to have it where one word says what a whole sentence would in English... and I think that in German they sort of agglutinate phonemes that way, although I doubt to the same extent... but it's why native Blackfoot speakers used to have such a hugh regard for what they called their "Great Speakers". With Blackfoot, if they had a great speaker, they'd love to sit around the campfire and hear the speaker tell a story with a whole new freshly minted agglutinated phonetic set of words that nobody had ever heard said that way before.
I knew a guy... Dr. Don Frantz, who's goal was to make a Blackfoot-English Dictionary, and he nearly lost his mind. It ended up being a funny sort of lookup-grid to show combination's of phonemes that would make different words that would mean the same things, and even then there were old-time native speakers who were telling him he wasn't quite covering it all.
The point is... ever since I studied Blackfoot, it mangled my ordinary sense for where sentences should begin and end, and it turned me into a guy who would hyphenate twelve words into one supercalifragilisticexbialodocious word if the spell-check software would let him get away with it.
Which means, I have to remember a rule of thumb, and for English, the rule of thumb for when to drop a period is this: One sentence equals one complete thought.
Which means, technically speaking, if a paragraphs length sentence is expressing one single complete thought with all its nuances, then by the rules of grammar it's a valid sentance, which means, it boils down to a question of style.
For that, I use a second rule of thumb taught to me by the great Gudrend Hess, niece of the German writer Herman Hess.
She told me that in German, sentences could become very run-on, and that one had to choose to draw an arbitrary line, and that when she was writing for a north American audience, she would punctuate her sentences with periods when she though it would break it into pieces that would be a complete thought to a twelve year old.
I asked her why a twelve year old, and she said because that was the average level of literacy in America, and as a writer, she wanted to reach the maximum audience to within one standard deviation of the literacy level of the average.
So... according to my Linguistics prof Gudrend Hess... break your sentences into bite-size pieces where each one represents a complete thought comprehensible to a mentally sound graduate of the sixth grade.
Permalink | Report
Voted as best: unwirklich, chriswingate
Other Answers (10)
November 02, 2009 08:11 AM
Sometimes getting the long winded, run on sentence on paper is important. Particularly if you may lose the train of thought. When doing an initial cut of getting something on the paper I would not worry about the run on sentence. However, in order to improve and have your writing better understood, even by the editor, it is best to make your own first edit. To get rid of the run on sentence, read it in parts. Look at the overall sentence and determine how many individual pieces you have in the sentence. Are you combining multiple ideas into one? For each sentence determine if you can break it into more than one without making it choppy.
As you practice doing this in edit mode, you will become more in tune with how the sentences you end with are flowing and should be able to work that style into the original written text in the future.
Tags: editing, grammar, writing
Helpful Answer?
(3)
(0)
Helpful: doubleminaz, smartweb, krazykatie
Tip maggieray for this answerVoted as best: konsiders
November 02, 2009 11:28 AM
I tend to write in run-on sentences, too. I try to break them up after writing the piece, during the editing process. I think it's most important to get the ideas onto paper first, then re-read the piece and edit where necessary. Notice that wherever you stick an "and" in a sentence is usually a good place to try to break the long sentence into two or more shorter sentences, or even move one of the shorter sentences to another paragraph that fits the change in subject. I've only been publishing online for going on three years, and when I look back on some of my old stuff, I can see how I've improved. So hang in there, it's a learning process!
Tags: editing, writing
Helpful Answer?
(2)
(0)
Helpful: smartweb, krazykatie
Tip jillbeth for this answer
November 02, 2009 02:37 PM
Hey krazy! Good luck with your writing!! Maybe I can help you a little. Let's look at your opening sentence:
"Upon deciding recently to become a writer, I have been practicing my style, and it has come to my attention that one of my major flaws is that I use a lot of run-on sentences."
Now lets see if we can pare it down a bit.
"Soon after I decided to become a writer, I discovered a major flaw while practicing my style. I use a lot of run-on sentences."
Notice that I kept the last eight words of your sentence exactly as they are, only changed to a simple declarative statement. You correctly identified and placed that thought as the pivot to your next topic; "what will I do to improve"?
Write your first draft however you like, then edit. Try to limit yourself to one comma per sentence at the beginning, just as an exercise. It will become easier with practice. Try to identify the important thoughts, and separate them from those that could be eliminated or combined. Look for words you can do without, like "and", "that", and "which". You may try making a numbered list of your thoughts. Looking at them in that format may help you to prioritize them, group them or eliminate those that may duplicate or seem unnecessary.
I commend you for attempting to begin reaching one of the primary accomplishments of writing, "economy of expression". Edgar Allan Poe became so skilled that many of his short stories can almost be read as poems. Ezra Pound was another famous proponent. "The young Pound shared Edgar Allan Poe's conviction that any word unessential to a work should vacate the premises."
http://www.hanknuwer.com/ezra.html
See if this sentence and it's edit make sense to you:
"I am like you in that I like to write, and there is almost nothing I would like to do better, because it makes me feel good to get my thoughts on paper."
OR
"I, like you, am fond of writing. Nothing makes me feel better than capturing my thoughts on paper."
It is probably worth your time to brush up on different types of sentences, so that by varying them, you will be able to create the effect you are seeking. You will come to know why you are choosing a conpound-complex sentence and or why you are choosing a simple declarative statement.
You are not at the mercy of your sentences, you are their God. You can create them and annihilate them as you wish! Rule them wisely!
Disclaimer: I may be totally wrong.
http://www.youtube.com/watch?v=BgkzMKlXFdI&feature=fvw
Helpful Answer?
(8)
(0)
Helpful: albanian, bunnyphuphu, topaz5433, doubleminaz, smartweb, lisak52, lilyloretta, krazykatie
Tip keepontryin for this answerVoted as best: krazykatie
November 03, 2009 09:58 PM
Wow that was a great help, @keepontryin. I will definatly try those techniques as exercises while I continue improving my style! I tend to overlook some things as I'm not currently being guided by anyone/thing and am going it alone.
I really liked your version of my opening sentence better. :)
Report
I really liked your version of my opening sentence better. :)
November 02, 2009 02:44 PM
I found some guidelines which might help you avoid run-on sentence at authorsden.com. ---quote---
The easiest way to avoid run on sentences is to scan the sentences you have written when you do your proofreading. Look for subjects and verbs. Determine if you have written two sentences. If you have, be sure you have joined them in one of the following ways.
----end of quote--
Tips on avoiding run on sentences.
1. Join sentences with junction to coordinate them.
2. Use a semicolon to join sentences.
3. Use therefore, however, nevertheless, consequently, etc.
Source(s):
http://www.authorsden.com/visit/viewarticle.asp?id=19869
Permalink | Report
November 02, 2009 03:25 PM
Painful though it may be, I recommend sentence diagramming. A sentence is intended to express a single, complete thought, and diagramming will help you enforce that. Also, I don't recommend relying on software for grammar checking. My experience has been that MS Word, for example, simply does not like long sentences, even when they are grammatically correct and express a complete, albeit complex, thought.
Sentence length and complexity is often a matter of personal choice. Long-winded sentences and run-on sentences are not the same entity. I tend to favor long, unwieldy sentences, and I've noticed that some of my proofreaders prefer them shorter while others are perfectly fine with them as they stand. Sometimes it's worth breaking up longer sentences for clarity, but other times I prefer to keep them on the rationale that the thought they express is suffers from being divided.
Permalink | Report
November 02, 2009 05:49 PM
I do not think there is a specific formula. It would probably stunt your stream of conscience to be constantly thinking about things as you write. You need to concentrate on the story, get the ideas down and then worry about the details later.
So, like you suggested, wait until you are editing and re-reading what you write to worry about it. If something reads weird it probably is weird.
Of course you could always set up a macro that will mark repetitive use of joining words as a spelling error. :)
Permalink | Report
November 02, 2009 05:58 PM
These are all great answers!! I tend to have both run ons and sentence fragments when I first write things out, especially in a forum like MA where it is more like a conversation. For that, it is not so important to catch them, but since I also design websites, and do Mahalo pages, it IS important to be clear and catch these things.
What *I* do to catch them is read my work over before submitting... if it seems odd but I just don't see what the problem is, I read it out loud.
You would be surprised what you will find reading your work out loud. This is especially true if you've read and re-read your work many times, as I do on websites, or for research projects I've done.
Since I know what I am saying, I tend to fill in the correct info when reading it silently. But reading out loud makes me change all kinds of things. I choose better words, tenses, change punctuation, and catch any sentence fragments or run ons that would have been there.
I find that my finished work is much more polished than it otherwise would have been...
and a final tip... if it is something important... especially if you will not be able to edit it, (if time allows) walk away from it and come back at another time.
a fresh set of eyes catches things that otherwise might have been missed.
=)
Source(s):
personal experience and my 2 cents...
Tags: proofreading, grammar, runon, english
Helpful Answer?
(1)
(0)
Helpful: krazykatie
Tip smartweb for this answer
November 02, 2009 06:28 PM
Three things: First: See if anything after a conjunction (such as "and") can be formulated into a new sentence.
Second, a tip from my high school English teacher: When you write a rough draft for a piece wait 24 hours before you revise it. That allows you to clear your head a bit and come back to revise the contents.
Third: If you have a friend or family member who doesn't mind looking over the writing for you, by all means ask, even pay them a small commission when it sells.
Good luck with your writing adventures.
Permalink | Report
November 02, 2009 08:29 PM
The best way to avoid a run on sentence is to use the free tools available to you. 1. Microsoft provides a grammar checker on your computer that will highlight the errors which can be accessed by opening up Microsoft word and clicking on the button in the top right hand corner, there you will see a box in the lower right hand corner "word options", click on it and then click on proofing.
You will need to check the following boxes:
a. ignore words in uppercase
b. ignore words that contain numbers
c. ignore internet and file addresses
d. flag repeated words
e. check spelling as you type
f. use contextual spelling
g. mark grammar error as you type
h. check grammar with spelling
2. There is another spell checker right when you open microsoft work, located in the upper right hand corner " spelling and grammar checker"
3. Free grammar checkers on the web.
•Spellchecker.net
•Grammar Slammer
www.whitesmoke.com
Permalink | Report
November 04, 2009 12:37 AM
A sentence can become a run-on sentence just because you forget to put in a comma. For example: The current was swift and he could not swim to shore. (This sentence is a run on because there is not a comma in front of the short conjunction that joins the two sentences.)
2. It is possible you might accidentally use "only" a comma to join two sentences which creates a comma splice, and a run-on sentence. For example: The current was swift, he could not swim to shore.
(This sentence is a run on because you cannot join two complete sentences with just a comma.)
3. Sometimes you might join two complete sentences without any punctuation at all. For example:
The current was swift he could not swim to shore.
(This sentence is a run on because there is no punctuation or conjunction between the two complete sentences.
The easiest way to avoid run on sentences is to scan the sentences you have written when you do your proofreading. Look for subjects and verbs. Determine if you have written two sentences. If you have, be sure you have joined them in one of the following ways.
(1)You can join two sentences with a coordinating conjunction:
,and ,for
,but ,nor
,or ,yet
(Be absolutely sure you place a comma in front of these short conjunctions.) For example:
The current was swift, and he could not swim to shore.
(2) You can join two sentences with a semicolon (;)
(Be sure the sentences are fairly short and closely related.
The current was swift; he could not swim to shore.
(3)You can join two sentences with a longer conjunction such as therefore, moreover, nevertheless, consequently, etc. If you use a longer conjunction, you must place a semicolon in front of it and a comma after it.
For example: The current was swift; consequently, he could not swim to shore.
If you are careful to determine that you have written two sentences, and then join them together with the proper punctuation, the problem of using run-on sentences in your writing will disappear
Permalink | Report
Voted as best: krystyne20
November 06, 2009 07:16 PM
Unfortunately, this answer has been plagiarized from http://www.authorsden.com/categories/article_top.asp?catid=10&id=19869.
Please see Mahalo Answers Etiquette for guidelines on how to support your answers with sources.
Report
Please see Mahalo Answers Etiquette for guidelines on how to support your answers with sources.
Answer this Question
Related Questions
Ask a Question
Buy Mahalo Dollars with Credit Card or PayPal
Top Members
Most Popular Tags
Categories
- Anonymous
- Arts & Design
- Beauty & Style
- Books & Authors
- Business
- Cars & Transportation
- Consumer Electronics
- Coupons Deals
- Education
- Entertainment
- Environment
- Fitness
- Food & Drink
- From Email
- From Iphone
- From Twitter
- Health
- History
- Hobbies
- Home & Garden
- How Tos
- Humor
- Jobs
- Legal
- Local
- Love & Relationships
- Mahalo Answers Community
- Money
- Music
- News
- NSFW
- Parenting
- Pets
- Science & Mathematics
- Services
- Shopping
- Social Science
- Society & Culture
- Sports
- Technology & Internet
- Travel
- Video Games
Welcome New Members
- vvenice, November 28, 2009 08:12 PM
- peterkleid, November 28, 2009 08:06 PM
- conundrum_janet..., November 28, 2009 08:05 PM
- pitz, November 28, 2009 08:04 PM
- amyrose85, November 28, 2009 08:01 PM
Mahalo Dollars are the currency of Mahalo Answers.
Each Mahalo Dollar costs $1.
Once you earn more than 40 Mahalo Dollars, you can request to be paid via PayPal. Each Mahalo Dollar is currently worth $0.75 when paid out via PayPal. Learn More
while you are correct in one definition of "ox", it is also used to refer to "any" member of the bovine family... so if a bovine is referred to as an "ox", it could also be a "bull", even though it would seem to be opposite. "male cow" is not actually a definition, but since here in America people tend to call all bovines "cows" it would make sense in the example cited. (cows are actually female bovine that have given birth)
so... you are both right, in a sense.
English has got to be the most confusing language there is! XD
English is full of synonyms because of the multiple-roots of the language, so I generally expect for there to be about three synonyms for each common thing, such that in order to help keep track within the context of style I sort them out according to their linguistic origins, and to my ear ox would have been what the original Celtic inhabitants of the British isles would have called the things, cow is what the Anglo-Saxon invaders called it, and bull would have come in after the Norman invasion from people who spoke a romantic language.
English is basically a mish-mash of three language groups: Celtic, spoken by the original inhabitants, Germanic, spoken by the Anglo-Saxon invaders, and Romantic, spoken by the Norman invaders, plus you can throw in some Greek (usually those words with 'ph' for the 'F' sound) and what we call "English" was a pidgin-language spoken in the market-place until the 1600's.
Prior to that time, the peasants tended to speak Celtic (Gaelic being an example) at home, the middle class spoke Anglic (what we'd call middle-English now) at home, and the upper class of nobility spoke Normandish at home, but they needed to trade, and so pidgin-language was worked out in the marketplace, and when Henry-VIII split the Church of England from the Roman Church it was inevitable that they would need a non-Latin Bible, and after arguing a bit about which dialect to use, they settled on the pidgin version that everyone more-or-less knew from the marketplace... and that's when English as we know it became "formalized" with Samuel Johnson's first dictionary, and why it was at that time that Shakespeare made a mark for himself by taking a bunch of stories that had been told by many before but in different languages and hammered them out in the now-official-definition of "proper" English. He was the first English play-write (whom we know of) to realize that not only did market-language have lots of synonyms, but it also had a very plastic grammar, such that it could make for speech hard to understand, but it could also be used to word-craft in ways that one couldn't with just Gaelic or Germanic or Normandish.
Like any tool with lots of extra buttons and options and features, a lot more can be done with it than other tools (languages) in the hands of someone who takes the time to learn how to use it, but like complex tools, those extra options can sometimes backfire such that the appliance just sits there blinking 12:00, however, it's winning out by virtue of the same grammatical plasticity that creates issues with things like run-on sentences.
I hear that from ESL students all the time. They hate the spelling, and they hate the plethora of synonyms and the huge vocabulary ("why do you have separate words for rat and mouse... they both pests... why do you have separate words for bean and pea... they both food seeds in pod... why do you have he and she... they both person...", etc.) but once they get a grip on the written grammar, they will continue to *speak* their mother tongue among each other, but they will *write* in English to each other, and I've read some of their stuff, and you know what? Technically, their grammar is correct, but man-oh-man sometimes I have to read it three times to understand what they're saying.
I mean, the irony is, it started as just a trade language, and even 150 years after Samuel Johnson and Shakespeare many were still thinking about it that way.
When the new US Congress was thinking about what languages they would write their laws in, it wasn't for sure that it would be English, because the majority of immigrants at that time were speaking German, and some wanted to make it officially German in order to further delineate a line between England and the US, but they decided to stick with English because they figured that in the long run it would be better for *trade*, because even though they didn't want to be a British territory anymore, they still wanted to be able to trade with British colonies like the Caribbean.
But many non-mercenaries noticed that because of the vocabulary full of synonyms, and because of the plastic grammar, both derived from polyglot roots, it's also a powerful tool for word-smithing, but it takes some work to get a grip on because it's got LOTs! of options...
I've talked to many, many people with non-English mother tongues, and they all say the same thing: Writing in their languages is not such an issue, because it's like driving with an automatic, but with English you have to learn how to shift with a standard, still... they like it the way professional race car and long-haul semi drivers want to control the transmission.
And that's why the question today is about run-on sentences, and why you'll notice there hadn't been a simple answer!
It's a legitimate question, and it's something that's been an issue for *everyone*!
What gave you the idea to study Blackfoot anyway? What a great idea!
Well, where I was living at the time, it was the second most commonly spoken language after English, so it made sense to do so. They formed a significant percentage of the population... basically 25%, or one in four, was Blackfoot, and although most spoke English, there were still some old-timers deep on the reserve who could only speak Siksika, and there was too much isolation between the Europeans and the Natives, and it wasn't for lack of trying on the part of the natives.
Besides, I was going for an honors degree, and part of that meant learning at least one other language, so I shrugged, and made it one I could go out and actually try out on real speakers.
It was fun, because although whites were accustomed to natives coming into town, it was very rare for whites to visit the reserve, so I always got real good treatment when I went.
They had a shopping mall built right in the middle of the prairies that looked surreal, like a picture of a shopping mall had been cut out of a magazine and pasted onto fence-less grassland with a ribbon of a road threading up to in, without a parking lot, so people would just park on graveled grassland, but inside it was utterly modern, state-of-the art with fountains and specialty shops with the latest designs in jeans and sneakers...
One shop was the Itoyopi cafe, where you could order ala cart, but the daily special was a paper plate of flat-bread piled with as much smoked meat as it could hold... enough to feed three people as far I could tell, yet I saw guys sit down and finish the whole thing... for $2.00... all made with modern Hobart restaurant kitchen equipment.
Then there was the time I decided to take a spring break from school and go on a backpacking/camping trip, and decided to camp of the reserve because it wasn't fenced plus there were no road or farm-lights lights around (they let their livestock run around free-range and would just sort them out according to branding), and they noticed the smoke from the fire, so some band police came up and over the ridge in a Toyota 4x4 and I gut busted for camping on the reserve without a permit... so yes... I'm one of the few white guys who's spent time in an Indian jail (and yes, the other natives in there gave me the gears about it... "Soo... what does it feel like for the white man to be in the Indian jail... >snicker snicker heyuck heyuck<").
They were going to fine me $200, but when they heard I could speak some pidgin Siksika, they let me go if I just paid the $35 fee for a camping permit.
And lots of other stuff happened too. It was neat. My Siksika name is Apohkiaayo.
Moreover, your use of a 160-word sentence, in an answer to a question about how to avoid run-on sentences, further damaged your credibility.
"Prior to that time, the peasants tended to speak Celtic (Gaelic being an example) at home, the middle class spoke Anglic (what we'd call middle-English now) at home, and the upper class of nobility spoke Normandish at home, but they needed to trade, and so pidgin-language was worked out in the marketplace, and when Henry-VIII split the Church of England from the Roman Church it was inevitable that they would need a non-Latin Bible, and after arguing a bit about which dialect to use, they settled on the pidgin version that everyone more-or-less knew from the marketplace... and that's when English as we know it became "formalized" with Samuel Johnson's first dictionary, and why it was at that time that Shakespeare made a mark for himself by taking a bunch of stories that had been told by many before but in different languages and hammered them out in the now-official-definition of "proper" English."
I thought it was funny and made an illustrated point, but alas, there's no good way to illustrate one's affective attitude when writing on this thing, what with the dearth of emoticons.
Besides, the issue of run-on sentences is actually just a question of style, and has nothing to do with what really matters in order for something to be "proper" English, which is grammar.
In fact, sometimes run-on sentences are better - style wise - for making a piece of writing sound more like speech, and the only real problem with run-on sentences is that if the reader or listener has a limited short-term memory buffer, like if they were weaned on TV, then they can't remember what you were talking about by they time you reach the period.
If you read stuff by Homer or Thucydides, you'll see sentences that are much longer than 160 words, but those are pieces of litterateur from the days when it was considered normal for people to be able to listen to an hour-long speech and remember the whole thing verbatim.
If you read my original question, which was actually, if you would like to be technical, (and i'm assuming you do,) many questions, you will see where I wrote "Is this a problem other people have?" Which is the part of the question where amost of @omicron 's extra information proved quite helpful.