Test for proper koi8-r cyr charset display.

�������� ��ਫ���� � ��� ⠪��..


...Wed, 22 Nov 2023 09:27:45 +0400

---
* Origin: nntp://news.fidonet.fi (2:221/6.0)

Hi Gleb,

On 2023-11-22 07:32:06, you wrote to All:

@MSGID: 2:221/6.0 655d9250
@PID: SmapiNNTPd/Linux/IPv6 3.0 20231120
@NOTE: tin/2.6.3-20231106 ("Pittyvaich") (Linux/5.10.16.3-microsoft-standard-WSL2 (x86_64)).
@CHRS: CP866 2
@TZUTC: 0200
Test for proper koi8-r cyr charset display.

I don't think koi8-r is the same charset as CP866... ?

�������� ��ਫ���� � ��� ⠪��..

...Wed, 22 Nov 2023 09:27:45 +0400

---
* Origin: nntp://news.fidonet.fi (2:221/6.0)
SEEN-BY: 124/5016 153/757 203/0 221/0 1 6 240/1120 5832 280/464 292/8125 SEEN-BY: 301/1 335/364 341/66 200 234 396/45 633/280 712/848 770/1 5020/400
SEEN-BY: 5020/1042
@PATH: 221/6 341/66 280/464

Bye, Wilfred.

--- FMail-lnx64 2.2.0.0
* Origin: FMail development HQ (2:280/464)

Hello, Gleb Hlebov.
On 22/11/2023 7.32 you wrote:

Test for proper koi8-r cyr charset display.
�������� ��ਫ���� � ��� ⠪��..

Looks ok to me. ;)

--- FastEcho/2 1.46.1 Revival
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)

Wilfred once wrote:

@MSGID: 2:221/6.0 655d9250
@PID: SmapiNNTPd/Linux/IPv6 3.0 20231120
@NOTE: tin/2.6.3-20231106 ("Pittyvaich") (Linux/5.10.16.3-microsoft-standard-WSL2 (x86_64)).
@CHRS: CP866 2
@TZUTC: 0200
Test for proper koi8-r cyr charset display.

I don't think koi8-r is the same charset as CP866... ?

Well, I believe it is converted from koi8-r to cp866 by usenet-fidonet
gate software? I have received this msg via my fidonet AKA and the cyrillics looks fine in GoldED.
The other reply from Tommi also displays correct charset.
Coulbe be that some msg readers have issues with cp866?

I use the following settings in reader's config:

mm_network_charset=KOI8-R
post_mime_encoding=base64


....Wed, 22 Nov 2023 13:34:10 +0400

---
* Origin: nntp://news.fidonet.fi (2:221/6.0)

On 11/22/2023 9:58 AM, Wilfred van Velzen wrote:

X-JAM-From: Wilfred van Velzen <2:280/464>
X-JAM-To: Gleb Hlebov
X-JAM-FTSKLUDGE: TID: FMail-lnx64 2.2.0.0
X-JAM-FTSKLUDGE: RFC-X-No-Archive: Yes
X-JAM-TZUTCINFO: 0100
X-JAM-FTSKLUDGE: CHRS: UTF-8 2

=======

X-JAM-PID: GED+LNX 1.1.5-b20161221
X-JAM-MSGID: 2:280/464 655db4c1
X-JAM-REPLYID: 2:221/6.0 655d9250
X-JAM-SEENBY2D: 124/5016 153/757 203/0 221/0 1 6 360 240/1120 5832 280/464 292/8125
X-JAM-SEENBY2D: 301/1 341/66 234 396/45 423/81 633/280 712/848 770/1 5020/400 X-JAM-PATH2D: 280/464 221/1
X-JAM-Attributes: TypeEcho
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=fixed

=============

Content-Transfer-Encoding: 8bit

@MSGID: 2:221/6.0 655d9250
@PID: SmapiNNTPd/Linux/IPv6 3.0 20231120
@NOTE: tin/2.6.3-20231106 ("Pittyvaich") (Linux/5.10.16.3-microsoft-standard-WSL2 (x86_64)).
@CHRS: CP866 2
@TZUTC: 0200
Test for proper koi8-r cyr charset display.

I don't think koi8-r is the same charset as CP866... ?

tommi@kco:~$ grep koi8 /bbs/smapinntpd.xlat
read CP866 koi8-r 866_koi.chs -keepsoftcr
post koi8-r CP866 koi_866.chs

Ž‚…Š€ ª¨à¨««¨æë ¨ ¢áñ â ª®¥..

