I hope it is correct in slrn.

������𦧨���

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

11 Apr 24 14:08:00 Gleb Hlebov (2:221/6) wrote:

==== begin of the message ====
@MSGID: 2:221/6.0 6617c490
@PID: SmapiNNTPd/Linux/IPv6 kco 20240401
@NOTE: slrn/1.0.3 (Linux).
@BBSID: KCO
@RFC-Content-Type: text/plain; format=fixed
@RFC-Content-Transfer-Encoding: 8bit
@CHRS: CP866 2
@TZUTC: 0300
@TID: hpt/lnx 1.9 2024-02-05

I hope it is correct in slrn.

������𦧨���

-+-
+ Origin: news://news.fidonet.fi (2:221/6.0)
SEEN+BY: 153/757 154/10 218/840 221/1 6 360 280/5555 301/1 335/364 341/66 234 SEEN+BY: 460/58 5020/1042
@PATH: 221/6
==== end of the message ====

---
* Origin: RBB Test Robot @ FIDOTEST (2:221/6.0)

11/04/2024 13:08, Gleb Hlebov -> All:

I hope it is correct in slrn.

АБВГДЕЁжзиклм
Looks good.

Carlos

--- Mozilla Thunderbird
* Origin: cyberiada-NNTP (2:341/234.99)

11/04/2024 13:08, Gleb Hlebov -> All:

I hope it is correct in slrn.

АБВГДЕЁжзиклм

Looks good from my UTF-8 reader.

(Sorry for my previous post, it seems I wrote my reply inside the quote marks...)

Carlos

--- Mozilla Thunderbird
* Origin: cyberiada-NNTP (2:341/234.99)

On 2024-04-11, Carlos Navarro <99@234.341.2> wrote:

I hope it is correct in slrn.
������𦧨���

Looks good from my UTF-8 reader.
(Sorry for my previous post, it seems I wrote my reply inside the quote marks...)

Sure... The reply looks good as well. :-)

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

Hello Gleb,

On Thu, Apr 11 2024 11:08:00 -0500, you wrote:

I hope it is correct in slrn.

АБВГДЕЁжзиклм

Looks good from this angle (tin), as well as Thunderbird. ;)

Regards,
Nick

... Take my advice, I don't use it anyway.
---
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hello Gleb,

On Thu, Apr 11 2024 12:48:26 -0500, you wrote:

Sure... The reply looks good as well. :-)

So, tin or slrn? Which do you like better? :)

Regards,
Nick

... Take my advice, I don't use it anyway.
---
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On Fri, 12 Apr 2024 00:44:06, Nicholas Boel <0@10.154.1> wrote in <fidotest>:

Sure... The reply looks good as well. :-)

So, tin or slrn? Which do you like better? :)

Well... I'm sticking with tin at the moment. All in all, from what I've
seen so far it behaves quite stable (slrn did freeze a couple of times
on re-connecting or opening a newsgroup) and it has a more convenient
"on the fly" settings menu, and last but not least, it's even capable of FTN-style quoting.


--
... Jenkinson's Law: It won't work.

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

On Fri, 12 Apr 2024 17:40:06 +0300, you wrote:

Well... I'm sticking with tin at the moment. All in all, from what I've seen so far it behaves quite stable (slrn did freeze a couple of times
on re-connecting or opening a newsgroup) and it has a more convenient
"on the fly" settings menu, and last but not least, it's even capable of FTN-style quoting.

I wonder if your slrn freezing a couple times is because it is such an old version?

And I did notice tin is able to quote with initials. I may have to test that while disabling smartquote in smapinntpd to see if it does it better. :)

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla Thunderbird
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hello Gleb,

On Fri, Apr 12 2024 09:40:06 -0500, you wrote:

Well... I'm sticking with tin at the moment. All in all, from what I've seen so far it behaves quite stable (slrn did freeze a couple of times
on re-connecting or opening a newsgroup) and it has a more convenient
"on the fly" settings menu, and last but not least, it's even capable of FTN-style quoting.

Quoting with initials seems to work ok, with 'smartquote=off' and 'showto=off'. :)

Regards,
Nick

... Take my advice, I don't use it anyway.
--- tin/2.6.3-20231224 ("Banff") (Linux/6.8.4-arch1-1 (x86_64))
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On Sat, 13 Apr 2024 02:53:36, Nicholas Boel <0@10.154.1> wrote:

Well... I'm sticking with tin at the moment. All in all, from what I've
seen so far it behaves quite stable (slrn did freeze a couple of times
on re-connecting or opening a newsgroup) and it has a more convenient
"on the fly" settings menu, and last but not least, it's even capable of
FTN-style quoting.

I wonder if your slrn freezing a couple times is because it is such an
old version?

Yep, it seems the authors stopped updating it in 2016. The official
site says 1.0.3 from 2016 is still the most recent build.

And I did notice tin is able to quote with initials. I may have to test that while disabling smartquote in smapinntpd to see if it does it better. :)

What's even better that it can show multi-level quotes in colors unlike many FTN readers that I've seen so far (e.g. GoldED can only display as many as
2 levels).


--
... You will always have one disk envelope too few. Or too many.

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

Hello Gleb Hlebov!

What's even better that it can show multi-level quotes in
colors unlike many FTN readers that I've seen so far (e.g.
GoldED can only display as many as 2 levels).

OpenXP offers colourization of multi-level quotes *and* for
different quote prefixes.

Eg.

AA >
AA >>
GB >
GB >>

..would all be different colours. Very customizable.


--
../|ug

--- OpenXP 5.0.58
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)

Hello Gleb,

On Tue, 16 Apr 2024 15:35:50 +0300, you wrote:

Yep, it seems the authors stopped updating it in 2016. The official
site says 1.0.3 from 2016 is still the most recent build.

To be honest, I can't find your version anywhere. The official slrn website says the last "release" version was 0.9.9p1.

Either way, I went with the dev version from git://git.jedsoft.org/git/slrn.git, which is believe is 1.0.4-pre-9 or something similar.

What's even better that it can show multi-level quotes in colors unlike many FTN readers that I've seen so far (e.g. GoldED can only display as > many as 2 levels).

I'm not much of a fan of colored text, but slrn is able to do that as well, I believe up to 4 or 5 levels. Then again, I don't quote much more than two levels unless I'm testing anyway. :)

I still prefer tin, though. You can look back on some real old documentation as well as their mailing lists, and see some Fidonet related topics, or posts by people from Fidonet, even. So there was definitely some FTN related functionality added into tin, which is pretty neat to see.

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla Thunderbird
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hello August,

On Tue, 16 Apr 2024 11:07:00 -0400, you wrote:

OpenXP offers colourization of multi-level quotes *and* for
different quote prefixes.

..would all be different colours. Very customizable.

I wasn't able to resize the window, and on a 32" monitor, the terminal looked like an oversized icon. Any way to get around that?

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla Thunderbird
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hello Nicholas Boel!

OpenXP offers colourization of multi-level quotes *and*

[...]

I wasn't able to resize the window, and on a 32" monitor,
the terminal looked like an oversized icon. Any way to get
around that?

Huh? Just right-click on the shortcut or the .exe and select
Properties. Then adjust the font and screen size to meet your
requirements.


--
../|ug

--- OpenXP 5.0.58
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)

Hello August,

On 16 Apr 24 20:15 you wrote:

I wasn't able to resize the window, and on a 32" monitor,
the terminal looked like an oversized icon. Any way to get
around that?

Huh? Just right-click on the shortcut or the .exe and select
Properties. Then adjust the font and screen size to meet your requirements.

I think I'm getting some things figured out. Still a lot of RTFM to do
though.

Regards,
Nick

.. Take my advice, I don't use it anyway.
--- OpenXP/5.0.58 (Win32)
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hello August,

On 16 Apr 24 21:21 you wrote:

I wasn't able to resize the window, and on a 32" monitor,
the terminal looked like an oversized icon. Any way to get
around that?

Huh? Just right-click on the shortcut or the .exe and select
Properties. Then adjust the font and screen size to meet your requirements.

By the way, I didn't see anything about fonts and screen sizes in properties, but I did find the way to adjust the screen size by lines and columns in OpenXP itself (which is kind of limited, but I found one I could use).

Otherwise, it's not too bad so far as I slowly figure everything out and make minor adjustments.

Regards,
Nick

.. Take my advice, I don't use it anyway.
--- OpenXP/5.0.58 (Win32)
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hi Nicholas...

