error C2679: binary '<<' : no operator found which takes a right-hand operand of type 'std::string' (or there is no acceptable conversion)

#1 June 17th, 2007, 10:55 AM

Hi,
I have written this code, and at the end, I am trying to write a
vector of strings into a text file. However, my program is nor
compiling, and it gives me the following error when I try to write to
the file:

error C2679: binary '<<' : no operator found which takes a right-hand
operand of type 'std::string' (or there is no acceptable conversion)

I don't know what I am doing wrong. I have posted my entire program
here.
Thank you

#include <iostream>
#include <fstream>
#include <iterator>
#include <algorithm>
#include <vector>
#include <math.h>
#include "string.h"

using namespace std;

char n_str[2000];
char a_str[2000];

char n_char[2000];
char a_char[2000];
string achar, nchar;

int main(int argc, char* argv[])
{
vector<stringn_word_list;
vector<stringa_word_list;

ifstream in_a("10_a.txt");
if (!in_a)
{
cout << "Error opening abnormal file" << endl;
}
while (!in_a.eof())
{
in_a.getline(a_str,2000);
a_word_list.push_back(a_str);
}
cout << a_word_list.size()<< endl;

ifstream in_n("10_n.txt");
if (!in_n)
{
cout << "Error opening normal file" << endl;
}
while (!in_n.eof())
{
in_n.getline(a_str,2000);
n_word_list.push_back(a_str);
}
cout << n_word_list.size()<< endl;

for (unsigned int i=0; i<a_word_list.size(); i++)
{
for (unsigned int j=0; j<n_word_list.size();j++)
{
if (a_word_list[i].compare( n_word_list[j]))
{
a_word_list.assign(1,"aa");

n_word_list.assign(1,"aa");

}
}
}

ofstream out_a("10_a_new.txt");
if (!out_a)
{
cout << "Error opening new abnormal file" << endl;
}
for (unsigned int i=0; i<a_word_list.size(); i++)
{
achar = a_word_list.at(i);
out_a << achar << endl; //ERROR
}

ofstream out_n("10_n_new.txt");
if (!out_n)
{
cout << "Error opening new normal file" << endl;
}
for (unsigned int i=0; i<n_word_list.size(); i++)
{
out_n << n_word_list.at(i) << endl; //ERROR
}
return 0;
}

#2 June 17th, 2007, 11:05 AM

On 17 juin, 11:52, aarth...@gmail.com wrote:

Quote:

Hi,
I have written this code, and at the end, I am trying to write a
vector of strings into a text file. However, my program is nor
compiling, and it gives me the following error when I try to write to
the file:
>
error C2679: binary '<<' : no operator found which takes a right-hand
operand of type 'std::string' (or there is no acceptable conversion)
>
I don't know what I am doing wrong. I have posted my entire program
here.
Thank you
>
#include <iostream>
#include <fstream>
#include <iterator>
#include <algorithm>
#include <vector>
#include <math.h>
#include "string.h"
>
using namespace std;
>
char n_str[2000];
char a_str[2000];
>
char n_char[2000];
char a_char[2000];
string achar, nchar;
>
int main(int argc, char* argv[])
{
vector<stringn_word_list;
vector<stringa_word_list;
>
ifstream in_a("10_a.txt");
if (!in_a)
{
cout << "Error opening abnormal file" << endl;
}
while (!in_a.eof())
{
in_a.getline(a_str,2000);
a_word_list.push_back(a_str);
}
cout << a_word_list.size()<< endl;
>
ifstream in_n("10_n.txt");
if (!in_n)
{
cout << "Error opening normal file" << endl;
}
while (!in_n.eof())
{
in_n.getline(a_str,2000);
n_word_list.push_back(a_str);
}
cout << n_word_list.size()<< endl;
>
for (unsigned int i=0; i<a_word_list.size(); i++)
{
for (unsigned int j=0; j<n_word_list.size();j++)
{
if (a_word_list[i].compare( n_word_list[j]))
{
a_word_list.assign(1,"aa");
>
n_word_list.assign(1,"aa");
>
}
}
}
>
ofstream out_a("10_a_new.txt");
if (!out_a)
{
cout << "Error opening new abnormal file" << endl;
}
for (unsigned int i=0; i<a_word_list.size(); i++)
{
achar = a_word_list.at(i);
out_a << achar << endl; //ERROR
}
>
ofstream out_n("10_n_new.txt");
if (!out_n)
{
cout << "Error opening new normal file" << endl;
}
for (unsigned int i=0; i<n_word_list.size(); i++)
{
out_n << n_word_list.at(i) << endl; //ERROR
}
return 0;
>
}

