olink Template Mods Inquiry

Thread: olink Template Mods Inquiry

Search this list only Search all lists
olink Template Mods Inquiry
	2007-02-16 16:24:32

docbook-rnc-5.0b1 xsl-1.72 oxygen-8.1 (eclipse-3.2.1 plugin) Utilizing .../xhtml/profile-chunk.xsl When the olink database is generated, the following declaration: <!DOCTYPE div PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> appears at the top of the document How can I modify the xsl template(s) to replace this output with <?xml version="1.0" encoding="UTF-8"?> Applying the aforementioned manually and applying couple of mods to …/common/targetdatabase.dtd <!ELEMENT span ANY > <!ATTLIST span   xmlns ; CDATA ; #IMPLIED > creates a valid olink database. Lastly, is this document output behavior a development oversight or am I incorrectly configuring/implementing olink database parameters? Ray
Re: olink Template Mods Inquiry
	2007-02-16 18:05:47

Hi Ray, I'm looking into this, as it is more complicated than it ought to be. I'll let you know what I find out. But I think you can get your olinks working with the current output if you replace the entity references in your master olink database file with XIncludes. That will handle the DOCTYPE that is generated in target.db by the xhtml stylesheet. See: http://www.sagehill.net/docbookxsl/OlinkVariations.html#XincludeOlinkdb Oxygen can handle the XIncludes if that option is turned on. I'm pretty sure the validation part is not needed, as the stylesheet processor doesn't validate the database file, and doesn't need to in order to work. Bob Stayton Sagehill Enterprises DocBook Consulting sagehill.net">bobssagehill.net   ; ----- Original Message ----- From: va.gov href="mailto:Ray.Millerva.gov">Miller, Ray (Centech) To: lists.oasis-open.org href="mailto:docbook-appslists.oasis-open.org">docbook-appslists.oasis-open.org Sent: Friday, February 16, 2007 2:24 PM Subject: [docbook-apps] olink Template Mods Inquiry docbook-rnc-5.0b1 xsl-1.72 oxygen-8.1 (eclipse-3.2.1 plugin) Utilizing .../xhtml/profile-chunk.xsl When the olink database is generated, the following declaration: <!DOCTYPE div PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> appears at the top of the document How can I modify the xsl template(s) to replace this output with <?xml version="1.0" encoding="UTF-8"?> Applying the aforementioned manually and applying couple of mods to …/common/targetdatabase.dtd <!ELEMENT span ANY > <!ATTLIST span   xmlns ; CDATA ; #IMPLIED > creates a valid olink database. Lastly, is this document output behavior a development oversight or am I incorrectly configuring/implementing olink database parameters? Ray
RE: olink Template Mods Inquiry
	2007-02-17 11:25:10

>> But I think you can get your olinks working with the current output if you replace the entity references in your master olink database file with XIncludes. That will handle the DOCTYPE that is generated in target.db by the xhtml stylesheet. See: http://www.sagehill.net/docbookxsl/OlinkVariations.html#XincludeOlinkdb Oxygen can handle the XIncludes if that option is turned on. I'm pretty sure the validation part is not needed, as the stylesheet processor doesn't validate the database file, and doesn't need to in order to work. <<  The Xinclude solution works perfectly; appended the following to …/xsl/common/targetdatabase.dtd so the master olink database file would validate: <!ELEMENT xi:include (xi:fallback?) > <!ATTLIST xi:include   xmlnsi   CDATA ;     #FIXED ;   "http://www.w3.org/2001/XInclude"   href     CDATA       #REQUIRED   parse   ; (xml\|text) "xml"   encoding  CDATA ;     #IMPLIED > <!ELEMENT xi:fallback ANY> <!ATTLIST xi:fallback   xmlnsi   CDATA ; #FIXED  "http://www.w3.org/2001/XInclude" > <!ELEMENT span ANY > <!ATTLIST span       xmlns ; CDATA ; #FIXED "http://www.w3.org/1999/xhtml" > Much appreciated Ray

[1-3]

about | contact Other archives ( Real Estate discussion Medical topics )