It seems that OpenXP inserts CRLF (#13#10) at the end of every line in the body text of packed messages, including kludges.

In FTS-4000 (http://ftsc.org/docs/fts-4000.001) we can read:
============
The <LF> and soft <CR> characters (character codes 10 and 141
respectively) should not be used within a control pragraph.
============

For better compatibility with all FTN software, I suggest that OpenXP is changed so that it strips LF characters (#10) and leaves only CR (#13) when it generates PKTs - if not in all the body text, at least in the kludge lines.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Costa Blanca, Spain (2:341/234.1)

Hello Carlos!

*** Sunday 13.03.22 at 09:55, Carlos Navarro wrote to All:

It seems that OpenXP inserts CRLF (#13#10) at the end of every line in
the body text of packed messages, including kludges.

Yes it does.

In FTS-4000 (http://ftsc.org/docs/fts-4000.001) we can read:
============
The <LF> and soft <CR> characters (character codes 10 and 141
respectively) should not be used within a control pragraph.
============

Here's the *full* paragraph to which you refer:
---------- 8< ----------
The <LF> and soft <CR> characters (character codes 10 and 141
respectively) should not be used within a control pragraph. If they
are, they should be disregarded by any program processing such a
message or copies thereof.
---------- 8< ----------

And then there's this: **********************************************************************
FTSC FIDONET TECHNICAL STANDARDS COMMITTEE **********************************************************************

Publication: FTS-4000
Revision: 1
Title: CONTROL PARAGRAPHS
Author(s): FTSC

Revision Date: 1 October 2000
Expiry Date: 1 October 2002 ----------------------------------------------------------------------
Looks like the document is no longer valid.

For better compatibility with all FTN software, I suggest that OpenXP is changed so that it strips LF characters (#10) and leaves only CR (#13) when it generates PKTs - if not in all the body text, at least in the kludge lines.

The only person who could address your suggestion would be the developer
but he doesn't monitor this echo :((

Regards,
Martin

--- OpenXP 5.0.51
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

14 Mar 2022 11:21, you wrote to me:

Here's the *full* paragraph to which you refer:
---------- 8< ----------
The <LF> and soft <CR> characters (character codes 10 and 141
respectively) should not be used within a control pragraph. If they
are, they should be disregarded by any program processing such a
message or copies thereof.
---------- 8< ----------

Yes, programs should ignore it. But better not to have LFs there, if possible. They serve no purpose anyway.

And then there's this: ********************************************************************** FTSC FIDONET TECHNICAL STANDARDS COMMITTEE **********************************************************************

Publication: FTS-4000
Revision: 1
Title: CONTROL PARAGRAPHS
Author(s): FTSC

Revision Date: 1 October 2000
Expiry Date: 1 October 2002 ---------------------------------------------------------------------- Looks like the document is no longer valid.

FTS-4000 is listed in ftsc.org/docs - Standards section. I see no replacement for it, so I guess it's just that it hasn't been updated. (I may ask about this in FTSC_PUBLIC.)

For better compatibility with all FTN software, I suggest that
OpenXP is changed so that it strips LF characters (#10) and
leaves only CR (#13) when it generates PKTs - if not in all the
body text, at least in the kludge lines.

The only person who could address your suggestion would be the
developer but he doesn't monitor this echo :((

Is the developer (gsandner) in Fidonet? If not, I suppose that the place to make suggestions is the SF repo.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Costa Blanca, Spain (2:341/234.1)

Hello Carlos!

*** Friday 18.03.22 at 21:10, Carlos Navarro wrote to Martin Foster:

[snip]

And then there's this:
**********************************************************************
FTSC FIDONET TECHNICAL STANDARDS COMMITTEE
**********************************************************************

Publication: FTS-4000
Revision: 1
Title: CONTROL PARAGRAPHS
Author(s): FTSC

Revision Date: 1 October 2000
Expiry Date: 1 October 2002
----------------------------------------------------------------------
Looks like the document is no longer valid.

FTS-4000 is listed in ftsc.org/docs - Standards section. I see no replacement for it, so I guess it's just that it hasn't been updated. (I may ask about this in FTSC_PUBLIC.)

Please do ;)

For better compatibility with all FTN software, I suggest that
OpenXP is changed so that it strips LF characters (#10) and
leaves only CR (#13) when it generates PKTs - if not in all the
body text, at least in the kludge lines.

The only person who could address your suggestion would be the
developer but he doesn't monitor this echo :((

Is the developer (gsandner) in Fidonet?

Yes, he has a Point address, which is listed in the Z2 Pointlist. However,
he doesn't take an active part in Fido, he uses his Point address mainly
for testing purposes.

If not, I suppose that the place to make suggestions is the SF repo.

Hmmm, that's the last place I would try to make contact!

FYI .....
The official support channel for CrossPoint and *ALL* of its major derivatives is the Usenet newsgroup "de.comm.software.crosspoint".

The newsgroup is also "gated" to the following Google Group: https://groups.google.com/g/de.comm.software.crosspoint

It is also gated via the Fido echo XPOINT, which originates from Tommi Koivula's system(not sure which AKA he uses for this).

Take your pick :-)

Please note that somebody(not me) forwarded your original post to the newsgroup on the same day that you posted it in here but so far, it has received nil response.

See my netmail for the rest of my reply .....

Regards,
Martin

--- OpenXP 5.0.51
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hi Carlos.

19 Mar 22 09:04, Martin Foster wrote to you:

The newsgroup is also "gated" to the following Google Group: https://groups.google.com/g/de.comm.software.crosspoint

It is also gated via the Fido echo XPOINT, which originates from Tommi Koivula's system(not sure which AKA he uses for this).

The gate runs at 2:221/10, but the echo (xpoint) is available at 2:341/66, so you can link it there. It is also available at my nntp servers.

Take your pick :-)

Exactly! :)

'Tommi

--- GoldED+/LNX 1.1.5-b20210627
* Origin: nntps://news.fidonet.fi (2:221/6)

19 Mar 2022 18:26, you wrote to me:

It is also gated via the Fido echo XPOINT, which originates from
Tommi Koivula's system(not sure which AKA he uses for this).

The gate runs at 2:221/10, but the echo (xpoint) is available at
2:341/66, so you can link it there. It is also available at my nntp servers.

Got it, thanks.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Costa Blanca, Spain (2:341/234.1)

19 Mar 2022 09:04, you wrote to me:

The official support channel for CrossPoint and *ALL* of its major derivatives is the Usenet newsgroup "de.comm.software.crosspoint".

The newsgroup is also "gated" to the following Google Group: https://groups.google.com/g/de.comm.software.crosspoint

It is also gated via the Fido echo XPOINT, which originates from Tommi
Koivula's system(not sure which AKA he uses for this).

Thanks for the info.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Costa Blanca, Spain (2:341/234.1)

Hello Marc!

** On Thursday 24.03.22 - 05:56, you wrote to Martin:

Martin, it's really disappointing that a developer of
FidoNet Point software takes no part in the Echo or
doesn't have an Echo dedicated to his software. IMO, this
doesn't speak highly of that software's continuing
development. :( Hopefully I'm wrong.

Fido's XPOINT echo serves to bridge communications to Gunter
with the newsgroup. OpenXP supports nntp, and that's what
Gunter seems to prefer using.

I remember many years ago, Harvey Parisien who developed
PPoint, not only participated here, but I believe was one
of the "founders" of the POINTS Echo with a full Node as
well as a Point until he retired from FidoNet years later.
I still contact him from time-to-time to chat. I took over
moderatorship of the echo when he retired - and that's
been YEARS ago.

Harvey.. is he the fellow who built some fax program for OS/2?


--
../|ug

--- OpenXP 5.0.51
* Origin: The ONLY point that matters! --> . <-- (2:221/1.58)

19 Mar 2022 09:04, you wrote to me:

Publication: FTS-4000

[...]

Expiry Date: 1 October 2002
----------------------------------------------------------------
------ Looks like the document is no longer valid.

FTS-4000 is listed in ftsc.org/docs - Standards section. I see no
replacement for it, so I guess it's just that it hasn't been
updated. (I may ask about this in FTSC_PUBLIC.)

Please do ;)

Done. :-) It hasn't been updated, but didn't expire.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234)

Hello Marc!

*** Thursday 24.03.22 at 05:56, Marc Lewis wrote to Martin Foster:

[snip]

The only person who could address your suggestion would be the
developer but he doesn't monitor this echo :((

Is the developer (gsandner) in Fidonet?

Yes, he has a Point address, which is listed in the Z2 Pointlist.
However, he doesn't take an active part in Fido, he uses his
Point address mainly for testing purposes.

[snip]

Martin, it's really disappointing that a developer of FidoNet Point software takes no part in the Echo or doesn't have an Echo dedicated
to his software.

Yes, it *is* disappointing but that's the way it is and it has actually worked surprisingly well.

IMO, this doesn't speak highly of that software's continuing
development. :( Hopefully I'm wrong.

FYI ...
The current developer appeared totally out of the blue just over 8 years
ago and since then, he's pushed out a staggering 50+ releases! If that's
not continuing development, I don't know what is :)

Regards,
Martin

--- OpenXP 5.0.51
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Carlos!

*** Thursday 24.03.22 at 17:21, Carlos Navarro wrote to Martin Foster:

Publication: FTS-4000

[...]

Expiry Date: 1 October 2002

^^^^^^^^^^^^ ^^^^^^^^^^^^^^

----------------------------------------------------------------
------ Looks like the document is no longer valid.

FTS-4000 is listed in ftsc.org/docs - Standards section. I see no
replacement for it, so I guess it's just that it hasn't been
updated. (I may ask about this in FTSC_PUBLIC.)

Please do ;)

Done. :-)

Yeah, seen it thanks.

It hasn't been updated, but didn't expire.

Ummmmmmmm, the document has expired - Period!

Regards,
Martin

--- OpenXP 5.0.51
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)