Can you give your compiler version and the line of the error, please ?

#3 June 17th, 2007, 11:05 AM

aarthi28@gmail.com wrote:

Quote:

Hi,
I have written this code, and at the end, I am trying to write a
vector of strings into a text file. However, my program is nor
compiling, and it gives me the following error when I try to write to
the file:
>
error C2679: binary '<<' : no operator found which takes a right-hand
operand of type 'std::string' (or there is no acceptable conversion)
>
I don't know what I am doing wrong.

It doesn't look like you are doing anything wrong, the code in question
looks fine to me.

--
Ian Collins.

#4 June 17th, 2007, 11:05 AM

Baltimore wrote:

Quote:

On 17 juin, 11:52, aarth...@gmail.com wrote:

Quote:

> for (unsigned int i=0; i<n_word_list.size(); i++)
> {
> out_n << n_word_list.at(i) << endl; //ERROR
> }
> return 0;
>>
>}

>
Can you give your compiler version and the line of the error, please ?
>

Did you have to quote the entire post to ask that?

--
Ian Collins.

#5 June 17th, 2007, 11:15 AM

I am using Visual Studio 2005, and I marked the two lines that are
giving me errors in my original post. I am re-posting the error
portion here.
Thank you

..
..
..
..
for (unsigned int i=0; i<a_word_list.size(); i++)
{
achar = a_word_list.at(i);
out_a << achar << endl; //ERROR
}

..
..
..

for (unsigned int i=0; i<n_word_list.size(); i++)
{
out_n << n_word_list.at(i) << endl; //ERROR
}
return 0;
..
..
..

#6 June 17th, 2007, 11:15 AM

Is there something else I can do to make this run? I don't know why I
am getting an error

#7 June 17th, 2007, 11:15 AM

On Sun, 17 Jun 2007 09:52:06 -0000, aarthi28@gmail.com wrote:

Quote:

>I have written this code, and at the end, I am trying to write a
>vector of strings into a text file. However, my program is nor
>compiling, and it gives me the following error when I try to write to
>the file:
>
>error C2679: binary '<<' : no operator found which takes a right-hand
>operand of type 'std::string' (or there is no acceptable conversion)
>
>I don't know what I am doing wrong. I have posted my entire program
>here.
>Thank you
>
>#include <iostream>
>#include <fstream>
>#include <iterator>
>#include <algorithm>
>#include <vector>
>#include <math.h>
>#include "string.h"

#include <string>

--
Roland Pibinger
"The best software is simple, elegant, and full of drama" - Grady Booch

#8 June 17th, 2007, 11:35 AM

aarthi28@gmail.com wrote:
:: Hi,
:: I have written this code, and at the end, I am trying to write a
:: vector of strings into a text file. However, my program is nor
:: compiling, and it gives me the following error when I try to write
:: to the file:
::
:: error C2679: binary '<<' : no operator found which takes a
:: right-hand operand of type 'std::string' (or there is no
:: acceptable conversion)
::
:: I don't know what I am doing wrong. I have posted my entire program
:: here.
:: Thank you
::
:: #include <iostream>
:: #include <fstream>
:: #include <iterator>
:: #include <algorithm>
:: #include <vector>
:: #include <math.h>
:: #include "string.h"
::
:: using namespace std;
::

The operators for std::string are found in the <stringheader.

Bo Persson

#9 June 17th, 2007, 11:45 AM

On 2007-06-17 11:52, aarthi28@gmail.com wrote:

Quote:

Hi,
I have written this code, and at the end, I am trying to write a
vector of strings into a text file. However, my program is nor
compiling, and it gives me the following error when I try to write to
the file:
>
error C2679: binary '<<' : no operator found which takes a right-hand
operand of type 'std::string' (or there is no acceptable conversion)
>
I don't know what I am doing wrong. I have posted my entire program
here.
Thank you
>
#include <iostream>
#include <fstream>
#include <iterator>
#include <algorithm>
#include <vector>
#include <math.h>
#include "string.h"

That does not look right to me. What does "string.h" contain? If you
wanted to use the C string header you should have used <string.hor
<cstring>. However I suspect that you wanted to use C++ strings, in
which case you should use <string(notice that none of the standard C++
headers have a .h when including). If you use <stringinstead of
"string.h" your code will compiler just fine.

--
Erik Wikström

#10 June 17th, 2007, 12:45 PM

aarthi28@gmail.com wrote:

Quote:

Hi,
I have written this code, and at the end, I am trying to write a
vector of strings into a text file. However, my program is nor
compiling, and it gives me the following error when I try to write to
the file:
>
error C2679: binary '<<' : no operator found which takes a right-hand
operand of type 'std::string' (or there is no acceptable conversion)
>
I don't know what I am doing wrong. I have posted my entire program
here.
Thank you

You are forgetting

#include <string>

No .h and <not ""

john

#11 June 17th, 2007, 03:15 PM

On Jun 17, 11:52 am, aarth...@gmail.com wrote:

Quote:

I have written this code, and at the end, I am trying to write
a vector of strings into a text file. However, my program is
nor compiling, and it gives me the following error when I try
to write to the file:

Quote:

error C2679: binary '<<' : no operator found which takes a right-hand
operand of type 'std::string' (or there is no acceptable conversion)

Quote:

I don't know what I am doing wrong. I have posted my entire
program here.

It really would have been better if you'd have created a minimum
example.

Quote:

#include <iostream>
#include <fstream>
#include <iterator>
#include <algorithm>
#include <vector>
#include <math.h>
#include "string.h"

As others have said, you haven't included <string>. So there's
no guarantee that you have all of the operations that are
normally provided for std::string.

Quote:

using namespace std;

Quote:

char n_str[2000];
char a_str[2000];

Quote:

char n_char[2000];
char a_char[2000];
string achar, nchar;

Quote:

int main(int argc, char* argv[])
{
vector<stringn_word_list;
vector<stringa_word_list;

Quote:

ifstream in_a("10_a.txt");
if (!in_a)
{
cout << "Error opening abnormal file" << endl;
}
while (!in_a.eof())

This line is wrong. What you want is actually:

std::string a_str ; // No point in reading into a C style
// array...
while ( std::getline( in_a, a_str ) ) {
a_word_list.push_back( a_str ) ;
}

[...]

Quote:

while (!in_n.eof())

Same comment as above.

Quote:

cout << n_word_list.size()<< endl;

And of course, this whole loop can be written as:

std::copy( a_word_list.begin(), a_word_list.end(),
std::ostream_iterator< std::string >( out_a,
"\n" ) ) ;
out_a.close() ; // Since you're not using it any more...
if ( ! out_a ) {
std::cerr << "Write error in out_a" << std::endl ;
}

As above.

Quote:

for (unsigned int i=0; i<n_word_list.size(); i++)
{
out_n << n_word_list.at(i) << endl; //ERROR
}

Since (rather exceptionally for a beginner) you are doing
correct error checking, don't forget to check that your writes
actually worked.

--
James Kanze (Gabi Software) email: james.kanze@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, +33 (0)1 30 23 00 34

#12 June 17th, 2007, 07:05 PM

aarthi28@gmail.com wrote:

Quote:

Is there something else I can do to make this run? I don't know why I
am getting an error

Please include sufficient quotes from the previous message to provide
context for your message. Google Groups does this automatically now, so
you have no excuse.

Brian

#13 June 17th, 2007, 07:15 PM

Baltimore wrote:

Quote:

On 17 juin, 11:52, aarth...@gmail.com wrote:

Quote:

Hi,
I have written this code, and at the end, I am trying to write a
vector of strings into a text file. However, my program is nor
compiling, and it gives me the following error when I try to write
to the file:

error C2679: binary '<<' : no operator found which takes a
right-hand operand of type 'std::string' (or there is no acceptable
conversion)

Quote:

out_a << achar << endl; //ERROR
out_n << n_word_list.at(i) << endl; //ERROR

Quote:

>
Can you give your compiler version and the line of the error, please ?

If the first matters, then it's probably off-topic. For the second, he
flagged the lines with comments. You'd probably have noticed had you
gone through the post and trimmed down the quotes.

Brian

#14 June 17th, 2007, 09:05 PM

On Jun 17, 8:05 pm, "Default User" <defaultuse...@yahoo.comwrote:

Quote:

Baltimore wrote:

Quote:

On 17 juin, 11:52, aarth...@gmail.com wrote:

Quote:

I have written this code, and at the end, I am trying to write a
vector of strings into a text file. However, my program is nor
compiling, and it gives me the following error when I try to write
to the file:

Quote:

error C2679: binary '<<' : no operator found which takes a
right-hand operand of type 'std::string' (or there is no acceptable
conversion)
out_a << achar << endl; //ERROR
out_n << n_word_list.at(i) << endl; //ERROR

Quote:

Can you give your compiler version and the line of the error, please ?

Quote:

If the first matters, then it's probably off-topic.

Since when? Questions concerning the conformance of a compiler
are on topic. More importantly, the poster doesn't know the
answer to his problem; indicating the compiler version may allow
someone to say that it is just a compiler bug, and that his code
is correct, and save a lot of other people a lot of work trying
to figure out why the code doesn't work. In general, when
asking about a specific error message, indicating the compiler
and its version (and possibly the OS it's running on, in the
case of g++) is just considered correct posting etiquette.

--
James Kanze (Gabi Software) email: james.kanze@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, +33 (0)1 30 23 00 34

#15 June 18th, 2007, 12:05 AM

James Kanze wrote:

Quote:

On Jun 17, 8:05 pm, "Default User" <defaultuse...@yahoo.comwrote:

Quote:

Baltimore wrote:

Quote:

On 17 juin, 11:52, aarth...@gmail.com wrote:

>

Quote:

I have written this code, and at the end, I am trying to write a
vector of strings into a text file. However, my program is nor
compiling, and it gives me the following error when I try to
write to the file:

>

Quote:

error C2679: binary '<<' : no operator found which takes a
right-hand operand of type 'std::string' (or there is no
acceptable conversion)
out_a << achar << endl; //ERROR
out_n << n_word_list.at(i) << endl; //ERROR

>

Quote:

Can you give your compiler version and the line of the error,
please ?

>

Quote:

If the first matters, then it's probably off-topic.

>
Since when? Questions concerning the conformance of a compiler
are on topic.

They CAN be, but seldom are, which is why I said "probably".

It's not usually the first question that needs to be asked.

Brian

#16 June 18th, 2007, 08:45 AM

On Jun 18, 1:01 am, "Default User" <defaultuse...@yahoo.comwrote:

Quote:

James Kanze wrote:

Quote:

On Jun 17, 8:05 pm, "Default User" <defaultuse...@yahoo.comwrote:

Quote:

Baltimore wrote:
On 17 juin, 11:52, aarth...@gmail.com wrote:

Quote:

I have written this code, and at the end, I am trying to write a
vector of strings into a text file. However, my program is nor
compiling, and it gives me the following error when I try to
write to the file:

Quote:

error C2679: binary '<<' : no operator found which takes a
right-hand operand of type 'std::string' (or there is no
acceptable conversion)
out_a << achar << endl; //ERROR
out_n << n_word_list.at(i) << endl; //ERROR

Quote:

Can you give your compiler version and the line of the error,
please ?

Quote:

If the first matters, then it's probably off-topic.

Quote:

Since when? Questions concerning the conformance of a compiler
are on topic.

Quote:

They CAN be, but seldom are, which is why I said "probably".

I'm sorry, but questions along the lines of: "The following code
doesn't compile. Is this a problem with my compiler, or is the
code actually illegal?" are perfectly on topic. Always.

Quote:

It's not usually the first question that needs to be asked.

Yes and no. It's standard etiquette in this group to indicate
the compiler and the version when there is a problem, because it
can make answering the question easier. From the FAQ, question
5.7:

How do I post a question about code that doesn't work
correctly?

[...]

5. Post the tools you used: compiler name, version
number, operating system, etc

6. Post the tool options you used: libraries, exact
compiler and linker options, etc

7. Post the exact messages you received; differentiate
between compiler, linker, and runtime messages

It's bad enough when we have people complaining about things
that are marginal (when in doubt, allow it), but to complain
about following the guidelines in the FAQ...

--
James Kanze (GABI Software, from CAI) email:james.kanze@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, +33 (0)1 30 23 00 34

#17 June 18th, 2007, 12:35 PM

On Jun 17, 12:10 pm, aarth...@gmail.com wrote:

Quote:

Is there something else I can do to make this run? I don't know why I
am getting an error

Maybe, you define a 'string' type in the "string.h" header.
So the 'achar' and 'nchar' variables could be of your own string type.
Write std::string for this variables and include <stringto use the
string library of C++.

#18 June 18th, 2007, 07:25 PM

James Kanze wrote:

Quote:

On Jun 18, 1:01 am, "Default User" <defaultuse...@yahoo.comwrote:

Quote:

James Kanze wrote:

Quote:

Since when? Questions concerning the conformance of a compiler
are on topic.

>

Quote:

They CAN be, but seldom are, which is why I said "probably".

>
I'm sorry, but questions along the lines of: "The following code
doesn't compile. Is this a problem with my compiler, or is the
code actually illegal?" are perfectly on topic. Always.

That wasn't the question, was it?

Quote:

It's not usually the first question that needs to be asked.

>
Yes and no. It's standard etiquette in this group to indicate
the compiler and the version when there is a problem, because it
can make answering the question easier.

That's fine, and had the OP done so that would be reasonable. However,
it's pointless for a respondent to make that his only contribution to
ask. Especially when he full-quoted and was unable to read the original
post for context.

Quote:

It's bad enough when we have people complaining about things
that are marginal (when in doubt, allow it), but to complain
about following the guidelines in the FAQ...

This is incorrect, as I didn't do that. You've made a strawman and
knocked it down. Congrats for going with the classics.

Quote:

--
James Kanze (GABI Software, from CAI) email:james.kanze@gmail.com
Conseils en informatique orientie objet/
Beratung in objektorientierter Datenverarbeitung
9 place Simard, 78210 St.-Cyr-l'Icole, France, +33 (0)1 30 23 00 34

BTW, if you can't get Google to post this correctly, consider dropping
it. I understand that some people have no choice but to use their
inadequate system, but it's incumbent upon you to work with the
problems.

Brian

#19 June 18th, 2007, 09:05 PM

On Jun 18, 8:18 pm, "Default User" <defaultuse...@yahoo.comwrote:

Quote:

James Kanze wrote:

[...]

Quote:

That's fine, and had the OP done so that would be reasonable.
However, it's pointless for a respondent to make that his only
contribution to ask. Especially when he full-quoted and was
unable to read the original post for context.

Just as pointless as for you to criticize the respondent for
doing so. His comment was technically correct. Your criticism
of it wasn't.

Quote:

It's bad enough when we have people complaining about things
that are marginal (when in doubt, allow it), but to complain
about following the guidelines in the FAQ...

Quote:

This is incorrect, as I didn't do that. You've made a strawman and
knocked it down. Congrats for going with the classics.

Quote:

--
James Kanze (GABI Software, from CAI) email:james.ka...@gmail.com
Conseils en informatique orientie objet/
Beratung in objektorientierter Datenverarbeitung
9 place Simard, 78210 St.-Cyr-l'Icole, France, +33 (0)1 30 23 00 34

Quote:

BTW, if you can't get Google to post this correctly, consider dropping
it. I understand that some people have no choice but to use their
inadequate system, but it's incumbent upon you to work with the
problems.

Modulo errors of manipulation on my part, my postings are
conform, even if they're not what I want. If OE can't quote
them correctly, it's not an acceptable newsreader. (Which
doesn't mean that I'll stop trying to get them to look like what
I want. I don't like quoted-ascii, and IMHO there's no need for
it today.)

