October 2000 - XEmacs-Beta - XEmacs Mailing List Archives

assertion of CHARSET_BY_LEADING_BYTE fails on gcc-2.95.2 20000220. 24 years, 1 month

MIYASHITA Hisashi (=?ISO-2022-JP?B?GyRCNVwyPBsoQiAbJEI+MBsoQjpISU1J?=)

I happened to a difficult problem at the newest version of XEmacs taken from CVS. (My environment is Debian GNU/Linux (potato), the latest version.) -- (gdb) run Starting program: /home/himi/OpenCVS/xemacs/xemacs/src/xemacs Fatal error: assertion failed, file mule-charset.h, line 569, lb >= 0x80 && lb <= 0xFF (gdb) bt #0 0x402be931 in kill () from /lib/libc.so.6 #1 0x402be618 in raise () from /lib/libc.so.6 #2 0x402bfc71 in abort () from /lib/libc.so.6 #3 0x80bf72b in assert_failed (file=0x828d1c9 "mule-charset.h", line=569, expr=0x828d1d8 "lb >= 0x80 && lb <= 0xFF") at emacs.c:3189 #4 0x81f187e in x_keysym_to_character (keysym=1244) at mule-charset.h:569 #5 0x81f1b51 in x_has_keysym (keysym=1244, hash_table=140042288, with_modifiers=1) at event-Xt.c:306 #6 0x81f1d7a in x_reset_key_mapping (d=0x8598df0) at event-Xt.c:406 #7 0x81f1e58 in x_reset_modifier_mapping (d=0x8598df0) at event-Xt.c:461 #8 0x81f789e in x_init_modifier_mapping (d=0x8598df0) at event-Xt.c:625 #9 0x81eef6e in x_init_device (d=0x8598df0, props=137214908) at device-x.c:803 #10 0x80adf1e in Fmake_device (type=137351036, connection=137214908, props=137214908) at device.c:588 #11 0x80c5c6d in Ffuncall (nargs=3, args=0xbffff2f8) at eval.c:3528 ...(snip)... -- This assertion failure is caused by CHARSET_BY_LEADING_BYTE(a)mule-charset.h. -- INLINE_HEADER Lisp_Object CHARSET_BY_LEADING_BYTE (Bufbyte lb); INLINE_HEADER Lisp_Object CHARSET_BY_LEADING_BYTE (Bufbyte lb) { extern struct charset_lookup *chlook; type_checking_assert (lb >= 0x80 && lb <= 0xFF); return chlook->charset_by_leading_byte[lb - 128]; } -- This function is embedded into x_keysym_to_character()(a)event-Xt.c And this part in x_keysym_to_character calls CHARSET_BY_LEADING_BYTE(), and fails because my X server have KATAKANA_JISX0201 keysyms. -- #define USE_CHARSET(var,cs) \ ((var) = CHARSET_BY_LEADING_BYTE (LEADING_BYTE_##cs)) ...(snip) case 4: /* Katakana */ USE_CHARSET (charset, KATAKANA_JISX0201); if ((keysym & 0xff) > 0xa0) code = keysym & 0x7f; break; -- Expanding the macro of USE_CHARSET, we obtain an expression, CHARSET_BY_LEADING_BYTE(LEADING_BYTE_KATAKANA_JISX0201). As you know, LEADING_BYTE_KATAKANA_JISX0201 is constant, its value is 0x89. Therefore, the following assertion in CHARSET_BY_LEADING_BYTE must be passed. -- type_checking_assert (lb >= 0x80 && lb <= 0xFF); -- At this time, I doubted soundness of the C-compiler gcc-2.95.2 20000220. Then, I changed the optimization option from -O3 to -O0, and remade xemacs. This xemacs works well. Next, I restore the optimization option to -O3, then, disassemble the corresponding part to x_keysym_to_character() as follows. -- (gdb) i reg eip eip 0x81f187e 136255614 (gdb) disas Dump of assembler code for function x_keysym_to_character: 0x81f1790 <x_keysym_to_character>: push %ebp 0x81f1791 <x_keysym_to_character+1>: mov %esp,%ebp 0x81f1793 <x_keysym_to_character+3>: sub $0xc,%esp 0x81f1796 <x_keysym_to_character+6>: push %edi 0x81f1797 <x_keysym_to_character+7>: push %esi 0x81f1798 <x_keysym_to_character+8>: push %ebx 0x81f1799 <x_keysym_to_character+9>: mov 0x8(%ebp),%ebx 0x81f179c <x_keysym_to_character+12>: mov $0x1,%esi 0x81f17a1 <x_keysym_to_character+17>: xor %edi,%edi 0x81f17a3 <x_keysym_to_character+19>: cmp $0x9f,%bl 0x81f17a6 <x_keysym_to_character+22>: ja 0x81f17b2 <x_keysym_to_character+34> 0x81f17a8 <x_keysym_to_character+24>: mov 0x82b50d4,%eax 0x81f17ad <x_keysym_to_character+29>: jmp 0x81f1a8a <x_keysym_to_character+762> 0x81f17b2 <x_keysym_to_character+34>: mov %ebx,%eax 0x81f17b4 <x_keysym_to_character+36>: shr $0x8,%eax 0x81f17b7 <x_keysym_to_character+39>: cmp $0x20,%eax 0x81f17ba <x_keysym_to_character+42>: ja 0x81f196b <x_keysym_to_character+475> 0x81f17c0 <x_keysym_to_character+48>: jmp *0x828ebe0(,%eax,4) 0x81f17c7 <x_keysym_to_character+55>: add $0xfffffffc,%esp 0x81f17ca <x_keysym_to_character+58>: push $0x828d1d8 0x81f17cf <x_keysym_to_character+63>: push $0x239 0x81f17d4 <x_keysym_to_character+68>: push $0x828d1c9 0x81f17d9 <x_keysym_to_character+73>: call 0x80bf654 <assert_failed> 0x81f17de <x_keysym_to_character+78>: add $0x10,%esp 0x81f17e1 <x_keysym_to_character+81>: mov 0x82b55e0,%eax 0x81f17e6 <x_keysym_to_character+86>: mov 0x4(%eax),%esi 0x81f17e9 <x_keysym_to_character+89>: jmp 0x81f1966 <x_keysym_to_character+470> .... (omitted, this part deals with other case than KATAKANA_JISX0201) .... 0x81f1867 <x_keysym_to_character+215>: add $0xfffffffc,%esp 0x81f186a <x_keysym_to_character+218>: push $0x828d1d8 0x81f186f <x_keysym_to_character+223>: push $0x239 0x81f1874 <x_keysym_to_character+228>: push $0x828d1c9 0x81f1879 <x_keysym_to_character+233>: call 0x80bf654 <assert_failed> 0x81f187e <x_keysym_to_character+238>: add $0x10,%esp <===== return address points here!!!!!!!!!!!! 0x81f1881 <x_keysym_to_character+241>: mov 0x82b55e0,%eax 0x81f1886 <x_keysym_to_character+246>: mov 0x24(%eax),%esi 0x81f1889 <x_keysym_to_character+249>: cmp $0xa0,%bl 0x81f188c <x_keysym_to_character+252>: jbe 0x81f196b <x_keysym_to_character+475> -- If you can read this asssembler code, you know that this part obviously calls assert_failed unconditionally. That means that GCC judged the expression of the assertion is always false. I suspected this problem is caused by type conversion, because if GCC always fails to evaluate such simple expressions as (lb >= 0x80 && lb <= 0xFF), GCC 2.95 should be useless. Therefore, I modified this part as follows. -- INLINE_HEADER Lisp_Object CHARSET_BY_LEADING_BYTE (Bufbyte lb); INLINE_HEADER Lisp_Object CHARSET_BY_LEADING_BYTE (Bufbyte lb) { extern struct charset_lookup *chlook; int test = lb; type_checking_assert (test >= 0x80 && test <= 0xFF); return chlook->charset_by_leading_byte[lb - 128]; } -- And I dissassembled this part, -- 0x81f17fa <x_keysym_to_character+106>: lea 0x0(%esi),%esi 0x81f1800 <x_keysym_to_character+112>: mov 0x82b54c0,%eax 0x81f1805 <x_keysym_to_character+117>: mov 0x24(%eax),%esi 0x81f1808 <x_keysym_to_character+120>: cmp $0xa0,%dl 0x81f180b <x_keysym_to_character+123>: jbe 0x81f185f <x_keysym_to_character+207> 0x81f180d <x_keysym_to_character+125>: jmp 0x81f185a <x_keysym_to_character+202> -- The assertion is cleaned because the expression can be statically evaluated, and it is always true. That's correct. Of course, this xemacs works well. >From these situations, I conludeded that this problem is caused by GCC's bug. Do you reproduce this problem also in your environment? from himi