:(

'Tommi

--- FastEcho/2 1.46.1 Revival
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)

Tommi once wrote:

Content-Type: text/plain; charset=koi8-r; format=fixed Content-Transfer-Encoding: 8bit

Test for proper koi8-r cyr charset display.
�������� ��ਫ���� � ��� ⠪��..

Looks ok to me. ;)

Thanks!
I understand it so that when someone replies using an editor that
converts the message into utf-8, all cyr characters would turn into
garbage, as in case of Wilfred's reply...


...Wed, 22 Nov 2023 13:54:15 +0400

---
* Origin: nntp://news.fidonet.fi (2:221/6.0)

On 11/22/2023 12:04 PM, Gleb Hlebov wrote:

Content-Type: text/plain; charset=koi8-r; format=fixed
Content-Transfer-Encoding: 8bit

Test for proper koi8-r cyr charset display.
�������� ��ਫ���� � ��� ⠪��..

Looks ok to me. ;)

Thanks!
I understand it so that when someone replies using an editor that
converts the message into utf-8, all cyr characters would turn into
garbage, as in case of Wilfred's reply...

Replying as utf-8 to messages written in cp866/koi8-r usually works only if the reader/editor fully supports utf-8. GoldED does not support utf-8.

'Tommi

---
* Origin: nntps://news.fidonet.fi (2:221/6.0)

Tommi once wrote:

Content-Type: text/plain; charset=utf-8; format=fixed

=============

tommi@kco:~$ grep koi8 /bbs/smapinntpd.xlat
read CP866 koi8-r 866_koi.chs -keepsoftcr
post koi8-r CP866 koi_866.chs

Ah, ok. Kind of what I've guessed.

Btw I noticed that some posts have the same weird timestamps? Any idea?
Like: Thu, 01 Jan 1970 03:59:59


....Wed, 22 Nov 2023 14:07:50 +0400

---
* Origin: nntp://news.fidonet.fi (2:221/6.0)

Hi Gleb.

22 Nov 23 12:12:26, you wrote to me:

Btw I noticed that some posts have the same weird timestamps? Any idea? Like: Thu, 01 Jan 1970 03:59:59

Nope, no idea.

'Tommi

---
* Origin: Point One (2:221/1.1)

Tommi once wrote:

Btw I noticed that some posts have the same weird timestamps? Any idea? Like: Thu, 01 Jan 1970 03:59:59

Nope, no idea.

I mean, in this case the timestamp in the header seems to be wrong for
some reason and the date appears as "01-Jan-1970" in my reader. What do
you think could be the cause?

Here's an example:

<...>
Newsgroups: english_tutor
Subject: test
Date: Tue, 21 Nov 2023 24:50:36

*^^^^^^^^*

Message-ID: <1340$english_tutor@SmapiNNTPd>
References: <618$english_tutor@SmapiNNTPd>
X-SMAPI-From: Ardith Hinton
X-SMAPI-To: Gleb Hlebov
X-SMAPI-DateWritten: 21 Nov 23 22:50:36
SMAPI-DateArrived: 22 Nov 23 08:57:02
<...>


....Thu, 23 Nov 2023 13:26:27 +0400

---
* Origin: nntp://news.fidonet.fi (2:221/6.0)

23 Nov 2023 11:44, you wrote to Tommi Koivula:

I mean, in this case the timestamp in the header seems to be wrong for some reason and the date appears as "01-Jan-1970" in my reader. What
do you think could be the cause?

[...]

Do you have the same issue if you connect to Tommi's other NNTP server, rbb.fidonet.fi?

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234)

Hi Gleb.

23 Nov 23 11:44, you wrote to me:

Here's an example:

<...>
Newsgroups: english_tutor
Subject: test
Date: Tue, 21 Nov 2023 24:50:36

*^^^^^^^^*

Message-ID: <1340$english_tutor@SmapiNNTPd>
References: <618$english_tutor@SmapiNNTPd>
X-SMAPI-From: Ardith Hinton
X-SMAPI-To: Gleb Hlebov
X-SMAPI-DateWritten: 21 Nov 23 22:50:36
SMAPI-DateArrived: 22 Nov 23 08:57:02
<...>

I checked the message in the msgbase. The real date/time is "21 Nov 23 22:50:36" there. However the msg has no TZUTC kludge, so SmapiNNTPd fails to convert the date to server timezone, which is 0200. Apparently a bug in (my?) SmapiNNTPd.

22+2=24. :)

....Thu, 23 Nov 2023 13:26:27 +0400

