home bbs files messages ]

Just a sample of the Echomail archive

<< oldest | < older | list | newer > | newest >> ]

 Message 2328 
 Wilfred van Velzen to Vitaliy Aksyonov 
 Re: Need volonteers to test another patc 
 09 Mar 24 21:53:51 
 
TID: FMail-lnx64 2.2.1.1
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: CP850 2
PID: GED+LNX 1.1.5-b20240306
MSGID: 2:280/464 65ed9437
REPLY: 1:104/117 65ecbeb4
Hi Vitaliy,

On 2024-03-09 12:49:34, you wrote to me:

 WvV>> Yesterday I did some experimenting with the latest golded (commit:
 WvV>> "call setlocale() before initscr() (#86)"), trying different ways to
 WvV>> start golded and different golded xlat configurations. I found 2
 WvV>> setups that work for me, so the messages with pseudo graphics in the
 WvV>> STATS area look ok:

 WvV>> My golded.cfg for both:

 WvV>> include charsets.cfg

 WvV>> XLATIMPORT CP437
 WvV>> XLATLOCALSET CP850
 WvV>> XLATEXPORT CP850

 VA> Do not use xlatexport cp850. This parameter is used to select charset
which
 VA> will be used when you write messages to message base. Unless you really
 VA> want cp850. I assume you want to have cp437 there.

My terminal uses cp850, so it's what I write my messages in. If I translate it
to cp437, it will possibly loose some characters that are not supported in
both. So I think I want it. ;-)

 WvV>> And starting golded in a local Konsole terminal "TERM=xterm" with
 WvV>> the default charset set to utf-8:

 WvV>> # sudo -u fido LANG=en_EN.CP850 luit -encoding 'CP850'
 WvV>> /usr/local/bin/golded -f

 VA> If you use luit - than having xterm in UTF-8 is correct.

 WvV>> And in the same kind of terminal but with the default charset set to
 WvV>> cp850, this one works:

 WvV>> # sudo -u fido LANG=en_US.CP850 /usr/local/bin/golded -f

 VA> This is correct commandline to if you have your terminal in cp850. Just
 VA> choose what works better for you. Probably luit and terminal in UTF-8 is
 VA> most convenient.

I'll see after I have tested with putty...

 WvV>> I will still have to test these in a putty terminal later during the
 WvV>> coming week.

 VA> Putty will work fine. Only I suggest you to change terminal type in putty
 VA> from xterm (they use if by default)

I think it's set to 'linux' in putty.

 VA> to putty or putty-256color. It's in Connection->Data section.

Ok, I'll try that.

 WvV>> And messages which have utf-8 characters, like the ones from Michiel
 WvV>> in the UTF area, don't display properly (of course). I did try
 WvV>> adding:

 WvV>> XLATCHARSET UTF-8 CP850 utf8_850.chs

 WvV>> But that didn't help. Of course only a small subset of utf-8
 WvV>> characters can be displayed with cp850...

 VA> Golded cannot read from UTF-8. There is no Unicode support. You must use
 VA> another editor or GoldEd with external editor to work with Unicode.

 VA> It may convert from one-byte charsets to UTF-8, but not vise versa.

Isn't this for incoming messages in utf-8, to show them in your local charset,
as far as possible?


Bye, Wilfred.

--- FMail-lnx64 2.2.1.1
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 15/0 18/200 90/1 103/705 105/81 106/201 124/5016 128/260
SEEN-BY: 129/305 135/225 153/757 7715 154/10 30 203/0 218/700 221/0
SEEN-BY: 226/30 227/114 229/110 112 113 206 307 317 400 426 428 470
SEEN-BY: 229/664 700 240/1120 5832 266/512 280/464 5003 5555 282/1038
SEEN-BY: 291/111 292/854 8125 301/1 310/31 320/219 322/757 341/66
SEEN-BY: 341/234 342/200 396/45 423/120 460/16 58 256 1124 5858 467/888
SEEN-BY: 633/280 712/848 770/1 5020/400 1042 5054/30
PATH: 280/464 460/58 229/426


<< oldest | < older | list | newer > | newest >> ]

(c) 1994,  bbs@darkrealms.ca