Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #7931 > unrolled thread

Re: NEED HELP-process words in a text file

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: NEED HELP-process words in a text file Chris Rebert <clp2@rebertia.com> - 2011-06-18 16:30 -0700
    Re: NEED HELP-process words in a text file Cousin Stanley <cousinstanley@gmail.com> - 2011-06-24 19:17 +0000
      Re: NEED HELP-process words in a text file John Gordon <gordon@panix.com> - 2011-06-24 19:32 +0000
        Re: NEED HELP-process words in a text file Cousin Stanley <cousinstanley@gmail.com> - 2011-06-24 21:36 +0000
      Re: NEED HELP-process words in a text file Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2011-06-24 23:43 +0000
        Re: NEED HELP-process words in a text file Ethan Furman <ethan@stoneleaf.us> - 2011-06-24 19:50 -0700
        Re: NEED HELP-process words in a text file Cousin Stanley <cousinstanley@gmail.com> - 2011-06-26 16:09 +0000

#7931 — Re: NEED HELP-process words in a text file

On Sat, Jun 18, 2011 at 4:21 PM, Cathy James <nambo4jb@gmail.com> wrote:
> Subject: NEED HELP-process words in a text file
>
> Dear Python Experts,
>
> First, I'd like to convey my appreciation to you all for your support
> and contributions.  I am a Python newborn and need help with my
> function. I commented on my program as to what it should do, but
> nothing is printing. I know I am off, but not sure where. Please
> help:(

Netiquette comment: Please avoid SHOUTING and including unnecessary
entreaties in your subject lines in the future.

Cheers,
Chris

[toc] | [next] | [standalone]

#8396

Chris Rebert wrote:

> Netiquette comment: Please avoid SHOUTING 
> ....

  The brilliant beam of light that first thought  
  capitilized words amounted to shouting
  never programmed cobol, fortran, or pl/1
  in the 1960s or 1970s .... :-) 

  How or why this behavior was cultivated
  and continues to spread is mind boggling 
  to me .... :-)


-- 
Stanley C. Kitching
Human Being
Phoenix, Arizona

[toc] | [prev] | [next] | [standalone]

#8397

In <iu2ns9$kkq$1@dont-email.me> Cousin Stanley <cousinstanley@gmail.com> writes:


>   How or why this behavior was cultivated
>   and continues to spread is mind boggling 

The behavior of writing in all caps, or the behavior of equating such
writing with shouting?

-- 
John Gordon                   A is for Amy, who fell down the stairs
gordon@panix.com              B is for Basil, assaulted by bears
                                -- Edward Gorey, "The Gashlycrumb Tinies"

[toc] | [prev] | [next] | [standalone]

#8415

John Gordon wrote:

> In <iu2ns9$kkq$1@dont-email.me> Cousin Stanley <cousinstanley@gmail.com> writes:
>
>>   How or why this behavior was cultivated
>>   and continues to spread is mind boggling 
>
> The behavior of writing in all caps, 
> or the behavior of equating such writing with shouting ?

  The latter .... 

    equating writing in all caps with shouting ....

  "It wobbles the mind."
 

-- 
Stanley C. Kitching
Human Being
Phoenix, Arizona

[toc] | [prev] | [next] | [standalone]

#8419

On Fri, 24 Jun 2011 19:17:29 +0000, Cousin Stanley wrote:

> Chris Rebert wrote:
> 
>> Netiquette comment: Please avoid SHOUTING ....
> 
>   The brilliant beam of light that first thought capitilized words
>   amounted to shouting never programmed cobol, fortran, or pl/1 in the
>   1960s or 1970s .... :-)

That's probably because the use of capitalisation for emphasis pre-dates 
the invention of computers by centuries. It is hardly an accident that 
the technical term for uppercase is derived from the same root as 
"majestic" and "major".

The history of so-called "minuscule" and "majuscule" letters is complex, 
and it hasn't been a universal rule that Capital Letters have ALWAYS been 
read as emphatic, but it has been true for hundreds of years (at least 
for languages that have capital letters).

Not the ONLY form of emphasis, of course (underlining, bold face, italics 
and  l e t t e r - s p a c i n g  are only a few of the other 
alternatives available), but in a plain-text medium with little control 
over the display of font, the use of lower and UPPER case letters is one 
of the few alternatives available. (The use of *markup* seems to have 
been a late invention in English, although in other languages it has been 
used much longer.)

If ONE word in uppercase is read in a SLIGHTLY louder voice, then 
naturally it doesn't take much imagination TO READ EVEN QUITE SHORT 
PASSAGES OF UNINTERRUPTED UPPERCASE WORDS AS SHOUTING LOUDLY -- 
regardless of the poor design of programming languages in the 60s and 70s.


-- 
Steven

[toc] | [prev] | [next] | [standalone]

#8428

Steven D'Aprano wrote:
> On Fri, 24 Jun 2011 19:17:29 +0000, Cousin Stanley wrote:
> 
>> Chris Rebert wrote:
>>
>>> Netiquette comment: Please avoid SHOUTING ....
>>   The brilliant beam of light that first thought capitilized words
>>   amounted to shouting never programmed cobol, fortran, or pl/1 in the
>>   1960s or 1970s .... :-)
> 
> That's probably because the use of capitalisation for emphasis pre-dates 
> the invention of computers by centuries. It is hardly an accident that 
> the technical term for uppercase is derived from the same root as 
> "majestic" and "major".
> 
> The history of so-called "minuscule" and "majuscule" letters is complex, 
> and it hasn't been a universal rule that Capital Letters have ALWAYS been 
> read as emphatic, but it has been true for hundreds of years (at least 
> for languages that have capital letters).
> 
> Not the ONLY form of emphasis, of course (underlining, bold face, italics 
> and  l e t t e r - s p a c i n g  are only a few of the other 
> alternatives available), but in a plain-text medium with little control 
> over the display of font, the use of lower and UPPER case letters is one 
> of the few alternatives available. (The use of *markup* seems to have 
> been a late invention in English, although in other languages it has been 
> used much longer.)
> 
> If ONE word in uppercase is read in a SLIGHTLY louder voice, then 
> naturally it doesn't take much imagination TO READ EVEN QUITE SHORT 
> PASSAGES OF UNINTERRUPTED UPPERCASE WORDS AS SHOUTING LOUDLY -- 
> regardless of the poor design of programming languages in the 60s and 70s.

Well said.  :)

~Ethan~

[toc] | [prev] | [next] | [standalone]

#8469

Steven D'Aprano wrote:

> If ONE word in uppercase is read in a SLIGHTLY louder voice, 
> then naturally it doesn't take much imagination TO READ 
> EVEN QUITE SHORT PASSAGES OF UNINTERRUPTED UPPERCASE WORDS 
> AS SHOUTING LOUDLY -- 

  And it doesn't take much of a reality check
  through my own personal faculties to realize 
  that my newsreader is not currently piped
  into a text-to-speech process and is not
  emitting any sound .... :-)

  Even then, there most likely wouldn't be 
  any extra emphasis on words written 
  in all capital letters unless the tts process
  was specifically altered to do so .... 

> regardless of the poor design of programming languages 
> in the 60s and 70s.

  I don't think programming languages of that era
  were poorly designed and especially not just because
  they happened to be coded in text with all caps .... 


-- 
Stanley C. Kitching
Human Being
Phoenix, Arizona

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web