Hello,

How about UTF-8 message notice here

1 U+1F600 😀 grinning face
2 U+1F603 😃 grinning face with big eyes
3 U+1F604 😄 grinning face with smiling eyes

P.S. Another one warn is also welcome 😀

Thanks.

--- Golden/Linux-amd64 1.2.18 2022-01-15 02:13 MSK (master)
* Origin: Стремитесь не к успеху, а к ценностям, которые он дает (2:5030/1081.102)

On 20.1.2022 11.16, Vitold Sedyshev wrote:

Hello,

How about UTF-8 message notice here

1 U+1F600 😀 grinning face
2 U+1F603 😃 grinning face with big eyes
3 U+1F604 😄 grinning face with smiling eyes

P.S. Another one warn is also welcome 😀

Looks fine in Thunderbird.

Thanks.

--- Golden/Linux-amd64 1.2.18 2022-01-15 02:13 MSK (master)
* Origin: Стремитесь не к успеху, а к ценностям, которые он дает (2:5030/1081.102)

'Tommi

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)

Glad to see you, Tommi!

On 20.1.2022 11.16, Vitold Sedyshev wrote:

Hello,

How about UTF-8 message notice here

1 U+1F600 ? grinning face
2 U+1F603 ? grinning face with big eyes
3 U+1F604 ? grinning face with smiling eyes

P.S. Another one warn is also welcome ?

Looks fine in Thunderbird.

Thanks.

--- Golden/Linux-amd64 1.2.18 2022-01-15 02:13 MSK (master)
* Origin: ��६���� �� � �ᯥ��, � � 業�����, ����� �� ���� (2:5030/1081.102)

'Tommi

Displays perfectly in Telegram

*** [Netmail-to-Telegram address: 474405162@2:460/256]

... Tag, you are IT!
--- tg BBS v0.7.1
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

On 20 Jan 2022 16.59, John Dovey wrote:

Glad to see you, Tommi!

TK> On 20.1.2022 11.16, Vitold Sedyshev wrote:
TK> > Hello,
TK> >
TK> > How about UTF-8 message notice here
TK> >
TK> > 1 U+1F600 ? grinning face
TK> > 2 U+1F603 ? grinning face with big eyes
TK> > 3 U+1F604 ? grinning face with smiling eyes
TK> >
TK> > P.S. Another one warn is also welcome ?
TK> Looks fine in Thunderbird.
TK> > Thanks.
TK> >
TK> > --- Golden/Linux-amd64 1.2.18 2022-01-15 02:13 MSK (master)
TK> > * Origin: Стремитесь не к успеху, а к ценностям, которые он дает (2:5030/1081.102)
TK> 'Tommi

Displays perfectly in Telegram

But not anymore, you replied with "@CHRS: cp866 2" :(

'Tommi

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

Hello, Vitold Sedyshev.
On 20/01/2022 12.16 you wrote:

Hello,
How about UTF-8 message notice here
1 U+1F600 😀 grinning face
2 U+1F603 😃 grinning face with big eyes
3 U+1F604 😄 grinning face with smiling eyes
P.S. Another one warn is also welcome 😀
Thanks.
--- Golden/Linux-amd64 1.2.18 2022-01-15 02:13 MSK (master)
* Origin: Стремитесь не к успеху, а к ценностям, которые он дает (2:5030/1081.102)

http://pics.rsh.ru/img/Screens1096_ndpkn07s.jpg


And ok in HotDodEd too. ;)

--
'Tommi
--- Hotdoged/2.13.5/Android
* Origin: .... ... .. . (2:221/6.52)

Glad to see you, Tommi!

On 20 Jan 2022 16.59, John Dovey wrote:

Glad to see you, Tommi!

