From: Yohanan <mitonanan12@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44672@debbugs.gnu.org
Subject: bug#44672: 28.0.50; 'ç' key on BR-ABNT2 keyboard translates to strange symbols
Date: Wed, 4 Aug 2021 23:47:13 -0300 [thread overview]
Message-ID: <CAPdX1+OUEs6d1YW4g6BbSpncdEVvLQN8B9Z7ap3FBgdevm3+gQ@mail.gmail.com> (raw)
In-Reply-To: <87mtpxhg29.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]
> Have you examined the file and confirmed that it's not really encoded in
> utf-8? It sounds unlikely that it's not, because that's exactly the
result
> you'd get if that's the case.
I actually meant "open with the web browser", not on emacs. I didn't
specify it
properly so my bad here :P
> As for the other issues, it kinda sounds like your terminal is confused
> as to what input methods and language environments it's running in.
Oh. I was using `st` and after reading this I tested it in `alacritty` and
`xterm`. It works on these, so it's probably an issue with my `st`.
Since it's probably not a bug with emacs, I think we can close it here.
Thanks
for the help!
On Wed, Aug 4, 2021 at 3:36 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Yohanan <mitonanan12@gmail.com> writes:
>
> > Try out the following HTML page:
> > <meta charset="ISO-8859-1">
> > ç
> > On my machine, opening a HTML file with this code shows:
> > ç
>
> Have you examined the file and confirmed that it's not really encoded in
> utf-8? It sounds unlikely that it's not, because that's exactly the
> result you'd get if that's the case.
>
> > I also experimented with the LC_ALL environment variable, and the result
> of
> > pasting the `ç` character onto a `LANG=en_US.UTF8 LC_ALL=en_US emacs -Q
> > -nw` emacs instance is a `ç` (yay!) but followed by what seems to be a
> space
> > character:
>
> As for the other issues, it kinda sounds like your terminal is confused
> as to what input methods and language environments it's running in.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
>
[-- Attachment #2: Type: text/html, Size: 2370 bytes --]
next prev parent reply other threads:[~2021-08-05 2:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 23:58 bug#44672: 28.0.50; 'ç' key on BR-ABNT2 keyboard translates to strange symbols YohananDiamond
2020-11-16 22:23 ` Lars Ingebrigtsen
[not found] ` <CAPdX1+Pv-LF+EB1G-v59mqOOpm=15TzbEzPKe_J_n8T1aDPtPw@mail.gmail.com>
2020-11-16 22:48 ` Lars Ingebrigtsen
[not found] ` <CAPdX1+PU68Qgvd+MbLwVRR5MFJbOf_fiEvbws3eJHdhBnA7ixg@mail.gmail.com>
2020-11-18 21:41 ` Lars Ingebrigtsen
2021-07-31 12:49 ` Lars Ingebrigtsen
2021-08-03 1:44 ` Yohanan
2021-08-04 5:37 ` Lars Ingebrigtsen
2021-08-04 6:36 ` Lars Ingebrigtsen
2021-08-05 2:47 ` Yohanan [this message]
2021-08-05 11:00 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPdX1+OUEs6d1YW4g6BbSpncdEVvLQN8B9Z7ap3FBgdevm3+gQ@mail.gmail.com \
--to=mitonanan12@gmail.com \
--cc=44672@debbugs.gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).