Hello August,
On 16 Apr 24 21:21 you wrote:

Huh? Just right-click on the shortcut or the .exe and select
Properties. Then adjust the font and screen size to meet your
requirements.

By the way, I didn't see anything about fonts and screen sizes in properties, but I did find the way to adjust the screen size by lines and columns in OpenXP itself (which is kind of limited, but I found one I could use).
Otherwise, it's not too bad so far as I slowly figure everything out and make minor adjustments.
Regards,
Nick
.. Take my advice, I don't use it anyway.

If you right-click on the open console header you should get see an option for properties. Are you running the windows version? ..or the Linux version?

--
/|ug
https://t.me/aabolins

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

Hello Aug,

On Wed, 17 Apr 2024 11:08:26 +0300, you wrote:

If you right-click on the open console header you should get see an
option for properties. Are you running the windows version? ..or the
Linux version?

I was testing the Windows version, and yes.. I found that out after the fact. You had originally told me to right click the .exe or the openxp icon, which didn't have anything regarding those settings. No worries, though. I eventually found it.

Looks like while reading UTF-8 seems to work, quoting and posting it doesn't seem possible, though.

Also, all messages in the reader view gets wrapped at 80 characters, so setting your screen size bigger than that doesn't really do much except give you more blank space. :(

It definitely has a lot of features - as well as multiple ways to get your fidonet messages, though.

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla Thunderbird
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hello Nicholas Boel!

Looks like while reading UTF-8 seems to work, quoting and
posting it doesn't seem possible, though.

Correct. For one thing, UTF-8 is limited to the Windows
charsets supplied.

UTF-8 is supported on the inbound and outbound in nntp mode.
But only in the inbound in Fido mode.

Also, all messages in the reader view gets wrapped at 80
characters, so setting your screen size bigger than that
doesn't really do much except give you more blank space.
:(

Not necessarily so. Look in Config/Options/Message Reader:

�� Internal message reader options �����������Ŀ
� �
� [x] Full screen �
� [x] Display clock �
� [x] Line break in column 80 �
� [x] Show reference arrows �
� [x] Fixed message header display �
� �
� [ ] Convert German ISO Umlauts �
� [x] Use UTF-8 �
� [x] *Highlight* words by colour �
� [x] Multi-coloured quotes �
� �
� [ ] Mouse scroll bar �
� [x] AutoScrolling �
� �
� [ ] Exit message reader with <Return> �
� �
� Viewer for URLs H:\ProgramFiles\Palemoon\ � ������������������������������������������������

And also look in Config/Options/Editor:

�� Editor setup ��������������Ŀ
� �
� Right margin 63 �
� �
� End of line marker �  �
� �
� [x] Auto indent �
� [x] Persistent Blocks �
� [x] Quote-Reflow �
� �
� [x] Enable Ctrl-X/C/V �
� �
��������������������������������

It definitely has a lot of features - as well as multiple
ways to get your fidonet messages, though.

It's very versatile. It's an email/nntp/fido client all in one.

You can even define an external editor if you want.


--
../|ug

--- OpenXP 5.0.58
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)

Hello August,

On Wed, 17 Apr 2024 23:38:00 -0400, you wrote:

Looks like while reading UTF-8 seems to work, quoting and
posting it doesn't seem possible, though.

Correct. For one thing, UTF-8 is limited to the Windows
charsets supplied.

Windows 11 supports utf-8 wherever it can for most things, as far as I can tell. This seems to be the only program I'm having issues with.

I've also tried 'chcp 65001 >null && openxp.exe' from the command prompt, as well as enabling 'Beta: Use Unicode UTF-8 for worldwide language support' in Settings > Languages and Region > Administrative language settings > Change system locale. No matter what, the openxp window's properties' current code page is set to 437, and can not be changed. I wonder if this is forced in the Windows version?

Unless there is another way, I don't know it.

UTF-8 is supported on the inbound and outbound in nntp mode.
But only in the inbound in Fido mode.

I'm currently tested in nntp mode only. I can read the messages fine, but when I hit CTRL-Q the utf-8 text is quoted as all question marks - even when passed to an external editor that supports utf-8 (notepad), and Config > External > Editor has 'Editor Charset' set to utf-8.

Definitely confused on that one.

