• space oddity

    From Carlos Navarro@2:341/234.1 to Nicholas Boel on Sun Feb 25 13:05:30 2024
    24 Feb 2024 07:58, you wrote to me:

    àNB>>> Yes, that's the one.. along with most of the others I wrote
    àNB>>> from Thunderbird. It seems Thunderbird adds non-breaking
    àNB>>> spaces (or &nbsp in html) anywhere there's two or more
    àNB>>> concurrent spaces next to each other.
    ^
    [...]

    I've manually removed all but one space in the quotes above to see if
    this indeed works on my end as well.

    All look fine except the ones I'm quoting above. I guess you did not remove the spaces in that block.

    *shakes fist at Thunderbird*

    :-)

    Have you tried adding '/flowed=off' to your username, or setting 'def_flowed off' in your Jam/SmapiNNTPd config? That way, those spaces will not converted to NBSPs.

    Carlos

    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: cyberiada (2:341/234.1)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Sun Feb 25 09:10:52 2024
    On Sat, 24 Feb 2024 22:38:06 +0100, Wilfred Van Velzen -> Nicholas Boel wrote:

    How did my original reply to Carlos look on your end?

    I think this is the message you're referring to:
    https://postimg.cc/gallery/kq34nZw

    Yes, that's the one.. along with most of the others I wrote from
    Thunderbird. It seems Thunderbird adds non-breaking spaces (or
    &nbsp in html) anywhere there's two or more concurrent spaces next
    to each other.

    They are here on these quotes, but on none of the others...?

    Yes that was kind of a test. I backspaced all of the 2nd and 3rd level quotes to the newly created quote character except for one paragraph of quoted text to nail down the problem. Now if I understand all of this correctly, there shouldn't be any issues with the above quotes.

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Carlos Navarro on Sun Feb 25 09:17:26 2024
    On Sun, 25 Feb 2024 19:05:30 +0100, Carlos Navarro -> Nicholas Boel wrote:

    I've manually removed all but one space in the quotes above to see if
    this indeed works on my end as well.

    All look fine except the ones I'm quoting above. I guess you did not remove
    the spaces in that block.

    Have you tried adding '/flowed=off' to your username, or setting 'def_flowed off' in your Jam/SmapiNNTPd config? That way, those spaces will
    not converted to NBSPs.

    I have not. I'm under the assumption this is a Thunderbird problem since with the same settings it doesn't occur with any of the other nntp clients I have installed here.

    I can definitely give it a shot, though!

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Carlos Navarro on Sun Feb 25 09:55:50 2024
    On Sun, 25 Feb 2024 19:05:30 +0100, Carlos Navarro -> Nicholas Boel wrote:

    Have you tried adding '/flowed=off' to your username, or setting 'def_flowed off' in your Jam/SmapiNNTPd config? That way, those spaces will not converted to NBSPs.

    This seems to work better in this regard.

    However, now obviously we're not using format=flowed text, so is it now hard wrapping the text that I'm currently writing?

    Isn't that supposed to be left alone (ie: no hard wrapping) so the next reader can deal with the message however it seems fit?

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Sun Feb 25 18:59:27 2024
    Hi Nicholas,

    On 2024-02-25 09:10:52, you wrote to me:

    How did my original reply to Carlos look on your end?

    I think this is the message you're referring to:
    https://postimg.cc/gallery/kq34nZw

    Yes, that's the one.. along with most of the others I wrote from
    Thunderbird. It seems Thunderbird adds non-breaking spaces (or
    &nbsp in html) anywhere there's two or more concurrent spaces next
    to each other.

    They are here on these quotes, but on none of the others...?

    Yes that was kind of a test. I backspaced all of the 2nd and 3rd level quotes to the newly created quote character except for one paragraph of quoted text to nail down the problem. Now if I understand all of this correctly, there shouldn't be any issues with the above quotes.

    Correct...


    Bye, Wilfred.

    --- FMail-lnx64 2.2.1.1
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Sun Feb 25 19:01:45 2024
    Hi Nicholas,

    On 2024-02-25 09:55:50, you wrote to Carlos Navarro:

    Have you tried adding '/flowed=off' to your username, or setting
    'def_flowed off' in your Jam/SmapiNNTPd config? That way, those
    spaces will not converted to NBSPs.

    This seems to work better in this regard.

    However, now obviously we're not using format=flowed text, so is it now hard wrapping the text that I'm currently writing?

    Isn't that supposed to be left alone (ie: no hard wrapping) so the next reader can deal with the message however it seems fit?

    There was no hard wrapping in the above qouted 1 lines by you...


    Bye, Wilfred.

    --- FMail-lnx64 2.2.1.1
    * Origin: FMail development HQ (2:280/464)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Sun Feb 25 12:39:48 2024
    On Mon, 26 Feb 2024 01:01:44 +0100, Wilfred Van Velzen -> Nicholas Boel wrote:

    There was no hard wrapping in the above qouted 1 lines by you...

    Confirmed in Golded. However, everything I write and see now in Thunderbird is wrapping at <80 columns, even though in Golded it shows otherwise.

    Oh well, at least the utf-8 "crap" as Tommi calls it is gone.

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Tommi Koivula@2:221/1 to Nicholas Boel on Sun Feb 25 21:03:50 2024
    On 25.02.2024 20:39, Nicholas Boel wrote:

    There was no hard wrapping in the above qouted 1 lines by you...

    Confirmed in Golded. However, everything I write and see now in
    Thunderbird is wrapping at <80 columns, even though in Golded it shows otherwise.

    Thunderbird has also some wrap settings in its "about:config".

    Oh well, at least the utf-8 "crap" as Tommi calls it is gone.

    :)

    'Tommi

    ---
    * Origin: jamnntpd/lnx (2:221/1.0)
  • From Tommi Koivula@2:221/10 to Nicholas Boel on Sun Feb 25 21:17:10 2024
    From: Tommi Koivula <tommi@rbb.homeip.net>

    On 25.02.2024 20:50, Nicholas Boel wrote:

    Confirmed in Golded. However, everything I write and see now in
    Thunderbird is wrapping at <80 columns, even though in Golded it
    shows otherwise.

    I _think_ that the "flowed" setting does not affect when entering
    messages to msgbase. It's about the nntp client how it sends the text.

    'Tommi

    ---
    * Origin: LCC SG - Linux 6.1.21-v7+ armv7l (2:221/10)
  • From Nicholas Boel@1:154/10 to Tommi Koivula on Sun Feb 25 13:49:48 2024
    On Sun, 25 Feb 2024 21:17:10 GMT, Tommi Koivula -> Nicholas Boel wrote:

    I _think_ that the "flowed" setting does not affect when entering
    messages to msgbase. It's about the nntp client how it sends the text.

    Agreed. And after disabling that option, messages seem to come in and go out with "format=fixed" which seems to change how Thunderbird reacts to how it reads the messages, as well as posting replies to them.

    When it was "format=flowed" I could write the entire window width before it wrapped to the next line. Now, with format=fixed it wraps at whatever it is set to wrap long lines at (probably 75-78).

    Definitely not a game changer, but just weird when I've been used to the other way (long lines) for quite some time with most current writing applications, and even including Golded.

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Mon Feb 26 16:57:24 2024
    On Mon, 26 Feb 2024 00:59:26 +0100, Wilfred Van Velzen -> Nicholas Boel wrote:

    How did my original reply to Carlos look on your end?

    I think this is the message you're referring to:
    https://postimg.cc/gallery/kq34nZw

    Yes, that's the one.. along with most of the others I wrote from
    Thunderbird. It seems Thunderbird adds non-breaking spaces (or
    &nbsp in html) anywhere there's two or more concurrent spaces next
    to each other.

    They are here on these quotes, but on none of the others...?

    Yes that was kind of a test. I backspaced all of the 2nd and 3rd level
    quotes to the newly created quote character except for one paragraph of
    quoted text to nail down the problem. Now if I understand all of this
    correctly, there shouldn't be any issues with the above quotes.

    Here's testing Smapinntpd with 'def-flowed=on' and Thunderbird with 'mailnews.display.disable_format_flowed_support = true' and 'mailnews.send_plaintext_flowed = false'.

    If this doesn't work, and the only option is to disable it in Smapinntpd,
    I'll probably just avoid Thunderbird, then. Since it seems to work fine in other clients. :(

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Tommi Koivula on Mon Feb 26 16:59:40 2024
    On Sun, 25 Feb 2024 21:17:10 GMT, Tommi Koivula -> Nicholas Boel wrote:

    I _think_ that the "flowed" setting does not affect when entering
    messages to msgbase. It's about the nntp client how it sends the text.
    I think I may have gotten it! The two settings regarding 'format-flowed' in Thunderbird need to be changed (see my previous message), and it seems to
    work with 'def-flowed=on' in Smapinntpd config!

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Carlos Navarro@2:341/234.99 to Nicholas Boel on Sat Feb 24 08:58:38 2024
    24/02/2024 1:36, Nicholas Boel -> Jay Harris:

    How did my original reply to Carlos look on your end?

    I think this is the message you're referring to:
    https://postimg.cc/gallery/kq34nZw

    Yes, that's the one.. along with most of the others I wrote from Thunderbird. It seems Thunderbird adds non-breaking spaces (or &nbsp in html) anywhere there's two or more concurrent spaces next to each other.


    Exactly.

    I've noticed this in Thunderbird (and Seamonkey):

    1. An extra space in inserted in quoted lines that begin with one or more spaces.

    2. If using format=flowed (def_flowed or user/flowed=on in Smapi/JamNNTPd), when there are two or more consecutive spaces in the quoted text, all but one are replaced by non-breaking spaces (UTF-8: 0xC2 0xA0 / LATIN-1: 0xA0) when posted to the NNTP server.

    As FTN-style quotes are usually prefixed by a space, another one is inserted and then the second one is converted to a NBSP.

    If you manually remove the extra spaces in the quotes before sending the reply, no NBSPs are posted. (I'm doing it in this reply.)

    Carlos

    --- Mozilla Thunderbird
    * Origin: cyberiada-NNTP (2:341/234.99)
  • From Nicholas Boel@1:154/10 to Carlos Navarro on Sat Feb 24 07:58:28 2024
    On Sat, 24 Feb 2024 14:58:38 +0100, Carlos Navarro -> Nicholas Boel wrote:

    How did my original reply to Carlos look on your end?

    I think this is the message you're referring to:
    https://postimg.cc/gallery/kq34nZw

     NB>> Yes, that's the one.. along with most of the others I wrote from
     NB>> Thunderbird. It seems Thunderbird adds non-breaking spaces (or &nbsp in
     NB>> html) anywhere there's two or more concurrent spaces next to each other.

    1. An extra space in inserted in quoted lines that begin with one or more spaces.

    2. If using format=flowed (def_flowed or user/flowed=on in Smapi/JamNNTPd),
    when there are two or more consecutive spaces in the quoted text, all but one are replaced by non-breaking spaces (UTF-8: 0xC2 0xA0 / LATIN-1: 0xA0) when posted to the NNTP server.

    As FTN-style quotes are usually prefixed by a space, another one is inserted and then the second one is converted to a NBSP.

    If you manually remove the extra spaces in the quotes before sending the reply, no NBSPs are posted. (I'm doing it in this reply.)

    I've manually removed all but one space in the quotes above to see if this indeed works on my end as well.

    *shakes fist at Thunderbird*

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Sat Feb 24 16:38:07 2024
    Hi Nicholas,

    On 2024-02-24 07:58:28, you wrote to Carlos Navarro:

    How did my original reply to Carlos look on your end?

    I think this is the message you're referring to:
    https://postimg.cc/gallery/kq34nZw

     NB>>> Yes, that's the one.. along with most of the others I wrote from
     NB>>> Thunderbird. It seems Thunderbird adds non-breaking spaces (or
     NB>>> &nbsp in html) anywhere there's two or more concurrent spaces next
     NB>>> to each other.

    They are here on these quotes, but on none of the others...?

    1. An extra space in inserted in quoted lines that begin with one or
    more spaces.

    2. If using format=flowed (def_flowed or user/flowed=on in
    Smapi/JamNNTPd), when there are two or more consecutive spaces in the
    quoted text, all but one are replaced by non-breaking spaces (UTF-8:
    0xC2 0xA0 / LATIN-1: 0xA0) when posted to the NNTP server.

    As FTN-style quotes are usually prefixed by a space, another one is
    inserted and then the second one is converted to a NBSP.

    If you manually remove the extra spaces in the quotes before sending
    the reply, no NBSPs are posted. (I'm doing it in this reply.)

    I've manually removed all but one space in the quotes above to see if this indeed works on my end as well.

    *shakes fist at Thunderbird*


    Bye, Wilfred.

    --- FMail-lnx64 2.2.1.1
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Tue Feb 27 12:04:19 2024
    Hi Nicholas,

    On 2024-02-26 16:57:24, you wrote to me:

    How did my original reply to Carlos look on your end?

    I think this is the message you're referring to:
    https://postimg.cc/gallery/kq34nZw

    Yes, that's the one.. along with most of the others I wrote from
    Thunderbird. It seems Thunderbird adds non-breaking spaces (or
    &nbsp in html) anywhere there's two or more concurrent spaces
    next to each other.

    They are here on these quotes, but on none of the others...?

    Yes that was kind of a test. I backspaced all of the 2nd and 3rd
    level quotes to the newly created quote character except for one
    paragraph of quoted text to nail down the problem. Now if I
    understand all of this correctly, there shouldn't be any issues with
    the above quotes.

    Here's testing Smapinntpd with 'def-flowed=on' and Thunderbird with 'mailnews.display.disable_format_flowed_support = true' and 'mailnews.send_plaintext_flowed = false'.

    If this doesn't work, and the only option is to disable it in Smapinntpd, I'll probably just avoid Thunderbird, then. Since it seems to work fine in other clients. :(

    Your lines were wrapped as seen above in the quotes. And there were no odd utf-8 characters in front of any of the quotes...

    Bye, Wilfred.

    --- FMail-lnx64 2.2.1.1
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/1 to Nicholas Boel on Tue Feb 27 20:17:16 2024

    Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit

    On Sun, 25 Feb 2024 21:17:10 GMT, Tommi Koivula -> Nicholas Boel wrote:

    TK> I _think_ that the "flowed" setting does not affect when entering
    TK> messages to msgbase. It's about the nntp client how it sends the text. I think I may have gotten it! The two settings regarding 'format-flowed' in Thunderbird need to be changed (see my previous message), and it seems to work with 'def-flowed=on' in Smapinntpd config!

    Ok.. Lets test, I just applied those two settings to this TB and logged
    in with tommi/flowed=on.


    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

    'Tommi

    ---
    * Origin: jamnntpd/lnx (2:221/1.0)
  • From Nicholas Boel@1:154/10 to Wilfred van Velzen on Tue Feb 27 17:32:58 2024
    On Tue, 27 Feb 2024 18:04:18 +0100, Wilfred Van Velzen -> Nicholas Boel wrote:

    Your lines were wrapped as seen above in the quotes. And there were no odd utf-8 characters in front of any of the quotes...

    Ayyyyy! That means I'm on to something! ;)

    I couldn't bring myself to change the server configuration when most other clients work fine. The change must be done in Thunderbird, in my opinion.

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Tommi Koivula on Tue Feb 27 17:37:54 2024
    On Wed, 28 Feb 2024 02:17:16 +0200, Tommi Koivula -> Nicholas Boel wrote:

    I think I may have gotten it! The two settings regarding 'format-flowed' in
    Thunderbird need to be changed (see my previous message), and it seems to
    work with 'def-flowed=on' in Smapinntpd config!

    Ok.. Lets test, I just applied those two settings to this TB and logged
    in with tommi/flowed=on.

    Doesn't look bad at all, and I don't see any utf-8 characters before the quotes.

    However, I wonder why your client is wrapping the end of a couple of the
    lines with no quote mark before it? One of them was the tearline.
    "Thunderb" was wrapped to the next line with no quote character before it.

    Simple solution is to just not quote the tearline. But maybe Jam/Smapinntpd doesn't take the tearline into consideration when quoting..?

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Wilfred van Velzen@2:280/464 to Nicholas Boel on Wed Feb 28 08:47:17 2024
    Hi Nicholas,

    On 2024-02-27 17:37:54, you wrote to Tommi Koivula:

    However, I wonder why your client is wrapping the end of a couple of
    the lines with no quote mark before it? One of them was the tearline. "Thunderb" was wrapped to the next line with no quote character before
    it.

    I think the wrapping is happening on your end. Because Tommi's message looked fine here: no wrapping of quoted lines...


    Bye, Wilfred.

    --- FMail-lnx64 2.2.1.1
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/1 to Wilfred van Velzen on Fri Mar 1 08:26:08 2024
    On 28.02.2024 9:47, Wilfred van Velzen wrote:


    On 2024-02-27 17:37:54, you wrote to Tommi Koivula:

    NB> However, I wonder why your client is wrapping the end of a couple of
    NB> the lines with no quote mark before it? One of them was the tearline.
    NB> "Thunderb" was wrapped to the next line with no quote character before
    NB> it.

    I think the wrapping is happening on your end. Because Tommi's
    message looked fine here: no wrapping of quoted lines...

    This is pretty strange. If I write a long line, it shows ok in Golded but not in TB.

    Very good example is HodDogEd, which in my phone wraps to ~70 chars. Some lines are wrapped twice, at ~70 and at ~79. :)

    'Tommi

    ...#define WRAP_WIDTH 972

    ---
    * Origin: jamnntpd/lnx (2:221/1.0)