2 participants
1 comments

Re: Menu-display bug? 24 years, 1 month

Markus Alt

Kai Haberzettl wrote: > > OK, I don't know if this is a problem of my windowmanager or of > XEmacs, but here goes: > > - XEmacs beta 36 from CVS ; Windowmaker 0.62.1 > > - pull down a menu on the XEmacs menubar > > - minimize XEmacs, not with the mouse but with the keyboard shortcut > > -> the menu stays on the screen and will not react to any input until > you resize XEmacs again. > > Kai Just to confirm this: I see the same behaviour with 21.2.36 and also an old 21.1.10. Windowmanager is kwm 0.14 patchlevel 3 of KDE 1.1.2. This is not the correct behaviour, agreed. The menu should either disappear when pressing <Alt> or nothing should happen at all, i.e. window should not be minimized, IMHO. But on the other hand - how often do you this, I mean minimizing an application's window in which you've just opened a pull-down menu? ;-) Markus

1 participants
0 comments

Crash 24 years, 1 month

Raymond Toy

xemacs 21.2.36, built from full tarball using gcc 2.95.2 on Solaris 2.7. I had just made a change to my Makefile, pressed C-x C-s to save it, and probably had also typed ahead with C-c m (personal keybinding for M-x compile). It crashed. No lisp backtrace, but the C backtrace is appended. Ray #0 0xfeb16870 in _libc_kill () from /usr/lib/libc.so.1 #1 0xaac24 in fatal_error_signal (sig=6) at emacs.c:531 #2 <signal handler called> #3 0xfeb16870 in _libc_kill () from /usr/lib/libc.so.1 #4 0xfeab92a4 in abort () from /usr/lib/libc.so.1 #5 0xadcf4 in assert_failed (file=0x5ce <Address 0x5ce out of bounds>, line=2783936, expr=0x2a7ac0 "start <= bmax") at emacs.c:3189 #6 0x19fdc4 in make_lisp_buffer_stream_1 (buf=0x6f3c00, start=8388609, end=3173, flags=3, mode=0x2a79d8 "r") at lstream.c:1486 #7 0x19ff70 in make_lisp_buffer_input_stream (buf=0x6f3c00, start=8388609, end=3173, flags=3) at lstream.c:1526 #8 0x13413c in Fwrite_region_internal (start=3, end=10729060, filename=7444276, append=3274756, visit=3274780, lockname=10535780, codesys=5754240) at fileio.c:3298 #9 0xb64e8 in Ffuncall (nargs=7, args=0xffbec144) at eval.c:3528 #10 0x7cc64 in execute_optimized_program (program=0xffbec144 "", stack_depth=7, constants_data=0x5a5e10) at bytecode.c:746 #11 0x7c494 in funcall_compiled_function (fun=5917684, nargs=7, args=0xffbec3d0) at bytecode.c:518 #12 0xb6610 in Ffuncall (nargs=7, args=0xffbec3b0) at eval.c:3563 #13 0xb6d74 in Fapply (nargs=2, args=0xffbec570) at eval.c:3804 #14 0xb65c4 in Ffuncall (nargs=2, args=0xffbec56c) at eval.c:3549 #15 0x7cc64 in execute_optimized_program (program=0xffbec56c "", stack_depth=2, constants_data=0x830910) at bytecode.c:746 #16 0x7c494 in funcall_compiled_function (fun=4045692, nargs=8, args=0xffbec7d0) at bytecode.c:518 #17 0xb6610 in Ffuncall (nargs=8, args=0xffbec7c8) at eval.c:3563 #18 0xb7924 in call8 (fn=8638828, arg0=3392380, arg1=3, arg2=6347, arg3=7444276, arg4=3274756, arg5=3274780, arg6=10535780, arg7=5754240) at eval.c:4320 #19 0x133a98 in Fwrite_region_internal (start=3, end=6347, filename=7444276, append=3274756, visit=3274780, lockname=10535780, codesys=5754240) at fileio.c:3190 #20 0xb64e8 in Ffuncall (nargs=7, args=0xffbecaf4) at eval.c:3528 #21 0x7cc64 in execute_optimized_program (program=0xffbecaf4 "", stack_depth=7, constants_data=0x5a5e10) at bytecode.c:746 #22 0x7c494 in funcall_compiled_function (fun=5917684, nargs=7, args=0xffbecd80) at bytecode.c:518 #23 0xb6610 in Ffuncall (nargs=7, args=0xffbecd60) at eval.c:3563 #24 0xb6d74 in Fapply (nargs=2, args=0xffbecf20) at eval.c:3804 #25 0xb65c4 in Ffuncall (nargs=2, args=0xffbecf1c) at eval.c:3549 #26 0x7cc64 in execute_optimized_program (program=0xffbecf1c "", stack_depth=2, constants_data=0x830810) at bytecode.c:746 #27 0x7c494 in funcall_compiled_function (fun=4045692, nargs=8, args=0xffbed180) at bytecode.c:518 #28 0xb6610 in Ffuncall (nargs=8, args=0xffbed178) at eval.c:3563 #29 0xb7924 in call8 (fn=8639020, arg0=3392380, arg1=3, arg2=6347, arg3=7444276, arg4=3274756, arg5=3274780, arg6=10535780, arg7=5754240) at eval.c:4320 #30 0x133a98 in Fwrite_region_internal (start=3, end=6347, filename=7444276, append=3274756, visit=3274780, lockname=10535780, codesys=5754240) at fileio.c:3190 #31 0xb64e8 in Ffuncall (nargs=7, args=0xffbed4a4) at eval.c:3528 #32 0x7cc64 in execute_optimized_program (program=0xffbed4a4 "", stack_depth=7, constants_data=0x5a5e10) at bytecode.c:746 #33 0x7c494 in funcall_compiled_function (fun=5917684, nargs=6, args=0xffbed730) at bytecode.c:518 #34 0xb6610 in Ffuncall (nargs=6, args=0xffbed714) at eval.c:3563 #35 0x7cc64 in execute_optimized_program (program=0xffbed714 "", stack_depth=6, constants_data=0x513fd0) at bytecode.c:746 #36 0x7c494 in funcall_compiled_function (fun=5287068, nargs=2, args=0xffbed988) at bytecode.c:518 #37 0xb6610 in Ffuncall (nargs=2, args=0xffbed97c) at eval.c:3563 #38 0x7cc64 in execute_optimized_program (program=0xffbed97c "", stack_depth=2, constants_data=0x503510) at bytecode.c:746 #39 0x7c494 in funcall_compiled_function (fun=5287152, nargs=0, args=0xffbedbe8) at bytecode.c:518 #40 0xb6610 in Ffuncall (nargs=0, args=0xffbedbe4) at eval.c:3563 #41 0x7cc64 in execute_optimized_program (program=0xffbedbe4 "", stack_depth=0, constants_data=0x503610) at bytecode.c:746 #42 0x7c494 in funcall_compiled_function (fun=5287124, nargs=0, args=0xffbede50) at bytecode.c:518 #43 0xb6610 in Ffuncall (nargs=0, args=0xffbede4c) at eval.c:3563 #44 0x7cc64 in execute_optimized_program (program=0xffbede4c "", stack_depth=0, constants_data=0x50b710) at bytecode.c:746 #45 0x7c494 in funcall_compiled_function (fun=5287012, nargs=1, args=0xffbee0b0) at bytecode.c:518 #46 0xb6610 in Ffuncall (nargs=1, args=0xffbee0a8) at eval.c:3563 #47 0x83364 in Fcall_interactively (function=4967076, record_flag=3274756, keys=3274756) at callint.c:946 #48 0xb4d98 in Fcommand_execute (cmd=4967076, record=3274756, keys=3274756) at eval.c:2970 #49 0x1130dc in execute_command_event (command_builder=0x41d3c0, event=10480780) at event-stream.c:3860 #50 0x113b2c in Fdispatch_event (event=10480780) at event-stream.c:4179 #51 0x8d31c in Fcommand_loop_1 () at cmdloop.c:579 #52 0x8d05c in command_loop_1 (dummy=6623872) at cmdloop.c:494 #53 0xb1410 in condition_case_1 (handlers=3274852, bfun=0x8d010 <command_loop_1>, barg=3274756, hfun=0x8d4fc <cmd_error>, harg=3274756) at eval.c:1651 #54 0x8d60c in command_loop_2 (dummy=3274756) at cmdloop.c:256 #55 0xb0f80 in internal_catch (tag=3359084, func=0x8d5c0 <command_loop_2>, arg=3274756, threw=0x0) at eval.c:1317 #56 0x8c958 in initial_command_loop (load_me=579008) at cmdloop.c:305 #57 0xac94c in xemacs_21_2_b36_sparc_sun_solaris2_7 (argc=1, argv=0xffbeea1c, envp=0xffbeea24, restart=0) at emacs.c:2228 #58 0xad170 in main (argc=1, argv=0xffbeea1c, envp=0xffbeea24) at emacs.c:2657