Also, all messages in the reader view gets wrapped at 80
characters, so setting your screen size bigger than that
doesn't really do much except give you more blank space.
:(

Not necessarily so. Look in Config/Options/Message Reader:

[x] Line break in column 80

[x] Use UTF-8

I have the top one unchecked, and the bottom one checked.

Right margin 63

I have this set to 74 I believe (to allow for quoted initials), however you can't set it to anything lower than 60 or higher than 77 anyways, it seems (I had tried 0 to see if it would just send text to the edge of the window).

There is also a setting in Config > Options > Miscellaneous of 'Line Break' which is set to 79. According to F1 (Help), that only seems to be for quoted lines and where it is to reflow those lines when they are quoted.

It definitely has a lot of features - as well as multiple
ways to get your fidonet messages, though.

It's very versatile. It's an email/nntp/fido client all in one.

Yep, I can definitely agree there.

You can even define an external editor if you want.

After dealing with the default key combinations to delete lines and whatnot, that was one of the first things I did. ;)

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla Thunderbird
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hello Nicholas Boel!

Windows 11 supports utf-8 wherever it can for most things, as far as I
can tell. This seems to be the only program I'm having issues with.

I've also tried 'chcp 65001 >null && openxp.exe' from the command prompt, as well as enabling 'Beta: Use Unicode UTF-8 for worldwide language support' in Settings > Languages and Region > Administrative language settings > Change system locale. No matter what, the openxp window's properties' current code page is set to 437, and can not be changed. I wonder if this is forced in the Windows version?

Correct. Codepage 437 seems to be the norm.

However, the bottom line seems to be the font used for the
terminal. I use TT Lucinda Console. The charset in there
simply does not support the myriad of utf-8 things.

I'm currently tested in nntp mode only. I can read the messages fine, but when I hit CTRL-Q the utf-8 text is quoted as all question marks - even when passed to an external editor that supports utf-8 (notepad), and Config > External > Editor has 'Editor Charset' set to utf-8.

Definitely confused on that one.

Again.. I do believe it's based on the limitations of the font
selected for the terminal.

Right margin 63

I have this set to 74 I believe (to allow for quoted initials), however you can't set it to anything lower than 60 or higher than 77 anyways, it seems (I had tried 0 to see if it would just send text to the edge of the window).

I never really explored the limits like that. I just tweeked
things until it looked right in the terminal.

BTW, if an incoming message arrives without <CR><LF>s, then the
message text *will* spread out to the edges.

There is also a setting in Config > Options > Miscellaneous of 'Line Break' which is set to 79. According to F1 (Help), that only seems to be for quoted lines and where it is to reflow those lines when they are quoted.

Yes.. I was going to point out the context-sensitive F1 (Help).

--
../|ug

--- OpenXP 5.0.58
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)

Hello August,

On Thu, 18 Apr 2024 11:45:00 -0400, you wrote:

wonder if this is forced in the Windows version?

Correct. Codepage 437 seems to be the norm.

Then writing in UTF-8 would be impossible, if cp437 is the norm.

However, the bottom line seems to be the font used for the
terminal. I use TT Lucinda Console. The charset in there
simply does not support the myriad of utf-8 things.

I happen to be using Consolas. Doesn't matter, reading it works fine, as soon as you try posting or quoting it, it doesn't.

Again.. I do believe it's based on the limitations of the font
selected for the terminal.

Doubtful. If the limitations of the font was the problem, I wouldn't be able to read it properly, either.

BTW, if an incoming message arrives without <CR><LF>s, then the
message text *will* spread out to the edges.

I'm using a format=flowed supported newsreader right now. All of my text goes to the right edge of the window, and when I resize the window the text rewraps.

This doesn't happen in OpenXP as of yet. Same exact message, no CR/LFs at all. It always wraps before 80 columns. The only time it goes further is if there is no spaces in the line (for example, a long link).

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla Thunderbird
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hello Nicholas Boel!

Correct. Codepage 437 seems to be the norm.

Then writing in UTF-8 would be impossible, if cp437 is the norm.

Well.. the code for OpenXP is open-source. If you know Pascal,
go for it! :D

However, the bottom line seems to be the font used for the
terminal. I use TT Lucinda Console. The charset in there
simply does not support the myriad of utf-8 things.

I happen to be using Consolas. Doesn't matter, reading it works fine, as soon as you try posting or quoting it, it doesn't.

