2.3.2
* nntpserv.c
- Fix for extra space at the beginning of the origin line
By looking at your change in the code, I'm afraid you have just disabled flowed text.
The problem is not only with Origin lines, it's with any line with
leading spaces.
Not 100% sure, but I think it may be that Thunderbird does not fully implement format=flowed according to the RFCs, WRT space stuffing.
On Sat, 30 Mar 2024 16:31:52 +0100, Carlos Navarro -> Nicholas Boel
wrote:
By looking at your change in the code, I'm afraid you have just
disabled flowed text.
Wouldn't this change only affect a line starting with " * Origin: " ?
The problem is not only with Origin lines, it's with any line
with leading spaces.
Not 100% sure, but I think it may be that Thunderbird does not
fully implement format=flowed according to the RFCs, WRT space
stuffing.
While I can believe this, I also saw the same extra space at the
beginning of the origin line with slrn, so I was led to believe this wasn't specific to Thunderbird.
Let's see what this line does.
By looking at your change in the code, I'm afraid you have just
disabled flowed text.
Wouldn't this change only affect a line starting with " * Origin:
" ?
When reading this message in Golded, my text seemed to have still been format=flowed?
While I can believe this, I also saw the same extra space at the
beginning of the origin line with slrn, so I was led to believe this wasn't specific to Thunderbird.
Wouldn't this change only affect a line starting with " * Origin:
" ?
When reading this message in Golded, my text seemed to have still been
format=flowed?
This is not about GoldED. It affects how you read/receive it in the NNTP client.
Open your message with TB, resize the window and check if you see it
like flowed or fixed
https://www.cyberiada.org/fido/tmpfiles/fixed-vs-flowed.png
Does slrn support format=flowed?
This is not about GoldED. It affects how you read/receive it in
the NNTP client.
Open your message with TB, resize the window and check if you see
it like flowed or fixed
https://www.cyberiada.org/fido/tmpfiles/fixed-vs-flowed.png
Mine has never looked like the top of that screenshot. So I don't
really know where you are seeing that, unless you have completely
disabled format=flowed from Thunderbird or are using def_flowed=off.
Not 100% sure, but I think it may be that Thunderbird does not fully implement format=flowed according to the RFCs, WRT space stuffing.
Does slrn support format=flowed?
Yes.
Just in case, I've tried applying your change to my test server. I can confirm that messages have "Content-Type: ... format=flowed" but paragraphs are fixed, not flowed. And, as I expected, resizing the
message window does not rewrap the paragraphs as in flowed text (like in the bottom of the screenshot).
Could it be you were reading cached messages?
To be more precise, TB seems to implement it properly for reading messages, but maybe not for quote-replying (with all those extra spaces)... But I'm not sure.
31 Mar 2024 08:20, you wrote to me:
Does slrn support format=flowed?
Yes.
Ok, will have to check it...
Can you please quote-reply this message with slrn?
Carlos
--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)
31 Mar 2024 08:20, you wrote to me:
Does slrn support format=flowed?
Yes.
Ok, will have to check it...
Can you please quote-reply this message with slrn?
Carlos
--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)
Can you please quote-reply this message with slrn?
--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)
Not sure how Smapinntpd will process it, but here quoting this I see
the extra space before the origin line as well. Otherwise, here is the quote-reply you are looking for. Everything above was quoted as-is,
with no manual intervention by me. So if there's anything unusual it
is either slrn (which I've seen no issues with yet - they have all
been TB related), or Smapinntpd itself.
31 Mar 2024 16:20, you wrote to me:
Can you please quote-reply this message with slrn?
--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)
Not sure how Smapinntpd will process it, but here quoting this I see
the extra space before the origin line as well. Otherwise, here is
quote-reply you are looking for. Everything above was quoted as-is,
with no manual intervention by me. So if there's anything unusual it
is either slrn (which I've seen no issues with yet - they have all
been TB related), or Smapinntpd itself.
Thank you Nick. So it's not only TB... slrn also adds (or keeps) the
extra space in quotes.
I don't know if the way they do is correct. If it is, then
Smapi/JamNNTPd should remove those stuffed spaces from the quotes when posting to the messagebase. Either way, I'm working on a fix.
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 88 |
Nodes: | 16 (0 / 16) |
Uptime: | 12:28:40 |
Calls: | 4,921 |
Calls today: | 7 |
Files: | 8,491 |
Messages: | 351,015 |