error C2679: binary '<<' : no operator found which takes a right-hand operand of type 'std::string'

[James Kanze]

James Kanze wrote:

[...]

It certainly was.

If you don't know how to read (the FAQ), I can't help you.

You're responsible for the broken software you use. If GG can't do
.sigs right, then don't use them.

Except that the .sig was correct in the original of the post you
quoted. I've fixed that so that it (normally) works.

What does OE have to do with anything? I'm talking about your broken
.sig separator, not quoting.

The .sig separator shows up correct in the posting, at least in
Google groups. "-- \n". The space is there in what is
propagating via NNTP.

 

[Default User]

James Kanze wrote:
[...]

Your criticism of it wasn't.

It certainly was.

If you don't know how to read (the FAQ), I can't help you.

I did not admonish anyone for following the FAQ. Drop the strawman.

Except that the .sig was correct in the original of the post you
quoted.

No, it wasn't. It's coming out without the space. I realize you pasted
it in with one, but Google is breaking it.

I've fixed that so that it (normally) works.

No, it doesn't. Never. Every .sig you put out is missing the space in
"-- ".

The .sig separator shows up correct in the posting, at least in
Google groups. "-- \n". The space is there in what is
propagating via NNTP.

Hmmm. That's not what I'm seeing here. I also checked it via Google
Groups, and I don't see the space there either (based on clicking
Reply).

Anybody else getting a correct .sig separator?





Brian

 

[James Kanze]

No, it wasn't. It's coming out without the space. I realize you pasted
it in with one, but Google is breaking it.

No, it doesn't. Never. Every .sig you put out is missing the space in
"-- ".

Hmmm. That's not what I'm seeing here. I also checked it via Google
Groups, and I don't see the space there either (based on clicking
Reply).

Google's wierd. If I click on Reply, the sig is quoted, and the
trailing space is stripped of. If I copy/paste the message into
another editor, however, the final space is there. If I click
on options, and then "show original posting", it's not.

My tests were based on copy/pasting the message into another
editor. Still, I suspect that if I get it anywhere, it is
present on the network; I can't quite imagine Google adding it
in in some cases.

Anybody else getting a correct .sig separator?

I'm curious as well. But when you normally don't see it, what
tool are you using?

(I'm also curious as to why this sort of thing has suddenly
started causing problems. For many, many years, I used "|>" for
citing, and didn't have the space, and it never caused anyone
problems anywhere.)

 

[Default User]

Google's wierd. If I click on Reply, the sig is quoted, and the
trailing space is stripped of. If I copy/paste the message into
another editor, however, the final space is there. If I click
on options, and then "show original posting", it's not.

Hmmm, I did a cut and paste from Google's display, and I do see the
space that way.

My tests were based on copy/pasting the message into another
editor. Still, I suspect that if I get it anywhere, it is
present on the network; I can't quite imagine Google adding it
in in some cases.

I'm actually posting this from Google Groups. I'll add a manual .sig
and see how it looks to me with my regular newsreader.

I'm curious as well. But when you normally don't see it, what
tool are you using?

My normal setup is XanaNews, with signatures set to "strict". That
means that it requires the space. It handles most other .sigs here.
It's fairly easy to tell because I have the fonts set to display .sigs
in a different color.

 

[Default User]

Default User wrote:

I'm actually posting this from Google Groups. I'll add a manual .sig
and see how it looks to me with my regular newsreader.

I don't see this as a correct .sig either.




Brian

 

[BobR]

I don't see this as a correct .sig either.
Brian

Slaughtered here too.

I have checked my own OE generated sig. uploaded to my ISP, and back == OK.
So, it is another 'news' capable program, ISP, or Google doing it.
Really hard to check OE on a GNU/Linux. Does it work with 'Wine'?

<G>
Maybe *you* should use OE and AT&T!! [ got buck$? ]
( .... and 'hand quote' James' messages, like I do. ;-{ )
</G>

Maybe when converting '\n' they are stripping out trailing whitespace too.
This line has five spaces after the period.

 

[James Kanze]

Slaughtered here too.

I have checked my own OE generated sig. uploaded to my ISP, and back == OK.
So, it is another 'news' capable program, ISP, or Google doing it.
Really hard to check OE on a GNU/Linux. Does it work with 'Wine'?

<G>
Maybe *you* should use OE and AT&T!! [ got buck$? ]
( .... and 'hand quote' James' messages, like I do. ;-{ )
</G>

Maybe when converting '\n' they are stripping out trailing whitespace too.
This line has five spaces after the period.

Not when I copy/paste it from Google news into my editor. It
has no spaces, where as the sig separator has one trailing
space.

The space in the .sig is probably there, in the messages
circulating in NNTP, but there is definitely some funny stuff
going on.

 

[Marcus Kwok]

I have checked my own OE generated sig. uploaded to my ISP, and back == OK.
[sig quoted intentionally]

Hmm, your .sig delimiter is missing the space when I read it here. Many
other posts do not have this problem, so I don't think it's on my end.

The funny thing is that I *have* seen *some* of your posts with a
correct delimiter.

Maybe when converting '\n' they are stripping out trailing whitespace too.
This line has five spaces after the period.

Could be. When reading over here, there are no spaces after the period.

 

[Default User]

Slaughtered here too.

Hard to tell how widespread it is, as most GG users don't have .sigs.

<G>
Maybe you should use OE and AT&T!! [ got buck$? ]

Good grief, no.

( .... and 'hand quote' James' messages, like I do. ;-{ )

Well, I just have to trim the .sig manually, rather than have XanaNews
do it for me.

</G>

Maybe when converting '\n' they are stripping out trailing whitespace
too. This line has five spaces after the period.

I don't see that.

Yours is missing the space in the .sig separator as well.




Brian

 

[BobR]

Marcus Kwok wrote in message...
Followup: To you and James [ I see default users post, will load on this
post]

I checked my outgoing posts (before send), and OE(5) *IS* stripping, but it
depends on the post I am replying to. I tried changing the 'encoding', no
soap.

Very strange. I may be forced to find a 'bootleg' OE6, and hope it will work
with win98se (the last ms for me! Debian!).

[sig quoted intentionally]

Hmm, your .sig delimiter is missing the space when I read it here. Many
other posts do not have this problem, so I don't think it's on my end.

The funny thing is that I *have* seen *some* of your posts with a
correct delimiter.

Maybe when converting '\n' they are stripping out trailing whitespace too.
This line has five spaces after the period.

Could be. When reading over here, there are no spaces after the period.

Here either. (stripped before I sent it. ;-{ )

[sig quoted intentionally]

Yet, your sig is good here.

Did Gates do it to us again?
( ms: Send money, get upgrade. Buy 'vista' for a million bucks, or suffer a
horrible death! <G> ( Dictatorships and monopolys, BAH humbug!) )