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


Groups > comp.lang.postscript > #2988

Re: Welcome to comp.lang.postscript!

From helbig@asclothestro.multivax.de (Phillip Helbig (undress to reply))
Newsgroups comp.lang.postscript
Subject Re: Welcome to comp.lang.postscript!
Date 2017-01-15 09:33 +0000
Organization Multivax C&R
Message-ID <o5fflc$2nad$1@news.kjsl.com> (permalink)
References (3 earlier) <cf371664-fea1-4d6f-af6e-aa199b0471fb@googlegroups.com> <2hki1dlv8p6z.1tfer5wwlqzj5$.dlg@40tude.net> <d8c59957-5628-45c7-b940-9688b3409f81@googlegroups.com> <3tydwwczlmho$.gebt0v1hiea3$.dlg@40tude.net> <o5clmn$1ul3$1@news.kjsl.com>

Show all headers | View raw


In article <1j38rmr7gdah2$.955et0612hpp.dlg@40tude.net>, tlvp
<mPiOsUcB.EtLlLvEp@att.net> writes: 

> >> Ah, so it's 40tude (or the posting client) that does the wrapping?
> >> I'd always though it was the reading client that did one's line-wrapping.
> >> About time I mended my impressions, if that impression is mistaken :-) .
> > 
> > Reading clients can wrap as well.  A BIG PROBLEM in usenet is that
> > posting clients wrap, so that the poster thinks that he submits
> > something well formatted, which then consists of one really long line
> > per paragraph.  Depending on the posting client, the servers in between,
> > and the client, readers will see this as a really long line, a truncated
> > line, or a post which has been unnecessarily base-64 encoded.
> 
> Thanks for those clarifications. I guess the moral for luser droog is this:
> 
> a suitable newsclient (and Dialog is one such) can send out a post with
> code lines not auto-wrapped; but there's no assurance a given newsclient
> will display that post with those lines still not wrapped -- they may have
> gotten irremediably wrapped "in transit", or (even if not) the reader
> itself may auto-wrap them of its own accord (though Dialog can have that
> behavior toggled off or on with a Ctrl+W; for other newsclients, I dunno).

More or less, but it is better to send posts consisting of lines of less 
than 80 characters (which means unquoted lines less than 72 characters, 
allowing for four "> " quote symbols, which should be more than enough).
You don't know how wide the reader's screen is.  If you post really long 
lines, there is no other solution than to truncate them, or force the 
reader to scroll, or perhaps to wrap them (displaying something other 
than what you wrote).  My experience is that posts are almost never 
automatically base64-encoded if no line is longer than 80 characters 
(and there are no characters other than 7-bit ASCII).  So write posts 
like this one with lines of at most 80 characters and with no 8-bit 
characters and almost all readers will see what you write.  (I have an 
editor which autowraps when I type, but it does so properly---in the 
text itself and not just on the display.  So it doesn't matter if I hit 
RETURN at the end of a line or let it autowrap---the result is the 
same.)

Back to comp.lang.postscript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Welcome to comp.lang.postscript! luser droog <luser.droog@gmail.com> - 2016-07-07 23:22 -0700
  Re: Welcome to comp.lang.postscript! Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-08-04 17:05 -0700
  Re: Welcome to comp.lang.postscript! Martin Leese <please@see.Web.for.e-mail.INVALID> - 2016-08-04 23:12 -0600
  Re: Welcome to comp.lang.postscript! luser droog <luser.droog@gmail.com> - 2017-01-02 16:28 -0800
    Re: Welcome to comp.lang.postscript! Carlos <angus@quovadis.com.ar> - 2017-01-03 15:24 +0100
      Re: Welcome to comp.lang.postscript! Michael Unger <spam.to.unger@spamgourmet.com> - 2017-01-03 17:27 +0100
      Re: Welcome to comp.lang.postscript! luser droog <luser.droog@gmail.com> - 2017-01-03 09:46 -0800
        Re: Welcome to comp.lang.postscript! luser droog <luser.droog@gmail.com> - 2017-01-11 20:03 -0800
          Re: Welcome to comp.lang.postscript! luser droog <luser.droog@gmail.com> - 2017-01-11 20:09 -0800
        Re: Welcome to comp.lang.postscript! tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-12 03:35 -0500
          Re: Welcome to comp.lang.postscript! Ross Presser <rpresser@gmail.com> - 2017-01-12 20:02 -0800
            Re: Welcome to comp.lang.postscript! tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-13 23:22 -0500
              Re: Welcome to comp.lang.postscript! helbig@asclothestro.multivax.de (Phillip Helbig (undress to reply)) - 2017-01-14 07:58 +0000
                Re: Welcome to comp.lang.postscript! tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-14 23:09 -0500
                Re: Welcome to comp.lang.postscript! helbig@asclothestro.multivax.de (Phillip Helbig (undress to reply)) - 2017-01-15 09:33 +0000
                Re: Welcome to comp.lang.postscript! tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-16 00:38 -0500
                Re: Welcome to comp.lang.postscript! helbig@asclothestro.multivax.de (Phillip Helbig (undress to reply)) - 2017-01-16 22:04 +0000
                Re: Welcome to comp.lang.postscript! luser droog <luser.droog@gmail.com> - 2017-01-24 10:11 -0800
                Re: Welcome to comp.lang.postscript! luser droog <luser.droog@gmail.com> - 2017-01-26 09:58 -0800
                Re: Welcome to comp.lang.postscript! luser droog <luser.droog@gmail.com> - 2017-01-26 10:04 -0800
                Re: Welcome to comp.lang.postscript! ken <ken@spamcop.net> - 2017-01-27 08:08 +0000

csiph-web