1 participants
0 comments

Re: 2000-10-15: http://xemacs.sourceforge.net/ featuring XHTML 1.0 now 24 years, 1 month

Adrian Aichner

>>>>> "Stephen" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: >>>>> "Terje" == Terje Bless <link(a)tss.no> writes: Terje> PSGML doesn't complain about any of those pages, it's Terje> broken in interesting ways. :-) Stephen> PSGML as such is a very complex, highly accurate Stephen> heuristic; that's why its validate option uses an Stephen> external program. Stephen> Obviously, we should too. Yes, please do :-) xemacsweb/batch-psgml-validate.el currently uses sgml-next-trouble-spot which is known not to be able to fully validate an SGML document: (Info-goto-node "(psgml)Validate") BUT! It does a pretty good job and is platform-independant (I use it with XEmacs/PSGML in a native Windows NT build). SP built fine on NT, but I haven't been able to use it successfully yet. Best regards, Adrian Stephen> -- Stephen> University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Stephen> Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 Stephen> _________________ _________________ _________________ _________________ Stephen> What are those straight lines for? "XEmacs rules." -- Adrian Aichner <adrian(a)xemacs.org>, http://www.xemacs.org

1 participants
0 comments

Re: xemacsweb: Document Acrobat Reader PDF bug 24 years, 1 month