It stays UTF-8 going out when replying to UTF-8 messages that
had arrived via nntp. It just not work that way with FTN
messages.

Again.. I do believe it's based on the limitations of the font
selected for the terminal.

Doubtful. If the limitations of the font was the problem, I wouldn't be able to read it properly, either.

Well.. maybe OpenXP's UTF-8 support is a minimal subset. For
true unadulterated UTF-8 reading and replying, I use Sylpheed
for specific echoes.

BTW, if an incoming message arrives without <CR><LF>s, then the
message text *will* spread out to the edges.

I'm using a format=flowed supported newsreader right now. All of my text goes to the right edge of the window, and when I resize the window the text rewraps.

My config is: Windows setting: terminal screen width = 100,
height = 41, font = 20pt Lucinda Console ..and OpenXP is: Config/Display/Lines:

�� Screen resolution ���������Ŀ
� �
� Lines 41 �
� Columns 100 �
� �
��������������������������������


I have plenty of examples that render full width in my current
configuration:

https://ibb.co/y0pypJk

Even yours..

https://ibb.co/bdxGz5t

This doesn't happen in OpenXP as of yet. Same exact message, no CR/LFs at all. It always wraps before 80 columns. The only time it goes further is if there is no spaces in the line (for example, a long link).

See above.. your last message was full width.


--
../|ug

--- OpenXP 5.0.58
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)

Hello Nicholas Boel!

I'm using a format=flowed supported newsreader right now.
All of my text goes to the right edge of the window, and
when I resize the window the text rewraps.

This doesn't happen in OpenXP as of yet. Same exact
message, no CR/LFs at all. It always wraps before 80
columns. The only time it goes further is if there is no
spaces in the line (for example, a long link).

Ah.. correct.. there is no free-flow option in OpenXP's editor.
There just seems to be a hard max and min range to choose from.

Again... maybe someone can address the issue looking at the
source code?

Personally, I like shorter width lines. This one is going out
set to a max of 63 chars. Meanwhile *some* kind of limit is
necessary for quoted text otherwise there wouldn't be much room
for adding the QQ>> QQ> etc pre-text.

--
../|ug

--- OpenXP 5.0.58
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)

Hello August,

On Fri, 19 Apr 2024 00:32:00 -0400, you wrote:

Well.. the code for OpenXP is open-source. If you know Pascal,
go for it! :D

No, it's ok.

It stays UTF-8 going out when replying to UTF-8 messages that
had arrived via nntp. It just not work that way with FTN
messages.

Oh, you mean it uses a UTF-8 CHRS kludge? Or do you mean the UTF-8 text is unchanged when you reply to it, even though it displays all question marks for the text?

Well.. maybe OpenXP's UTF-8 support is a minimal subset. For
true unadulterated UTF-8 reading and replying, I use Sylpheed
for specific echoes.

I have a few newsreaders here that I've been tinkering with also. ;)

I have plenty of examples that render full width in my current configuration:

https://ibb.co/y0pypJk

Even yours..

https://ibb.co/bdxGz5t

Are you using the Linux version? I only ask because your tearline doesn't have anything to do with 'Win', or 'Win32', or 'Windows' like mine did.

I wonder if I set this up on Linux with the exact same settings if things might be a bit different.

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla Thunderbird
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hello August,

On Fri, 19 Apr 2024 00:56:00 -0400, you wrote:

Hello Nicholas Boel!

I'm using a format=flowed supported newsreader right now.
All of my text goes to the right edge of the window, and
when I resize the window the text rewraps.

This doesn't happen in OpenXP as of yet. Same exact
message, no CR/LFs at all. It always wraps before 80
columns. The only time it goes further is if there is no
spaces in the line (for example, a long link).

Ah.. correct.. there is no free-flow option in OpenXP's editor.
There just seems to be a hard max and min range to choose from.

Yet somehow you're bypassing that min and max if you are able to see a full screen width >80 characters?

Personally, I like shorter width lines. This one is going out
set to a max of 63 chars. Meanwhile *some* kind of limit is
necessary for quoted text otherwise there wouldn't be much room
for adding the QQ>> QQ> etc pre-text.

