Re: AW: DOCBOOK-APPS: [QUESTION] translating whitespaces into nbsp;
At 23:17 04/10/2002, Daniel S. Haischt wrote:
but if i am using ...
translate('This is a foobar sentence.', ' ', '#160;')
... with saxon i am getting the following result ...
ThisA isA aA foobarA sentence.
You need to set the output encoding to html.
HTH DaveP
RE: DOCBOOK-APPS: XInclude doesn't validate with xmllint
On Wed, 2002-10-02 at 11:41, Jeff Beal wrote: No one seems to have mentioned this yet, and it may just be a typo in your e-mail, but the element has to be xi:include xmlns:xi=http://www.w3.org/2001/XInclude; href=Called.xml/, not just xi xmlns:xi=http://www.w3.org/2001/XInclude; href=Called.xml/ It turns out to be a combination of problems: 1) as Jeff pointed out, it should be xi:include (my error) 2) I needed to remove the --valid option and use --postvalid for xmllint Also, xmllint puts out the SGML_CATALOG_FILE message (see below) if you use the default /etc/xml/catalog. So the non-use of catalogs does not apply. -Original Message- From: John Himpel [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 01, 2002 10:35 PM To: [EMAIL PROTECTED] Subject: DOCBOOK-APPS: XInclude doesn't validate with xmllint Greetings, I am trying to validate two xml files using the modular document technique that Bob Stayton shows in www.sagehill.net. My version of xmllint: xmllint: using libxml version 20423 File: Caller.xml ?xml version='1.0' encoding='utf-8' ? !DOCTYPE book PUBLIC -//OASIS//DTD DocBook XML V4.2//EN http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd; book id=XFree86 titleXFree86 Documentation (Docbook Version)/title xi xmlns:xi=http://www.w3.org/2001/XInclude; href=Called.xml / /book File: Called.xml ?xml version=1.0? !DOCTYPE chapter PUBLIC -//OASIS//DTD DocBook XML V4.2//EN http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd; chapter id='Called' title Chapter Title. /title section titlePreface/title paraSimple paragraph./para /section /chapter Command: xmllint --catalogs --noout --xinclude --valid --dtdvalid http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd Caller.xml Result: Variable $SGML_CATALOG_FILES not set Caller.xml:6: validity error: No declaration for attribute href on element xi xi xmlns:xi=http://www.w3.org/2001/XInclude; href=Called.xml / ^ Caller.xml:6: validity error: No declaration for element xi xi xmlns:xi=http://www.w3.org/2001/XInclude; href=Called.xml / ^ Caller.xml:7: validity error: Element book content doesn't follow the DTD Expecting ((title , subtitle? , titleabbrev?)? , bookinfo? , (dedication | toc | lot | glossary | bibliography | preface | chapter | reference | part | article | appendix | index | setindex | colophon)*), got (title xi ) /book ^ Element book content doesn't follow the DTD I don't know if the problem is DocBook or if the problem is xmllint. Any pointers or suggestions would be welcome. Thanks
AW: AW: DOCBOOK-APPS: [QUESTION] translating whitespaces into nbsp;
that did the trick, thanx!
i had the output encoding set to text, because
i was generating a java script file.
regards
daniel s. haischt
--
-Ursprungliche Nachricht-
Von: Dave Pawson [mailto:[EMAIL PROTECTED]]
Gesendet: Samstag, 5. Oktober 2002 09:15
An: Daniel S. Haischt; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Betreff: Re: AW: DOCBOOK-APPS: [QUESTION] translating whitespaces into
nbsp;
At 23:17 04/10/2002, Daniel S. Haischt wrote:
but if i am using ...
translate('This is a foobar sentence.', ' ', '#160;')
... with saxon i am getting the following result ...
ThisA isA aA foobarA sentence.
You need to set the output encoding to html.
HTH DaveP
DOCBOOK-APPS: [NOTE] callout graphics are not included within theactuall source listing
hello, note: this mail belongs to the website DTD. i tried to use the programlistingco/ element within one of my website XML source files. the website XML source file includes the website-full DTD. to test the programlistingco/ element with the website DTD i tried to use the example that comes with TDG on page 'programlistingco.html'. actually, the resulting HTML document gets almost rendered as expected. allthough the callout graphics will only be displayed for the calloutlist/ element but not for the programlisting/ element. that means the explanation of the source code contains the callout graphics. but the source code listing itself does not. any ideas? With best regards / Mit freundlichen Gruessen Daniel S. Haischt IT Consulting __ [revolutionary and alpha geek] Daniel S. Haischt Grabenstrasse 11 D-71083 Herrenberg G E R M A N Y FON: +49 -7032-992909 +49 -700-DHAISCHT FAX: +49 -7032-992910 CELLULAR: +49 -172-7668936 email: [EMAIL PROTECTED] web: http://www.daniel-s-haischt.biz -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS dx s:- a- C++ UB P+++ L E W+++ N+++ o-- K- w--- O++ M++ V- PS+ PE++ Y+ PGP++ t+++ 5+ X+++ R+ tv++ b+++ DI+ D+++ G e++ h-- r+ y+ --END GEEK CODE BLOCK--
DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint
Daniel Veillard [EMAIL PROTECTED] writes: You should really start accepting that URL can be used as identifiers like any other string, sigh ... It can, but a SYSTEM identifiers is not canonical (= it is not fixed). Let's hope somebody will finish the LSB some time soon regarding XML. Scrollkeeper seems to prefer the SYSTEM identifier, though. All in all, XML is nicely complex (and limited nevertheless ;) ). -- [EMAIL PROTECTED] (work) / [EMAIL PROTECTED] (home): | http://www.suse.de/~ke/ | ,__o Free Translation Project:|_-\_, http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)
Re: DOCBOOK-APPS: [NOTE] callout graphics are not included within theactuall source listing
On Sat, Oct 05, 2002 at 03:42:02PM +0200, Daniel S. Haischt wrote: hello, note: this mail belongs to the website DTD. i tried to use the programlistingco/ element within one of my website XML source files. the website XML source file includes the website-full DTD. to test the programlistingco/ element with the website DTD i tried to use the example that comes with TDG on page 'programlistingco.html'. actually, the resulting HTML document gets almost rendered as expected. allthough the callout graphics will only be displayed for the calloutlist/ element but not for the programlisting/ element. that means the explanation of the source code contains the callout graphics. but the source code listing itself does not. Callouts placed with an areaspec require an XSL extension function. You turn that on by setting these two parameters: use.extensions=1 callouts.extension=1 and processing your file with Saxon or Xalan with the the appropriate DocBook extensions jar file in your CLASSPATH. -- Bob Stayton 400 Encinal Street Publications Architect Santa Cruz, CA 95060 Technical Publications voice: (831) 427-7796 Caldera International, Inc. fax: (831) 429-1887 email: [EMAIL PROTECTED]
DOCBOOK-APPS: Re: Testing that xrefs point to xreflabels
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 / [EMAIL PROTECTED] was heard to say: | My Parser tends to chuck out loads of noise - My aim is to get just a nice What sort of errors is your parser producing? Usually that means you've got errors in your document, and that's going to cause problems later on. Be seeing you, norm - -- Norman Walsh [EMAIL PROTECTED] | Few men are so sufficiently http://www.oasis-open.org/docbook/ | discerning to appreciate all the Chair, DocBook Technical Committee | evil that they do.--La | Rochefoucauld -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 http://mailcrypt.sourceforge.net/ iD8DBQE9n09LOyltUcwYWjsRAtn+AKCv27xmhTJiyjzmy+SiZzNItpMWnwCfZ2fb PZ7K7lWb0cbWPSNURwX+0Sg= =6adr -END PGP SIGNATURE-
DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 / Bob Stayton [EMAIL PROTECTED] was heard to say: | I started to extend the DocBook DTD to permit xi:include, | but I think it is kind of impossible (except for maybe | Norm 8^). The xi:include element can replace *any* | element or group of elements, so the content models of | every element would get hopelessly complex. Try adding xi:include to ndxterm.mix. It's a bit of a hack, but that'll allow it anywhere indexterm is allowed and that's most places. Be seeing you, norm - -- Norman Walsh [EMAIL PROTECTED] | The happiest people seem to be http://www.oasis-open.org/docbook/ | those that have no particular Chair, DocBook Technical Committee | reason for being happy except that | they are so.--W. R. Inge -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 http://mailcrypt.sourceforge.net/ iD8DBQE9n1BSOyltUcwYWjsRAnh8AJ98pV8R0+ZpxNiLFd61L9dwHZpv9QCfbIri gajqczAMYRwccLXf1TSxONs= =v86b -END PGP SIGNATURE-
DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 / Bob Stayton [EMAIL PROTECTED] was heard to say: | Try modelling these examples in a chapter element | declaration: | | chapter | xi:include href=AllChapterContent/ | /chapter Ah, yes, if you want xi:include to replace required elements, you're not going to get the DTD to do that without a lot of work. Be seeing you, norm - -- Norman Walsh [EMAIL PROTECTED] | The voice of the intellect is a http://www.oasis-open.org/docbook/ | soft one, but it does not rest Chair, DocBook Technical Committee | until it has gained a | hearing.--Freud -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 http://mailcrypt.sourceforge.net/ iD8DBQE9n1FaOyltUcwYWjsRAlY7AJ98LldqUTttSe160bT+NDGJVBF+YQCgieXx yhz7t/72K7jM8bgMbB+Mn9I= =84+G -END PGP SIGNATURE-
DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 / Peter Ring [EMAIL PROTECTED] was heard to say: | maintenance a no-brainer. BTW, the catalog.dtd that you get from | http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd is | version 1.7, while the one in the spec is version 1.9. So much for entity | resolution over the net ;) Ooops. Ah, well, I'm in the middle of edits for a new spec release so I'll fix that :-) Be seeing you, norm - -- Norman Walsh [EMAIL PROTECTED] | Nothing is worth more than this http://www.oasis-open.org/docbook/ | day.--Goethe Chair, DocBook Technical Committee | -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 http://mailcrypt.sourceforge.net/ iD8DBQE9n1HaOyltUcwYWjsRAgV0AKCea3d5zA+eXYIitzPsv5+3JaumiACfTgp1 RrFK+N2OeqiFT4IHyrENusg= =bosU -END PGP SIGNATURE-
DOCBOOK-APPS: Re: AW: [QUESTION] translating whitespaces into nbsp;
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 / Daniel S. Haischt [EMAIL PROTECTED] was heard to say: | but saxon should support the unicode representation | of extended characters, shouldn't it? I'm sure it does. And I think the xsl:param name=saxon.character.representation select='entity;decimal'/ parameter would let you pick the default you want. For HTML, using names for the ISO Latin 1 characters is what most people expect. Be seeing you, norm - -- Norman Walsh [EMAIL PROTECTED] | Our ignorance of history makes us http://www.oasis-open.org/docbook/ | libel our own times. People have Chair, DocBook Technical Committee | always been like this.--Flaubert -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 http://mailcrypt.sourceforge.net/ iD8DBQE9n1LYOyltUcwYWjsRAsOOAKCCpGGOpdmMhBMuP/XM/juKnBcq2wCbBh1u Z42Leev0ojOQnLCO0A09pNk= =BF4t -END PGP SIGNATURE-
DOCBOOK-APPS: Re: AW: [QUESTION] translating whitespaces into nbsp;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
/ Daniel S. Haischt [EMAIL PROTECTED] was heard to say:
| but if i am using ...
|
| translate('This is a foobar sentence.', ' ', '#160;')
|
| ... with saxon i am getting the following result ...
|
| ThisA isA aA foobarA sentence.
That's the right answer. You're just not used to looking at UTF-8 in
what ever editor you're using. Try selecting a different encoding.
Be seeing you,
norm
- --
Norman Walsh [EMAIL PROTECTED] | The present moment is a powerful
http://www.oasis-open.org/docbook/ | goddess.--Goethe
Chair, DocBook Technical Committee |
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 http://mailcrypt.sourceforge.net/
iD8DBQE9n1MJOyltUcwYWjsRAoEGAKCwtiHHgpUYv7uLpOC76mwS/y1J3wCeKAbA
WZ65OEDw2oq+uIkILqvJ37k=
=dvO0
-END PGP SIGNATURE-
AW: DOCBOOK-APPS: [NOTE] callout graphics are not included within theactuall source listing
hummm, ok thanx for the help that worked. i guess i have to recap all the parameters for the HTML stylesheets ;-) regards daniel s. haischt -- -Ursprungliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Gesendet: Samstag, 5. Oktober 2002 22:22 An: Daniel S. Haischt; [EMAIL PROTECTED] Betreff: Re: DOCBOOK-APPS: [NOTE] callout graphics are not included within the actuall source listing On Sat, Oct 05, 2002 at 03:42:02PM +0200, Daniel S. Haischt wrote: hello, note: this mail belongs to the website DTD. i tried to use the programlistingco/ element within one of my website XML source files. the website XML source file includes the website-full DTD. to test the programlistingco/ element with the website DTD i tried to use the example that comes with TDG on page 'programlistingco.html'. actually, the resulting HTML document gets almost rendered as expected. allthough the callout graphics will only be displayed for the calloutlist/ element but not for the programlisting/ element. that means the explanation of the source code contains the callout graphics. but the source code listing itself does not. Callouts placed with an areaspec require an XSL extension function. You turn that on by setting these two parameters: use.extensions=1 callouts.extension=1 and processing your file with Saxon or Xalan with the the appropriate DocBook extensions jar file in your CLASSPATH. -- Bob Stayton 400 Encinal Street Publications Architect Santa Cruz, CA 95060 Technical Publications voice: (831) 427-7796 Caldera International, Inc. fax: (831) 429-1887 email: [EMAIL PROTECTED]