Adrian Aichner

>>>>> "Stephen" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: >>>>> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes: >>>>> "Stephen" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: APA> Hi Stephen, APA> could you please try commiting this patch? Stephen> Do I use ssh? what identity? do I need to make a new Stephen> one or has it been transferred from cvs.xemacs.org? Yes, yours (yaseppochi), please follow http://sfdocs.sourceforge.net/sfdocs/display_topic.php?topicid=29 if you havn't done that already. Be aware of SFs 6 hour cron delay. It used to be possible to know when the next update will be. I can't find the page in theSF site docs now. Please try this and let me know how that goes: cvs -w -f -z3 -dyaseppochi＠cvs.sourceforge.net:/cvsroot/xemacs commit -m \ "xemacsweb: Document Acrobat Reader PDF bug \ <14821.45049.395433.328650(a)turnbull.sk.tsukuba.ac.jp>" \ Documentation/ChangeLog Documentation/index.content You'll have to use ssh1 and set CVS_RSH if you haven't done so. Please see http://sourceforge.net/cvs/?group_id=11, which is referenced from http://xemacs.sourceforge.net/About/Website.html#XWCR Hope this helps, Adrian Stephen> -- Stephen> University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Stephen> Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 Stephen> _________________ _________________ _________________ _________________ Stephen> What are those straight lines for? "XEmacs rules." -- Adrian Aichner <adrian(a)xemacs.org>, http://www.xemacs.org

