unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: owner@emacsbugs.donarmstrong.com (Emacs bug Tracking System)
To: Glenn Morris <rgm@gnu.org>
Subject: bug#4255: marked as done (23.1; [PATCH] two typos in lispref/nonascii.texi)
Date: Wed, 26 Aug 2009 03:05:08 +0000	[thread overview]
Message-ID: <handler.4255.D4255.12512554261083.ackdone@emacsbugs.donarmstrong.com> (raw)
In-Reply-To: 19091.47098.944477.525259@a1i15.kph.uni-mainz.de

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

Your message dated Tue, 25 Aug 2009 22:57:04 -0400
with message-id <iw7hwrwadb.fsf@fencepost.gnu.org>
and subject line Re: bug#4255: 23.1; [PATCH] two typos in lispref/nonascii.texi
has caused the Emacs bug report #4255,
regarding 23.1; [PATCH] two typos in lispref/nonascii.texi
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
4255: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=4255
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 3007 bytes --]

From: Ulrich Mueller <ulm@gentoo.org>
To: bug-gnu-emacs@gnu.org
Subject: 23.1; [PATCH] two typos in lispref/nonascii.texi
Date: Tue, 25 Aug 2009 12:07:54 +0200
Message-ID: <19091.47098.944477.525259@a1i15.kph.uni-mainz.de>

--- emacs/doc/lispref/nonascii.texi
+++ emacs/doc/lispref/nonascii.texi
@@ -283,7 +283,7 @@
 range from 0 to 255---the values that can fit in one byte.  The valid
 character codes for multibyte representation range from 0 to 4194303
 (#x3FFFFF).  In this code space, values 0 through 127 are for
-@acronym{ASCII} charcters, and values 129 through 4194175 (#x3FFF7F)
+@acronym{ASCII} characters, and values 128 through 4194175 (#x3FFF7F)
 are for non-@acronym{ASCII} characters.  Values 0 through 1114111
 (#10FFFF) correspond to Unicode characters of the same codepoint;
 values 1114112 (#110000) through 4194175 (#x3FFF7F) represent



[-- Attachment #3: Type: message/rfc822, Size: 1488 bytes --]

From: Glenn Morris <rgm@gnu.org>
To: 4255-done@emacsbugs.donarmstrong.com
Subject: Re: bug#4255: 23.1; [PATCH] two typos in lispref/nonascii.texi
Date: Tue, 25 Aug 2009 22:57:04 -0400
Message-ID: <iw7hwrwadb.fsf@fencepost.gnu.org>


Thanks.

      reply	other threads:[~2009-08-26  3:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <iw7hwrwadb.fsf@fencepost.gnu.org>
2009-08-25 10:07 ` bug#4255: 23.1; [PATCH] two typos in lispref/nonascii.texi Ulrich Mueller
2009-08-26  3:05   ` Emacs bug Tracking System [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=handler.4255.D4255.12512554261083.ackdone@emacsbugs.donarmstrong.com \
    --to=owner@emacsbugs.donarmstrong.com \
    --cc=rgm@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).