bug#3526: 23.0.94; `list-character-sets' display

["Drew Adams" <drew.adams@oracle.com>]

> 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.

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}.]

> 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.

>   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".]

> For instance, in

a

> Japanese language environment, the charset @code{japanese-jisx0208}
> has the highest priority (@xref{describe-language-environment}).
> So,

So

> Emacs tries to use a font whose @code{registry} property is
> ``JISX0208.1983-0''
> for 

whose [not for]

> characters belonging to that charset.
> 
>   Another example is a use of @code{charset} text property.  

Another example is use of the @code{charset} text property.

> When Emacs reads a file encoded in a coding
> systems 

system

> that uses escape sequences to switch charsets (e.g. iso-2022-int-1),
> the buffer text keep the information of the original charset
> by @code{charset} text property.  
> By using this information, Emacs can write the file with
> the same byte sequence as the original.

that uses escape sequences to switch charsets (e.g. iso-2022-int-1),
text property @code{charset} is attached to the buffer text, to record the
charset in which the file is encoded. Emacs uses this information to be able to
write the file again using the original byte sequence.

> @findex list-charset-chars
> @cindex characters in a certain charset
> @findex describe-character-set
>   There are two commands for obtaining information about Emacs
> charsets.  The command @kbd{M-x list-charset-chars} prompts for a
> charset name, and displays all the characters in that character set.

charset name and displays all the characters in that character set.

> The command @kbd{M-x describe-character-set} prompts for a charset
> name and displays information about that charset, including its
> internal representation within Emacs.
> 
> @findex list-character-sets
>   To display a list of all the supported charsets, 

To display a list of all supported charsets,

> type @kbd{M-x list-character-sets}. 

> The list gives the names of charsets and
> additional information to identity each charset (see ISO/IEC's this
> page <http://www.itscj.ipsj.or.jp/ISO-IR/> for the detail).  

The list shows charset names and other identifying ISO/IEC information
(see <http://www.itscj.ipsj.or.jp/ISO-IR/> for details).

> In the
> list, charsets are categorized into two; the normal charsets are
> listed first, and the supplementary charsets are listed last. 

Charsets are listed in two groups: normal and supplementary charsets.

> A
> charset in the latter category is used for defining another charset
> (as a parent or a subset), or was used only in Emacs of the older
> versions.

A @dfn{supplementary charset} is used to define another charset as its parent or
subset. 

[parent or child? ancestor or descendent? superset or subset? Not sure what's
correct here, but parent and subset are not parallel.]

Some of the charsets listed as supplementary are obsolete; they were used in
Emacs versions prior to version 23.

[Is that correct? If so, why not get rid of these here? Why show stuff that is
no longer in Emacs?]

>   To find out which charset a character in the buffer belongs to,

To find out which charset a character belongs to,

> put point before it and type @kbd{C-u C-x =}.

[But this last sentence has nothing to do with `list-character-sets' display, so
it should be moved elsewhere (e.g. earlier in the node). You might also want to
cross-ref another node that mentions `C-x =' (and vice versa).

HTH. Someone else should check that the content makes sense using the edits I
suggested. I don't want to mess up the meaning by guessing wrong.

Thx - Drew