From: torys.anderson@gmail.com (Tory S. Anderson)
To: emacs list <help-gnu-emacs@gnu.org>
Subject: Re: Displaying special characters
Date: Fri, 19 Sep 2014 17:17:03 -0400 [thread overview]
Message-ID: <87y4tfl38w.fsf@gmail.com> (raw)
In-Reply-To: <8738bnmi6v.fsf@gmail.com> (Tory S. Anderson's message of "Fri, 19 Sep 2014 17:08:56 -0400")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=shift_jis, Size: 668 bytes --]
Ah; found it. Somehow toggle-enable-multibyte-characters was switched off; I'm not sure how that happened. Curiously, it doesn't seem to work in this email buffer, though.
torys.anderson@gmail.com (Tory S. Anderson) writes:
> I wrote out notes a whiel ago and used the TeX input mode to add special/accented characters. But now when I load the file, they are all represented as code symbols:
>
> Distinguishes between fabula and sjuz†et.
>
> Is there any way to recover/display these properly?
> - Tory
>
> PS: even trying to send this message it yells at me about "unprintable characters." In case they don't come through, I see "sjuz\314\206et"
prev parent reply other threads:[~2014-09-19 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 21:08 Displaying special characters Tory S. Anderson
2014-09-19 21:17 ` Tory S. Anderson [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
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=87y4tfl38w.fsf@gmail.com \
--to=torys.anderson@gmail.com \
--cc=help-gnu-emacs@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.
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).