1 participants
0 comments

Re: 2000-10-15: http://xemacs.sourceforge.net/ featuring XHTML 1.0 now 24 years, 1 month

Adrian Aichner

>>>>> "Terje" == Terje Bless <link(a)tss.no> writes: Terje> On 15.10.00 at 23:12, Adrian Aichner <adrian(a)xemacs.org> wrote: >> As some of you know, new website content is contained in .content >> files, which are pre-processed into .html files by genpage and then >> validated against their DTD with XEmacs/PSGML. Terje> <URL:http://validator.w3.org/check?uri=http://xemacs.sourceforge.net/>. Hello Terje, thanks for testing! This patch should take care of the problem: ChangeLog: 2000-10-16 Adrian Aichner <adrian(a)xemacs.org> * template.html: Using Ampersands in Attribute Values (see C.12 in http://www.w3.org/TR/2000/REC-xhtml1-20000126/#guidelines). Index: template.html =================================================================== RCS file: /cvsroot/xemacs/xemacsweb/template.html,v retrieving revision 1.18 diff -u -u -r1.18 template.html --- template.html 2000/10/15 18:53:12 1.18 +++ template.html 2000/10/15 22:46:30 ＠＠ -177,7 +177,7 ＠＠  <td rowspan="1" colspan="6" bgcolor="#CCCCCC"><img src="" alt="" height="10" width="1"/></td></tr> </table> -<small>Conform with <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" +<small>Conform with &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <br clear="none"/>Automatically validated by PSGML 1.2.1, 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid.</small> </body> Terje> -- Terje> As a cat owner, I know this for a fact... Terje> Nothing says "I love you" like a decapitated gopher on your front porch. -- Adrian Aichner <adrian(a)xemacs.org>, http://www.xemacs.org

