From: Kenichi Handa <handa@m17n.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 3526@emacsbugs.donarmstrong.com
Subject: bug#3526: 23.0.94; `list-character-sets' display
Date: Thu, 18 Jun 2009 09:50:18 +0900 [thread overview]
Message-ID: <E1MH5pa-0006fv-Nf@etlken> (raw)
In-Reply-To: <0F745F1932EF4338B8D737D20FB2B94F@us.oracle.com> (drew.adams@oracle.com)
In article <0F745F1932EF4338B8D737D20FB2B94F@us.oracle.com>, "Drew Adams" <drew.adams@oracle.com> writes:
> > This is the one-line help in *Character Set List* buffer,
> > ------------------------------------------------------------
> > Character sets for defining another charset or obsolete now
> > ------------------------------------------------------------
> Did you mean "are" instead of "or"? If so, the English (with "are") is correct.
I mean "or". What I want to say is:
"Character sets listed below exist:
* for defining another charset, or
* for backward compatibility."
> If this is a statement about something being obsolete that was previously
> supported, then it belongs in NEWS, not here. The text here should just help
> with what is displayed - it should not try to explain why something that was
> previously explained is no longer explained.
> (If that's not when this statement means, then I don't know what it is saying.)
> > and this is the "Charsets" node of mule.texi.
> >
> > ------------------------------------------------------------
> > @node Charsets
> > @section Charsets
> > @cindex charsets
> >
> > Emacs defines most of popular character sets (e.g. ascii,
> > iso-8859-1, cp1250, big5, unicode) as @dfn{charsets} and a few of its
> > own charsets (e.g. emacs, unicode-bmp, eight-bit).
> Emacs defines most popular character sets (e.g. ascii, iso-8859-1, cp1250, big5,
> unicode), as well as a few of its own (e.g. emacs, unicode-bmp, eight-bit), as
> @dfn{charsets}.
> [Or better: End the sentence at the comma, and use a separate sentence to say
> that Emacs refers to character sets as @dfn{charsets}.]
Thank you for the correction for mule.texi. But, it's not
efficient that I hear you (and Jason's) comments in mail,
and commit changes. Could you please directly commit the
changes? Of course, I'll answer questions.
> > All supported characters
> All characters supported by Emacs
> [As opposed to all chars supported by one or more character sets.]
> > belong to one or more charsets. Usually you don't have to
> > take care of ``charset'', but knowing about it may help understanding
> > the behavior of Emacs in some cases.
> I think something like this is what you want:
> You generally do not need to pay attention to charsets as you use Emacs.
> However, it can help to know a little about them.
Yes.
> > One example is a font selection.
> One example is font selection.
> [or "One example is selecting a font"]
> > In each language environment,
> > charsets have different priorities. Emacs, at first, tries to use a
> > font that matches with charsets of higher priority.
> Emacs first tries to use a font that matches charsets of higher priority.
> [But why "first"? I don't see anything that counteracts this. So just "Emacs
> tries".]
Ok for deleting that "at first".
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2009-06-18 0:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k4yb2wbz.fsf@stupidchicken.com>
2009-06-10 20:27 ` bug#3526: 23.0.94; `list-character-sets' display Drew Adams
2009-06-11 0:52 ` Kenichi Handa
2009-06-11 14:46 ` Drew Adams
2009-06-17 1:23 ` Kenichi Handa
2009-06-17 5:05 ` Drew Adams
2009-06-17 6:42 ` Kenichi Handa
2009-06-17 14:56 ` Drew Adams
2009-06-17 15:55 ` Jason Rumney
2009-06-17 16:13 ` Drew Adams
2009-06-18 0:50 ` Kenichi Handa [this message]
2009-06-18 1:01 ` Drew Adams
2009-10-31 19:40 ` bug#3526: marked as done (23.0.94; `list-character-sets' display) Emacs bug Tracking System
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=E1MH5pa-0006fv-Nf@etlken \
--to=handa@m17n.org \
--cc=3526@emacsbugs.donarmstrong.com \
--cc=drew.adams@oracle.com \
/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.