The difficulty is converting an invalid utf8 to a unicode and then converting it back to the original invalid utf8.
The display of invalid sequence depends on front-end's font engine. I hope you can bear with it. Вс, 23 апр 2017, robert therriault написал(а): > Thanks Bill, > > I thought it may be related and I also suspected that it might not be an easy > fix. > > It does result in some strange situations where a UTF-8 sequence 224 176 157 > is interpreted one way in the first row of an array and differently in the > second row. I suppose that is the nature of UTF-8 shards. It is a messy > business. > > <2 6 $ 'cఝa' > ┌──────┐ > │cఝac │ > │à°acà│ > └──────┘ > > Cheers, bob > > > On Apr 23, 2017, at 12:05 AM, bill lam <[email protected]> wrote: > > > > _3 s: 2 5 $ 'cb鲨a' > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm -- regards, ==================================================== GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 gpg --keyserver subkeys.pgp.net --armor --export 4434BAB3 ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
