switching to any other than English keyboard layout is not handled correctly anymore on the prompt at minimum

[Ariel Burbaickij]

>It sounds like your program wants UTF-8, but your
>keyboard is putting out latin1.

OK, I did the following: I went to cmd.exe and changed Active code page
from 437 (latin1 ?) to 65001 (UTF-8 ?) but there were no changes in the
behaviour in Cygwin terminal. In cmd.exe itself it handles Russian and
German itself just fine also with 437 code page. For BabelMap -- I do not
see how it can be useful for regular input of non-English string and not
just one single character here and there. And again -- it is not something
that was present from day zero or somewhere close in Cygwin, it worked just
fine on my old laptop, I migrated to a new one and this is what I see for
the first time.

Best Regards
Ariel Burbaickij

On Tue, Jan 26, 2021 at 12:17 AM L A Walsh <cygwin@tlinx.org> wrote:

> On 2021/01/25 14:20, Ariel Burbaickij via Cygwin wrote:
> >  and this is what I get upon attempt to submit
> > little sweet ö:
> >  $(__fzf_cd__)Ignoring redcarpet-3.4.0 because its extensions are not
> > built. ...
> >         1: from /usr/bin/fzf:929:in `get_input'
> > /usr/bin/fzf:929:in `ord': invalid byte sequence in UTF-8 (ArgumentError)
> > $
> > and I mean what I say, pressing ö immediately leads to it, no tricks, no
> > custom builds, no debugs enabled,  no nothing.
> >
> ---
>     Remember in my first post, I said that the codes you included were
> not valid UTF-8.  It sounds like your program wants UTF-8, but your
> keyboard is putting out latin1.
>
> Did you download that program I mentioned?  In there you can select
> the 'o' with diaeresis then copy/paste it into your program.
>
> The character you are inserting into your program isn't encoded in
> UTF-8, so I'm pretty sure that your keyboard isn't producing
> UTF-8 encoding.
>
> You mention that it does work after you restart your terminal.
>
> Setting in locale don't take effect in the current terminal, but in
> future ones that you start.  So it is a good idea to restart your terminal
> after you change locale.
>
> I assume the error you are showing is from a window that wasn't restarted
> after your locale was changed?
>
>
>