Hello All!

I'm doing tests with smapinntpd, I switched from Thunderbird to PAN to see if the TO: field is ok with PAN but when I try to post a message I get this in the
log of the server:

POST failed (Unsupported charset "UTF-8")

How can I do to support the UTF-8 charset?

Many thanks. :)

Ciao!
Fabio

--- GoldED+/LNX 1.1.5-b20180707
* Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)

Hello All!

29 Jul 19 15:04, I wrote to you:

I'm doing tests with smapinntpd, I switched from Thunderbird to PAN to
see if the TO: field is ok with PAN but when I try to post a message I
get this in the log of the server:

POST failed (Unsupported charset "UTF-8")

How can I do to support the UTF-8 charset?

Ok, RTFM always works. :)
UTF-8 posting is always unsupported! :(
And PAN has a bug, also if you set another charset it posts always in utf-8.

Now I'll try with another reader. Any Suggestion? (Platform Linux).

Ciao!
Fabio

--- GoldED+/LNX 1.1.5-b20180707
* Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)

From Fabio Bizzi To All

Hello All!
29 Jul 19 15:04, I wrote to you:

I'm doing tests with smapinntpd, I switched from Thunderbird to PAN to see if the TO: field is ok with PAN but when I try to post a message I get this in the log of the server:
POST failed (Unsupported charset "UTF-8")
How can I do to support the UTF-8 charset?

Ok, RTFM always works. :)
UTF-8 posting is always unsupported! :(
And PAN has a bug, also if you set another charset it posts always in utf-8. Now I'll try with another reader. Any Suggestion? (Platform Linux).

Nope, docs are outdated, posting utf8 works fine. See my kludges.

I'll post my config asap. Now mobile only.

You may try claws mail or sylpheed. I like sylpheed. ;)

--- HotdogEd/2.13.5 (Android; Google Android; rv:1) Hotdoged/1557368964000 HotdogEd/2.13.5
* Origin: smapinntpd/linux @ nntps://news.fidonet.fi (2:221/6.0)

Hello, Tommi Koivula.
On 30/07/19 12:07 you wrote:

From Fabio Bizzi To All

Nope, docs are outdated, posting utf8 works fine. See my kludges.
I'll post my config asap. Now mobile only. You may try claws mail
or sylpheed. I like sylpheed. ;)

Many thanks!!! :)
I'll wait for the config. ;)
--
Ciao! :)
Fabio.
--- Hotdoged/2.13.5/Android
* Origin: ]\/[imac boss android point (2:335/364.3)

Tuesday July 30 2019 12:07, Tommi Koivula wrote to Fabio Bizzi:

Nope, docs are outdated, posting utf8 works fine. See my kludges.

I'll post my config asap. Now mobile only.

I only added these two lines to my .xlat file:

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

'Tommi

---
* Origin: rbb.fidonet.fi (2:221/360)

Hi! Tommi,

On 07/31/2019 12:22 AM, you wrote Fabio Bizzi:

Tuesday July 30 2019 12:07, Tommi Koivula wrote to Fabio Bizzi:

Nope, docs are outdated, posting utf8 works fine. See my kludges.

I'll post my config asap. Now mobile only.

I only added these two lines to my .xlat file:

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

I did the same thing after Björn posted his back in January 2010. After that I thought I was just lucky if I was careful.

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Don't force it, just get a bigger hammer. (3:640/1384.125)

Hello Tommi!

30 Jul 19 17:22, you wrote to me:

I only added these two lines to my .xlat file:

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

Many Thanks!!! :)

Ciao!
Fabio

--- GoldED+/LNX 1.1.5-b20180707
* Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)

Nope, docs are outdated, posting utf8 works fine. See my kludges.

I'll post my config asap. Now mobile only.

I only added these two lines to my .xlat file:

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

I did the same thing after Björn posted his back in January 2010.

So it has to work ok then. :D

'Tommi

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

Hi Fabio.

31 Jul 19 07:38:26, you wrote to me:

Hello Tommi!

30 Jul 19 17:22, you wrote to me:

I only added these two lines to my .xlat file:

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

Many Thanks!!! :)

Prego! :)

I have these in this server:

=== Cut ===
read UTF-8 utf-8 utf_utf.chs
readalias utf_8 utf-8
post utf-8 UTF-8 utf_utf.chs
postalias utf_8 utf-8
=== Cut ===

But the chs table is useless, it converts nothing. I don't remember why I have added the aliases. ;)

'Tommi

... \\COW has been up for: 15 day(s), 12 hour(s), 53 minute(s), 9 second(s)
---
* Origin: *** JamNNTPd @ nntp://fidonews.mine.nu *** (2:221/1.6)

Ok, this message is edited and posted with PAN in UTF-8 via smapinntpd,

Not really. It *does* have the kludge, but it's still ASCII only.

Content-Type: text/plain; charset=us-ascii; format=flowed

You have to add a combination of characters that are not all supported with any other single code page.

For instance Еще раз спасибо за вашу помощь and Tack igen för all er hjälp.


..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se (2:203/2)

Hello Fabio,

On Wednesday July 31 2019 10:17, you wrote to :

@MSGID: 2:335/364 5d414eb7
@PID: GED+LNX 1.1.5-b20180707
@CHRS: UTF-8 2

^
Should be '4'


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

@CHRS: UTF-8 2

MvdV> ^
MvdV> Should be '4'

But no known FTN program uses it for anything meaningful.



..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se (2:203/2)

For instance Еще раз спасибо за вашу помощь
and Tack igen för all er hjälp.

Ok, let's see if it works now. :)
Еще раз спасибо за вашу помощь

It does.



..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se (2:203/2)

Hello Fabio,

On Wednesday July 31 2019 14:16, you wrote to :

@CHRS: UTF-8 2
^
Should be '4'

I saw that all the messages from smapinntpd and jamnntpd have the
UTF-8 2.

BTW I'm not aware of character encoding, the 2 or the 4 stands for? :)

http://ftsc.org/docs/fts-5003.001


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

BTW I'm not aware of character encoding, the 2 or the 4 stands for? :)

Never mind, Fabio. It was supposed to mean "level of internationalisation" but nobody has really been able to explain what that means, and there is no known implementation that uses it.

It works perfectly well whatever number you put in that position, and has done so for more than a decade.



..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se (2:203/2)

I don't want to be blamed for it :P

It's cool, man. I've been pestered about it for many years -- on and off. 8-)



..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se (2:203/2)

On Wed, 31 Jul 2019 19:51:12 +0200 Fabio Bizzi wrote:

P.S I found how to quote with Sylpheed! WoW :P

Oh yes, no overquoting. ;)

Tommi

--- Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
* Origin: smapinntpd/linux @ nntps://news.fidonet.fi (2:221/6.0)