TK> On 20.1.2022 11.16, Vitold Sedyshev wrote:
TK> > Hello,
TK> >
TK> > How about UTF-8 message notice here
TK> >
TK> > 1 U+1F600 ? grinning face
TK> > 2 U+1F603 ? grinning face with big eyes
TK> > 3 U+1F604 ? grinning face with smiling eyes
TK> >
TK> > P.S. Another one warn is also welcome ?
TK> Looks fine in Thunderbird.
TK> > Thanks.
TK> >
TK> > --- Golden/Linux-amd64 1.2.18 2022-01-15 02:13 MSK (master)
TK> > * Origin: ��६���� �� � �ᯥ��, � � 業�����, ����� �� ���� (2:5030/1081.102)
TK> 'Tommi

Displays perfectly in Telegram

But not anymore, you replied with "@CHRS: cp866 2" :(
'Tommi

https://brorabbit.g0x.ru/pic/image_2022-01-20_14-01-54.png


*** [Netmail-to-Telegram address: 474405162@2:460/256]

... Tag, you are IT!
--- tg BBS v0.7.1
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

Hi All...

utf-8 it works nicely in the fido->telegram direction, but not back.

Ciao!
/|ug (https://t.me/aabolins)

--- Want fido for iOS/MacOS/Android/Win/Linux? Info=https://shrtco.de/tpJ9yV
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

Glad to see you, Tommi!

Hello, Vitold Sedyshev.
On 20/01/2022 12.16 you wrote:

Hello,
How about UTF-8 message notice here
1 U+1F600 ? grinning face
2 U+1F603 ? grinning face with big eyes
3 U+1F604 ? grinning face with smiling eyes
P.S. Another one warn is also welcome ?
Thanks.
--- Golden/Linux-amd64 1.2.18 2022-01-15 02:13 MSK (master)
* Origin: ��६���� �� � �ᯥ��, � � 業�����, ����� �� ���� (2:5030/1081.102)

http://pics.rsh.ru/img/Screens1096_ndpkn07s.jpg
And ok in HotDodEd too. ;)
--
'Tommi

https://brorabbit.g0x.ru/pic/image_2022-01-20_14-05-07.png


*** [Netmail-to-Telegram address: 474405162@2:460/256]

... Tag, you are IT!
--- tg BBS v0.7.1
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

Hi All...

Isn't it just a matter of leaving the message content alone (unmodified) and using @chrs utf-8 instead of @chrs cp866?

Ciao!
/|ug (https://t.me/aabolins)

--- Want fido for iOS/MacOS/Android/Win/Linux? Info=https://shrtco.de/tpJ9yV
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

Glad to see you, August!

Isn't it just a matter of leaving the message content alone (unmodified) and using @chrs utf-8 instead of @chrs cp866?

I'm afraid I don't know.

*** [Netmail-to-Telegram address: 474405162@2:460/256]

... Tag, you are IT!
--- tg BBS v0.7.1
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

Hola Vitold!

20 Jan 22 12:16, Vitold Sedyshev dijo a All:

@MSGID: 2:5030/1081.102 5DEE7200
@TZUTC: 0300
@CHRS: UTF-8 4
@TID: Golden/Linux 1.2.18 2022-01-15 02:13 MSK (master)
Hello,

How about UTF-8 message notice here

1 U+1F600 ÛßØÀ grinning face
2 U+1F603 ÛßØÁ grinning face with big eyes
3 U+1F604 󧯀 grinning face with smiling eyes

P.S. Another one warn is also welcome ÛßØÀ

Thanks.

--- Golden/Linux-amd64 1.2.18 2022-01-15 02:13 MSK (master)
* Origin: áÂÀõüøÂõÁÌ ýõ ú ÁÁ¿õÅÁ, ð ú ÆõýýþÁÂÏü, úþÂþÀËõ þý ôðõ (2:5030/1081.102) SEEN-BY: 50/109 221/1 6 360 280/5555 301/1 335/364 341/66 460/58 463/68 SEEN-BY: 467/888 4500/1 5000/111 5001/100 5005/49 5019/40 5020/846 848 1042
SEEN-BY: 5020/2047 2140 4441 12000 5030/1081 5054/8 5058/104 5060/900 5064/56
SEEN-BY: 5080/102 5083/444
@PATH: 5030/1081 5020/4441 1042 221/6

It does not look very good for me

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20180707 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)

Hello, Angel Ripoll.
On 21/1/22 11:00 you wrote:

It does not look very good for me

GoldEd+ has a limited UTF-8 support that cannot currently include that kind of symbols.

Check the same message with HotdogEd, looks ok.

Carlos
--- Hotdoged/2.13.5/Android
* Origin: Costa Blanca, Spain (2:341/234.12)

How about UTF-8 message notice here

1 U+1F600 😀 grinning face
2 U+1F603 😃 grinning face with big eyes
3 U+1F604 😄 grinning face with smiling eyes

P.S. Another one warn is also welcome 😀

Looks fine in WinPoint too (with monochrome icons).

Thanks.

--- Golden/Linux-amd64 1.2.18 2022-01-15 02:13 MSK (master)
* Origin: Стремитесь не к успеху, а к ценностям, которые он дает
(2:5030/1081.102)

Cyrillic text looks fine too.

Carlos

--- WinPoint 394.0
* Origin: Original *WinPoint* Origin (2:341/234.5)

Hi, Vitold!

20 ﭢ 22 12:16, Vitold Sedyshev -> All:

@MSGID: 2:5030/1081.102 5DEE7200
@TZUTC: 0300
@CHRS: UTF-8 4
@UUID: 56358748-394e-40f1-bc47-77a1ab91ec85
@TID: Golden/Linux 1.2.18 2022-01-15 02:13 MSK (master)
Hello,

How about UTF-8 message notice here

Test failed. Messages in UTF-8 should be in those echo conferences where it is allowed.

1 U+1F600 😀 grinning face
2 U+1F603 😃 grinning face with big eyes
3 U+1F604 😄 grinning face with smiling eyes

P.S. Another one warn is also welcome 😀

Thanks.

--- Golden/Linux-amd64 1.2.18 2022-01-15 02:13 MSK (master)
* Origin: Стремитесь не к успеху, а к ценностям, которые он дает (2:5030/1081.102)

This is a violation of the standard. The ORIGIN string must be no longer than 79 characters.

SEEN-BY: 50/109 221/1 6 360 280/464 5555 301/1 335/364 341/66 460/58
256
1124
SEEN-BY: 460/5858 463/68 467/888 4500/1 4600/140 5000/111 5001/100 5005/49 SEEN-BY: 5019/40 5020/846 848 1042 2047 2140 4441 12000 5030/1081 5054/8 30
SEEN-BY: 5058/104 5060/900 5064/56 5080/102 5083/444
@PATH: 5030/1081 5020/4441 1042 221/6 460/58

Have nice nights.
Stas Mishchenkov.

--- ����� ࠧ ��堩 ��� ��᫥����. ��⮬� �� ������� ⠪ � �㤥�.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, Vitold!

Hello,
How about UTF-8 message notice here
1 U+1F600 ? grinning face
2 U+1F603 ? grinning face with big eyes
3 U+1F604 ? grinning face with smiling eyes
P.S. Another one warn is also welcome ?
Thanks.

https://brorabbit.g0x.ru/pic/61ec023f.jpg


Have a nice carrot!
Brother Rabbit.

... A good companion not only listens attentively, but pours the drink on time --- Use "%Tearline text" to customize tearline.
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

Hi, John!

20 ﭢ 22 17:59, John Dovey -> Tommi Koivula:

On 20.1.2022 11.16, Vitold Sedyshev wrote:

Hello,

How about UTF-8 message notice here

1 U+1F600 ? grinning face
2 U+1F603 ? grinning face with big eyes
3 U+1F604 ? grinning face with smiling eyes

P.S. Another one warn is also welcome ?

Looks fine in Thunderbird.

Thanks.

--- Golden/Linux-amd64 1.2.18 2022-01-15 02:13 MSK (master)
* Origin: ��६���� �� � �ᯥ��, � � 業�����, ����� �� ����

(2:5030/1081.102) 'Tommi

This is a violation of the standard. The ORIGIN string must be no longer than 79 characters.

Displays perfectly in Telegram

Thank you. I'm trying to make it good. ;)

Have nice nights.
Stas Mishchenkov.

--- ���騭� ॢ����, ��⮬� �� �����, �� �� ᯮᮡ�� ���騭�.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, Tommi!

20 ﭢ 22 17:42, Tommi Koivula -> John Dovey:

Displays perfectly in Telegram

But not anymore, you replied with "@CHRS: cp866 2" :(

Yes. That's the way it should be.

Have nice nights.
Stas Mishchenkov.

--- �� �⪫��뢠�� �� ����� - ������ �� ��� 㦥 ᥣ����.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, August!

20 ﭢ 22 22:05, August Abolins -> All:

utf-8 it works nicely in the fido->telegram direction, but not back.

That's the way it should be. This will only work well in echo conferences that explicitly allow or recommend the use of UTF-8. In other echo conferences, we are required to maintain backward compatibility with 8-bit char software.

Have nice nights.
Stas Mishchenkov.

--- �� �� �� ����, ���騭 � ��ᥭ, ⠪ �yp���� � y�p��!
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, Tommi!

Hello, Vitold Sedyshev.
On 20/01/2022 12.16 you wrote:

Hello,
How about UTF-8 message notice here
1 U+1F600 ? grinning face
2 U+1F603 ? grinning face with big eyes
3 U+1F604 ? grinning face with smiling eyes
P.S. Another one warn is also welcome ?
Thanks.
--- Golden/Linux-amd64 1.2.18 2022-01-15 02:13 MSK (master)
* Origin: ��६���� �� � �ᯥ��, � � 業�����, ����� �� ���� (2:5030/1081.102)

http://pics.rsh.ru/img/Screens1096_ndpkn07s.jpg
And ok in HotDodEd too. ;)
--
'Tommi

I wouldn't say it's all good. ;)
https://brorabbit.g0x.ru/pic/61ec042b.jpg


