Since LFS started using docbook-1.78.1, there is a lot of unused data

in the stylesheet directory. Basically, a whole docbook-stylesheet is
there, while we need only fo and xhtml (+ some common dirs). Each time
we checkout the repo, we have to download this whole thing, which is by
far the biggest part of the repo (~33 M). By removing unused cruft,
this could be down to ~12 M.

Of course, it would be even better to remove completely the stylesheets
and use host ones (repo size down to 2M). but let's do this first, it is
easier :)


git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11778 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

1 files changed, 0 insertions, 62 deletions

diff --git a/stylesheets/lfs-xsl/docbook-xsl-1.78.1/params/textinsert.extension.xml b/stylesheets/lfs-xsl/docbook-xsl-1.78.1/params/textinsert.extension.xml
deleted file mode 100644
index a6f1ea400..000000000
--- a/stylesheets/lfs-xsl/docbook-xsl-1.78.1/params/textinsert.extension.xml
+++ /dev/null
@@ -1,62 +0,0 @@
-<refentry xmlns="http://docbook.org/ns/docbook"
-  xmlns:xlink="http://www.w3.org/1999/xlink"
-  xmlns:xi="http://www.w3.org/2001/XInclude"
-  xmlns:src="http://nwalsh.com/xmlns/litprog/fragment"
-  xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-  version="5.0" xml:id="textinsert.extension">
-  <refmeta>
-    <refentrytitle>textinsert.extension</refentrytitle>
-    <refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
-  </refmeta>
-  <refnamediv>
-    <refname>textinsert.extension</refname>
-    <refpurpose>Enables the textinsert extension element</refpurpose>
-  </refnamediv>
-  <refsynopsisdiv>
-    <src:fragment xml:id="textinsert.extension.frag">
-  <xsl:param name="textinsert.extension" select="1"/>
-</src:fragment>
-  </refsynopsisdiv>
-  <refsection><info><title>Description</title></info>
-    <para>The textinsert extension element inserts the contents of
-      a file into the result tree (as text).</para>
-    <note>
-      <para>To use the textinsert extension element, you must use
-        either Saxon or Xalan as your XSLT processor (it doesn’t
-        work with xsltproc), along with either the DocBook Saxon
-        extensions or DocBook Xalan extensions (for more
-        information about those extensions, see <link
-          role="tcg" xlink:href="InstallingAProcessor.html#SaxonExtensions"
-          >DocBook Saxon Extensions</link> and <link
-          role="tcg" xlink:href="InstallingAProcessor.html#XalanExtensions"
-          >DocBook Xalan Extensions</link>), and you must set both
-        the <parameter>use.extensions</parameter> and
-        <parameter>textinsert.extension</parameter> parameters to
-        <literal>1</literal>.</para>
-      <para>As an alternative to using the textinsert element,
-        consider using an Xinclude element with the
-        <literal>parse="text"</literal> attribute and value
-        specified, as detailed in <link
-          role="tcg" xlink:href="ExternalCode.html#XIncludeCode"
-          >Using XInclude for text inclusions</link>.</para>
-    </note>
-  </refsection>
-  <refsection><info><title>See Also</title></info>
-    <para>You can also use the <tag
-        class="xmlpi">dbhtml-include href</tag> processing
-      instruction to insert external files — both files containing
-      plain text and files with markup content (including HTML
-      content).</para>
-  </refsection>
-  <refsection><info><title>More information</title></info>
-    <para>For how-to documentation on inserting contents of
-      external code files and other text files into output, see
-      <link
-        role="tcg" xlink:href="ExternalCode.html"
-        >External code files</link>.</para>
-    <para>For guidelines on inserting contents of
-      HTML files into output, see <link
-        role="tcg" xlink:href="InsertExtHtml.html"
-        >Inserting external HTML code</link>.</para>
-  </refsection>
-</refentry>