From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: sirciny <sirciny@gmail.com>
Cc: Help-gnu-emacs@gnu.org
Subject: Re: Encoding
Date: Tue, 11 Jun 2013 11:22:53 +0200 [thread overview]
Message-ID: <FDB5C7C6-4C88-4022-B5A3-0F795AA1B3D7@Web.DE> (raw)
In-Reply-To: <1370904464694-288388.post@n5.nabble.com>
Am 11.06.2013 um 00:47 schrieb sirciny:
> How can I get rid of this error and keep my new font (and avoid the
> problem if I change my font attributes in the future)?
There is no connection between the font you've chosen and the encoding issue. If a font is missing the glyphs for characters used in some (exotic?) encoding, then replacement characters, open boxes, are used for them.
The mode-line of a buffer contains in the left corner an indicator for the encoding used.
GNU Emacs learns from environment variables which encoding to use or to prefer, for example LANG or LC_CTYPE. Try to set these! Then you won't need to set anything in GNU Emacs.
You could check GNU Emacs' behaviour when you launch it with -q or -Q and when LANG and/or LC_CTYPE are set to a reasonable value.
--
Greetings
Pete
Upgraded, adj.:
Didn't work the first time.
next prev parent reply other threads:[~2013-06-11 9:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 22:47 Encoding sirciny
2013-06-11 9:22 ` Peter Dyballa [this message]
2013-06-12 13:11 ` Encoding sirciny
-- strict thread matches above, loose matches on Subject: below --
2011-03-13 1:01 encoding rinefez
2011-03-13 1:07 ` encoding Pascal J. Bourguignon
2011-03-13 18:59 ` encoding rinefez
2011-03-15 0:35 ` encoding rinefez
2011-03-15 0:51 ` encoding Pascal J. Bourguignon
2011-03-15 1:21 ` encoding rinefez
2009-01-08 0:35 encoding Alan
2009-01-08 4:27 ` encoding Eli Zaretskii
2004-06-21 7:41 Encoding Rob Kramer
2004-06-21 18:43 ` Encoding Kevin Rodgers
2004-06-30 16:51 ` Encoding Kai Grossjohann
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=FDB5C7C6-4C88-4022-B5A3-0F795AA1B3D7@Web.DE \
--to=peter_dyballa@web.de \
--cc=Help-gnu-emacs@gnu.org \
--cc=sirciny@gmail.com \
/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.
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).