Have a nice carrot!
Brother Rabbit.

... A good companion not only listens attentively, but pours the drink on time --- Use "%Tearline text" to customize tearline.
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

Hello Stas,

On Saturday January 22 2022 16:22, you wrote to August Abolins:

That's the way it should be. This will only work well in echo
conferences that explicitly allow or recommend the use of UTF-8. In
other echo conferences, we are required to maintain backward
compatibility with 8-bit char software.

As decreed by who?

I would say it is the other way around. UTF-8 is allowed wherever it is not explicitly forbidden.

FYI: UTF-8 /is/ backward compatible with 8-bit char software. Contrary to UTF-16 or UTF-32. That is why we can use UTF-8 in Fidonet en we can not use UTF-16 and UTF-32.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: ZC1 certified techno-dick (2:280/5555)

Hi, Stas!

On Sat, 22 Jan 2022 16:03:40 +0300 Stas Mishchenkov writes:

@MSGID: 2:5030/1081.102 5DEE7200
@TZUTC: 0300
@CHRS: UTF-8 4
@UUID: 56358748-394e-40f1-bc47-77a1ab91ec85
@TID: Golden/Linux 1.2.18 2022-01-15 02:13 MSK (master)
Hello,

How about UTF-8 message notice here

Test failed. Messages in UTF-8 should be in those echo conferences where it is allowed.

