Frederic Bouvier wrote:
>
> The telnet interface produce wrong line ending when I run both FlightGear
> and the telnet client on Win2k. I've just sent a patch to Curt that produce
> line ending based on the platform where fgfs is running ( something between
> #ifdef and #endif ).
>
> For the mom
Frederic Bouvier wrote:
> Perhaps I didn't made me clear. The problem is when FlightGear send text to
> the telnet client. Each line begins where the previous ends because Win2k
> telnet client needs a cariage return (\r) with the line feed (\n).
OK. The Telnet protocol (RFC854) requires that li
From: "Julian Foad" <[EMAIL PROTECTED]>
> Frederic Bouvier wrote:
> >
> > The telnet interface produce wrong line ending when I run both
FlightGear
> > and the telnet client on Win2k. I've just sent a patch to Curt that
produce
> > line ending based on the platform where fgfs is running ( somethin
I (Julian Foad) wrote:
>
> Idea: the receiver should accept any of these four line endings:
Sorry, I misunderstood. I was thinking of a peer-to-peer type connection.
- Julian
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear
Frederic Bouvier wrote:
>
> The telnet interface produce wrong line ending when I run both FlightGear
> and the telnet client on Win2k. I've just sent a patch to Curt that produce
> line ending based on the platform where fgfs is running ( something between
> #ifdef and #endif ).
>
> For the mom
The telnet interface produce wrong line ending when I run both FlightGear
and the telnet client on Win2k. I've just sent a patch to Curt that produce
line ending based on the platform where fgfs is running ( something between
#ifdef and #endif ).
For the moment, this patch only address the issue
