From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: patch for broken cp866 in codepage.el (21.2 and 21.2,92)
Date: Sun, 17 Nov 2002 07:47:35 +0200 (IST) [thread overview]
Message-ID: <Pine.SUN.3.91.1021117074659.16604A-100000@is> (raw)
In-Reply-To: <Pine.LNX.4.44L.0211141354020.2822-200000@arrakis.zephyrous>
On Thu, 14 Nov 2002, Ivan Zakharyaschev wrote:
> I'd like to point out the fact that the coversion table for cp866
> (defined in international/codepage.el) is broken in 21.2 and the
> prestest 21.2.92.
>
> The attched patch is supposed to fix it. I think this is a mere
> simple bugfix, and is worth being applied to the most stable branches of
> Emacs (RC, pretest, etc.)
Thanks, I installed your fixes in both branch and HEAD.
prev parent reply other threads:[~2002-11-17 5:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 11:04 patch for broken cp866 in codepage.el (21.2 and 21.2,92) Ivan Zakharyaschev
2002-11-17 5:47 ` Eli Zaretskii [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=Pine.SUN.3.91.1021117074659.16604A-100000@is \
--to=eliz@is.elta.co.il \
--cc=emacs-devel@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 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).