And why it's not allowed here with the proper CHRS?

--- Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
* Origin: Somewhere in the North (2:4500/1.59)

Hi Stas...

Hi, August!
20 ﭢ 22 22:05, August Abolins -> All:

utf-8 it works nicely in the fido->telegram direction, but not back.

That's the way it should be. This will only work well in echo conferences that explicitly allow or recommend the use of UTF-8. In other echo conferences, we are required to maintain backward compatibility with 8-bit char software.
Have nice nights.
Stas Mishchenkov.

Good point! But it *is* doable, right? I believe we at least have the UTF-8 echo for that (testing) purpose? It seems more and more echos are open to accepting and processing @CHRS UTF-8 messages.

Ciao!
/|ug (https://t.me/aabolins)

--- Want fido for iOS/MacOS/Android/Win/Linux? Info=https://shrtco.de/tpJ9yV
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

On 22.01.2022 15:38, Zhenja Kaliuta wrote:

Test failed. Messages in UTF-8 should be in those echo conferences where it is allowed.

And why it's not allowed here with the proper CHRS?

It is.

In this echo everything is allowed. :)

'Tommi

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)

On 22.01.2022 15:15, Stas Mishchenkov wrote:

Hi, Tommi!

20 янв 22 17:42, Tommi Koivula -> John Dovey:

