CVS update by viteno packages ...
19 years, 8 months
CVS Monitor
CVS Monitor
User: viteno
Date: 05/04/03 13:59:06
Modified: packages ChangeLog
Log:
Package release
Revision Changes Path
1.514 +4 -0 XEmacs/packages/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/ChangeLog,v
retrieving revision 1.513
retrieving revision 1.514
diff -u -p -r1.513 -r1.514
--- ChangeLog 2005/03/26 19:13:17 1.513
+++ ChangeLog 2005/04/03 11:59:05 1.514
＠＠ -1,3 +1,7 ＠＠
+2005-04-03 Norbert Koch <viteno(a)xemacs.org>
+
+ * Packages released: gnus mail-lib.
+
2005-03-26 Norbert Koch <viteno(a)xemacs.org>
* Packages released: texinfo text-modes.
- 1 participants
- 0 comments
CVS update by aidan packages/mule-packages/latin-euro-standards, latin-euro-standards.texi ...
19 years, 8 months
CVS Monitor
CVS Monitor
User: aidan
Date: 05/04/03 12:58:10
Modified: packages/mule-packages/latin-euro-standards ChangeLog
latin-euro-standards.texi
Log:
Minor copy-editing of the latin-euro-standards docs.
Revision Changes Path
1.6 +5 -0 XEmacs/packages/mule-packages/latin-euro-standards/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/mule-packages/latin-euro-standards/ChangeLog,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -p -r1.5 -r1.6
--- ChangeLog 2005/02/16 22:24:51 1.5
+++ ChangeLog 2005/04/03 10:58:09 1.6
＠＠ -1,3 +1,8 ＠＠
+2005-04-03 Aidan Kehoe <kehoea(a)parhasard.net>
+
+ * latin-euro-standards.texi: Minor copy-editing; make the dir
+ entry shorter, to give a better chance of it being seen.
+
2005-02-16 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 1.03 released.
1.2 +3 -4 XEmacs/packages/mule-packages/latin-euro-standards/latin-euro-standards.texi
Index: latin-euro-standards.texi
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/mule-packages/latin-euro-standards/latin-euro-standards.texi,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -p -r1.1 -r1.2
--- latin-euro-standards.texi 2005/02/14 23:37:55 1.1
+++ latin-euro-standards.texi 2005/04/03 10:58:09 1.2
＠＠ -5,7 +5,7 ＠＠
＠c ** #### something uses these headers, find out how and explain here
＠c %**start of header
＠setfilename latin-euro-standards.info
-＠settitle Recent ISO 8859 character encoding standards
+＠settitle Recent ISO 8859 character encoding standards.
＠setchapternewpage odd
＠c %**end of header
＠＠ -18,8 +18,7 ＠＠
＠footnotestyle end
＠direntry
-* latin-euro-standards:: Make recent ISO 8859 character
-encodings available to XEmacs.
+* latin-euro-standards:: Recent ISO 8859 encodings in XEmacs.
＠end direntry
＠c ** It is often convenient to use a macro for names which have unusual
＠＠ -216,7 +215,7 ＠＠ together with the associated Mule charac
It is intended to be used by the Mule-UCS (＠pxref{Top,,, mule-ucs,
Mule-UCS User Manual}) and Latin Unity (＠pxref{Top,,, latin-unity,
Latin Unity for Emacsen}) packages, and was, indeed, refactored out
-from the former.
+from the latter.
Each file provides a language environment named, e.g. ＠samp{Latin-7}, a
coding system named ＠samp{iso-8859-13} (etc.) and a Mule character set
- 1 participants
- 0 comments
CVS update by youngs packages/xemacs-packages/gnus/lisp ...
19 years, 8 months
CVS Monitor
CVS Monitor
User: youngs
Date: 05/04/03 03:50:16
Modified: packages/xemacs-packages/gnus/lisp gnus-sum.el
Log:
2005-04-03 Steve Youngs <steve(a)sxemacs.org>
* lisp/gnus-sum.el (gnus-summary-make-menu-bar): Fix an
"unrecognised menu descriptor" error.
From Katsumi Yamaoka <yamaoka(a)jpl.org>
Revision Changes Path
1.91 +6 -0 XEmacs/packages/xemacs-packages/gnus/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/gnus/ChangeLog,v
retrieving revision 1.90
retrieving revision 1.91
diff -u -p -r1.90 -r1.91
--- ChangeLog 2005/03/20 11:32:00 1.90
+++ ChangeLog 2005/04/03 01:50:08 1.91
＠＠ -1,3 +1,9 ＠＠
+2005-04-03 Steve Youngs <steve(a)sxemacs.org>
+
+ * lisp/gnus-sum.el (gnus-summary-make-menu-bar): Fix an
+ "unrecognised menu descriptor" error.
+ From Katsumi Yamaoka <yamaoka(a)jpl.org>
+
2005-03-20 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 1.84 released.
1.7 +1 -1 XEmacs/packages/xemacs-packages/gnus/lisp/gnus-sum.el
Index: gnus-sum.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/gnus/lisp/gnus-sum.el,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -p -r1.6 -r1.7
--- gnus-sum.el 2005/03/13 00:23:28 1.6
+++ gnus-sum.el 2005/04/03 01:50:15 1.7
＠＠ -2250,7 +2250,7 ＠＠ gnus-summary-show-article-from-menu-as-c
,＠(if (featurep 'xemacs) '(t)
'(:help "Generate and print a PostScript image"))])
("Copy, move,... (Backend)"
- ,＠(if (featurep 'xemacs) '(t)
+ ,＠(if (featurep 'xemacs) nil
'(:help "Copying, moving, expiring articles..."))
["Respool article..." gnus-summary-respool-article t]
["Move article..." gnus-summary-move-article
- 1 participants
- 0 comments
CVS update by viteno xemacs ...
19 years, 8 months
CVS Monitor
CVS Monitor
User: viteno
Date: 05/04/02 23:51:16
Modified: xemacs version.sh
Log:
Update xemacs_extra_name.
Revision Changes Path
1.1116 +1 -1 XEmacs/xemacs/version.sh
Index: version.sh
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/version.sh,v
retrieving revision 1.1115
retrieving revision 1.1116
diff -u -p -r1.1115 -r1.1116
--- version.sh 2005/04/01 21:51:18 1.1115
+++ version.sh 2005/04/02 21:51:16 1.1116
＠＠ -8,5 +8,5 ＠＠ emacs_kit_version=
infodock_major_version=4
infodock_minor_version=0
infodock_build_version=8
-xemacs_extra_name="(+CVS-20050401)"
+xemacs_extra_name="(+CVS-20050402)"
xemacs_release_date="2005-02-18"
- 1 participants
- 0 comments
CVS update by aidan packages/xemacs-packages/mail-lib ...
19 years, 8 months
CVS Monitor
CVS Monitor
User: aidan
Date: 05/04/02 00:28:07
Modified: packages/xemacs-packages/mail-lib ChangeLog sendmail.el
Log:
Write FCCs to Unix mailboxes using the binary coding system, not the default
buffer-file-coding-system.
Revision Changes Path
1.158 +8 -0 XEmacs/packages/xemacs-packages/mail-lib/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/mail-lib/ChangeLog,v
retrieving revision 1.157
retrieving revision 1.158
diff -u -p -r1.157 -r1.158
--- ChangeLog 2005/03/09 20:23:00 1.157
+++ ChangeLog 2005/04/01 22:28:06 1.158
＠＠ -1,3 +1,11 ＠＠
+2005-04-02 Aidan Kehoe <kehoea(a)parhasard.net>
+
+ * sendmail.el (mail-do-fcc): Write the Unix mail file using the
+ binary coding system, as is appropriate for a file where non-ASCII
+ characters are encoded using separate MIME character sets for
+ every message, and thus no other single Mule coding system is
+ appropriate.
+
2005-03-09 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 1.72 released.
1.19 +10 -2 XEmacs/packages/xemacs-packages/mail-lib/sendmail.el
Index: sendmail.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/mail-lib/sendmail.el,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -p -r1.18 -r1.19
--- sendmail.el 2004/11/08 02:50:32 1.18
+++ sendmail.el 2005/04/01 22:28:07 1.19
＠＠ -1225,8 +1225,16 ＠＠ external program defined by `sendmail-pr
(insert "\n\C-_")
(write-region (point-min) (point-max) (car fcc-list) t)
(erase-buffer)))
- (write-region
- (1+ (point-min)) (point-max) (car fcc-list) t)))
+ ;; MIME processing should have eliminated any characters
+ ;; outside the range 0-255; if MIME processing hasn't been
+ ;; done, there's no reasonable expectation that the data will
+ ;; be preserved in a Unix mailbox, so we just write tildes for
+ ;; those chars. We set the coding system for write to 'binary
+ ;; to prevent any double-encoding that may occur if
+ ;; buffer-file-coding-system has been initialised to a
+ ;; non-binary-compatible coding system like, say, UTF-8.
+ (let ((coding-system-for-write 'binary))
+ (write-region (1+ (point-min)) (point-max) (car fcc-list) t))))
(and buffer (not dont-write-the-file)
(with-current-buffer buffer
(set-visited-file-modtime))))
- 1 participants
- 0 comments
CVS update by viteno xemacs ...
19 years, 8 months
CVS Monitor
CVS Monitor
User: viteno
Date: 05/04/01 23:51:19
Modified: xemacs version.sh
Log:
Update xemacs_extra_name.
Revision Changes Path
1.1115 +1 -1 XEmacs/xemacs/version.sh
Index: version.sh
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/version.sh,v
retrieving revision 1.1114
retrieving revision 1.1115
diff -u -p -r1.1114 -r1.1115
--- version.sh 2005/03/31 21:51:36 1.1114
+++ version.sh 2005/04/01 21:51:18 1.1115
＠＠ -8,5 +8,5 ＠＠ emacs_kit_version=
infodock_major_version=4
infodock_minor_version=0
infodock_build_version=8
-xemacs_extra_name="(+CVS-20050331)"
+xemacs_extra_name="(+CVS-20050401)"
xemacs_release_date="2005-02-18"
- 1 participants
- 0 comments
CVS update by aidan xemacs/src ...
19 years, 8 months
CVS Monitor
CVS Monitor
User: aidan
Date: 05/04/01 02:27:26
Branch: xemacs/src sjt-xft
Modified: xemacs/src ChangeLog objects-x.c
Log:
Make the debug messages mule clean, treat FC font names as UTF-8.
Revision Changes Path
1.758.2.22 +14 -0 XEmacs/xemacs/src/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/ChangeLog,v
retrieving revision 1.758.2.21
retrieving revision 1.758.2.22
diff -u -p -r1.758.2.21 -r1.758.2.22
--- ChangeLog 2005/03/15 05:23:36 1.758.2.21
+++ ChangeLog 2005/04/01 00:27:18 1.758.2.22
＠＠ -1,3 +1,17 ＠＠
+2005-04-01 Aidan Kehoe <kehoea(a)parhasard.net>
+
+ * objects-x.c:
+ * objects-x.c (x_initialize_font_instance):
+ * objects-x.c (CHECKING_LANG):
+ General mule-sanity cleanup for the debug messages, to eliminate
+ the issue Giacomo Boffi saw in
+ 16970.44359.621213.994821(a)boffi95.stru.polimi.it.
+
+ * objects-x.c (x_find_charset_font):
+ Font names are also treated as UTF-8; relatedly, when passing back
+ the font's full name, the character coverage bitmap isn't included
+ any more, because that would make it an invalid UTF-8 string.
+
2005-03-11 Stephen J. Turnbull <stephen(a)xemacs.org>
* XEmacs 21.5.20 "cilantro" is released.
1.26.2.16 +94 -27 XEmacs/xemacs/src/objects-x.c
Index: objects-x.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/objects-x.c,v
retrieving revision 1.26.2.15
retrieving revision 1.26.2.16
diff -u -p -r1.26.2.15 -r1.26.2.16
--- objects-x.c 2005/03/15 05:24:35 1.26.2.15
+++ objects-x.c 2005/04/01 00:27:22 1.26.2.16
＠＠ -221,7 +221,8 ＠＠ x_initialize_font_instance (Lisp_Font_In
#ifdef USE_XFT
if (debug_xft > 2)
- stderr_out ("attempting to initialize font spec %s\n", extname);
+ stderr_out ("attempting to initialize font spec %s\n",
+ XSTRING_DATA(f->name));
/* #### serialize (optimize) these later... */
/* #### This function really needs to go away.
The problem is that the fontconfig/Xft functions work much too hard
＠＠ -288,13 +289,15 ＠＠ x_initialize_font_instance (Lisp_Font_In
stderr_out ("initialized metrics ascent %d descent %d width %d height %d\n",
f->ascent, f->descent, f->width, f->height);
if (debug_xft > 2) /* we also output on initialization of any font below */
- stderr_out ("initialized Xft font %s\n", extname);
+ stderr_out ("initialized Xft font %s\n",
+ XSTRING_DATA(f->name));
fs = NULL; /* we don' need no steenkin' X font */
}
else
{
if (debug_xft > 0)
- stderr_out ("couldn't initialize Xft font %s\n", extname);
+ stderr_out ("couldn't initialize Xft font %s\n",
+ XSTRING_DATA(f->name));
}
#endif
＠＠ -369,11 +372,11 ＠＠ x_initialize_font_instance (Lisp_Font_In
/* #### check for weirdness */
if (n * f->height < d * f->width)
stderr_out ("font %s: width:height is %d:%d, larger than %d:%d\n",
- extname, f->width, f->height, n, d);
+ XSTRING_DATA(f->name), f->width, f->height, n, d);
if (f->height <= 0 || f->width <= 0)
stderr_out ("bogus dimensions of font %s: width = %d, height = %d\n",
- extname, f->width, f->height);
- stderr_out ("initialized font %s\n", extname);
+ XSTRING_DATA(f->name), f->width, f->height);
+ stderr_out ("initialized font %s\n", XSTRING_DATA(f->name));
}
#else
#undef rf
＠＠ -1114,12 +1117,19 ＠＠ mule_to_fc_charset (Lisp_Object cs)
/* print an Xft pattern to stderr
LEVEL is the debug level (to compare to debug_xft)
FORMAT is a newline-terminated printf format with one %s for the pattern
- PATTERN is an FcPattern *. */
-#define PRINT_XFT_PATTERN(level,format,pattern) \
- do { \
- FcChar8 *name = FcNameUnparse (pattern); \
- DEBUG_XFT1 (level, format, name); \
- free (name); \
+ PATTERN is an FcPattern *.
+
+ Qbinary is the only coding system that's appropriate; while the font
+ names themselves are UTF-8, the coverage information is a pure bitmap
+ that won't be in any valid multibyte encoding. */
+#define PRINT_XFT_PATTERN(level,format,pattern) \
+ do { \
+ DECLARE_EISTRING (eistrpxft_name); \
+ FcChar8 *name = FcNameUnparse (pattern); \
+ \
+ eicpy_ext(eistrpxft_name, name, Qbinary); \
+ DEBUG_XFT1 (level, format, eidata(eistrpxft_name)); \
+ free (name); \
} while (0)
/* print a progress message
＠＠ -1127,8 +1137,13 ＠＠ mule_to_fc_charset (Lisp_Object cs)
FORMAT is a newline-terminated printf format with two %s for font and lang
FONT is the Xft font
LANG is the language being checked for support. */
-#define CHECKING_LANG(level,font,lang) \
- DEBUG_XFT2 (level, "checking if %s handles %s\n", font, lang)
+#define CHECKING_LANG(level,font,lang) \
+ do { \
+ DECLARE_EISTRING (eistrcl_name); \
+ eicpy_ext(eistrcl_name, font, Qbinary); \
+ DEBUG_XFT2 (level, "checking if %s handles %s\n", \
+ eidata(eistrcl_name), lang); \
+ } while (0)
struct charset_reporter {
Lisp_Object *charset;
＠＠ -1195,10 +1210,14 ＠＠ x_find_charset_font (Lisp_Object device,
return Qnil;
#ifdef USE_XFT
- /* #### does Xft permit/require a different encoding? */
- LISP_STRING_TO_EXTERNAL (font, patternext, Qx_font_name_encoding);
+ /* Fontconfig converts all strings to UTF-8 before passing them back to
+ callers--see FcFreeTypeQuery, in fcfreetype.c, for where it does
+ this. I don't believe this is documented. */
+
+ LISP_STRING_TO_EXTERNAL (font, patternext, Qutf_8);
- DEBUG_XFT1 (1, "confirming charset for font instance %s\n", patternext);
+ DEBUG_XFT1 (1, "confirming charset for font instance %s\n",
+ XSTRING_DATA(font));
/* #### this looks like a fair amount of work, but the basic design
has never been rethought, and it should be
＠＠ -1216,9 +1235,11 ＠＠ x_find_charset_font (Lisp_Object device,
FcChar8 *lang = "en";
FcCharSet *fccs = NULL;
FcChar8 *shortname;
+ DECLARE_EISTRING (eistr_shortname);
fcc = FcConfigGetCurrent ();
patternxft = FcNameParse (patternext); /* #### needs freeing */
+
PRINT_XFT_PATTERN (1,"FcNameParse'ed name is %s\n",patternxft);
/* #### Next two return FcBool, but what does the return mean? */
/* The order is correct according the fontconfig docs. */
＠＠ -1236,6 +1257,8 ＠＠ x_find_charset_font (Lisp_Object device,
FcPatternDel (p, FC_LANG);
shortname = FcNameUnparse (p); /* #### needs freeing */
FcPatternDestroy (p);
+ eicpy_ext(eistr_shortname, shortname, Qutf_8);
+ free(shortname);
}
/* The language approach may better in the long run, but we can't use
＠＠ -1254,7 +1277,7 ＠＠ x_find_charset_font (Lisp_Object device,
if (cr->rfc3066)
{
- CHECKING_LANG (0, shortname, cr->language);
+ CHECKING_LANG (0, eidata(eistr_shortname), cr->language);
lang = cr->rfc3066;
}
else if (cr->charset)
＠＠ -1275,6 +1298,8 ＠＠ x_find_charset_font (Lisp_Object device,
/* default to "en" */
}
+ ASSERT_ASCTEXT_ASCII(lang);
+
if (fccs)
{
/* check for character set coverage */
＠＠ -1285,6 +1310,7 ＠＠ x_find_charset_font (Lisp_Object device,
if (r == FcResultTypeMismatch)
{
+ free(patternxft);
/* Urk! Fall back and punt to core font. */
DEBUG_XFT0 (0, "Unexpected type return in charset value\n");
/* uncomment this to not try core font */
＠＠ -1292,14 +1318,43 ＠＠ x_find_charset_font (Lisp_Object device,
}
else if (r == FcResultMatch && FcCharSetIsSubset (fccs, v))
{
- DEBUG_XFT2 (0, "Xft font %s supports %s\n", shortname, lang);
- /* #### would it be better to return shortname? */
- retval = (build_string (FcNameUnparse (patternxft)));
+ FcChar8 *unparsed = FcNameUnparse(patternxft);
+ DECLARE_EISTRING (eistr_longname);
+
+#ifdef __GNUC__
+#warning "Perhaps the shortname won't identify the font uniquely--see comment."
+#endif
+ /* If we're going to use the full font name above, we can't
+ treat it as any other encoding than Qbinary, because the
+ bitmap of character coverage which forms part of it gives
+ no guarantees that it'll encode as anything else.
+
+ However, fontconfig returns foundry and name information in
+ UTF-8. So the shortname above will better correspond to the
+ font's name, because we can treat it as valid UTF-8, and
+ non-ASCII characters will show up properly as Mule
+ characters.
+
+ So, in the interest of getting XEmacs' font selection
+ almost coherent, I'm passing back the short name, as a Lisp
+ String, decoded from UTF-8. */
+
+ eicpy_ext(eistr_longname, unparsed, Qbinary);
+ free(unparsed);
+ free(patternxft);
+
+ DEBUG_XFT2 (0, "Xft font, full specification, %s supports %s\n",
+ eidata(eistr_longname), lang);
+ DEBUG_XFT1 (0, "We're returning the short specification %s, in the interest of preserving the encoding of the font's name. ",
+ eidata(eistr_shortname));
+
+ retval = eimake_string(eistr_shortname);
}
else
{
+ free(patternxft);
DEBUG_XFT2 (0, "Xft font %s doesn't support %s\n",
- shortname, lang);
+ eidata(eistr_shortname), lang);
/* comment this to try the core font */
retval = Qnil;
}
＠＠ -1316,10 +1371,13 ＠＠ x_find_charset_font (Lisp_Object device,
FcValue v;
/* the main event */
FcResult r = FcPatternGet (patternxft, FC_LANG, i, &v);
+ /* Not using patternxft beyond here. */
+
if (r == FcResultMatch)
{
if (v.type != FcTypeLangSet) /* excessive paranoia */
{
+ ASSERT_ASCTEXT_ASCII(FcTypeOfValueToString(v));
/* Urk! Fall back and punt to core font. */
DEBUG_XFT1 (0, "Unexpected type of lang value (%s)\n",
FcTypeOfValueToString (v));
＠＠ -1328,23 +1386,32 ＠＠ x_find_charset_font (Lisp_Object device,
}
else if (FcLangSetHasLang (v.u.l, lang) != FcLangDifferentLang)
{
- DEBUG_XFT2 (0, "Xft font %s supports %s\n", shortname, lang);
- /* #### would it be better to return shortname? */
- return (build_string (FcNameUnparse (patternxft)));
+ DEBUG_XFT2 (0, "Xft font %s supports %s\n",
+ eidata(eistr_shortname), lang);
+ free(patternxft);
+ /* #### would it be better to return shortname?
+
+ Aidan says yes. The full pattern with the bitmap
+ coverage is massively unwieldy. */
+
+ return eimake_string(eistr_shortname);
}
else
{
DEBUG_XFT2 (0, "Xft font %s doesn't support %s\n",
- shortname, lang);
+ eidata(eistr_shortname), lang);
return Qnil;
}
}
+ ASSERT_ASCTEXT_ASCII(FcResultToString(r));
DEBUG_XFT1 (0, "Unexpected result getting lang=%s\n",
FcResultToString (r));
+ free(patternxft);
}
}
- DEBUG_XFT1 (0, "shit happens, try X11 charset match for %s\n", patternext);
+ DEBUG_XFT1 (0, "shit happens, try X11 charset match for %s\n",
+ XSTRING_DATA(font));
#endif /* USE_XFT */
names = XListFonts (DEVICE_X_DISPLAY (XDEVICE (device)),
- 1 participants
- 0 comments