'Tommi

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

On 23.11.2023 15:40, Carlos Navarro wrote:

23 Nov 2023 11:44, you wrote to Tommi Koivula:

I mean, in this case the timestamp in the header seems to be wrong for some reason and the date appears as "01-Jan-1970" in my reader. What
do you think could be the cause?

[...]

Do you have the same issue if you connect to Tommi's other NNTP server, rbb.fidonet.fi?

My Jamnntpd seems to show the date in GMT, SmapiNNTPd fails because there is no TZ information in the msg.

Smapinntpd: Date: Tue, 21 Nov 2023 24:50:36
Jamnntpd: Date: Tue, 21 Nov 2023 20:50:36 GMT

Thunderbird has no problem showing the invalid time. :D

'Tommi

---
* Origin: rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)

On 23.11.2023 9:44, Gleb Hlebov wrote:

Newsgroups: english_tutor
Subject: test
Date: Tue, 21 Nov 2023 24:50:36

*^^^^^^^^*

I may have fixed it. Please check.

== cut
Newsgroups: english_tutor
Subject: test
Date: Tue, 21 Nov 2023 22:50:36 GMT
Message-ID: <1340$english_tutor@SmapiNNTPd>
References: <618$english_tutor@SmapiNNTPd>
X-SMAPI-From: Ardith Hinton
X-SMAPI-To: Gleb Hlebov
X-SMAPI-DateWritten: 21 Nov 23 22:50:36
== cut

'Tommi

---
* Origin: nntps://news.fidonet.fi (2:221/6.0)

Carlos Navarro once wrote:

I mean, in this case the timestamp in the header seems to be wrong for some reason and the date appears as "01-Jan-1970" in my reader.

Do you have the same issue if you connect to Tommi's other NNTP server, rbb.fidonet.fi?

I've now tried both rbb and news and the said issue seems to be gone, at
least I can see those messages dated correctly.

Carlos

....Fri, 24 Nov 2023 10:08:03 +0400

--- FastEcho/2 1.46.1 Revival
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)

Tommi Koivula once wrote:

I may have fixed it. Please check.

Yep, everything now looks as it should,
thank you!


....Fri, 24 Nov 2023 10:21:58 +0400

--- FastEcho/2 1.46.1 Revival
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)

Carlos Navarro <0@234.341.2> once wrote:

I mean, in this case the timestamp in the header seems to be wrong for some reason and the date appears as "01-Jan-1970" in my reader. What

However as far as I can see there's something that causes "timestamp
anomaly" in my news reader, it shows "01-Jan-1970" (it may be also "31-Dec-1979") when it reads incorrect kludges, like the following:

=======================================
From 0@40.19.1 Fri Nov 24 10:39:47 2023
Path: JamNNTPd!not-for-mail
From: "Chad Adams : ALL" <0@40.19.1>
To: ALL
X-Comment-To: ALL
Newsgroups: fidotest
Subject: Testing CTL-A Tosser Fix
Date: Tue, 7 Mar 2023 10:20:51 -06:0

^^^^^

[...]
=======================================


....Fri, 24 Nov 2023 10:47:07 +0400

--- FastEcho/2 1.46.1 Revival
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)

On 11/24/2023 8:24 AM, Gleb Hlebov wrote:

I may have fixed it. Please check.

Yep, everything now looks as it should,
thank you!

Thank you for finding this thing. I never noticed it because Thunderbird fixes the invalid timestamp. :)

'Tommi

--- FastEcho/2 1.46.1 Revival
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)

On 11/24/2023 8:55 AM, Gleb Hlebov wrote:

Carlos Navarro <0@234.341.2> once wrote:

I mean, in this case the timestamp in the header seems to be wrong for >> GH> some reason and the date appears as "01-Jan-1970" in my reader. What

However as far as I can see there's something that causes "timestamp
anomaly" in my news reader, it shows "01-Jan-1970" (it may be also "31-Dec-1979") when it reads incorrect kludges, like the following:

=======================================
From 0@40.19.1 Fri Nov 24 10:39:47 2023
Path: JamNNTPd!not-for-mail
From: "Chad Adams : ALL" <0@40.19.1>
To: ALL
X-Comment-To: ALL
Newsgroups: fidotest
Subject: Testing CTL-A Tosser Fix
Date: Tue, 7 Mar 2023 10:20:51 -06:0

^^^^^

[...]
=======================================

Well, that is/was a bug that CyberBBS thing writing invalid kludges.

'Tommi

--- FastEcho/2 1.46.1 Revival
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)