>> Displays perfectly in Telegram

TK> But not anymore, you replied with "@CHRS: cp866 2" :(

Yes. That's the way it should be.

I'd prefer UPPERCASE CP866.

'Tommi

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)

On 22.01.2022 15:18, Brother Rabbit wrote:

Hi, Tommi!

TK> Hello, Vitold Sedyshev.
TK> On 20/01/2022 12.16 you wrote:
VS>> Hello,
VS>> How about UTF-8 message notice here
VS>> 1 U+1F600 ? grinning face
VS>> 2 U+1F603 ? grinning face with big eyes
VS>> 3 U+1F604 ? grinning face with smiling eyes
VS>> P.S. Another one warn is also welcome ?
VS>> Thanks.
VS>> --- Golden/Linux-amd64 1.2.18 2022-01-15 02:13 MSK (master)
VS>> * Origin: Стремитесь не к успеху, а к ценностям, которые он дает (2:5030/1081.102)
TK> http://pics.rsh.ru/img/Screens1096_ndpkn07s.jpg
TK> And ok in HotDodEd too. ;)
TK> --
TK> 'Tommi

I wouldn't say it's all good. ;)
https://brorabbit.g0x.ru/pic/61ec042b.jpg

In GoldED it is crap for sure. :)

'Tommi

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)

Glad to see you, All!

Porno Memes? Where do I sign up? ?

*** [Netmail-to-Telegram address: 474405162@2:460/256]

... Tag, you are IT!
--- tg BBS v0.7.1
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

*** �⢥� �� ᮮ�饭�� �� _Carbon.Mail (Carbon.Mail).

Hi, Zhenja!

22 ﭢ 22 15:38, Zhenja Kaliuta -> Stas Mishchenkov:

How about UTF-8 message notice here

Test failed. Messages in UTF-8 should be in those echo conferences where
it is allowed.

And why it's not allowed here with the proper CHRS?

Okay. Let's go from the other side. Maybe I really just don't know something. Is there a way to force e.g. GoldEd to correctly display messages in UTF-8?

Have nice nights.
Stas Mishchenkov.

--- ���, �� �� ����, ��室���� �� ���⭮� ��஭� ����.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, Stas!

On Sun, 23 Jan 2022 19:13:30 +0300 Stas Mishchenkov writes:

How about UTF-8 message notice here

Test failed. Messages in UTF-8 should be in those echo conferences where
it is allowed.

And why it's not allowed here with the proper CHRS?

Okay. Let's go from the other side. Maybe I really just don't know something. Is there a way to force e.g. GoldEd to correctly display messages in UTF-8?

Why GoldEd's problems should be others' problems?

And yes, I bet it displays perfectly us-ascii part of UTF-8.

I would rather ask why you push CP866 to the areas where cyrillic is unlikely expected?

