From: Richard Stallman <rms@gnu.org>
Subject: [d.love@dl.ac.uk: bad translations in quail latin-3-prefix]
Date: Wed, 26 Jun 2002 18:39:15 -0400 [thread overview]
Message-ID: <E17NLRT-00052S-00@fencepost.gnu.org> (raw)
Can anyone comment on this change? Is it correct?
(Does anyone on this list use Latin-3?)
------- Start of forwarded message -------
To: bug-gnu-emacs@gnu.org
Subject: bad translations in quail latin-3-prefix
From: Dave Love <d.love@dl.ac.uk>
Sender: bug-gnu-emacs-admin@gnu.org
Date: 24 Jun 2002 22:12:51 +0100
- --BROMURE-COSCO-Kh-11-AGT.-AMME-ASO
Content-Type: text/plain; charset=iso-8859-3
Content-Transfer-Encoding: quoted-printable
Some of the sequences translate to invalid Latin-3 code points, and
~o->=F5 doesn't make sense. I can't tell whether there was some more
valid intent here.
- --BROMURE-COSCO-Kh-11-AGT.-AMME-ASO
Content-Type: text/x-patch; charset=iso-8859-3
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
2002-06-20 Dave Love <fx@gnu.org>
* quail/latin-pre.el ("latin-3-prefix"): Remove bogus Latin-3
characters and ~o -> =F5, ~O -> =D5.
*** latin-pre.el.~1.14.~ Mon Jul 16 21:22:24 2001
- --- latin-pre.el Thu Jun 20 21:19:32 2002
***************
*** 652,668 ****
("\"s" ?=DF)
("\"\"" ?=A8)
("\" " ?\")
- - ("~A" ?=C3)
("~C" ?=C7)
- - ("~D" ?=D0)
("~N" ?=D1)
- - ("~O" ?=D5)
- - ("~a" ?=E3)
("~c" ?=E7)
- - ("~d" ?=F0)
("~n" ?=F1)
- - ("~o" ?=F5)
- - ("~$" ?=A5)
("~S" ?=AA)
("~s" ?=BA)
("~G" ?=AB)
- --- 652,661 ----
***************
*** 682,688 ****
("/h" ?=B1)
("/i" ?=B9)
("/z" ?=BF)
- - ("/r" ?=AE)
("/." ?=FF)
("/#" ?=A3)
("/$" ?=A4)
- --- 675,680 ----
- --BROMURE-COSCO-Kh-11-AGT.-AMME-ASO--
_______________________________________________
Bug-gnu-emacs mailing list
Bug-gnu-emacs@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs
------- End of forwarded message -------
reply other threads:[~2002-06-26 22:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E17NLRT-00052S-00@fencepost.gnu.org \
--to=rms@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.