Subj : :read !trans -b -no-ansi -s latvian -t english
To   : Maurice Kinal
From : August Abolins
Date : Tue Mar 09 2021 22:48:00

Hello Maurice!

** On Wednesday 10.03.21 - 01:54, you wrote to me:

 AA>> @CHRS: CP437 2

 MK> Hm.  That is really weird because your quote from me shows;

 MK>> ... В чужой монастырь со своим уставом не ходят.
 MK>>     Don't go to another monastery with your own rules

 MK> Which are obviously cp866.  It isn't possible for the cp437
 MK> codepage to display russian characters.

Yes.. I know that.  But it's cool to know that OpenXP doesn't  
necessarily grunge then up to the point where they can't be  
decoded after a reply using cp437.

 AA>> support russian and english chars simultaneously).

 MK> I can throw in latvian to the above and have them all in
 MK> the same msg simultaneously ... and a few more while we're
 MK> at it.

Understood. utf-8 would be the ticket for that.  But then, it  
still remains for utf-8 to be supported in OpenXP which is not  
likely to happen.

 AA>> Don't worry about the Latvian.

 MK> I wasn't worried but just being complete.  There is no good
 MK> reason latvian and others can't be supported by having the
 MK> right tools at hand. I believe we have proved that.

For Latvian, I just have to stick with TB or Telegram. It ain't  
gonna work in OpenXP unless I can get utf-8 support *and* a  
Windows console font that works with that.

 MK> As for your CHRS kludge I think it stands as further
 MK> evidence how lame the CHRS kludge actually is.  I don't
 MK> think it is a keeper.

Yes.. in your CP866 message to me and my CP437 quoted reply to  
you, that may be the case.  But atleast OpenXP did not butcher  
the "original" to the point that you couldn't read the quoted  
Russian chars back to you.  THAT is not so lame.  ;)
--
  ../|ug

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

.