PS: I can see UTF-8 and even iconv mentioned in the sources.
--- Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
* Origin: Somewhere in the North (2:4500/1.59)

23 Jan 2022 19:13, you wrote to Zhenja Kaliuta:

Is there a way to force e.g. GoldEd to correctly display
messages in UTF-8?

Yes, at least for most accented and umlauted characters, n with tilde, c with cedilla and other necessary for languages based on the latin alphabet.

ÁÉÍÓÚ áéíóú
ÀÈÌÒÙ àèìòù
ÄËÏÖÜ äëïöü
ÂÊÎÔÛ âêîôû
ñÑ çÇ ¿

(The only one that cannot be translated when writing in Spanish is the opening exclamation mark.)

See Michiel's article "Training Golded to play UTF-8 Part 2", FidoNews 37:18 (4 May 2020)

It's about CP850 <-> UTF-8 translation, but it is possible for LATIN-1 <-> UTF-8 too.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Costa Blanca, Spain (2:341/234)

Hello Carlos,

On Sunday January 23 2022 19:27, you wrote to Stas Mishchenkov:

See Michiel's article "Training Golded to play UTF-8 Part 2", FidoNews 37:18 (4 May 2020)

http://www.vlist.eu/downloads/fidonews/myarticles/goldutf1.art http://www.vlist.eu/downloads/fidonews/myarticles/goldutf2.art


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: ZC1 certified techno-dick (2:280/5555)

23 Jan 2022 19:35, you wrote to me:

See Michiel's article "Training Golded to play UTF-8 Part 2",
FidoNews
37:18 (4 May 2020)

http://www.vlist.eu/downloads/fidonews/myarticles/goldutf1.art http://www.vlist.eu/downloads/fidonews/myarticles/goldutf2.art

I suggest that you specify, in every article in your site, which FN issue was published on (or at least the date)

BTW, I think you didn't post these two useful articles to the GOLDED and UTF-8 echos, did you?

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Costa Blanca, Spain (2:341/234)

Hello Carlos,

On Sunday January 23 2022 20:07, you wrote to me:

http://www.vlist.eu/downloads/fidonews/myarticles/goldutf1.art
http://www.vlist.eu/downloads/fidonews/myarticles/goldutf2.art

I suggest that you specify, in every article in your site, which FN
issue was published on (or at least the date)

I will consider that for the next time.

BTW, I think you didn't post these two useful articles to the GOLDED
and UTF-8 echos, did you?

I didn't.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: ZC1 certified techno-dick (2:280/5555)

Hi, John!

22 ﭢ 22 22:22, John Dovey -> All:

Porno Memes? Where do I sign up? ?

https://t.me/Sexxxx_memes_Videos1_slivy ;)

Have nice nights.
Stas Mishchenkov.

--- ��� ����� �㬠���, ⥬ ����� � ⥡� �������諥������.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

*** �⢥� �� ᮮ�饭�� �� _Carbon.Mail (Carbon.Mail).

Hi, Tommi!

22 ﭢ 22 19:09, Tommi Koivula -> Stas Mishchenkov:

TK> But not anymore, you replied with "@CHRS: cp866 2" :(

Yes. That's the way it should be.

I'd prefer UPPERCASE CP866.

Yes. It's right.

Have nice nights.
Stas Mishchenkov.

--- �� 堫�� �� ⮫쪮 ���� ᫠���, �� � ᢨ���� ���⭠, 堫�쭠 � ���ୠ.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hello Tommi!

*** Saturday 22.01.22 at 19:09, Tommi Koivula wrote to Stas Mishchenkov:

Displays perfectly in Telegram

TK> But not anymore, you replied with "@CHRS: cp866 2" :(

Yes. That's the way it should be.

I'd prefer UPPERCASE CP866.

Yeah, so would I because although WinPoint supports CP866, it reports
cp866 as an unsupported charset.

Regards,
Martin

--- OpenXP 5.0.51
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)