D
David H. Lipman
| And another "m" in remember, lol.
|
Yes mam !
|
Yes mam !
M
Magda
... Magda - 28.11.2005 16:52 :
...
... > On Sun, 27 Nov 2005 18:22:36 +0100, in alt.comp.anti-virus, Peter Seiler
... > <[email protected]> arranged some electrons, so they looked like this :
... >
... > ... David H. Lipman - 27.11.2005 16:18 :
... > ...
... > ... David, if possible please do a favour posting normally with max. 72
... > ... character per line. Thanks.
... >
... > Every time someone complains about the length of my lines, I increase it by ten
... > characters.
... >
...
... at least it's up to you.
...
... BTW: finally it's up to you also how to quote. Your quoting markers
... "..." instead of ">>" produce a total confusing and wrong repost as you
... can see above. Your meaning could be: "Every time someone complains
... about my quoting-markers "...", I increase it by ten". Ok, lets go on
... with the chaos in usenet behavior.
Which 17" monitor can't display more than 72 characters?? Please!
...
... > On Sun, 27 Nov 2005 18:22:36 +0100, in alt.comp.anti-virus, Peter Seiler
... > <[email protected]> arranged some electrons, so they looked like this :
... >
... > ... David H. Lipman - 27.11.2005 16:18 :
... > ...
... > ... David, if possible please do a favour posting normally with max. 72
... > ... character per line. Thanks.
... >
... > Every time someone complains about the length of my lines, I increase it by ten
... > characters.
... >
...
... at least it's up to you.
...
... BTW: finally it's up to you also how to quote. Your quoting markers
... "..." instead of ">>" produce a total confusing and wrong repost as you
... can see above. Your meaning could be: "Every time someone complains
... about my quoting-markers "...", I increase it by ten". Ok, lets go on
... with the chaos in usenet behavior.
Which 17" monitor can't display more than 72 characters?? Please!
B
Beauregard T. Shagnasty
No, it looks as if you arranged them, with your misconfigured settings.
That's not the point.
My message pane [1] is only about two-thirds of the width of the
newsreader window to begin with, and set to use a serif font of 14 point
so I can read it. Anything much longer than 72 (ok, 80 [2]) either
causes a horizontal scrollbar, or wraps the lines partway so I end up
with broken lines.
Common Usenet netiquette is "less than 80 characters" and using ">" for
quoting marks.
Notice how your three dots screws up quoting above.
Why are you being ornery?
[1] Standard config: groups in full-height left vertical pane, headers
in short upper right pane, current message in tall lower right pane.
[2] After multiple replies and quotes, even 80 chars fails to wrap
correctly.
That's not the point.
My message pane [1] is only about two-thirds of the width of the
newsreader window to begin with, and set to use a serif font of 14 point
so I can read it. Anything much longer than 72 (ok, 80 [2]) either
causes a horizontal scrollbar, or wraps the lines partway so I end up
with broken lines.
Common Usenet netiquette is "less than 80 characters" and using ">" for
quoting marks.
Notice how your three dots screws up quoting above.
Why are you being ornery?
[1] Standard config: groups in full-height left vertical pane, headers
in short upper right pane, current message in tall lower right pane.
[2] After multiple replies and quotes, even 80 chars fails to wrap
correctly.
P
Peter Seiler
David H. Lipman - 28.11.2005 19:28 :
;-)
;-)
P
Peter Seiler
Heather - 28.11.2005 19:45 :
are you a lesson-teacher? lol.
are you a lesson-teacher? lol.
M
Magda
... My message pane [1] is only about two-thirds of the width of the
... newsreader window to begin with, and set to use a serif font of 14 point
... so I can read it. Anything much longer than 72 (ok, 80 [2]) either
... causes a horizontal scrollbar, or wraps the lines partway so I end up
... with broken lines.
So, because *your* message pane is small, the rest of the world has to bend for *your*
needs. *My* message pane is as large as my screen itself. Tahoma 12 is good enoug for me.
... Common Usenet netiquette is "less than 80 characters" and using ">" for
... quoting marks.
Matter of choice & taste. Why do we have to follow the Internet "rules" from 20 years ago?
.... Notice how your three dots screws up quoting above.
I don't see any screwing up.
... Why are you being ornery?
...
... [1] Standard config: groups in full-height left vertical pane, headers
... in short upper right pane, current message in tall lower right pane.
... [2] After multiple replies and quotes, even 80 chars fails to wrap
... correctly.
... newsreader window to begin with, and set to use a serif font of 14 point
... so I can read it. Anything much longer than 72 (ok, 80 [2]) either
... causes a horizontal scrollbar, or wraps the lines partway so I end up
... with broken lines.
So, because *your* message pane is small, the rest of the world has to bend for *your*
needs. *My* message pane is as large as my screen itself. Tahoma 12 is good enoug for me.
... Common Usenet netiquette is "less than 80 characters" and using ">" for
... quoting marks.
Matter of choice & taste. Why do we have to follow the Internet "rules" from 20 years ago?
.... Notice how your three dots screws up quoting above.
I don't see any screwing up.
... Why are you being ornery?
...
... [1] Standard config: groups in full-height left vertical pane, headers
... in short upper right pane, current message in tall lower right pane.
... [2] After multiple replies and quotes, even 80 chars fails to wrap
... correctly.
P
Peter Seiler
Magda - 28.11.2005 21:10 :
1. you give no statement to my last paragraph concerning quoting markers.
2. length of lines:
ther are people with 15" monitor. But that's not the main point! Many
browser and mailclients have another/additional pane on the left (or
sometimes right) side of the message pane! And with usual seized
fonts/typo the terrible result especially within longer threads is as
described.
See what Beauregard wrote today.
How learnable you are and flexible in changing your behavior if you have
been wrong? But stay a little bit egoistic/asocial to the
recipients/readers and do what you want further.
1. you give no statement to my last paragraph concerning quoting markers.
2. length of lines:
ther are people with 15" monitor. But that's not the main point! Many
browser and mailclients have another/additional pane on the left (or
sometimes right) side of the message pane! And with usual seized
fonts/typo the terrible result especially within longer threads is as
described.
See what Beauregard wrote today.
How learnable you are and flexible in changing your behavior if you have
been wrong? But stay a little bit egoistic/asocial to the
recipients/readers and do what you want further.
S
Shane
David H. Lipman said:| And another "m" in remember, lol.
|
Yes mam !
Don't you mean 'Ma'?
Shane
H
Heather
Nah....just an English-freak and I love to tease him. David rarely makesPeter Seiler said:
spelling or grammar errors, so I just HAD to catch him out on this one. I
make allowances for those (like yourself) whose first language is not
English though. It is not an easy language to learn the crazy "rules" of
spelling, to be honest.
Only in the US do they drop the British/Canadian spellings such as "colour,
behaviour, rumour, etc". But we will get them whipped into shape one day,
lol.
Cheers.....Heather
D
David H. Lipman
From: "Heather" <[email protected]>
| Nah....just an English-freak and I love to tease him. David rarely makes
| spelling or grammar errors, so I just HAD to catch him out on this one. I
| make allowances for those (like yourself) whose first language is not
| English though. It is not an easy language to learn the crazy "rules" of
| spelling, to be honest.
|
| Only in the US do they drop the British/Canadian spellings such as "colour,
| behaviour, rumour, etc". But we will get them whipped into shape one day,
| lol.
|
| Cheers.....Heather
|
Rarely ?
Sh!t -- I embarrass myself by the sheer number of grammatical and spelling errors I and
others find in my posts.
Luckily, News Groups are considered "conversational" expressions and are therefore don't
have the spelling and grammatical constraints of formal documents and publications.
I accept 'Laines's Mom's corrections.
{ Hopefully with grace and dignity }
| Nah....just an English-freak and I love to tease him. David rarely makes
| spelling or grammar errors, so I just HAD to catch him out on this one. I
| make allowances for those (like yourself) whose first language is not
| English though. It is not an easy language to learn the crazy "rules" of
| spelling, to be honest.
|
| Only in the US do they drop the British/Canadian spellings such as "colour,
| behaviour, rumour, etc". But we will get them whipped into shape one day,
| lol.
|
| Cheers.....Heather
|
Rarely ?
Sh!t -- I embarrass myself by the sheer number of grammatical and spelling errors I and
others find in my posts.
Luckily, News Groups are considered "conversational" expressions and are therefore don't
have the spelling and grammatical constraints of formal documents and publications.
I accept 'Laines's Mom's corrections.
{ Hopefully with grace and dignity
}
B
Beauregard T. Shagnasty
Magda said:
See how your longer line appears when I reply? It reads the same way
when I opened your post.
As Peter said, you are obviously egotistical and asocial.
Bye.
M
me
Hi,
From RFC1855 Netiquette
Guidelines for Network Etiquette
[ quot ]
Limit line length to fewer than 65 characters and end a line
with a carriage return.
[ /quot ]
J
M
Magda
... ...
... > -snip-
... > So, because *your* message pane is small, the rest of the
... > world has to bend for *your* needs. *My* message pane is as
... > large as my screen itself. Tahoma 12 is good enoug for me.
... >
... > ... Common Usenet netiquette is "less than 80 characters"
... > and using ">" for ... quoting marks.
... >
... > Matter of choice & taste. Why do we have to follow the
... > Internet "rules" from 20 years ago?
... >
... > ... Notice how your three dots screws up quoting above.
... >
... > I don't see any screwing up.
... > -snip-
... >
...
... Hi,
...
... From RFC1855 Netiquette
... Guidelines for Network Etiquette
... [ quot ]
... Limit line length to fewer than 65 characters and end a line
... with a carriage return.
... [ /quot ]
So, all the "72" apologists are wrong too. LOL
... > -snip-
... > So, because *your* message pane is small, the rest of the
... > world has to bend for *your* needs. *My* message pane is as
... > large as my screen itself. Tahoma 12 is good enoug for me.
... >
... > ... Common Usenet netiquette is "less than 80 characters"
... > and using ">" for ... quoting marks.
... >
... > Matter of choice & taste. Why do we have to follow the
... > Internet "rules" from 20 years ago?
... >
... > ... Notice how your three dots screws up quoting above.
... >
... > I don't see any screwing up.
... > -snip-
... >
...
... Hi,
...
... From RFC1855 Netiquette
... Guidelines for Network Etiquette
... [ quot ]
... Limit line length to fewer than 65 characters and end a line
... with a carriage return.
... [ /quot ]
So, all the "72" apologists are wrong too. LOL