Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #14875
| From | Miles Bader <miles@gnu.org> |
|---|---|
| Newsgroups | comp.lang.c++ |
| Subject | Re: copy/pass a va_list to another thread |
| Date | 2012-03-11 10:49 +0900 |
| Message-ID | <877gyroqjn.fsf@catnip.gol.com> (permalink) |
| References | (3 earlier) <jjb5ih$aoc$1@dont-email.me> <878vj9sfdj.fsf@catnip.gol.com> <jje23c$uph$1@dont-email.me> <87k42tqr69.fsf@catnip.gol.com> <jjf7qv$2uh$1@dont-email.me> |
"Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> writes:
>>> But there are people using e.g. Thunderbird as newsreader, and as of
>>> 2012 Thunderbird treats a quoted printable paragraph as one long
>>> single line.
>>
>> Quoted-printable is a _transfer encoding_, and shouldn't affect the way
>> the article content is displayed by your newsreader.... and indeed,
>> looking at the article you're complaining about, the problem isn't with
>> quoted-printable at all, it's that the original article doesn't have
>> any newlines in its paragraphs.
>
> That is incorrect.
What is incorrect?
Let's look at what I said; I said three things:
(1) "Quoted-printable is a _transfer encoding_."
That's obviously true -- note the header where QP is enabled:
"Content-Transfer-Encoding: quoted-printable"
(2) "It shouldn't affect the way the article content is displayed by
your newsreader."
This is true, simply by the meaning of a "transfer encoding" -- an
encoding which is intended to avoid problems in transit, but which is
entirely undone before the mail/news-reader interprets the underlying
text. It is intended to make sure the underlying text is
transparently transferred.
(3) "... looking at the article you're complaining about, the problem
isn't with quoted-printable at all, it's that the original article
doesn't have any newlines in its paragraphs."
This is can be verified by examination. Here's a paragraph from the
QP-encoded form of the original article:
Maybe. I am hoping for some boost or C++ standard mechanism, which I haven'=
t heard of yet, that solves this problem that I presume many developers hav=
e run across, when dealing with a function that takes a variable argument l=
ist parameter.
Notice that there's a "=" at the end of each line? In the QP
encoding, that means "remove this newline", and is only used if the
_original_ text had a line which was "too long".
Thus in the sender's original text, that whole paragraph was one long
line. QP split that long line into short lines for transfer, and when
the receiver undoes the QP-encoding, the original long line is
restored -- but note that the problem is that the long line was there
in the first place, which is a problem that is orthogonal to the
transfer-encoding used.
After the QP-encoding is _removed_, the original paragraph should look
like this:
Maybe. I am hoping for some boost or C++ standard mechanism, which I haven't heard of yet, that solves this problem that I presume many developers have run across, when dealing with a function that takes a variable argument list parameter.
We'll see what my software does with this, but what you end up seeing
should have no connection with the transfer encoding, because the
latter is intended to be transparent.
>> should really be addressed at the fact that the sender's software
>> didn't wrap lines, not that it used quoted-printable to encode
>> those long lines.
>
> That is dumb.
Wait, that's your argument...?
A little more detail, perhaps?
>> Here: as a test, I'll try to make sure my newsreader uses
>> quoted-printable, and you can tell me if you have problems reading it
>> or not. My lines are properly wrapped.
>
> You are posting with text/plain, not quoted printable
Sorry, I tried to make my software use QP, but failed to do so (note
my followup to my previous message).
> and your paragraphs are not paragraphs but individual lines.
Yes, that's what I meant by "My lines are properly wrapped."
In other words, I made sure that my post was in a reasonably standard
form for news (shortish lines) _before_ it was sent; if QP had been
applied on top (I tried...), it wouldn't have made any difference.
-miles
--
Fast, small, soon; pick any 2.
Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
copy/pass a va_list to another thread Christopher <cpisz@austin.rr.com> - 2012-03-07 14:36 -0800
Re: copy/pass a va_list to another thread "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2012-03-08 02:04 +0100
Re: copy/pass a va_list to another thread Christopher <cpisz@austin.rr.com> - 2012-03-08 11:54 -0800
Re: copy/pass a va_list to another thread "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2012-03-08 21:41 +0100
Re: copy/pass a va_list to another thread Christopher <cpisz@austin.rr.com> - 2012-03-08 13:56 -0800
OT: Free Usenet Access red floyd <no.spam.here@its.invalid> - 2012-03-08 16:09 -0800
Re: OT: Free Usenet Access Christopher Pisz <someone@somewhere.net> - 2012-03-09 10:26 -0600
New Google Groups problems (was Re: copy/pass a va_list to another thread) Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-03-09 12:27 +0000
Re: copy/pass a va_list to another thread Robert Miles <milesrf@Usenet-News.net> - 2012-04-21 23:43 -0500
XSUsenet.COM @Jeff-Relf.Me - 2012-04-21 22:12 -0700
Re: copy/pass a va_list to another thread Miles Bader <miles@gnu.org> - 2012-03-10 05:12 +0900
Re: copy/pass a va_list to another thread "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2012-03-10 00:00 +0100
Re: copy/pass a va_list to another thread Miles Bader <miles@gnu.org> - 2012-03-10 08:40 +0900
Re: copy/pass a va_list to another thread Miles Bader <miles@gnu.org> - 2012-03-10 08:42 +0900
MIME (Re: copy/pass a va_list to another thread) Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-03-10 07:04 +0000
Re: MIME (Re: copy/pass a va_list to another thread) Miles Bader <miles@gnu.org> - 2012-03-10 16:56 +0900
Re: MIME (Re: copy/pass a va_list to another thread) Gareth Owen <gwowen@gmail.com> - 2012-03-11 07:37 +0000
Re: copy/pass a va_list to another thread "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2012-03-10 10:44 +0100
Re: copy/pass a va_list to another thread Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-03-10 14:43 +0000
Re: copy/pass a va_list to another thread "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2012-03-10 21:17 +0100
Re: copy/pass a va_list to another thread Miles Bader <miles@gnu.org> - 2012-03-11 10:49 +0900
Re: copy/pass a va_list to another thread Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-03-11 07:11 +0000
Re: copy/pass a va_list to another thread Miles Bader <miles@gnu.org> - 2012-03-11 19:03 +0900
Re: copy/pass a va_list to another thread Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-03-11 11:49 +0000
Re: copy/pass a va_list to another thread Miles Bader <miles@gnu.org> - 2012-03-11 23:01 +0900
Re: copy/pass a va_list to another thread "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2012-03-11 18:25 +0100
Re: copy/pass a va_list to another thread Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-03-11 23:53 +0000
Re: copy/pass a va_list to another thread Mike McCarty <mcmccarty@gmail.com> - 2012-03-10 05:47 -0800
Re: copy/pass a va_list to another thread Dombo <dombo@disposable.invalid> - 2012-03-10 19:51 +0100
Re: copy/pass a va_list to another thread "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2012-03-10 21:23 +0100
Re: copy/pass a va_list to another thread Dombo <dombo@disposable.invalid> - 2012-03-11 14:36 +0100
Re: copy/pass a va_list to another thread "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2012-03-11 18:33 +0100
Re: copy/pass a va_list to another thread Dombo <dombo@disposable.invalid> - 2012-03-11 20:41 +0100
Re: copy/pass a va_list to another thread "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2012-03-11 21:49 +0100
Re: copy/pass a va_list to another thread Rui Maciel <rui.maciel@gmail.com> - 2012-03-11 17:18 +0000
Re: copy/pass a va_list to another thread "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2012-03-11 18:39 +0100
Re: copy/pass a va_list to another thread Rui Maciel <rui.maciel@gmail.com> - 2012-03-11 18:54 +0000
Re: copy/pass a va_list to another thread Christian Gollwitzer <auriocus@gmx.de> - 2012-03-12 19:03 +0100
Re: copy/pass a va_list to another thread Rui Maciel <rui.maciel@gmail.com> - 2012-03-11 17:09 +0000
Re: copy/pass a va_list to another thread scott@slp53.sl.home (Scott Lurndal) - 2012-03-11 01:26 +0000
Re: copy/pass a va_list to another thread Miles Bader <miles@gnu.org> - 2012-03-11 11:18 +0900
Re: copy/pass a va_list to another thread scott@slp53.sl.home (Scott Lurndal) - 2012-03-11 16:41 +0000
Re: copy/pass a va_list to another thread scott@slp53.sl.home (Scott Lurndal) - 2012-03-08 23:07 +0000
Re: copy/pass a va_list to another thread Paavo Helde <myfirstname@osa.pri.ee> - 2012-03-08 23:17 -0600
Re: copy/pass a va_list to another thread Stuart Redmann <DerTopper@web.de> - 2012-03-10 05:10 -0800
Re: copy/pass a va_list to another thread 88888 Dihedral <dihedral88888@googlemail.com> - 2012-03-10 05:42 -0800
Re: copy/pass a va_list to another thread Robert Miles <milesrf@Usenet-News.net> - 2012-04-21 23:20 -0500
Re: copy/pass a va_list to another thread BGB <cr88192@hotmail.com> - 2012-03-08 09:25 -0700
csiph-web