I hope it is correct in slrn.
ŠŠŠŠŠŠŠŠ¶Š·ŠøŠŗŠ»Š¼
Looks good.
I hope it is correct in slrn.
ŠŠŠŠŠŠŠŠ¶Š·ŠøŠŗŠ»Š¼
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...)
I hope it is correct in slrn.
ŠŠŠŠŠŠŠŠ¶Š·ŠøŠŗŠ»Š¼
Sure... The reply looks good as well. :-)
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.
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.
Well... I'm sticking with tin at the moment. All in all, from what I'veI wonder if your slrn freezing a couple times is because it is such an
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.
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. :)
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).
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.
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.
..would all be different colours. Very customizable.
[...]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?
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 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.
Hello August,
On 16 Apr 24 21:21 you wrote:
Huh? Just right-click on the shortcut or the .exe and selectBy 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).
Properties. Then adjust the font and screen size to meet your
requirements.
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?
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.
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:
[x] Line break in column 80
[x] Use UTF-8
Right margin 63
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.
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?
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.
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.
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.
Again.. I do believe it's based on the limitations of the font
selected for the terminal.
BTW, if an incoming message arrives without <CR><LF>s, then the
message text *will* spread out to the edges.
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).
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).
Well.. the code for OpenXP is open-source. If you know Pascal,
go for it! :D
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.
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 plenty of examples that render full width in my current configuration: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.
https://ibb.co/y0pypJk
Even yours..
https://ibb.co/bdxGz5t
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.
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.
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.
;)
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?
’ 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 Nytr
’ 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 Anne!
’ Frisian:’ Seine yn it Nije Jier!
’ Gaelic: Shona Nua bliana
’ Galician: Ano Novo
’ German:’ Glckliches 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 Nyttr
’ 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.
I wonder if I set this up on Linux with the exact same
settings if things might be a bit different.
(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.
Russian: ? ????? ?????
Spanish: PrĆ³spero AƱo Nuevo
My messages should have the MAILER-ID kludge. It's Win(32).
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.
Yep, it seems the authors stopped updating it in 2016. The officialTo be honest, I can't find your version anywhere. The official slrn
site says 1.0.3 from 2016 is still the most recent build.
website says the last "release" version was 0.9.9p1.
What's even better that it can show multi-level quotes inOpenXP offers colourization of multi-level quotes *and* for
colors unlike many FTN readers that I've seen so far (e.g.
GoldED can only display as many as 2 levels).
different quote prefixes.
[...] Maybe it has something to do with the German way of
writing programs. :-)
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. :-)
| Sysop: | Saxainden |
|---|---|
| Location: | Littleton, CO |
| Users: | 30 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 16:08:44 |
| Calls: | 359 |
| Calls today: | 1 |
| Messages: | 36,389 |