Re: [Q] Handle bytes in the range 0x80-0xC0 better when dealing with ISO-IR 196.
17 years, 5 months
Aidan Kehoe
Ar an ceathrú lá is fiche de mí na Samhain, scríobh Stephen J. Turnbull:
> > I have a tentative plan to add a charset to XEmacs, 256 characters of
> > which reflect corrupt Unicode data. These 256 characters will be
> > generated by Unicode-oriented coding systems when they encounter
> > invalid data:
>
> I wish you wouldn't. Let's just get Unicode inside, and figure out
> how to signal errors in a useful way from inside a coding stream.
While I admit that Unicode inside would be better: however, given that we
can now preserve arbitrary Unicode with the current architecture without
trouble--the lack of this feature was the primary reason I wanted to move
when I proposed it--and given that building and testing on
X11-server-side-mule, X11-server-side-nomule, XFT-mule, XFT-nomule,
GTK-mule, GTK-nomule, Win32-mule, Win32-nomule before committing any change
is already a _lot_ of work, I have personally no intention of committing a
change that adds Unicode internally as a compile-time flag.
I intend to get what I have working locally, and up to date--it isn’t
now--and I will post that to -patches. But the trade off of so much more
testing versus the limited advantages to it (better behaviour when
searching, and faster redisplay on XFT and Windows, and OK, a more
understandable architecture) doesn’t seem sensible to me. If the option of
no-Mule is removed, or we removed support for GTK, then that would be
different.
> > (decode-coding-string "\x80\x80" 'utf-8)
> > => "\200\200" ;; With funky redisplay properties once display tables and
> > ;; char tables are integrated. Which, whee, is more work.
> >
> > And will be ignored by them when writing:
> >
> > (encode-coding-string (decode-coding-string "\x80\x80" 'utf-8) 'utf-8)
> > => ""
>
> Yuck. You realize that you can't do that with the autosave code,
> right?
Which is well and good, it’s desired that the autosave files reflect XEmacs’
state, not necessarily what will be written. Similarly 南 will be preserved
in auto-saves and trashed in iso-8859-2 buffers.
> And you don't want to do that if the buffer is unmodified, right?
Which is well and good, what the coding systems do will be irrelevant if the
buffer is unmodified, because they’re not invoked.
> Sounds like a hell of a lot of work to get right, and it will still be
> fragile.
Much less work than allowing coding systems to throw errors, as I understand
it.
> > This will allow applications like David Kastrup’s reconstruct-utf-8
> > sequences-from-fragmentary-TeX-error-messages to be possible, while
> > not contradicting the relevant Unicode standards. With Unicode as the
> > internal encoding, there’s no need to have a separate Mule character
> > set; we can stick their codes somewhere above the astral planes. But
> > we should maintain the same syntax code for them. Note also that, as
> > far as I can work out, these 256 codes will be sufficient for
> > representing error data for all the other Unicode-oriented
> > representations well as UTF-8.
>
> Sounds dangerous and messy to me.
Well, David’s problem is an actual problem. And the many ways in which we
fail http://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-test.txt is something
that annoys me the purist in me immensely--implementing such a thing would
address both.
--
Santa Maradona, priez pour moi!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
XEmacs Packages have been pre-released (2006-11-23-11)
17 years, 5 months
Norbert Koch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey there everyone.
I have just added the following packages to the 'Pre-Releases'
directory:
New Packages in Pre-Release:
===========================
calendar-1.30-pkg.tar.gz upstream version: none
Previously Announced Packages Still in Pre-Release:
==================================================
debug-1.18-pkg.tar.gz upstream version: none
edebug-1.22-pkg.tar.gz upstream version: none
ediff-1.65-pkg.tar.gz upstream version: 2.75
edit-utils-2.36-pkg.tar.gz upstream version: none
haskell-mode-1.10-pkg.tar.gz upstream version: 2.1
hyperbole-1.16-pkg.tar.gz upstream version: 4.18
ilisp-1.34-pkg.tar.gz upstream version: 5.12.0
latin-unity-1.19-pkg.tar.gz upstream version: 1.19
leim-1.24-pkg.tar.gz upstream version: none
locale-1.24-pkg.tar.gz upstream version: none
mail-lib-1.78-pkg.tar.gz upstream version: none
net-utils-1.49-pkg.tar.gz upstream version: N/A
ocaml-0.06-pkg.tar.gz upstream version: 3.06
os-utils-1.39-pkg.tar.gz upstream version: none
pcl-cvs-1.67-pkg.tar.gz upstream version: R-2_9_9
prog-modes-2.09-pkg.tar.gz upstream version: none
python-modes-1.08-pkg.tar.gz upstream version: none
text-modes-1.92-pkg.tar.gz upstream version: none
tramp-1.34-pkg.tar.gz upstream version: 2.0.54
vhdl-1.22-pkg.tar.gz upstream version: 3.33.12
viper-1.52-pkg.tar.gz upstream version: 3.09
w3-1.33-pkg.tar.gz upstream version: 4.0pre47
xemacs-base-2.08-pkg.tar.gz upstream version: none
xemacs-devel-1.75-pkg.tar.gz upstream version: none
Detailed Changes:
================
- ------- ChangeLog Entries from xemacs-packages/calendar/ChangeLog -------
2006-11-23 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 1.30 released.
2006-11-22 Adrian Aichner <adrian(a)xemacs.org>
* timeclock.el: Typo fixes.
* timeclock.el (timeclock-history): New.
* timeclock.el (timeclock-use-history): New.
* timeclock.el (timeclock-log): Honor timeclock-use-history.
* timeclock.el (timeclock-read-moment): Provide error on
unexpected data in timeclock-file, going unnoticed until now.
* timeclock.el (timeclock-find-discrep): Report line number of
discrepancy to ease manual fixing.
2006-11-22 Adrian Aichner <adrian(a)xemacs.org>
* timeclock.el: Keep timeclock-file buffer around, so that an
encrypted timeclock-file does not have to be opened on each
clocking operation (requiring entry of encryption key).
* timeclock.el (timeclock-get-timeclock-file-buffer): New.
* timeclock.el (timeclock-log): Don't kill timeclock-file buffer.
* timeclock.el (timeclock-log-data): Use
`timeclock-get-timeclock-file-buffer', which avoids reading
timeclock-file, if it's already in a live buffer.
* timeclock.el (timeclock-find-discrep): Ditto.
* timeclock.el (timeclock-visit-timelog): Ditto.
Installing These:
================
Manually:
- --------
1) Download the packages that you want to install from:
/ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/
2) Unpack them to: [1]
/usr/local/lib/xemacs/xemacs-packages/
3) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.[245].x):
- ----------------------------------------------
1) Tools -> Packages -> Add Download Site -> Pre-Releases
2) Tools -> Packages -> List and Install
3) Select the packages you wish to install (there are brief
instructions at the bottom of the packages buffer).
4) Packages -> Install/Remove Selected
5) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.1.14):
- -------------------------------------------
1) Options -> Manage Packages -> Add Download Site -> Pre-Releases
2) Options -> Manage Packages -> List and Install
3 - 5) As per XEmacs 21.[245].x.
norbert - XEmacs Package Release Manager.
Footnotes:
[1] Note: Mule packages should be installed into:
/usr/local/lib/xemacs/mule-packages/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFFZYmygu3ywdHdhM0RAk0bAJ9WpDoaF+uJCzsK3NQZ6nNEk5tc5gCcC82v
dU4gfPUhYhyiXKz6vCCs5+E=
=Ci7i
-----END PGP SIGNATURE-----
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
cygwin version of xemacs-21.4.19 coredumps when trying to Page setup.../Print <buffer> to...
17 years, 5 months
Dr. Volker Zell
Hi
When clicking on Page setup.../Print <buffer> to... below File menu the
cygwin version of Xemacs (21.4.19) core dumps.
09:36 PM [524]> /usr/src/xemacs-21.4.19-2/build/src/xemacs.exe -q
Fatal error: assertion failed, file /usr/src/xemacs-21.4.19-2/src/xemacs-21.4.19/src/device.h, line 250, EQ (DEVICE_TYPE (d), sym)
*** starting debugger for pid 4980, tid 3680
*** continuing pid 4980 from debugger call (1)
Aborted (core dumped)
09:32 PM [524]> gdb /usr/src/xemacs-21.4.19-2/build/src/xemacs.exe -q
(gdb) r
Starting program: /usr/src/xemacs-21.4.19-2/build/src/xemacs.exe
Loaded symbols for /c/WINDOWS/system32/ntdll.dll
Loaded symbols for /c/WINDOWS/system32/kernel32.dll
Loaded symbols for /usr/X11R6/bin/cygX11-6.dll
Loaded symbols for /usr/bin/cygwin1.dll
Loaded symbols for /c/WINDOWS/system32/advapi32.dll
Loaded symbols for /c/WINDOWS/system32/rpcrt4.dll
Loaded symbols for /usr/X11R6/bin/cygXaw3d-7.dll
Loaded symbols for /usr/X11R6/bin/cygXext-6.dll
Loaded symbols for /usr/X11R6/bin/cygXmu-6.dll
Loaded symbols for /usr/X11R6/bin/cygXt-6.dll
Loaded symbols for /usr/X11R6/bin/cygICE-6.dll
Loaded symbols for /usr/X11R6/bin/cygSM-6.dll
Loaded symbols for /usr/X11R6/bin/cygXpm-4.dll
Loaded symbols for /usr/bin/cygcompface-0.dll
Loaded symbols for /usr/bin/cygdb-4.3.dll
Loaded symbols for /usr/bin/cygjpeg-62.dll
Loaded symbols for /usr/bin/cyglber-2-2-7.dll
Loaded symbols for /usr/bin/cygldap-2-2-7.dll
Loaded symbols for /usr/bin/cygcrypto-0.9.8.dll
Loaded symbols for /usr/bin/cygminires.dll
Loaded symbols for /usr/bin/cygsasl2-2.dll
Loaded symbols for /usr/bin/cygssl-0.9.8.dll
Loaded symbols for /usr/bin/cygncurses-8.dll
Loaded symbols for /usr/bin/cygpng12.dll
Loaded symbols for /usr/bin/cygz.dll
Loaded symbols for /usr/bin/cygpq.dll
Loaded symbols for /usr/bin/cygcrypt-0.dll
Loaded symbols for /usr/bin/cygintl-3.dll
Loaded symbols for /usr/bin/cygiconv-2.dll
Loaded symbols for /usr/bin/cygtiff-5.dll
Loaded symbols for /c/WINDOWS/system32/comctl32.dll
Loaded symbols for /c/WINDOWS/system32/gdi32.dll
Loaded symbols for /c/WINDOWS/system32/user32.dll
Loaded symbols for /c/WINDOWS/system32/comdlg32.dll
Loaded symbols for /c/WINDOWS/system32/shlwapi.dll
Loaded symbols for /c/WINDOWS/system32/msvcrt.dll
Loaded symbols for /c/WINDOWS/system32/shell32.dll
Loaded symbols for /c/WINDOWS/system32/winmm.dll
Loaded symbols for /c/WINDOWS/system32/winspool.drv
BFD: /c/WINDOWS/System32/spool/DRIVERS/W32X86/3/HPBF042G.DLL: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .text
BFD: /c/WINDOWS/System32/spool/DRIVERS/W32X86/3/HPBF042G.DLL: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .rdata
BFD: /c/WINDOWS/System32/spool/DRIVERS/W32X86/3/HPBF042G.DLL: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .data
BFD: /c/WINDOWS/System32/spool/DRIVERS/W32X86/3/HPBF042G.DLL: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .text
BFD: /c/WINDOWS/System32/spool/DRIVERS/W32X86/3/HPBF042G.DLL: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .rdata
BFD: /c/WINDOWS/System32/spool/DRIVERS/W32X86/3/HPBF042G.DLL: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .data
BFD: /c/WINDOWS/System32/spool/DRIVERS/W32X86/3/HPBF042G.DLL: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .text
BFD: /c/WINDOWS/System32/spool/DRIVERS/W32X86/3/HPBF042G.DLL: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .rdata
BFD: /c/WINDOWS/System32/spool/DRIVERS/W32X86/3/HPBF042G.DLL: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .data
Fatal error: assertion failed, file /usr/src/xemacs-21.4.19-2/src/xemacs-21.4.19/src/device.h, line 250, EQ (DEVICE_TYPE (d), sym)
Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to thread 5496.0x1178]
0x7c901231 in ntdll!DbgUiConnectToDbg () from /c/WINDOWS/system32/ntdll.dll
(gdb) bt
#0 0x7c901231 in ntdll!DbgUiConnectToDbg () from /c/WINDOWS/system32/ntdll.dll
#1 0x61004855 in break_here () from /usr/bin/cygwin1.dll
#2 0x61016be8 in try_to_debug () from /usr/bin/cygwin1.dll
#3 0x61017f4c in _cygtls::signal_exit () from /usr/bin/cygwin1.dll
#4 0x610185c8 in sigpacket::process () from /usr/bin/cygwin1.dll
#5 0x6109940a in wait_sig () from /usr/bin/cygwin1.dll
#6 0x61002f32 in cygthread::callfunc () from /usr/bin/cygwin1.dll
#7 0x61003769 in cygthread::stub () from /usr/bin/cygwin1.dll
#8 0x00001074 in ?? ()
#9 0x00000000 in ?? ()
(gdb)
Any hints how to debug this further ?
Ciao
Volker
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
strlwr
17 years, 5 months
Ilya N. Golubev
Your 2006-11-01 change of `sysdep.c' in main cvs trunk makes `strlwr',
`wcslen' require iso c99, and breaks compilation with pre- c99
compilers. Please fix.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
[AC21.5] Fix breakage in xftFont resource for tabs and menubar
17 years, 5 months
Stephen J. Turnbull
APPROVE COMMIT 21.5
Tested on Mac OS X "Tiger".
There have been several reports of problems with Xft font resources
recently. This patch addresses issues with use of *X resources* to
set Xft fonts for the Tabs and Menubar. It will not help the others
(including very poor Options Menu and Customize support, and problems
with buffer fonts).
Apparently some experimental work I was doing on creating an Xt
resource converter for Xft fonts leaked into an integration branch.
As part of that work I changed the name of the resource used for Xft
fonts from "xftFont" to "fcFontName", and reserved the xftFont
resource for the (incomplete) automatic converter.
This patch restores the functionality of the "xftFont" resource of the
Tabs and Menubar widgets. For completeness, I will mention that it
gives precedence to the fcFontName resource, but this is only for my
convenience; this patch should "just work" with properly set xftFont
resources in .Xresources.
I've also changed the default font for Tabs from the absurd Aircut to
Helvetica. (I'm currently using Bitstream Vera:italic, which is a
nice effect.)
diff --git a/lwlib/ChangeLog b/lwlib/ChangeLog
index 32a1740..1dac37d 100644
--- a/lwlib/ChangeLog
+++ b/lwlib/ChangeLog
＠＠ -1,3 +1,18 ＠＠
+2006-11-17 Stephen J. Turnbull <stephen(a)xemacs.org>
+
+ * xlwmenu.c (xlwMenuResources):
+ * xlwmenu.c (XlwMenuInitialize):
+ * xlwmenuP.h (_XlwMenu_part):
+ * xlwtabs.c (resources):
+ * xlwtabs.c (TabsInit):
+ * xlwtabsP.h (TabsPart):
+ New xftFontName member in each widget part struct, corresponds to
+ xftFont String resource.
+ Initialize renderFont private member from fcFontName if non-NULL,
+ otherwise initialize from xftFontName.
+
+ * xlwtabs.h: Update parameter table.
+
2006-06-16 Jerry James <james(a)xemacs.org>
* lwlib-Xlw.c (xlw_scrollbar_callback): Do not dereference
diff --git a/lwlib/xlwmenu.c b/lwlib/xlwmenu.c
index b6a5110..9445cb8 100644
--- a/lwlib/xlwmenu.c
+++ b/lwlib/xlwmenu.c
＠＠ -95,11 +95,11 ＠＠ xlwMenuResources[] =
#ifdef USE_XFT_MENUBARS
{XtNfcFontName, XtCFcFontName, XtRString, sizeof (String),
offset(menu.fcFontName),
- XtRString, (XtPointer) "Helvetica-12:bold"},
+ XtRString, (XtPointer) NULL},
/* #### This needs to be fixed to give a proper type and converter for
XftFonts. See also xlwtabs.c. */
- {XtNxftFont, XtCXftFont, XtRPointer, sizeof(XtPointer),
- offset(menu.renderFont), XtRPointer, (XtPointer) NULL },
+ {XtNxftFont, XtCXftFont, XtRString, sizeof(XtPointer),
+ offset(menu.xftFontName), XtRString, (XtPointer) "Helvetica-12:bold" },
#endif
# ifdef USE_XFONTSET
/* #### Consider using the same method as for Motif; see the comment in
＠＠ -3241,6 +3241,9 ＠＠ XlwMenuInitialize (Widget UNUSED (reques
#endif
#ifdef USE_XFT_MENUBARS
+ /* #### kludge for name change */
+ if (!mw->menu.fcFontName)
+ mw->menu.fcFontName = mw->menu.xftFontName;
/* to do this right, we should add a new Xt Resource type +
conversion function
*/
diff --git a/lwlib/xlwmenuP.h b/lwlib/xlwmenuP.h
index b14fde9..b091399 100644
--- a/lwlib/xlwmenuP.h
+++ b/lwlib/xlwmenuP.h
＠＠ -35,6 +35,7 ＠＠ typedef struct _XlwMenu_part
XFontStruct * font;
#ifdef USE_XFT_MENUBARS
String fcFontName;
+ String xftFontName;
XftFont *renderFont;
#endif
# ifdef USE_XFONTSET
diff --git a/lwlib/xlwtabs.c b/lwlib/xlwtabs.c
index b13f0b4..e99ee61 100644
--- a/lwlib/xlwtabs.c
+++ b/lwlib/xlwtabs.c
＠＠ -153,11 +153,11 ＠＠ static XtResource resources[] = {
/* #### Maybe use "-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-1" here?
or XtDefaultFont? */
{XtNfcFontName, XtCFcFontName, XtRString, sizeof(String),
- offset(fcFontName), XtRString, (XtPointer) "AirCut-16" },
+ offset(fcFontName), XtRString, (XtPointer) NULL },
/* #### This needs to be fixed to give a proper type and converter for
XftFonts. See also xlwmenu.c. */
- {XtNxftFont, XtCXftFont, XtRPointer, sizeof(XtPointer),
- offset(renderFont), XtRPointer, (XtPointer) NULL },
+ {XtNxftFont, XtCXftFont, XtRString, sizeof(String),
+ offset(xftFontName), XtRString, (XtPointer) "Helvetica-12" },
#endif
{XtNinternalWidth, XtCWidth, XtRDimension, sizeof(Dimension),
offset(internalWidth), XtRImmediate, (XtPointer)4 },
＠＠ -479,10 +479,12 ＠＠ TabsInit(Widget request, Widget new_, Ar
newTw->tabs.tab_height = 2 * newTw->tabs.internalHeight + SHADWID ;
#ifdef USE_XFT_TABS
+ /* #### kludge for name change */
+ if (!newTw->tabs.fcFontName)
+ newTw->tabs.fcFontName = newTw->tabs.xftFontName;
/* must get font here
- to do this right, we should add a new Xt Resource type +
- conversion function
- */
+ #### to do this right, we should add a new Xt Resource type +
+ conversion function */
newTw->tabs.renderFont =
xft_open_font_by_name (XtDisplay ((Widget) newTw),
newTw->tabs.fcFontName);
diff --git a/lwlib/xlwtabs.h b/lwlib/xlwtabs.h
index 3216556..3f9694c 100644
--- a/lwlib/xlwtabs.h
+++ b/lwlib/xlwtabs.h
＠＠ -44,8 +44,8 ＠＠
Name Class RepType Default Value
---- ----- ------- -------------
font Font XFontStruct* XtDefaultFont
- fcFontName FcFontName String AirCut-16 *0
- xftFont XftFont XtPointer NULL *8
+ fcFontName FcFontName String NULL *0
+ xftFont XftFont String Helvetica-12 *8
internalWidth Width Dimension 4 *1
internalHeight Height Dimension 2 *1
topWidget TopWidget Widget *2
diff --git a/lwlib/xlwtabsP.h b/lwlib/xlwtabsP.h
index 9bc6e44..b99c9b2 100644
--- a/lwlib/xlwtabsP.h
+++ b/lwlib/xlwtabsP.h
＠＠ -76,6 +76,7 ＠＠ typedef struct {
#ifdef USE_XFT_TABS
XftFont *renderFont;
String fcFontName;
+ String xftFontName;
#endif
Dimension internalHeight, internalWidth ;
Widget topWidget ;
diff --git a/man/ChangeLog b/man/ChangeLog
index ed67b60..f53bd76 100644
--- a/man/ChangeLog
+++ b/man/ChangeLog
＠＠ -1,3 +1,11 ＠＠
+2006-11-16 Stephen J. Turnbull <stephen(a)xemacs.org>
+
+ * internals/internals.texi
+ (Better Rendering Support -- Configuration with the Interim Patches):
+ Fix examples of configuration via X resources.
+ (Better Rendering Support -- Implementation): Fix description of
+ xftFont resources, introduce fcFontName resource.
+
2006-11-11 Aidan Kehoe <kehoea(a)parhasard.net>
* lispref/faces.texi (Face Convenience Functions):
diff --git a/man/internals/internals.texi b/man/internals/internals.texi
index 2f0df88..ca61879 100644
--- a/man/internals/internals.texi
+++ b/man/internals/internals.texi
＠＠ -27629,12 +27629,16 ＠＠ of ＠file{Xft}'s rendering functionality
＠item fontconfig
Fontconfig is dramatically different from the X model in several ways.
-In particular, ＠emph{fontconfig always returns a font}. However, the
+In particular, for the convenient interface ＠emph{fontconfig always
+returns a font}. However, the
font returned need not be anything like the desired font. This means
that XEmacs must adopt a strategy of delegating the search to
fontconfig, then sanity-checking the return, rather than trying to use
the fontconfig API to search using techniques appropriate for the X11
-core font API.
+core font API. (This isn't actually true. fontconfig has more complex
+interfaces which allow listing a subset of fonts that match a pattern,
+and don't go out of their may to return something no matter what. But
+the original patches didn't use this approach.)
＠item Font menus
The ＠samp{Options->Font} and ＠samp{Options->Font Sizes} menus are
＠＠ -27647,17 +27651,20 ＠＠ the size is strange. And the ＠samp{Opti
disabled, and has been for eons.
＠item X resources
-Currently in Stephen's patch there are ＠emph{four} treatments of font
+Currently in Stephen's patch there are ＠emph{five} treatments of font
resources. There are the ＠samp{XEmacs.(a)var{face}.attributeFont}
resources used to set a single global font specification. In the
widgets, some (still) have a ＠samp{font} resource using the automatic
＠file{Xt} resource conversion to ＠samp{FontStruct}, some have separate
-＠samp{font} and ＠samp{xftFont} resources with the former automatically
+＠samp{font} and ＠samp{fcFontName} resources with the former automatically
converted to ＠samp{FontStruct} by ＠file{Xt} and the latter left as a
-string, to be converted by ＠samp{XftParseName} later, and some have a
+string, to be converted by ＠samp{FcParseName} later, and some have a
single ＠samp{font} resource which is converted to ＠samp{FontStruct} by
＠file{Xt} or the latter left as a string, depending on whether
-＠file{Xft} was enabled by ＠samp{configure} or not.
+＠file{Xft} was enabled by ＠samp{configure} or not. There is also the
+＠samp{xftFont} resource which may be retargeted to use an Xt converter
+function, but currently simply just an alias for the ＠samp{fcFontName}
+resource.
Stephen thinks that all of these should be converted to use the face
approach, perhaps with some way to set specifications for individual
＠＠ -27894,8 +27901,12 ＠＠ at best. Probably we will should to a s
this resource, and convert to a face in XEmacs rather than a font in
Xt/Xft.
＠example
-XEmacs*Tabs.xftFont: Bitstream Vera Sans-16
-XEmacs*menubar*xftFont: Bitstream Vera Sans-16
+! DEPRECATED resource xftFont.
+! To be retargeted to an Xt converter which returns a font.
+!XEmacs*Tabs.xftFont: Bitstream Vera Sans-16
+!XEmacs*menubar*xftFont: Bitstream Vera Sans-16
+XEmacs*Tabs.fcFontName: Bitstream Vera Sans-16
+XEmacs*menubar*fcFontName: Bitstream Vera Sans-16
XEmacs.modeline.attributeFont: Bitstream Charter-16
XEmacs.default.attributeFont: Bitstream Vera Sans Mono-16
＠end example
＠＠ -27903,7 +27914,14 ＠＠ I highly recommend use of a proportional
allows a lot more text to fit there. (Previously the font sizes were
quite varied, and there was a comment that this weirdness gave good
balance. This isn't true on my main platform, Mac OS X, and needs to be
-rechecked on Linux, where it was observed.)
+rechecked on Linux, where it was observed.) Note that you can probably
+specify a particular Japanese font with something like
+＠example
+XEmacs.default.attributeFont: Bitstream Vera Sans Mono,Sazanami Mincho-16
+＠end example
+Order is important; Japanese fonts will support English, but Sazanami's
+Roman characters are not very pretty compared to the Bitstream font.
+＠strong{Note:} ＠emph{This is untested, but should work in theory.}
＠end itemize
**** End of patch
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: [mule] xemacs doesn't recognize some symbols
17 years, 5 months
Aidan Kehoe
Ar an t-ochtú lá is fiche de mí Deireadh Fómhair, scríobh stephen(a)xemacs.org:
> > (If it’s falling back, it’s to the US layout, yes.)
>
> IIRC, XEmacs has no concept of keyboard layout (at least in X11).
By the way, that’s very wrong, and always has been. The function
x-keysym-on-keyboard-p has been available for years, and JWZ’s complaining
about which modifiers are bound to which keysyms *requires* intimate
knowledge of the keyboard layout, worked out at each start.
On X11 we do fall back to the US key layout to solve the ‘Russian C-x
problem’ as Ben called it. But this is specific to 21.5.
> It just accepts keysyms from the server.
Also, not totally true--for things like some X11 input methods, where they
supply nonsensical keysym numbers with single-character string keysym names,
those names are interpreted using keyboard-coding-system and bound to
self-insert-command.
--
Santa Maradona, priez pour moi!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
[BUG] Cannot install 21.5.b27 since +CVS-20061116
17 years, 5 months
robert delius royar
When I make XEmacs, the process fails in one of the lisp file load
stages with the error
Load file misc: not found
Fatal error during load, aborting
The lisp directory contains the misc.el file.
If I make clean and configure again, then I see
config.status: WARNING: Makefile.in.in seems to ignore the --datarootdir setting
config.status: WARNING: lib-src/Makefile.in.in seems to ignore the --datarootdir setting
config.status: WARNING: lib-src/config.values.in seems to ignore the --datarootdir setting
./temacs -nd -no-packages -batch -l
/Users/royar/src/xemacs/src/../lisp/update-elc.el
Loading /Users/royar/src/xemacs/src/../lisp/update-elc.el...
Loading find-paths.el...
Loading packages.el...
Loading setup-paths.el...
Loading /Users/royar/src/xemacs/lisp/dumped-lisp.el...
Loading loadup-el.el...
Loading loadup.el...
Using load-path (/Users/royar/src/xemacs/lisp/)
Using module-load-path (/Users/royar/src/xemacs/modules)
Loading dumped-lisp.el...
Loading backquote.el...
Loading bytecomp-runtime.el...
Loading find-paths.el...
Loading packages.el...
Loading setup-paths.el...
Loading subr.el...
Loading post-gc.el...
Loading replace.el...
Loading version.el...
Loading cl.el...
Loading cl-extra.el...
Requiring obsolete.el...
Loading cl-seq.el...
Loading widget.el...
Loading custom.el...
Loading cl-macs.el...
Requiring cus-face.el...
Requiring font.el...
Requiring disp-table.el...
Loading cus-start.el...
Loading cmdloop.el...
Loading keymap.el...
Loading syntax.el...
Loading device.el...
Loading console.el...
Loading obsolete.el...
Loading specifier.el...
Loading frame.el...
Loading fontconfig.el...
Loading x-faces.el...
Loading faces.el...
Loading cl-macs.el...
Loading glyphs.el...
Loading objects.el...
Loading extents.el...
Loading events.el...
Loading hash-table.el...
Loading text-props.el...
Loading process.el...
Loading multicast.el...
Loading map-ynp.el...
Loading undo-stack.el...
Loading window.el...
Loading window-xemacs.el...
Loading simple.el...
Loading newcomment.el...
Loading keydefs.el...
Loading abbrev.el...
Loading derived.el...
Loading minibuf.el...
Loading list-mode.el...
Loading modeline.el...
Loading cus-file.el...
Loading startup.el...
Load file misc: not found
Fatal error during load, aborting
make[1]: *** [NEEDTODUMP] Error 1
make: *** [src] Error 2
--
Dr. Robert Delius Royar Associate Professor of English
Morehead State University Morehead, Kentucky
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
change log file, navigate to the changes
17 years, 5 months
Uwe Brauer
Hello
Does anybody know about a package which would allow to
annote the changes but set a mark, such that later I could navigate to
that part of the buffer where the change occurred. Bm.el or bookmark.el
would be candidates, but they are not connected to change-log
Example
Original file
Hello world.
This is a great idea.
Changed to
Hello world.
This is a good idea.
Change log entry would be
2006-11-16 Uwe Brauer <oub(a)mat.ucm.es>
* test: Change great to good.
Setting the mouse say on test, and using a modified ffap-guesser
XEmacs would jump where the change occurred. In order to do this at
least the char-number should be stored, best would be a string before
and after the change in order to simplify the search. Bm.el and
bookmarks.el do this.
Thanks and regards
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