3 participants
3 comments

DRI cvspolicy.txt 24 years, 1 month

Karl M. Hegbloom

An interesting document regarding CVS policy is found at http://dri.sourceforge.net/cvspolicy.txt

1 participants
0 comments

EFS fixes 24 years, 1 month

Michael Sperber

I've checked a new version of EFS into CVS. It has only one minor bugfix meant to correct the spurious CWD problem. I'd appreciate if people could test it before the next package release. Note that it doesn't matter a damn what architectures you run EFS *on*. It does matter what kind of ftp server you connect *to*. The more kinds the better. Steve: please check back with me before the next package release. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla

2 participants
1 comments

Re: 2000-10-15: http://xemacs.sourceforge.net/ featuring XHTML 1.0 now 24 years, 1 month

Adrian Aichner

>>>>> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes: <foot in mouth /> This is the correct patch: Index: template.html =================================================================== RCS file: /cvsroot/xemacs/xemacsweb/template.html,v retrieving revision 1.18 diff -u -u -r1.18 template.html --- template.html 2000/10/15 18:53:12 1.18 +++ template.html 2000/10/15 23:01:55 ＠＠ -158,7 +158,7 ＠＠ <br clear="none"/> Hosted by <a href="http://sourceforge.net"> - <img src="http://sourceforge.net/sflogo.php?group_id=11&type=1" + <img src="http://sourceforge.net/sflogo.php?group_id=11&type=1" width="88" height="31" border="0" Adrian >>>>> "Terje" == Terje Bless <link(a)tss.no> writes: Terje> On 15.10.00 at 23:12, Adrian Aichner <adrian(a)xemacs.org> wrote: >>> As some of you know, new website content is contained in .content >>> files, which are pre-processed into .html files by genpage and then >>> validated against their DTD with XEmacs/PSGML. Terje> <URL:http://validator.w3.org/check?uri=http://xemacs.sourceforge.net/>. APA> Hello Terje, APA> thanks for testing! APA> This patch should take care of the problem: APA> ChangeLog: APA> 2000-10-16 Adrian Aichner <adrian(a)xemacs.org> APA> * template.html: Using Ampersands in Attribute Values (see C.12 in APA> http://www.w3.org/TR/2000/REC-xhtml1-20000126/#guidelines). APA> Index: template.html APA> =================================================================== APA> RCS file: /cvsroot/xemacs/xemacsweb/template.html,v APA> retrieving revision 1.18 APA> diff -u -u -r1.18 template.html APA> --- template.html 2000/10/15 18:53:12 1.18 APA> +++ template.html 2000/10/15 22:46:30 APA> ＠＠ -177,7 +177,7 ＠＠ APA>  APA> <td rowspan="1" colspan="6" bgcolor="#CCCCCC"><img src="" alt="" height="10" width="1"/></td></tr> APA> </table> APA> -<small>Conform with <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" APA> +<small>Conform with &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" APA> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> APA> <br clear="none"/>Automatically validated by PSGML 1.2.1, 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid.</small> APA> </body> Terje> -- Terje> As a cat owner, I know this for a fact... Terje> Nothing says "I love you" like a decapitated gopher on your front porch. APA> -- APA> Adrian Aichner <adrian(a)xemacs.org>, http://www.xemacs.org -- Adrian Aichner <adrian(a)xemacs.org>, http://www.xemacs.org

