all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 46171@debbugs.gnu.org,
	Gordillo-Marquijano Daniel-Fabian
	<daniel-f.gordillo@inetum.world>
Subject: bug#46171: 27.1; buffer-file-coding-system
Date: Mon, 01 Feb 2021 10:22:38 +0100	[thread overview]
Message-ID: <87pn1kp2g1.fsf@gnus.org> (raw)
In-Reply-To: <83pn1nyhd2.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 29 Jan 2021 15:58:49 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> It isn't always possible to identify the UTF-8 encoding, so when the
> default of the locale is not UTF-8 (and it never is on MS-Windows),
> Emacs sometimes guesses wrong.
>
> To work around this, if you know the file is encoded in UTF-8, you can
> tell Emacs about that:
>
>   C-x RET c utf-8 RET C-x C-f <the-file> RET
>
> OTOH, if SQL files are always encoded in UTF-8 (are they?), we can add
> this knowledge to Emacs, assuming these files have some known
> file-name extension, or have some telltale string at their beginning.

SQL files can be in any coding system, so we can't really do anything
here on the Emacs side -- sometimes Emacs will guess wrong on the coding
system, and the user will have to provide some hints, as you say here.

So I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2021-02-01  9:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29 12:14 bug#46171: 27.1; buffer-file-coding-system daniel-f.gordillo--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-29 13:58 ` Eli Zaretskii
2021-01-29 19:36   ` bug#46171: [External] : " Drew Adams
2021-02-01  9:22   ` Lars Ingebrigtsen [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pn1kp2g1.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=46171@debbugs.gnu.org \
    --cc=daniel-f.gordillo@inetum.world \
    --cc=eliz@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.