|
From: | Jason Rumney |
Subject: | bug#3526: 23.0.94; `list-character-sets' display |
Date: | Wed, 17 Jun 2009 23:55:59 +0800 |
User-agent: | Thunderbird 2.0.0.21 (Windows/20090302) |
Drew Adams wrote:
Emacs tries to use a font whose @code{registry} property is ``JISX0208.1983-0''forwhose [not for]characters belonging to that charset.
I'd be more inclined to remove a `whose' than add another one to that sentence.
So Emacs tries to use a font with a @code{registry} property of ``JISX0208.1983-0'' for characters belonging to that charset.
A @dfn{supplementary charset} is used to define another charset as its parent orsubset.[parent or child? ancestor or descendent? superset or subset? Not sure what's correct here, but parent and subset are not parallel.]
I think the parent is the "another charset", and subset is the "supplementary charset". But as worded above, it isn't clear which charset "its parent or subset" is referring to anyway, so I'd reword it further:
A @dfn{supplementary charset} is used to define another charset. It does not form a complete charset on its own, so should not generally be used directly.
I think charsets like mule-unicode-0100-23ff, which existed in previous versions because of technical restrictions on the size of charsets, may be referred to by old lisp code, so we need to keep them around for compatibility.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?]
Since the described function acts on a character in a buffer, I think the original wording is correct.To find out which charset a character in the buffer belongs to,To find out which charset a character belongs to,
[Prev in Thread] | Current Thread | [Next in Thread] |