Subj : space oddity (fixes)
To   : Carlos Navarro
From : Nicholas Boel
Date : Sun Apr 21 2024 14:32:06

Hello Carlos,

On Mon, Apr 22 2024 00:08:32 +0000, you wrote:

 NB>> Or while using HotdogEd with flowed=off, it still wraps at the 72/79
 NB>> columns set by jam/smapinntpd, which then HotdogEd would still wrap
 NB>> the text early because it doesn't have that many columns on the
 NB>> screen?

 CN> Yes, but it does the same with both flowed off and on (format=flowed and
 CN> format=fixed look almost identical on readers that don't support f=f).
 CN> If you use it in horizontal view, or on a larger screen like a tablet,
 CN> it looks better.

Which is why I'm wondering if the wrap is set in HotdogEd for 79 characters by default. Then it would obviously have that issue when using a phone with only ~58 character width available.

 CN> I think we had seen that tin does support f=f, at least it removed
 CN> stuffed spaces. Does it wrap paragraphs at more than 72 chars, or are
 CN> they adjusted to the screen width?

I tested tin on the tin nntp server that contained very old messages. However, this was the only time I saw paragraphs adjusted to the screen width. Anything that has come through jam/smapinntpd has been wrapped at 72-79 characters.

 CN> Also, what about slrn?

I have never seen paragraphs adjusted to screen width with slrn, BUT I haven't tried anything else besides jam/smapinntpd with it, either. I will have to test that and see.

 CN> It may be that they send paragraphs as long lines, instead of breaking
 CN> them into several lines with soft-wrapping trailing spaces as in
 CN> format=flowed. Smapi/JamNNTPd properly handles both formats when posting
 CN> to the messagebase.

 NB>> So is it a HotdogEd problem that you're looking to come up with a work
 NB>> around for, specifically?

 CN> No, it may be good for other newsreaders too. If I'm not mistaken,
 CN> Smapi/JamNNTPd would work like other NNTP servers do.

I think with what I just described above (where I've seen screen width paragraphs outside of jam/smapinntpd), I see now where you guys are pointing out the difference against a "real" NNTP server.

Some clients probably don't understand the 'soft-wrapping trailing spaces', or don't care to put them back together to re-form long lines, but can handle long lines themselves just fine. Am I understanding what you are describing here, now?

Regards,
Nick

.... Take my advice, I don't use it anyway.
--- slrn/pre1.0.4-9 (FreeBSD)
 * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

.