Re: XEmacs doesn't support windows-1252
16 years, 9 months
Aidan Kehoe
Ar an séú lá is fiche de mí Iúil, scríobh Mike FABIAN:
> And when I check this character in an e-mail I received which
> uses charset=windows-1252, I get
>
> (split-char ?”)
> (chinese-gb2312 33 49)
>
> and the character is displayed in a very ugly Chinese font which looks
> double width even in the X-frame. In the terminal, XEmacs again
> treats the character as double width but the terminal treats it as
> single width which causes problems.
>
> (split-char (string-to-char
> (decode-coding-string (format "%c%c%c" #xe2 #x80 #x9d) 'utf-8)))
> (latin-iso8859-16 53)
>
> Is it possible to get the sane mapping to a European [character set]
> *always*?
Sure. You can structure make-8-bit-coding-system call like so:
(make-8-bit-coding-system
'windows-1252
(list
(list #x80 (decode-char 'ucs #x20AC)) ;; EURO SIGN
(list #x82 (decode-char 'ucs #x201A)) ;; SINGLE LOW-9 QUOTATION MARK
[...]
(list #x9F (decode-char 'ucs #x0178)));; LATIN CAPITAL LETTER Y WITH DIAERESIS
"Microsoft's Code Page 1252, for Western Europe and the Americas."
'(mnemonic "cp1252"
documentation
"This is an extension of ISO 8859-1 that provides the Euro sign and
several punctuation marks not otherwise available in ISO 8859 1. It is
incompatible with ISO 2022, which is not a problem in the regions
where it is used. "
aliases (cp1252)))
and have the octets on disk always represented in the jit-ucs-charset-?
XEmacs character set (because the evaluation then takes place at dump time,
when the other Mule character sets are not available.) This has the
disadvantage that it’s against the spirit of ISO 2022 (when it comes to our
auto-save files) and that for the ISO 8859-1 characters, case information is
not preserved (to my surprise; that’s something I need to look into.)
> Footnotes:
> ¹ I type this character using an entry in my ~/.Xmodmap, no matter
> whether I am typing into an X-frame or into a terminal frame. I.e. I type
> it the same way but the results are different.
Right. Because in the terminal it depends on the current Unicode -> Mule
mapping, while under X11 it depends on the Unicode -> Mule mapping at the
time when XEmacs appeared on the relevant display, which normally is before
~/.xemacs/init.el was evaluated.
I had planned to make available an XEmacs with Unicode as an internal
encoding (and I have most of the necessary work for that on my disk), but I
don’t think that is maintainable in the presence of both the Mule and the
non-Mule compilation options (which means, in the presence of Unicode
internally, four ./configure options with which everything needs to be
tested when anyone makes any change that’s relevant to character
encoding). And the elimination of the non-Mule compilation options has been
vetoed, so it looks like users are stuck with the internal Mule encoding.
--
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
[Bug: 21.4.19] dead keys on Windows
16 years, 9 months
Cezary Sliwa
--text follows this line--
================================================================
Dear Bug Team!
When I press "~" (it is a dead key in the Polish keyboard
layout), strange things happen. For example pressing the
sequence "~" [space] "a" produces a space and the "±" character
(Xemacs notices "~" has been pressed and remembers to put an
accent despite the intervening space). Pressing "~" twice
produces "~~", so how can I obtain just one "~"? (it should
be possible with the "~" [space] sequence, but it produces
a space.
================================================================
System Info to help track down your bug:
---------------------------------------
OS version:
Microsoft Windows XP [Version 5.1.2600]
OS: Windows_NT
XEmacs 21.4.19 "Constant Variable" configured for `i586-pc-win32'.
Building XEmacs in "e:\\acs\\software\\XEmacsWindowsKit\\xemacs-21.4-2006-01-28\\nt".
Using compiler "cl -nologo -W3 -O2 -G5 -MD".
Installing XEmacs in "c:\\XEmacs-built\\XEmacs-21.4.19".
Package path is "~\\.xemacs;;c:\\XEmacs-built\\site-packages;c:\\XEmacs-built\\xemacs-packages".
Compiling in support for Microsoft Windows native GUI.
Compiling in support for XPM images.
Compiling in support for GIF images.
Compiling in support for PNG images.
Compiling in support for TIFF images.
Compiling in support for JPEG images.
Compiling in support for toolbars.
Compiling in support for dialogs.
Compiling in support for widgets.
Compiling in support for native sounds.
Compiling in fast dired implementation.
Using portable dumper.
Using system malloc.
Using DLL version of C runtime library
Load-Path Lisp Shadows:
----------------------
nil
Installed XEmacs Packages:
-------------------------
(xemacs-devel ver: 1.72 upstream: No-Upstream-Ver)
(xemacs-base ver: 2.01 upstream: No-Upstream-Ver)
(time ver: 1.14 upstream: 1.17)
(text-modes ver: 1.9 upstream: No-Upstream-Ver)
(texinfo ver: 1.3 upstream: No-Upstream-Ver)
(speedbar ver: 1.28 upstream: 0.14beta4)
(sounds-wav ver: 1.12 upstream: No-Upstream-Ver)
(sh-script ver: 1.21 upstream: 2.0f)
(semantic ver: 1.19 upstream: 1.4.2)
(prog-modes ver: 2.06 upstream: No-Upstream-Ver)
(perl-modes ver: 1.08 upstream: No-Upstream-Ver)
(pc ver: 1.28 upstream: No-Upstream-Ver)
(os-utils ver: 1.36 upstream: No-Upstream-Ver)
(net-utils ver: 1.48 upstream: N/A)
(mail-lib ver: 1.75 upstream: No-Upstream-Ver)
(fsf-compat ver: 1.15 upstream: No-Upstream-Ver)
(eieio ver: 1.05 upstream: 0.17)
(efs ver: 1.33 upstream: 1.23)
(edit-utils ver: 2.32 upstream: No-Upstream-Ver)
(ediff ver: 1.6 upstream: 2.75)
(edebug ver: 1.21 upstream: No-Upstream-Ver)
(ecb ver: 1.22 upstream: 2.31)
(dired ver: 1.17 upstream: 7.13)
(debug ver: 1.17 upstream: No-Upstream-Ver)
(cc-mode ver: 1.45 upstream: 5.30.10)
(c-support ver: 1.22 upstream: No-Upstream-Ver)
Features:
--------
(view-less view ehelp electric mail-abbrevs xemacsbug shadow sendmail
rfc822 xemacs-devel-autoloads xemacs-base-autoloads time-autoloads
text-modes-autoloads texinfo-autoloads speedbar-autoloads
sounds-wav-autoloads sh-script-autoloads semantic-autoloads
prog-modes-autoloads perl-modes-autoloads pc-autoloads
os-utils-autoloads net-utils-autoloads mail-lib-autoloads
fsf-compat-autoloads eieio-autoloads efs-autoloads
edit-utils-autoloads ediff-autoloads edebug-autoloads ecb-autoloads
dired-autoloads debug-autoloads cc-mode-autoloads c-support-autoloads
lisp-autoloads loadhist auto-show fontl-hooks code-cmds gutter-items
menubar-items x-menubar dragdrop mode-motion mouse itimer auto-save
lisp-mode easymenu iso8859-1 page buff-menu lib-complete help-nomule
cus-file derived frame text-props obsolete cus-start custom widget
cl-extra mini-cl cl cl-19 packages backquote very-early-lisp
file-coding mswindows-scrollbars mswindows toolbar native-sound
scrollbar network-streams subprocesses menu-accelerator-support
menubar md5 xemacs gutter tiff png gif jpeg xpm xbm lisp-float-type
windows-nt dragdrop-api dialog devices window-system base64)
Recent keystrokes:
-----------------
down up up C-z C-Sh-BS C-Sh-BS C-M-BS C-M-BS C-M-BS
C-M-BS C-M-BS C-M-BS C-M-BS C-M-BS C-M-BS C-M-BS C-M-BS
C-M-BS C-M-BS C-M-BS C-u C-M-BS C-u C-M-BS t h i s
SPC o n e SPC p p r up up up up up up up up up up up
up down down down down down down down down down down
down down down down up up C-e BS BS r o d u c e s RET
a SPC s p a c e . RET button1 button1up misc-user button1
button1up C-x k RET C-x o C-x k RET C-x 1 misc-use
r
Recent messages (most recent first):
-----------------------------------
C-Sh-BS not defined.
C-Sh-BS not defined.
The region is not active now
Buffer is read-only: #<buffer "*Bug Help*">
Type M-x mail-send-and-exit to send the bug report, C-x k to cancel.
space = page forward; b = page back; h = help; q = quit.
Loading view-less...done
Loading view-less...
Loading ehelp...done
Loading ehelp...
Loading xemacsbug...done
Loading xemacsbug...
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: XEmacs doesn't support windows-1252
16 years, 9 months
Aidan Kehoe
Ar an séú lá is fiche de mí Iúil, scríobh Mike FABIAN:
> Aidan Kehoe <kehoea(a)parhasard.net> さんは書きました:
>
> > Ar an séú lá is fiche de mí Iúil, scríobh Mike FABIAN:
> >
> > > Aidan Kehoe <kehoea(a)parhasard.net> さんは書きました:
> > >
> > > > Mike, you can cvs update, add this to lisp/mule/latin.el, and
> > > > rebuild.
> > >
> > > > (make-8-bit-coding-system
> > >
> > > It doesn't build anymore then:
> >
> > Right, that’s why I mentioned “cvs update” above. make-8-bit-coding-system
> > has only been in the trunk since the 22nd.
>
> I forgot to mention that I *did* a CVS update before trying that.
Does the file
/usr/src/packages/BUILD/xemacs-21.5.28/lisp/mule/mule-coding.el
contain that function? It does for me when I check out the tree. But then I
have occasionally had weirdnesses with that CVS server too.
> (cvs up -A).
>
>
> Still doesn't build.
>
> --
> Mike FABIAN <mfabian(a)suse.de> http://www.suse.de/~mfabian
> 睡眠不足はいい仕事の敵だ。
> I � Unicode
--
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: XEmacs doesn't support windows-1252
16 years, 9 months
Aidan Kehoe
Ar an séú lá is fiche de mí Iúil, scríobh Mike FABIAN:
> Aidan Kehoe <kehoea(a)parhasard.net> さんは書きました:
>
> > Mike, you can cvs update, add this to lisp/mule/latin.el, and
> > rebuild.
>
> > (make-8-bit-coding-system
>
> It doesn't build anymore then:
Right, that’s why I mentioned “cvs update” above. make-8-bit-coding-system
has only been in the trunk since the 22nd.
> ./xemacs -nd -no-packages -batch -l /usr/src/packages/BUILD/xemacs-21.5.28/src/../lisp/update-elc.el
>
> Loading /usr/src/packages/BUILD/xemacs-21.5.28/src/../lisp/update-elc.el...
> [...]
> Loading mule-coding.el...
> [...]
> Loading mule-ccl.el...
> [...]
> Loading latin.el...
> *** Error in XEmacs initialization
> (void-function make-8-bit-coding-system)
> *** Backtrace
> really-early-error-handler((void-function make-8-bit-coding-system))
--
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: XEmacs cannot display U+FFFD (REPLACEMENT CHARACTER) correctly
16 years, 9 months
Aidan Kehoe
Ar an ceathrú lá is fiche de mí Iúil, scríobh Mike FABIAN:
> Aidan Kehoe <kehoea(a)parhasard.net> さんは書きました:
>
> > [...] Okay, for the sake of round-trip compatibility (especially with a
> > future Unicode-oriented XEmacs), we should map those 7 characters
> > either to a private-use area (and one outside of the BMP) or an area
> > outside of Unicode. Do you have any objections to the following
> > mapping?
> >
> > 0xA15A => U+FA15A
> > 0xA1C3 => U+FA1C3
> > 0xA1C5 => U+FA1C5
> > 0xA1FE => U+FA1FE
> > 0xA240 => U+FA240
> > 0xA2CC => U+FA2CC
> > 0xA2CE => U+FA2CE
>
> Looks fine.
>
> To make sure that this really works I tried the attached patch
> and it does work indeed.
Ok. As I understand it, we need to state explicitly in the file that we’ve
modified it, if we’re to distribute it.
--
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
XEmacs doesn't support windows-1252
16 years, 9 months
Mike FABIAN
In unicode.el, the tables for some charsets commonly used
under Microsoft Windows are commented out:
(defun load-unicode-tables ()
"Initialize the Unicode translation tables for all standard charsets."
[...]
;; "CP1250.TXT"
;; "CP1251.TXT"
;; "CP1252.TXT"
;; "CP1253.TXT"
;; "CP1254.TXT"
;; "CP1255.TXT"
;; "CP1256.TXT"
;; "CP1257.TXT"
;; "CP1258.TXT"
;; "CP874.TXT"
;; "CP932.TXT"
;; "CP936.TXT"
;; "CP949.TXT"
;; "CP950.TXT"
Why?
Sometimes I get mail which uses some of these windows charsets
even from Linux users. For example from some Mutt users:
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.5.16 (2007-06-09)
Usually these mails contain some characters which are only in
windows-1252 and not in iso-8859-1. For example such characters:
“ U+201C LEFT DOUBLE QUOTATION MARK
” U+201D RIGHT DOUBLE QUOTATION MARK
– U+2013 EN DASH
And my Gnus running under XEmacs cannot display such mails correctly
because of the lack of support for the windows-1252 charset.
Can this be fixed easily or would it cause problems to load
these translation tables as well in unicode.el?
--
Mike FABIAN <mfabian(a)suse.de> http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
I � Unicode
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Cannot build latest CVS of 21.5.28
16 years, 9 months
robert delius royar
On my OS X system, I see a failure in the file mule-ccl.c
gcc-4.0 -c -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts
-Wpacked -Wpointer-arith -Wunused-parameter -g -Os -pipe -mcpu=970
-mtune=970 -mpim-altivec -I/opt/local/include -Demacs -I.
-I/Users/royar/src/xemacs/src -DHAVE_CONFIG_H
-I/usr/X11R6/include/freetype2 -I/opt/local/include -I/usr/X11R6/include
mule-ccl.c
mule-ccl.c: In function 'ccl_driver':
mule-ccl.c:1565: error: incompatible types in assignment
mule-ccl.c:1566: error: request for member 's' in something not a structure or union
mule-ccl.c:1568: error: request for member 'gu' in something not a structure or union
mule-ccl.c:1568: error: request for member 'gu' in something not a structure or union
mule-ccl.c:1568: error: request for member 's' in something not a structure or union
The configure command was
./configure --with-mule --with-widgets=athena --with-athena=3d \
--with-dialogs=athena --with-scrollbars=lucid --without-debug \
--with-union-type --without-error-checking --with-dynamic \
--prefix=${ParentPath} --with-png --with-jpeg --with-tiff \
--with-xmu --with-xim=no --enable-sound=esd --disable-xfs \
--enable-dump-in-exec --with-modules --enable-external-widget \
--with-dynamic --disable-kkcc --disable-mc-alloc \
--enable-optimization --with-cflags-optimization='-Os -pipe -mcpu=970 -mtune=970 -mpim-altivec' \
--with-site-runtime-libraries="/opt/local/lib:/usr/X11R6/lib" \
--with-site-libraries="/opt/local/lib:/usr/X11R6/lib" --with-xft=emacs,gauges,notabs,nomenubars \
--with-neon --with-curl \
--with-compiler=gcc-4.0 CPPFLAGS='-I/opt/local/include' LDFLAGS='-L/opt/local/lib'
The Changelog says
2007-07-21 Aidan Kehoe <kehoea(a)parhasard.net>
[...]
* mule-ccl.c (ccl_driver):
Add Dave Love's hash table lookup CCL code, which has been in GNU
for years.
Move mule-to-unicode to accept its argument in the same format as
write-multibyte-character.
Move to accepting characters as well as integers in lots of
places; with XEmacs (and even with GNU Emacs), where the
character-integer map is not constant from one invocation to the
next, it makes sense for CCL programs with character literals to
accept those literals as characters, not integers.
If we're a debug build, allow access to ccl-program-table from
Lisp, which can make debugging things easier.
Take out font-ccl-encoder-alist, since it was never implemented,
and was not ever a stellar idea.
Provide translation-hash-table-vector, as in GNU.
--
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
Re: compile.el and kill-all-local-variables
16 years, 9 months
Stephen J. Turnbull
Marcus Harnisch writes:
> I wonder if the call to `kill-all-local-variables' is a bit too
> sledgehammerish and should be replaced by something less invasive.
Talk to RMS about that. ;-)
One problem we have here is that compile.el is a high-level
application that we want to maintain GNU compatibility. I see your
problem, but varying here would open us up to various subtle bugs.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: custom-load.el and MH-E compatibility macros
16 years, 9 months
Mike Kupfer
>>>>> "ST" == Stephen J Turnbull <stephen(a)xemacs.org> writes:
MikeK> I thought about moving the deffoo-mh definitions to their own file,
MikeK> and modifying the build rules to load the macros before invoking
MikeK> Custom-make-dependencies. For example, if I define a new makefile
MikeK> macro called CUSTOM_LOAD_PREMAKE
ST> This seems the most sensible way to proceed, except that I would
ST> prefer that the Makefile variable be named CUSTOM_LOAD_PRELOADS.
In theory, the variable could contain other "forms", such as -f or
-eval. If "preloads" is considered sufficiently generic to cover that
usage (or if we can't think of a better name), I'm fine with it.
cheers,
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: Why not enable font lock by default?
16 years, 9 months
Stephen J. Turnbull
Jason Spiro writes:
> I will post a poll to the newsgroup. But is polling the developer
> mailing list really worthwhile? I think we should go with whatever
> the users prefer, not the developers.
It's the list where you are most likely to find developers, but it's
not "the developers' list." (Not speaking for my colleagues:) I don't
make a sharp distinction between user and developer. These are roles
that the same person plays in varying degrees according to context and
phase of the moon.
The reason it's called "xemacs-beta" is that beta testers are supposed
to hang out here. As active contributors they are more likely to
respond, and should given extra weight. They are also likely to have
better-informed opinions.
> I will start an EmacsWiki page at
> http://www.emacswiki.org/wiki/XEmacsFontificationSystems instead.
OK.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta