• Error when posting

    From Flavio Bessa@4:801/188 to All on Mon Feb 21 13:07:09 2022
    Hello again,

    I was able to set up Jamnntpd as a service, can read the Jam messagebase, and now am trying to post a message using Mozilla Thunderbird.

    Now I am getting an error message saying the posting failed as UTF-8 is not supported.. I triple-checked and Thunderbird is configured to use LATIN-1 and also the config files are using LATIN-1 for that specific area.

    Should I download the utf-8 chrs file and add it to the jamnntpd.xlat config?

    ... Why is the man who invests all your money called a broker?

    --- Mystic BBS v1.12 A47 2021/12/25 (macOS/64)
    * Origin: Saturn's Orbit BBS - Private System (4:801/188)
  • From Tommi Koivula@2:221/360 to Flavio Bessa on Mon Feb 21 20:59:51 2022
    On 21 Feb 2022 18.07, Flavio Bessa wrote:

    Now I am getting an error message saying the posting failed as UTF-8
    is not supported.. I triple-checked and Thunderbird is configured to
    use LATIN-1 and also the config files are using LATIN-1 for that
    specific area.

    Should I download the utf-8 chrs file and add it to the jamnntpd.xlat
    config?


    All I did was to add these lines:

    read UTF-8 utf-8
    post utf-8 UTF-8


    Which Thunderbird are you using? The newest TB seems to always post messages in utf-8. Annoying...

    'Tommi

    ---
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Flavio Bessa@4:801/188 to Tommi Koivula on Tue Feb 22 16:57:58 2022
    On 21 Feb 2022, Tommi Koivula said the following...

    All I did was to add these lines:

    read UTF-8 utf-8
    post utf-8 UTF-8


    Which Thunderbird are you using? The newest TB seems to always post messages in utf-8. Annoying...

    Thanks, I will give it a try.

    Exactly. That started to happen after the latest TB upgrade for Mac.

    I checked other news clients and it worked fine...

    ... Top secret! Burn before reading!

    --- Mystic BBS v1.12 A47 2021/12/25 (macOS/64)
    * Origin: Saturn's Orbit BBS - Private System (4:801/188)
  • From Oli@2:280/464.47 to Flavio Bessa on Wed Feb 23 15:47:35 2022
    Flavio wrote (2022-02-22):

    On 21 Feb 2022, Tommi Koivula said the following...

    All I did was to add these lines:

    read UTF-8 utf-8
    post utf-8 UTF-8


    Which Thunderbird are you using? The newest TB seems to always post
    messages in utf-8. Annoying...

    Thanks, I will give it a try.

    That should work. I have the same configuration and no problems with posting UTF-8 messages.

    Exactly. That started to happen after the latest TB upgrade for
    Mac.

    I checked other news clients and it worked fine...

    Looks like this 'feature' has been introduced by Firefox:

    https://old.reddit.com/r/Thunderbird/comments/ps6gxp/is_text_encoding_options_gone/

    I haven't used the newer Thunderbird versions. Does it always use UTF-8 even if the text in the mail is only 7-bit ASCII?

    * Origin: They're made out of meat (2:280/464.47)
  • From Tommi Koivula@2:221/1 to Oli on Wed Feb 23 18:00:36 2022

    That should work. I have the same configuration and no problems with posting UTF-8 messages.

    FB> Exactly. That started to happen after the latest TB upgrade for
    FB> Mac.

    FB> I checked other news clients and it worked fine...

    Looks like this 'feature' has been introduced by Firefox:

    https://old.reddit.com/r/Thunderbird/comments/ps6gxp/is_text_encoding_options_gone/

    I haven't used the newer Thunderbird versions. Does it always use UTF-8 even if the text in the mail is only 7-bit ASCII?

    I have the newest TB in this computer. This always posts UTF-8. :(

    However, if the message is plain 7 bit ascii, the CHRS kludge really doesn't matter. ;)

    'Tommi

    --- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)
  • From Benny Pedersen@2:230/0 to Tommi Koivula on Mon Mar 28 12:56:52 2022
    Hello Tommi!

    21 Feb 2022 20:59, Tommi Koivula wrote to Flavio Bessa:

    use LATIN-1 and also the config files are using LATIN-1 for that
    specific area.

    Should I download the utf-8 chrs file and add it to the jamnntpd.xlat
    config?


    All I did was to add these lines:

    read UTF-8 utf-8
    post utf-8 UTF-8

    Which Thunderbird are you using? The newest TB seems to always post messages in utf-8. Annoying...

    in fidonet its only iso8859-1

    as LATIN-1, jamnntpd is good, but it does not solve clents not understanding what utf-8 is

    so imho "post utf-8 utf-8" should be "post utf-8 latin-1"

    as i remember it

    that will convert all to utf-8 ready for thunderbird, and give it back to fidonet clients as latin-1, setup latin-1 as default write in thunderbird. best of 2 diffrents worlds


    Regards Benny

    ... too late to die young :)

    --- Msged/LNX 6.1.2 (Linux/5.16.17-gentoo-dist (x86_64))
    * Origin: gopher://fido.junc.eu/ (2:230/0)
  • From Oli@2:280/464.47 to Benny Pedersen on Tue Mar 29 08:39:40 2022
    Benny wrote (2022-03-28):

    All I did was to add these lines:

    read UTF-8 utf-8
    post utf-8 UTF-8

    Which Thunderbird are you using? The newest TB seems to always post
    messages in utf-8. Annoying...

    in fidonet its only iso8859-1

    as LATIN-1, jamnntpd is good, but it does not solve clents not understanding what utf-8 is

    We cannot avoid UTF-8 forever.

    so imho "post utf-8 utf-8" should be "post utf-8 latin-1"

    as i remember it

    that will convert all to utf-8 ready for thunderbird, and give it back to fidonet clients as latin-1, setup latin-1 as default write in
    thunderbird. best of 2 diffrents worlds

    No, it won't work without a proper xlat file as parameter. The only thing you will get is UTF-8 text with the wrong charset set (= garbage).

    ---
    * Origin: War is Peace. Freedom is Slavery. Ignorance is Strength. (2:280/464.47)
  • From Benny Pedersen@2:230/0 to Oli on Fri Apr 1 10:53:52 2022
    Hello Oli!

    29 Mar 2022 08:39, Oli wrote to Benny Pedersen:

    We cannot avoid UTF-8 forever.

    or make idn default :)

    html did not solve it either

    No, it won't work without a proper xlat file as parameter. The only
    thing you will get is UTF-8 text with the wrong charset set (=
    garbage).

    yep all detail must work

    that why i make fun of html


    Regards Benny

    ... too late to die young :)

    --- Msged/LNX 6.1.2 (Linux/5.16.17-gentoo-dist (x86_64))
    * Origin: gopher://fido.junc.eu/ (2:230/0)