--
James Kanze (Gabi Software) email: james.kanze@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, +33 (0)1 30 23 00 34

#20 June 18th, 2007, 11:35 PM

James Kanze wrote:

Quote:

On Jun 18, 8:18 pm, "Default User" <defaultuse...@yahoo.comwrote:

Quote:

James Kanze wrote:

>
[...]

Quote:

That's fine, and had the OP done so that would be reasonable.
However, it's pointless for a respondent to make that his only
contribution to ask. Especially when he full-quoted and was
unable to read the original post for context.

>
Just as pointless as for you to criticize the respondent for
doing so. His comment was technically correct.

No, it wasn't. He completely missed the sections where the OP had
flagged the errors. At best, you could say it was half right.

Quote:

Your criticism of it wasn't.

It certainly was.

Quote:

BTW, if you can't get Google to post this correctly, consider
dropping it. I understand that some people have no choice but to
use their inadequate system, but it's incumbent upon you to work
with the problems.

>
Modulo errors of manipulation on my part, my postings are
conform, even if they're not what I want.

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

Quote:

If OE can't quote
them correctly, it's not an acceptable newsreader.

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

Brian

#21 June 19th, 2007, 08:25 AM

On Jun 19, 12:27 am, "Default User" <defaultuse...@yahoo.comwrote:

Quote:

James Kanze wrote:

[...]

Quote:

Your criticism of it wasn't.

Quote:

It certainly was.

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

Quote:

BTW, if you can't get Google to post this correctly, consider
dropping it. I understand that some people have no choice but to
use their inadequate system, but it's incumbent upon you to work
with the problems.

Quote:

Modulo errors of manipulation on my part, my postings are
conform, even if they're not what I want.

Quote:

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.

Quote:

If OE can't quote
them correctly, it's not an acceptable newsreader.

Quote:

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.

--
James Kanze (GABI Software, from CAI) email:james.kanze@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, +33 (0)1 30 23 00 34

#22 June 19th, 2007, 05:15 PM

James Kanze wrote:

Quote:

On Jun 19, 12:27 am, "Default User" <defaultuse...@yahoo.comwrote:

Quote:

James Kanze wrote:

>
[...]

Quote:

Your criticism of it wasn't.

>

Quote:

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.

Quote:

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.

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

Quote:

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

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

Quote:

If OE can't quote
them correctly, it's not an acceptable newsreader.

>

Quote:

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.

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

#23 June 20th, 2007, 10:05 AM

On Jun 19, 6:09 pm, "Default User" <defaultuse...@yahoo.comwrote:

Quote:

James Kanze wrote:

Quote:

On Jun 19, 12:27 am, "Default User" <defaultuse...@yahoo.comwrote:

Quote:

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

Quote:

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

Quote:

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

Quote:

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

Quote:

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

Quote:

If OE can't quote
them correctly, it's not an acceptable newsreader.

Quote:

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

Quote:

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.

Quote:

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.

Quote:

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.)

--
James Kanze (GABI Software, from CAI) email:james.kanze@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, +33 (0)1 30 23 00 34

#24 June 20th, 2007, 05:15 PM

On Jun 20, 4:02 am, James Kanze <james.ka...@gmail.comwrote:

Quote:

On Jun 19, 6:09 pm, "Default User" <defaultuse...@yahoo.comwrote:

Quote:

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.

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

Quote:

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.

Quote:

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?

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.

Quote:

(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.)

--
Manual signature, dash dash space entered by hand.

#25 June 20th, 2007, 05:45 PM

Default User wrote:

Quote:

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.

Quote:

--
Manual signature, dash dash space entered by hand.

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

Brian