1 participants
0 comments

2000-10-15: http://xemacs.sourceforge.net/ featuring XHTML 1.0 now 24 years, 1 month

Adrian Aichner

Hello All! As some of you know, new website content is contained in .content files, which are pre-processed into .html files by genpage and then validated against their DTD with XEmacs/PSGML. This whole process is triggered by commits of XEmacs developers. I have converted the genpage template template.html and all (currently 99) .content files to comply with the XHTML 1.0 DTD. This puts us in the enviable position of moving to XML easily whenever we decide to do so. Needless to say that all 99 auto-generated .html files fully comply with XHTML 1.0. I have manually fixed all validation errors in my local working directory of xemacsweb prior to commiting the changes. I am asking you all now to give http://xemacs.sourceforge.net/ a hard time and report any problem with site content to XEmacs Web Maintainers <xemacs-webmaint(a)xemacs.org> and XEmacs Beta List <xemacs-beta(a)xemacs.org> or even to me :-) at <adrian(a)xemacs.org>. The entire website (CVS module xemacsweb) has been rtagged pre-xhtml prior to this massive change. BTW: The sourceforge CVS server was able to swallow my big commit[1] in one piece and the automatic website update went well. Best regards, Adrian Footnotes: [1] cvs -f -z3 -dadriana＠cvs.sourceforge.net:/cvsroot/xemacs commit -m \ "Re: [xemacsweb PATCH] Convert ALL .content files to XHTML 1.0 \ Transitional <uk8bakktz.fsf(a)ecf.teradyne.com>" ChangeLog \ batch-psgml-validate.el index.content template.html About/ChangeLog \ About/Website.content About/XEmacsVsGNUemacs.content \ About/created.content About/index.content About/Screenshots/ChangeLog \ About/Screenshots/index.content Architecting-XEmacs/ChangeLog \ Architecting-XEmacs/I18N.content \ Architecting-XEmacs/color-list.content \ Architecting-XEmacs/compat-package.content \ Architecting-XEmacs/custom.content \ Architecting-XEmacs/dialog-boxes.content \ Architecting-XEmacs/dot-xemacs.content \ Architecting-XEmacs/drag-n-drop.content \ Architecting-XEmacs/dynamic-modules.content \ Architecting-XEmacs/elisp-structures.content \ Architecting-XEmacs/enabling-extensions.content \ Architecting-XEmacs/encourage.content \ Architecting-XEmacs/extent.content \ Architecting-XEmacs/faster-elisp.content \ Architecting-XEmacs/index.content \ Architecting-XEmacs/init-files.content \ Architecting-XEmacs/intro.content \ Architecting-XEmacs/keybinding-schemes.content \ Architecting-XEmacs/keyboard-actions.content \ Architecting-XEmacs/lisp-engine-replacement.content \ Architecting-XEmacs/lisp-engine.content \ Architecting-XEmacs/lisp-interface.content \ Architecting-XEmacs/long-term-I18N.content \ Architecting-XEmacs/mail-home.content \ Architecting-XEmacs/misc-user-event.content \ Architecting-XEmacs/mule-plan.content \ Architecting-XEmacs/package-changes.content \ Architecting-XEmacs/packages.content \ Architecting-XEmacs/pointer.content \ Architecting-XEmacs/profiling.content \ Architecting-XEmacs/proto.content \ Architecting-XEmacs/redisplay.content \ Architecting-XEmacs/senstive-callbacks.content \ Architecting-XEmacs/showstoppers.content \ Architecting-XEmacs/symbol-value-handlers.content \ Architecting-XEmacs/toolbar-customization.content \ Architecting-XEmacs/translation-macros.content \ Architecting-XEmacs/unexec.content \ Architecting-XEmacs/version-number.content \ Architecting-XEmacs/website.content \ Architecting-XEmacs/windows-I18N.content \ Architecting-XEmacs/windows-install.content \ Architecting-XEmacs/windows-key-bindings.content \ Architecting-XEmacs/windows-ole.content \ Architecting-XEmacs/windows-printing.content \ Architecting-XEmacs/xemacs-intro.content \ Architecting-XEmacs/xemacs-short-intro.content \ Architecting-XEmacs/xemacs-tour.content Develop/ChangeLog \ Develop/devTeam.content Develop/index.content Develop/jobs.content \ Develop/otherDev.content Documentation/ChangeLog \ Documentation/index.content Documentation/packageGuide.content \ Download/ChangeLog Download/elispPackages.content \ Download/elispSites.content Download/index.content \ Download/optLibs.content FAQ/ChangeLog FAQ/index.content \ FAQ/xemacs-faq.html FAQ/xemacs-faq_1.html FAQ/xemacs-faq_2.html \ FAQ/xemacs-faq_3.html FAQ/xemacs-faq_4.html FAQ/xemacs-faq_5.html \ FAQ/xemacs-faq_6.html FAQ/xemacs-faq_7.html FAQ/xemacs-faq_8.html \ FAQ/xemacs-faq_toc.html FAQ/xemacs-new.html FAQ/old/ChangeLog \ FAQ/old/XEmacs-FAQ-changes.html FAQ/old/index.html \ FAQ/old/xemacs-current.html FAQ/old/xemacs-customization.html \ FAQ/old/xemacs-deleted.html FAQ/old/xemacs-faq.html \ FAQ/old/xemacs-installation.html FAQ/old/xemacs-merge.html \ FAQ/old/xemacs-miscellaneous.html FAQ/old/xemacs-subsystems.html \ FAQ/oldstuff/ChangeLog FAQ/oldstuff/index.html \ FAQ/oldstuff/xemacs-faq_1.html FAQ/oldstuff/xemacs-faq_2.html \ FAQ/oldstuff/xemacs-faq_3.html FAQ/oldstuff/xemacs-faq_4.html \ FAQ/oldstuff/xemacs-faq_5.html FAQ/oldstuff/xemacs-faq_6.html \ FAQ/oldstuff/xemacs-faq_7.html FAQ/oldstuff/xemacs-faq_8.html \ FAQ/oldstuff/xemacs-faq_toc.html FAQ/upload/ChangeLog \ FAQ/upload/xemacs-faq.html FAQ/upload/xemacs-faq_1.html \ FAQ/upload/xemacs-faq_2.html FAQ/upload/xemacs-faq_3.html \ FAQ/upload/xemacs-faq_4.html FAQ/upload/xemacs-faq_5.html \ FAQ/upload/xemacs-faq_6.html FAQ/upload/xemacs-faq_7.html \ FAQ/upload/xemacs-faq_8.html FAQ/upload/xemacs-faq_toc.html \ Install/ChangeLog Install/index.content Languages/German/ChangeLog \ Languages/German/index.content Languages/Japanese/index.content \ Links/ChangeLog Links/customization.content Links/index.content \ Links/install.content Links/troubleshooting.content \ Links/tutorials_1.content Links/tutorials_2.content \ Links/tutorials_3.content Links/tutorials_foot.content \ Links/tutorials_toc.content Releases/21.1.6.content \ Releases/21.1.6.win.content Releases/21.1.7.changelog.content \ Releases/21.1.7.content Releases/21.1.8.content \ Releases/21.2.27.content Releases/21.2.28.content \ Releases/21.2.29.content Releases/21.2.30.content \ Releases/21.2.31.content Releases/21.2.32.content \ Releases/21.2.33.content Releases/21.2.34.content \ Releases/21.2.35.content Releases/21.2.36.content Releases/ChangeLog \ Releases/index.content Releases/patchProb.content -- Adrian Aichner <adrian(a)xemacs.org>, http://www.xemacs.org

2 participants
1 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta October 2000