Re: Full Unicode Pathnames
17 years, 5 months
Vin Shelton
>
> -----Original Message-----
> From: Adrian Aichner [mailto:adrian＠xemacs.org]
> Sent: Saturday, November 25, 2006 6:18 AM
> To: Benson Margulies; Vin Shelton
> Subject: Re: Full Unicode Pathnames
>
> "Benson Margulies" <bim2006(a)basistech.com> writes:
>
> > Don't build with /MDd, build with /MD, and redistribute the
> > redistributable non-debug version.
>
> Vin, Benson, building with
> DEBUG_XEMACS=0
> in config.inc should do.
>
On 11/25/06, Benson Margulies <bim2006(a)basistech.com> wrote:
> Sure, I'll do that. But I'm suggesting that you do that for the
> installe.
21.5 is still a beta release. I assumed the debugging info was useful
to the development community. I don't have a strong feeling one way
or the other; subscribers to xemacs-beta let me know how you think the
21.5 setup kits should be built.
- Vin
--
The Journey by Mary Oliver
http://www.poemhunter.com/p/m/poem.asp?poet=6771&poem=30506
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: [Bug: 21.5-b27] Suboptimal interaction of latin-unity and VM.
17 years, 5 months
Aidan Kehoe
Ar an cúigiú lá is fiche de mí na Samhain, scríobh Stephen J. Turnbull:
> > it is very unclear to me why latin-unity-sanity-check passes the text
> > on to the Mule detection mechanism when writing, instead of accepting
> > 'binary as a reasonable way of encoding control-1, latin-iso8859-1 and
> > ascii.
>
> "detection" is the wrong word. What this means is that you're at the
> mercy of whatever Mule decides to do with your content when b-f-c-s is
> set to 'binary (eg, it typically corrupts Japanese).
>
> In fact, if you have your b-f-c-s set to binary, it does just accept
> 'binary as a reasonable way of encoding those sets. (At least it did
> the last time I checked.)
I’ve renamed my ~/.vm file to ~/.vm-. I start XEmacs:
$ xemacs-21.5-b27 -vanilla &
In *scratch*, I type:
(latin-unity-install) C-j
=> (latin-unity-sanity-check)
(setq font-running-xemacs t) ;; to work around an issue W3 is seeing
=> t
I type M-x vm-visit-folder RET /tmp/aidan/spam RET
I make a change, press S , and I get the coding system conflict message. It
says, again, that:
“All preapproved coding systems (buffer-default==binary
preferred==utf-16-little-endian-bom) fail to appropriately encode some
of the characters present in the buffer.”
This time it lists:
iso-8859-1 iso-8859-2 iso-8859-3 iso-8859-4 iso-8859-9 iso-8859-15 utf-8
iso-2022-7 ctext escape-quoted
as recommended because they can encode any character in the buffer.
The folder in question is available at http://www.parhasard.net/spam.bz2 .
--
Santa Maradona, priez pour moi!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: cygwin version of xemacs-21.4.19 coredumps when trying to Page setup.../Print <buffer> to...
17 years, 5 months
Stephen J. Turnbull
Dr. Volker Zell writes:
> The Windows version now pops up the windows printer dialogs, but the X
> version gives:
>
> Feature not yet implemented: "Dialog box type", page-setup
> Feature not yet implemented: "Dialog box type", print
>
> Isn't this supposed to work out of the box ?
No. The Cygwin version knows that it's on a Windows system and wants
to use the Windows facilities. Is that known to be incorrect? X
users normally use lpr? Or what do they do on Cygwin? I suppose lpr
has the best chance of working out of the box.
If you want Unix-style facilities, edit the page-setup button out of
the toolbar (there is no X equivalent, unless you want to bind it to
`(lambda () (customize-group 'lpr))').
For the print button, use C-h k <click on print button> to find out
what's bound to it. If it's not `toolbar-print', try binding
`toolbar-print' to that button. (M-x edit-toolbar is a convenient way
to do that.) If it is already `toolbar-print', what is the value of
the variable `toolbar-print-function'? Does setting that to
'lpr-buffer help?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
[Bug: 21.5-b27] Suboptimal interaction of latin-unity and VM.
17 years, 5 months
Aidan Kehoe
================================================================
Dear Bug Team!
The docstring for latin-unity-sanity-check says:
“This function does _not_ do the safe thing when
`buffer-file-coding-system' is nil (= no-conversion). It considers that
"non-Latin", and passes it on to the Mule detection mechanism. This
could result in corruption. So avoid setting `buffer-file-coding-system'
to nil or 'no-conversion or 'binary.”
However, when dealing with Unix mail spools, as VM does, it’s the correct
and reasonable thing to do to set buffer-file-coding-system to 'binary,
since MIME means that identical octets can mean different things in
different messages in the same file.
I just did a (latin-unity-install) in this XEmacs, without setting the
latin-unity-preapproved-coding-system-list. Now, when I visit a VM folder,
make a change, and try to save it, I get this:
Choose a coding system to save buffer inbox.
All preapproved coding systems (buffer-default==binary
preferred==utf-16-little-endian-bom)
fail to appropriately encode some of the characters present in the
buffer. Character sets in the buffer are:
control-1 latin-iso8859-1 ascii
Please pick a coding system. The following are recommended because they
can encode any character in the buffer:
iso-8859-1 utf-8 iso-2022-7 ctext escape-quoted
Note that if you select a coding system that can not encode some
characters in your buffer, those characters will be changed to an
arbitrary replacement character, by default `~', on output.
[...]
(Even when the folder is empty!) I don’t know where it’s getting
utf-16-little-endian-bom. 'binary is going to remain equivalent to
'iso-8859-1 for us; it is very unclear to me why latin-unity-sanity-check
passes the text on to the Mule detection mechanism when writing, instead of
accepting it as a reasonable way of encoding control-1, latin-iso8859-1 and
ascii.
Bye,
Aidan
================================================================
System Info to help track down your bug:
---------------------------------------
uname -a: Linux icarus.asclepian.ie 2.6.8-2-386 #1 Tue Aug 16 12:46:35 UTC 2005 i686 GNU/Linux
./configure '--with-cflags-optimization=-Os -fomit-frame-pointer -march=pentium2 -msse -msse2 -mfpmath=sse,387' '--with-debug' '--with-memory-usage-stats' '--without-x' '--with-modules' '--with-rel-alloc' '--without-kkcc' '--without-newgc' '--with-pdump' '--with-mule' '--without-sound' '--without-png' '--without-jpeg' '--without-tiff' '--without-xface' '--without-gif' '--without-xpm' '--with-tty' '--without-error-checking' '--prefix=/home/aidan'
XEmacs 21.5-b27 "fiddleheads" (+CVS-20060824) configured for `i686-pc-linux'.
Compilation Environment and Installation Defaults:
Source code location: /home/aidan/xemacs-21.5
Installation prefix: /home/aidan
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler version: gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
- GCC specs file: /usr/lib/gcc-lib/i486-linux/3.3.5/specs
- Compiler command: gcc -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wunused-parameter -g -Os -fomit-frame-pointer -march=pentium2 -msse -msse2 -mfpmath=sse,387
libc version: GNU libc 2.3.2.ds1-22sarge3 (Debian)
Relocating allocator for buffers: yes
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Window System:
TTY:
Compiling in support for ncurses.
Images:
Sound:
Databases:
Compiling in support for Berkeley database.
Compiling in support for LDAP.
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Mail:
Compiling in support for "file" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
Compiling in support for dynamic shared object modules.
Using the new portable dumper.
Dumping into executable.
Compiling in support for extra debugging code.
Load-Path Lisp Shadows:
----------------------
(/home/aidan/emacs-lisp/redo
/home/aidan/lib/xemacs/xemacs-packages/lisp/edit-utils/redo
/home/aidan/emacs-lisp/sendmail
/home/aidan/lib/xemacs/xemacs-packages/lisp/mail-lib/sendmail
/home/aidan/emacs-lisp/vm-mime
/home/aidan/lib/xemacs/xemacs-packages/lisp/vm/vm-mime
/home/aidan/lib/xemacs/mule-packages/lisp/mule-base/korea-util
/home/aidan/lib/xemacs-21.5-b27/lisp/mule/korea-util
/home/aidan/lib/xemacs/mule-packages/lisp/mule-base/ethio-util
/home/aidan/lib/xemacs-21.5-b27/lisp/mule/ethio-util
/home/aidan/lib/xemacs/mule-packages/lisp/leim/quail/cyrillic
/home/aidan/lib/xemacs-21.5-b27/lisp/mule/cyrillic
/home/aidan/lib/xemacs/mule-packages/lisp/mule-base/cyril-util
/home/aidan/lib/xemacs-21.5-b27/lisp/mule/cyril-util
/home/aidan/lib/xemacs/mule-packages/lisp/mule-base/china-util
/home/aidan/lib/xemacs-21.5-b27/lisp/mule/china-util
/home/aidan/lib/xemacs/mule-packages/lisp/mule-base/japan-util
/home/aidan/lib/xemacs-21.5-b27/lisp/mule/japan-util
/home/aidan/lib/xemacs/mule-packages/lisp/mule-base/viet-util
/home/aidan/lib/xemacs-21.5-b27/lisp/mule/viet-util
/home/aidan/lib/xemacs/mule-packages/lisp/leim/quail/thai-xtis
/home/aidan/lib/xemacs-21.5-b27/lisp/mule/thai-xtis
/home/aidan/lib/xemacs/mule-packages/lisp/leim/quail/greek
/home/aidan/lib/xemacs-21.5-b27/lisp/mule/greek
/home/aidan/lib/xemacs/xemacs-packages/lisp/build/build-report
/home/aidan/lib/xemacs-21.5-b27/lisp/build-report
/home/aidan/lib/xemacs/xemacs-packages/lisp/xemacs-base/regexp-opt
/home/aidan/lib/xemacs-21.5-b27/lisp/regexp-opt
/home/aidan/emacs-lisp/Mule-UCS-current/lisp/unicode
/home/aidan/lib/xemacs-21.5-b27/lisp/unicode
/home/aidan/lib/xemacs/xemacs-packages/lisp/xemacs-base/easy-mmode
/home/aidan/lib/xemacs-21.5-b27/lisp/easy-mmode)
Installed XEmacs Packages:
-------------------------
(xslt-process ver: 1.11 upstream: regular)
(xemacs-devel ver: 1.7 upstream: No-Upstream-Ver)
(xemacs-base ver: 1.94 upstream: No-Upstream-Ver)
(vm ver: 7.19 upstream: 7.17)
(view-process ver: 1.13 upstream: 2.4)
(vc-cc ver: 1.22 upstream: No-Upstream-Ver)
(vc ver: 1.4 upstream: No-Upstream-Ver)
(tpu ver: 1.14 upstream: 4.2X)
(time ver: 1.14 upstream: 1.17)
(textools ver: 1.15 upstream: No-Upstream-Ver)
(text-modes ver: 1.82 upstream: No-Upstream-Ver)
(texinfo ver: 1.28 upstream: No-Upstream-Ver)
(strokes ver: 1.1 upstream: No-Upstream-Ver)
(speedbar ver: 1.27 upstream: 0.14beta4)
(sml-mode ver: 0.11 upstream: 3.9.5)
(sieve ver: 1.17 upstream: No-Upstream-Ver)
(sh-script ver: 1.18 upstream: 2.0e)
(sgml ver: 1.11 upstream: No-Upstream-Ver)
(scheme ver: 1.14 upstream: No-Upstream-Ver)
(rmail ver: 1.14 upstream: No-Upstream-Ver)
(reftex ver: 1.34 upstream: 4.21)
(python-modes ver: 1.06 upstream: No-Upstream-Ver)
(prog-modes ver: 2.01 upstream: No-Upstream-Ver)
(perl-modes ver: 1.06 upstream: No-Upstream-Ver)
(pcl-cvs ver: 1.66 upstream: R-2_9_9)
(pc ver: 1.26 upstream: No-Upstream-Ver)
(os-utils ver: 1.35 upstream: No-Upstream-Ver)
(oo-browser ver: 1.04 upstream: 4.08)
(ocaml ver: 0.05 upstream: 3.06)
(net-utils ver: 1.44 upstream: N/A)
(mmm-mode ver: 1.02 upstream: 0.4.7)
(misc-games ver: 1.18 upstream: No-Upstream-Ver)
(mailcrypt ver: 2.14 upstream: 3.5.8)
(mail-lib ver: 1.7 upstream: No-Upstream-Ver)
(ispell ver: 1.29 upstream: 3.6)
(ilisp ver: 1.33 upstream: 5.12.0)
(igrep ver: 1.13 upstream: 2.111)
(ibuffer ver: 1.09 upstream: No-Upstream-Ver)
(gnats ver: 1.16 upstream: 3.101)
(general-docs ver: 1.03 upstream: No-Upstream-Ver)
(games ver: 1.15 upstream: 1.04)
(fsf-compat ver: 1.15 upstream: No-Upstream-Ver)
(frame-icon ver: 1.11 upstream: No-Upstream-Ver)
(forms ver: 1.15 upstream: 2.37)
(footnote ver: 1.16 upstream: 0.18x)
(eterm ver: 1.15 upstream: No-Upstream-Ver)
(ess ver: 1.12 upstream: 5.2.3)
(erc ver: 0.12 upstream: Version 4.0 Revision: 1.675)
(emerge ver: 1.11 upstream: No-Upstream-Ver)
(elib ver: 1.11 upstream: 1.0)
(eieio ver: 1.05 upstream: 0.17)
(efs ver: 1.33 upstream: 1.23)
(edt ver: 1.13 upstream: No-Upstream-Ver)
(edit-utils ver: 2.19 upstream: No-Upstream-Ver)
(ediff ver: 1.5 upstream: 2.75)
(edebug ver: 1.21 upstream: No-Upstream-Ver)
(ecrypto ver: 0.19 upstream: 2.0)
(dired ver: 1.16 upstream: 7.12)
(dictionary ver: 1.15 upstream: 1.8)
(debug ver: 1.17 upstream: No-Upstream-Ver)
(cc-mode ver: 1.43 upstream: 5.30.9)
(calendar ver: 1.23 upstream: No-Upstream-Ver)
(calc ver: 1.26 upstream: 2.02fX3)
(c-support ver: 1.2 upstream: No-Upstream-Ver)
(build ver: 1.14 upstream: 2.02)
(auctex ver: 1.42 upstream: 11.53)
(apel ver: 1.27 upstream: 10.2)
(mule-base ver: 1.46 upstream: No-Upstream-Ver)
(lookup ver: 1.14 upstream: 1.0)
(locale ver: 1.22 upstream: No-Upstream-Ver)
(leim ver: 1.22 upstream: No-Upstream-Ver)
(latin-unity ver: 1.19 upstream: 1.19)
(latin-euro-standards ver: 1.07 upstream: 1.07)
Installed Modules:
-----------------
Features:
--------
(xemacsbug shadow debug vm-sort mail-utils atomic-extents mail-abbrevs
vm-mouse vm-virtual vm-delete vm-mime vm-page vm-undo vm-toolbar vm-motion
vm-summary tapestry vm-folder vm-misc vm-window hyper-apropos add-log
find-func view-less view efs-cu timer-funcs ipa-im-utf-8 cyrillic-im-utf-8
quail latin-unity-tables latin-unity-vars latin-unity erc-autojoin
erc-button wid-edit erc-ring erc-pcomplete pcomplete erc-track erc-match
erc-fill erc-stamp erc-netsplit erc erc-backend erc-compat time-date
parse-time thingatpt pp format-spec mspools non-standard-1252 vm-pine
vm-message vm-minibuf vm-rfaddons overlay vm-macro vm-reply sendmail cookie1
vm-autoload vm-vars highlight-headers vm-version vm crypt crypt++
crypt+pgp-pub scroll-in-place redo desktop savehist alist
after-save-commands mail-extr timezone mailcrypt rfc822 comint ring mmm
advice advice-preload tex-site vm-startup lazy-shot font-lock time cus-face
latin-unity-latin10 latin-unity-latin9 latin-unity-latin8 latin-unity-latin7
latin-euro-standards latin-euro-latin10 latin-euro-latin9 latin-euro-latin8
latin-euro-latin7 gnuserv xslt-process-autoloads xemacs-devel-autoloads
xemacs-base-autoloads vm-autoloads view-process-autoloads vc-cc-autoloads
vc-autoloads tpu-autoloads time-autoloads textools-autoloads
text-modes-autoloads texinfo-autoloads strokes-autoloads speedbar-autoloads
sml-mode-autoloads sieve-autoloads sh-script-autoloads sgml-autoloads
scheme-autoloads rmail-autoloads reftex-autoloads python-modes-autoloads
prog-modes-autoloads perl-modes-autoloads pcl-cvs-autoloads pc-autoloads
os-utils-autoloads oo-browser-autoloads ocaml-autoloads net-utils-autoloads
mmm-mode-autoloads misc-games-autoloads mailcrypt-autoloads
mail-lib-autoloads ispell-autoloads ilisp-autoloads igrep-autoloads
ibuffer-autoloads gnats-autoloads general-docs-autoloads games-autoloads
fsf-compat-autoloads frame-icon-autoloads forms-autoloads footnote-autoloads
eterm-autoloads ess-autoloads erc-autoloads emerge-autoloads elib-autoloads
eieio-autoloads efs-autoloads edt-autoloads edit-utils-autoloads
ediff-autoloads edebug-autoloads ecrypto-autoloads dired-autoloads
dictionary-autoloads debug-autoloads cc-mode-autoloads calendar-autoloads
calc-autoloads c-support-autoloads build-autoloads auctex-autoloads
apel-autoloads mule-base-autoloads lookup-autoloads locale-autoloads
leim-autoloads latin-unity-autoloads latin-euro-standards-autoloads
modules-autoloads mule-autoloads auto-autoloads rsz-minibuf auto-show
fontl-hooks canna-leim tibetan lao devanagari indian slovenian czech
romanian ccl code-cmds gutter-items behavior itimer auto-save lisp-mode
easymenu easy-mmode iso8859-1 page buff-menu lib-complete loadhist cus-file
derived newcomment env text-props frame obsolete cus-start custom widget
cl-extra cl cl-19 packages backquote unicode tty-frames tty unix-processes
multicast network-streams subprocesses modules berkeley-db md5 xemacs mule
gutter lisp-float-type file-coding linux devices base64)
Recent keystrokes:
-----------------
e n d - r e p r e s e n t a t i o n s C-b C-r b u f
f e r - d e f a u l t C-r C-p C-p C-n C-n C-n C-r c
o d i n g - s y s t e m C-r C-r C-s C-s C-r C-r C-r
ESC O A ESC O A ESC O A ESC O A ESC x r e p o r t -
x e m a c s - b u g RET C-g ESC x ESC p RET
Recent messages (most recent first):
-----------------------------------
Quit
Loading xemacsbug...done
Loading xemacsbug...
12:37pm 0.22
12:37pm 0.08
Quit
Counting messages in ~/mail/spam.spool... done
Counting messages in ~/mail/spam.spool...
12:36pm 0.16
utf-8
throwing utf-8
(utf-8 nil)
(utf-8 (511 . 1536) (0 . 0))
sys is utf-8
(511 . 1536) (0 . 0)
12:36pm 0.21
12:35pm 0.30
Quit
(511 . 1536)
12:35pm 0.23
--
Santa Maradona, priez pour moi!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: Full Unicode Pathnames
17 years, 5 months
Glynn Clements
Benson Margulies wrote:
> Have you given any thought to supporting full Unicode file names on
> Win32? The semi-obvious strategy is to represent in UTF-8 in lisp and
> down to the bottom of the C code, and then transcode and call the W
> APIs.
The problem with using UTF-8 is that you still have to transcode to
the system codepage when using any 8-bit interfaces (e.g. passing data
to subprocesses). Although there is a UTF-8 codepage (CP-65001), I've
never encountered anyone using it as their system codepage.
--
Glynn Clements <glynn(a)gclements.plus.com>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: [Q] Handle bytes in the range 0x80-0xC0 better when dealing with ISO-IR 196.
17 years, 5 months
David Kastrup
Aidan Kehoe <kehoea(a)parhasard.net> writes:
> Ar an tríú lá is fiche de mí na Samhain, scríobh David Kastrup:
>
> > > 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:
> > >
> > > (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.
> >
> > Here is what Emacs 22 returns:
> >
> > #("\xc2\x80\xc2\x80" 0 2 (display #("\\200" 0 4 (face escape-glyph)) help-echo utf-8-help-echo untranslated-utf-8 128) 2 4 (display #("\\200" 0 4 (face escape-glyph)) help-echo utf-8-help-echo untranslated-utf-8 128))
> >
> > > And will be ignored by them when writing:
> > >
> > > (encode-coding-string (decode-coding-string "\x80\x80" 'utf-8) 'utf-8)
> > > => ""
> >
> > Here is what Emacs 22 returns:
> >
> > "\200\200"
>
> Quite an old GNU Emacs 23.0.0 gives me this:
>
> (encode-coding-string "\x80\x80" 'utf-8)
> => "\200\200"
>
> (decode-coding-string "\x80\x80" 'utf-8)
> => "\200\200"
>
> Savannah’s being unco-operative about allowing me to cvs update, otherwise
> it would be worth reporting the former as a bug.
I am not sure. It is round-trip, but of course it leaves bad bytes in
the buffer. And some of them might combine badly with others.
> Were it my implementation, I would regard the latter as a bug too.
Yes, could be worth working over. I suppose that "Emacs 23" will only
start getting a really solid beating once it is moved to HEAD.
> > > 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.
> >
> > Not just for "unicode-oriented". The recipe should be workable for
> > the iso-latin-* stuff as a file encoding, too, I think.
>
> Hmm? _Are_ there invalid sequences for the ISO-8859-N file
> encodings?
If the file is in iso-8859-N, but the locale and/or the process
encoding (which might come from a master file in utf-8 that includes a
subfile in iso-*)...
The possibilities for complications are pretty much endless. Polish
people, for example, tend to use Latin-2 encodings in their files, but
Latin-1 locales. They just "know" which characters will be displayed
wrong and how, and in a Polish locale, more things go wrong than in an
English one.
You don't really want to know the number of idiocies I have to cater
for in connection with AUCTeX/TeX/LaTeX.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: cygwin version of xemacs-21.4.19 coredumps when trying to Page setup.../Print <buffer> to...
17 years, 5 months
Aidan Kehoe
Ar an dara lá is fiche de mí na Samhain, scríobh Dr. Volker Zell:
> Wow.... this fixes the crash.
>
> The Windows version now pops up the windows printer dialogs, but the X
> version gives:
>
> Feature not yet implemented: "Dialog box type", page-setup
> Feature not yet implemented: "Dialog box type", print
>
> Isn't this supposed to work out of the box ?
Of course! :-) .
You’re right, it makes more sense for the X11 version to use LPR. And when
that day comes that someone makes it possible to have X11 and Win32 frames
simultaneously in a single XEmacs, it should choose based on the selected
frame.
--
Santa Maradona, priez pour moi!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: [Q] Handle bytes in the range 0x80-0xC0 better when dealing with ISO-IR 196.
17 years, 5 months
Aidan Kehoe
Ar an dara lá is fiche de mí na Samhain, scríobh Stephen J. Turnbull:
> > + /* ASCII, or the lower control characters.
> > +
> > + Perhaps we should signal an error if the character is in
> > + the range 0x80-0xc0; this is illegal UTF-8. */
> > + Dynarr_add (dst, (c & 0x7f));
>
> Please do. This is corrupting the data.
>
> I don't have a clue how to recover from it, but the user should at
> least be told.
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:
(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)
=> ""
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.
--
Santa Maradona, priez pour moi!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
[buglet] xemacs -nw & smilies in gnus
17 years, 5 months
Giacomo Boffi
i rebuilt xemacs beta
(insert (emacs-version)) XEmacs 21.5 (beta27) "fiddleheads"
(+CVS-20061107) [Lucid] (i686-pc-linux, Mule) of Wed Nov 8 2006 on
boffi95
and now gnus "hilights" smilies in article buffers even when xemacs
runs in a terminal (emulator), more precisely gnus inserts in the
buffer the full pathname of the xpm file, that it is considered a
single gliph (i.e., i can place the cursor before or after the full
pathname, but not into it)
note that (a) gnus displays correctly smilies under X, (b) until a
couple of weeks ago gnus *did* something to the smilies, but them were
rendered with ascii characters
(insert (gnus-version)) Gnus v5.10.7
grazie, ciao
g
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: Bug and Patch: XEmacs W3 Doesn't display anything
17 years, 5 months
Mike FABIAN
"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> さんは書きました:
> Mike FABIAN writes:
>
> > Is it correct? or was font.el omitted on purpose?
>
> It is omitted on purpose; we have a more recent, more
> xemacs-compatible version of that file in core. If the problem occurs
> in a moderately fresh checkout of 21.5, they most likely what happened
> is that I deleted some relevant functions because I couldn't find them
> used anywhere. I'll put them back.
>
> What version(s) of XEmacs is(are) showing the problem?
XEmacs 21.5.27 CVS checkout from 20060705.
--
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