From aichner at ecf.teradyne.com Sun Feb 26 16:42:07 2017 Content-Type: multipart/mixed; boundary="===============4699393344926805473==" MIME-Version: 1.0 From: Adrian Aichner To: xemacs-beta at xemacs.org Subject: Re: PSGML's syntax table for HTML inappropriate? Date: 2000-09-21 11:58:17 +0200 Message-ID: In-Reply-To: "Stephen J. Turnbull"'s message of "Thu, 21 Sep 2000 18:45:35 +0900 (JST)" --===============4699393344926805473== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable >>>>> "Stephen" =3D=3D Stephen J Turnbull wri= tes: Stephen> I'm trying to migrate my HTML to XHTML. Unfortunately, PSGML = barfs on Stephen> the required "xml:lang" attribute because of the colon. Stephen> The HTML 4.0 spec seems to indicate that (for HTML) the colon,= among Stephen> other characters, should be considered a name constituent. Please send me a test-case. I have psgml package 1.19 installed and am willing to give it a try. Adrian Stephen> Changing the syntax type of colon to "symbol constituent" in t= he PSGML Stephen> parser's syntax table leads to reasonable behavior for my X?HT= ML Stephen> documents, but I do not understand ISO 8879 or PSGML well enou= gh to Stephen> say whether this is really a correct solution. Nor can I say = how to Stephen> implement it given that (AFAIK) the "correct" syntax table wou= ld vary Stephen> according to the SGML instance. Stephen> This arose in XEmacs PSGML package 1.18, psgml-version 1.0.1. Stephen> Thanks for your attention to this issue. Stephen> -- = Stephen> University of Tsukuba Tennodai 1-1-1 Tsukuba 30= 5-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 --===============4699393344926805473==-- From turnbull at sk.tsukuba.ac.jp Sun Feb 26 16:42:07 2017 Content-Type: multipart/mixed; boundary="===============4673708615099101708==" MIME-Version: 1.0 From: Stephen J. Turnbull To: xemacs-beta at xemacs.org Subject: Re: PSGML's syntax table for HTML inappropriate? Date: 2000-09-21 19:29:55 +0900 Message-ID: <14793.58147.659149.918416@turnbull.sk.tsukuba.ac.jp> In-Reply-To: uem2ekqx2.fsf@ecf.teradyne.com --===============4673708615099101708== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable >>>>> "APA" =3D=3D Adrian Aichner writes: APA> Please send me a test-case. I have psgml package 1.19 APA> installed and am willing to give it a try. This is of course "degenerate" UTF-8. You'll need the XHTML DTD and a couple of entity definition files (at least, they're not in v1.18 of the XEmacs PSGML package): http://web3.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd http://web3.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent http://web3.w3.org/TR/xhtml1/DTD/xhtml-special.ent http://web3.w3.org/TR/xhtml1/DTD/xhtml-symbol.ent The problem is in the `xml:lang' attribute of the `html' element. The error occurs when parsing (C-c C-p) the DTD. Which reminds me; until I set up the catalogs correctly, PSGML silently substituted the HTML 3.2 DTD for XHTML 1.0. It would be nice if PSGML warned about this situation. ------------------------------ cut here ------------------------------ More Computer Wisdom

More Computer Wisdom

Even PSGML is subject to Murphy's Law.

------------------------------ cut here ------------------------------ -- = University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules." --===============4673708615099101708==-- From james at eecs.ukans.edu Sun Feb 26 16:42:08 2017 Content-Type: multipart/mixed; boundary="===============4081659847492459857==" MIME-Version: 1.0 From: Jerry James To: xemacs-beta at xemacs.org Subject: Re: PSGML's syntax table for HTML inappropriate? Date: 2000-09-22 10:00:50 -0500 Message-ID: In-Reply-To: 14793.58147.659149.918416@turnbull.sk.tsukuba.ac.jp --===============4081659847492459857== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Stephen J. Turnbull wrote: > This is of course "degenerate" UTF-8. You'll need the XHTML DTD and a > couple of entity definition files (at least, they're not in v1.18 of > the XEmacs PSGML package): > = > http://web3.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd > http://web3.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent > http://web3.w3.org/TR/xhtml1/DTD/xhtml-special.ent > http://web3.w3.org/TR/xhtml1/DTD/xhtml-symbol.ent This surprised me, because I submitted those files as part of the patch to bring the XEmacs PSGML package up to date. Indeed, fetching psgml-1.18-pkg.tar.gz from the package download site, I see this: % tar tzf psgml-1.18-pkg.tar.gz pkginfo/MANIFEST.psgml [snip] etc/psgml/xhtml-lat1.ent etc/psgml/xhtml-special.ent etc/psgml/xhtml-symbol.ent etc/psgml/xhtml1-frameset.dtd etc/psgml/xhtml1-strict.dtd etc/psgml/xhtml1-transitional-mathml.dtd etc/psgml/xhtml1-transitional.dtd etc/psgml/xhtml1.dcl [snip] It seems that something is wrong with your PSGML installation. > The problem is in the `xml:lang' attribute of the `html' element. The > error occurs when parsing (C-c C-p) the DTD. I have version 1.19 of the XEmacs PSGML package installed, but it has no trouble with your example. After parsing the prolog (C-c C-p), I can do a "next trouble spot" (C-c C-o), and it goes to the end and reports "Ok". > Which reminds me; until I set up the catalogs correctly, PSGML > silently substituted the HTML 3.2 DTD for XHTML 1.0. It would be nice > if PSGML warned about this situation. I can't get that to happen. How did you do it? What was wrong with the CATALOG? I see no errors in it that would cause this behavior. -- = Jerry James --===============4081659847492459857==-- From turnbull at sk.tsukuba.ac.jp Sun Feb 26 16:42:08 2017 Content-Type: multipart/mixed; boundary="===============3941063878715516489==" MIME-Version: 1.0 From: Stephen J. Turnbull To: xemacs-beta at xemacs.org Subject: Re: PSGML's syntax table for HTML inappropriate? Date: 2000-09-25 09:39:12 +0900 Message-ID: <14798.40624.458599.646831@turnbull.sk.tsukuba.ac.jp> In-Reply-To: pswvg4lbdp.fsf@diannao.ittc.ukans.edu --===============3941063878715516489== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable >>>>> "Jerry" =3D=3D Jerry James writes: Jerry> This surprised me, because I submitted those files as part Jerry> of the patch to bring the XEmacs PSGML package up to date. Jerry> Indeed, fetching psgml-1.18-pkg.tar.gz from the package Jerry> download site, I see this: This looks like my bad. I thought my 21.1 (email environment) and 21.2 (where I was using PSGML) package hierarchies were the same, but they're not. I had set things up to automatically revert to the common environment (maintained via package-user-interface) after testing new package stuff (installed into a separate hierarchy), but obviously that is not working correctly, and I've been running with old packages in 21.2 for a couple of months now. >> Which reminds me; until I set up the catalogs correctly, PSGML >> silently substituted the HTML 3.2 DTD for XHTML 1.0. It would >> be nice if PSGML warned about this situation. Jerry> I can't get that to happen. How did you do it? What was Jerry> wrong with the CATALOG? I see no errors in it that would Since it was obsolete, it was missing the XHTML entries. Jerry> cause this behavior. Try removing the XHTML entries from the catalog. It seems that the version of PSGML I have installed simply substitutes its default version of the DTD for short names where the full public ID can't be matched in the catalog. -- = University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules." --===============3941063878715516489==--