[COMMIT] Make charset symbols equivalent to charsets in specifier matchspecs

[Aidan Kehoe]

 Ar an naoiú lá de mí na Samhain, scríobh Aidan Kehoe: 

 >  > So, now `specifier-matching-instance' MATCHSPEC `car' must be
 >  > `(get-charset 'jit-ucs-charset-0)', and this does make difference with
 >  > just `'jit-ucs-charset-0'?  If so, please document.
 > 
 > I’m sorry, you’re right here; at the moment the car of MATCHSPEC must be a
 > charset object, not a symbol. I didn’t change that intentionally; it is
 > needlessly confusing and I intend changing it back. 

This puts that change in place. 

APPROVE COMMIT

NOTE: This patch has been committed.

src/ChangeLog addition:

2006-11-09  Aidan Kehoe  <kehoea at parhasard.net>

	* specifier.c (specifier_instance_from_inst_list):
	Accept symbols as well as charset objects as the cons of a
	font-related specifier matchspec. Thank you Ilya. 
	

XEmacs Trunk source patch:
Diff command:   cvs -q diff -u
Files affected: src/specifier.c
===================================================================
RCS

Index: src/specifier.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/specifier.c,v
retrieving revision 1.46
diff -u -r1.46 specifier.c
--- src/specifier.c	2006/11/06 19:35:45	1.46
+++ src/specifier.c	2006/11/09 12:35:38
@@ -2829,7 +2829,7 @@
     specbind (Qinhibit_quit, Qt);
 
 #ifdef MULE
-  if (CONSP(matchspec) && (CHARSETP(XCAR(matchspec))))
+  if (CONSP(matchspec) && (CHARSETP(Ffind_charset(XCAR(matchspec)))))
     {
       charset = Ffind_charset(XCAR(matchspec));
 

-- 
Santa Maradona, priez pour moi!