Yes, agreed. Some kind of limit is necessary for *quoted* text, but I don't think it is necessary for unquoted text when that text usually gets reflowed when quoted anyways. ;)

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla Thunderbird
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hello Nicholas!

Ah.. correct.. there is no free-flow option in OpenXP's
editor. There just seems to be a hard max and min range
to choose from.

Yet somehow you're bypassing that min and max if you are
able to see a full screen width >80 characters?

No.. there is no width limit in the "viewer". The limits
pertain to the "editor".

As soon as I would commence a reply to any full-width/free-flow
message using the internal editor, the limits configured in
OpenXP will take effect.

Personally, I like shorter width lines. This one is
going out set to a max of 63 chars. Meanwhile *some*
kind of limit is necessary for quoted text otherwise
there wouldn't be much room for adding the QQ>> QQ> etc
pre-text.

Yes, agreed. Some kind of limit is necessary for *quoted*
text, but I don't think it is necessary for unquoted text
when that text usually gets reflowed when quoted anyways.
;)

I like OpenXP's manual reflow feature. It helps to keep
paragraphs neat and even for the end of each line. But it
would be nice to have the option to mark a paragraph and have
it "free-flow" going out. Instead, OpenXP always adds a <CR>
at the end of each line set to the width that you specify up to
the max allowed.

--
../|ug

--- OpenXP 5.0.58
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)

Hello Nicholas!

It stays UTF-8 going out when replying to UTF-8 messages
that had arrived via nntp. It just not work that way
with FTN messages.

Oh, you mean it uses a UTF-8 CHRS kludge? Or do you mean the UTF-8 text
is unchanged when you reply to it, even though it displays all question marks for the text?

(BTW.. I purposely did not reflow your quote above. However, it
should be automatically limited to 79 chars including the
indent and your quote initials.)

Good question. I would have to run some tests to remind myself
what it does. But I seem to recall reading somewhere that if an
original nntp message arrives with utf-8, it will go out with
the same char-type: utf-8. The chars in the nntp message
should not change in the editor if the original arrived as utf-
8.

However, OpenXP does not render all utf-8 chars readable.

Link up with the UTF-8 (ftn) echo and see how OpenXP handles
the content there. I did a variety of UTF-8 tests there in
January 2020.

For the heck of it, here is the multi-language "Happy New Year"
table. Let's see what OpenXP does with it here:

� Arabic: ??? ????? ?????
� Argentine: Feliz A�o Nuevo
� Armenian: ????????? ??? ????
� Basque: Urte Berri On!
� Bengali: ??? ???? ???
� Bohemian: Vesele Vanoce
� Brazilian: Feliz Ano Novo
� Bulgarian: ??????? ???? ??????
� Catalan: Feli� any nou!
� Cantonese: ????
� Croatian: Sretan Bozic
� Czech: Stastny Novy Rok
� Danish: Godt Nyt�r
� Dutch: Gelukkig Nieuwjaar!
� English: Happy New Year
� Espa�ol:� Pr�spero A�o Nuevo
� Esperanto: Gajan Kristnaskon
� Estonian: Head uut aastat
� Finnish: Onnellista Uutta Vuotta
� Flemish: Gelukkig nieuw jaar
� French: Bonne Ann�e!
� Frisian:� Seine yn it Nije Jier!
� Gaelic: Shona Nua bliana
� Galician: Ano Novo
� German:� Gl�ckliches Neues Jahr!
� Greek: �?�???��??? �? ??? ?�??
� Hebrew: ??? ???? ???????
� Hindi: Shub Naya Baras
� Hungarian: Boldog Uj �vet
� Icelandic: Hamingjusamur Nytt Ar
� Indonesian: Selamat tahun baru
� Italian: Felice Anno Nuovo
� Japanese: ???????????????
� Latin: Annum Nuovo!
� Nederlands: Gelukkig nieuwjaar
� Norwegian: Godt Nytt�r
� Polish: Szczesliwego nowego roku
� Portuguese: Feliz Ano Novo
� Rumanian: Anul Nou Fericit
� Russian: ? ????? ?????
� Spanish: Pr�spero A�o Nuevo
� Swahili: Mwaka Mpya�
� Swedish: Gott Nytt �r
� Turkish: Kutlu Olsun
� Ukrainian: ? ????? ?????
� Zulu: Jabulela unyaka omusha

