From: Lennart Borgman <lennart.borgman@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Teemu Likonen <tlikonen@iki.fi>, Emacs-Devel <emacs-devel@gnu.org>
Subject: Re: utf8 char display in buffer
Date: Thu, 11 Jun 2009 15:08:18 +0200 [thread overview]
Message-ID: <e01d8a50906110608r782240ads699fc97fb3b68e29@mail.gmail.com> (raw)
In-Reply-To: <e01d8a50906110607w59eadd5fo836193db7b4186d3@mail.gmail.com>
Hm, the check out date is 2009-05-29, not the date below.
On Thu, Jun 11, 2009 at 3:07 PM, Lennart
Borgman<lennart.borgman@gmail.com> wrote:
> On Thu, Jun 11, 2009 at 3:04 PM, Andreas Schwab<schwab@linux-m68k.org> wrote:
>> Lennart Borgman <lennart.borgman@gmail.com> writes:
>>
>>> Teemu mentioned this on gnu-emacs. It seems nice, but the help text
>>> that C-h l rfc1345 brings up is not that much helpful for someone who
>>> does not know this well. Could it perhaps be enhanced with some links
>>> to relevant information?
>>
>> This has been fixed in Emacs 23, where the complete translation table is
>> included.
>
> Really? This is what I get with
> GNU Emacs 23.0.94.1 (i386-mingw-nt5.1.2600) of 2009-06-10 on
> LENNART-69DE564 (patched)
>
> ------------------------------
> Input method: rfc1345 (`m' in mode line) for UTF-8
> Unicode characters input method using RFC1345 mnemonics (non-ASCII only).
> E.g. &a' -> á
>
> [back]
> ------------------------------
>
next prev parent reply other threads:[~2009-06-11 13:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.227.1244485995.2239.help-gnu-emacs@gnu.org>
[not found] ` <878wjzugdo.fsf@iki.fi>
2009-06-11 12:55 ` utf8 char display in buffer Lennart Borgman
2009-06-11 13:04 ` Andreas Schwab
2009-06-11 13:07 ` Lennart Borgman
2009-06-11 13:08 ` Lennart Borgman [this message]
2009-06-11 13:24 ` Tassilo Horn
[not found] ` <mailman.297.1244559110.2239.help-gnu-emacs@gnu.org>
[not found] ` <7I2dndeTy7sqkLLXnZ2dnUVZ_gmdnZ2d@sysmatrix.net>
[not found] ` <pc7hbyofaoq.fsf@panix2.panix.com>
[not found] ` <aJKdnVvH4ebY5a3XnZ2dnUVZ_vOdnZ2d@sysmatrix.net>
[not found] ` <mailman.522.1244818530.2239.help-gnu-emacs@gnu.org>
[not found] ` <pc7fxe5mpfh.fsf@panix2.panix.com>
[not found] ` <JOqdncHRqaVlG6_XnZ2dnUVZ_u6dnZ2d@sysmatrix.net>
[not found] ` <db6d8fe0-4cd5-4499-a8a8-466203889a83@y34g2000prb.googlegroups.com>
[not found] ` <4A32D54D.1040405@mousecar.com>
2009-06-12 22:27 ` Lennart Borgman
2009-06-12 23:38 ` ken
2009-06-13 4:11 ` Eli Zaretskii
2009-06-13 12:30 ` ken
2009-06-13 13:23 ` Eli Zaretskii
2009-06-14 20:59 ` Stefan Monnier
2009-06-13 1:36 ` Miles Bader
2009-06-13 1:43 ` Lennart Borgman
2009-06-13 5:50 ` Richard Stallman
2009-06-15 4:34 ` Miles Bader
2009-06-15 19:30 ` Richard Stallman
2009-06-16 0:30 ` James Cloos
2009-06-16 1:10 ` Miles Bader
2009-06-16 1:12 ` Miles Bader
2009-06-17 5:07 ` Richard Stallman
2009-06-16 13:53 ` Chong Yidong
2009-06-16 20:48 ` Stefan Monnier
2009-06-15 20:06 ` Chong Yidong
2009-06-15 21:57 ` Drew Adams
2009-06-16 5:30 ` Richard Stallman
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=e01d8a50906110608r782240ads699fc97fb3b68e29@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.org \
--cc=tlikonen@iki.fi \
/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).