Subj : test tearline, origin
To   : Richard Menedetter
From : Michiel van der Vlist
Date : Tue Apr 02 2019 14:16:24

Hello Richard Menedetter!

02 Apr 19 15:09:54, Richard Menedetter wrote to Michiel van der Vlist:


 RM> Indeed.
 RM> I got it working 1 minute.
 RM> It displayed the Cyrillic characters perfectly, but when I wanted to save I got this:
 RM> 2019/04/02 15:05:22 goAtEd-linux/amd64 1.0.3-151-fdf5d41d started 
 RM> panic: encoding: rune not supported by encoding.

I got that too in my first attempt to enter non-ASCII characters. It is a bit of an overreactions.

I found out it happens when you attempt to enter a character that is not supported by the character set in use. For example when you try to enter an umlauted character when CP866 is active.

I have this in my config:

  - name: UTF-8
    chrs: UTF-8 4


--- goAtEd-windows/386 1.0.3-151-fdf5d41d
 * Origin: UTF-8 Evangelist (2:280/5555)

.