Even yours..
https://ibb.co/bdxGz5t

Are you using the Linux version? I only ask because your
tearline doesn't have anything to do with 'Win', or
'Win32', or 'Windows' like mine did.

My messages should have the MAILER-ID kludge. It's Win(32).

I wonder if I set this up on Linux with the exact same
settings if things might be a bit different.

Matching the terminal window size with Linux to the one in
OpenXP would be a good start. Atleast you will then see any
free-flow messages full width.


--
../|ug

--- OpenXP 5.0.58
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)

Hello August,

On Fri, 19 Apr 2024 02:02:00 -0400, you wrote:

(BTW.. I purposely did not reflow your quote above. However, it
should be automatically limited to 79 chars including the
indent and your quote initials.)

It was within the limits.

Good question. I would have to run some tests to remind myself
what it does. But I seem to recall reading somewhere that if an
original nntp message arrives with utf-8, it will go out with
the same char-type: utf-8. The chars in the nntp message
should not change in the editor if the original arrived as utf-
8.

The message I'm replying to had a CHRS: CP437 kludge. So it looks like it is indeed forced. :(

However, OpenXP does not render all utf-8 chars readable.

It seems it renders only what it can translate to CP437?

Russian: ? ????? ?????
Spanish: Próspero Año Nuevo

It looks like what could be preserved in CP437 was passed along, and anything above and beyond that ended up with question marks.

So far I've had success with reading that entire list the best with Thunderbird, but have come close to that (maybe one or two in that list that weren't readable - which could just be the console font I'm using) with slrn, tin, and even Golded on Linux, as well as Claws Mail, Sylpheed, and a couple other random newsreaders I've deleted already on Windows.

My messages should have the MAILER-ID kludge. It's Win(32).

Ah yes, I see you have a PID kludge that states it's Win32, whereas mine was in the tearline. Probably just a config setting that makes the difference. I had just noticed your tearline was different than mine.

Matching the terminal window size with Linux to the one in
OpenXP would be a good start. Atleast you will then see any
free-flow messages full width.

I think if CP437 is forced somewhere along the line, it won't matter whether it's on Linux or Windows.

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla Thunderbird
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On 2024-04-16, Nicholas Boel <0@10.154.1> wrote:

Yep, it seems the authors stopped updating it in 2016. The official
site says 1.0.3 from 2016 is still the most recent build.

To be honest, I can't find your version anywhere. The official slrn
website says the last "release" version was 0.9.9p1.

I think I just somehow googled it and it offered me https://slrn.info,
titled "Home of the slrn newsreader". Although it's complicated... There is also an abandoned page at sourceforge (last updated 2013) and there are
some slrn forks on github.com, among which there seem to be the
"official" jedsoft page which lists version pre1.0.4-6. Anyway, too much
of a mess for me. :-)


--
... Jenkinson's Law: It won't work.

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

On Tue, 16 Apr 2024 11:07:00, August Abolins <21@757.153.1> wrote:

What's even better that it can show multi-level quotes in
colors unlike many FTN readers that I've seen so far (e.g.
GoldED can only display as many as 2 levels).

OpenXP offers colourization of multi-level quotes *and* for
different quote prefixes.

I was trying to set up OpenXp the other day without too much delving
into the manual but that seems impossible. It appears I will have to do
it step-by-step while reading the manual and applying one setting at a
time. Maybe it has something to do with the German way of writing
programs.
:-)

--
"God, please save me from your followers!" -- Bumper Sticker

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

Hello Gleb!

[...] Maybe it has something to do with the German way of
writing programs. :-)

I followed the user-produced manual step-by-step. It was
extremely helpful.

--
../|ug

--- OpenXP 5.0.58
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)

Hello Gleb,

On Fri, 19 Apr 2024 12:32:42 +0300, you wrote:

I think I just somehow googled it and it offered me https://slrn.info, titled "Home of the slrn newsreader". Although it's complicated... There is
also an abandoned page at sourceforge (last updated 2013) and there are some slrn forks on github.com, among which there seem to be the
"official" jedsoft page which lists version pre1.0.4-6. Anyway, too much of a mess for me. :-)

Agreed. I believe I'm using pre1.0.4-9 here, but it's all good. Tin seems to do just as much, if not more - especially when it comes to FTN related things.

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla Thunderbird
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)