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, 83 deletions

diff --git a/stylesheets/lfs-xsl/docbook-xsl-1.78.1/params/insert.olink.page.number.xml b/stylesheets/lfs-xsl/docbook-xsl-1.78.1/params/insert.olink.page.number.xml
deleted file mode 100644
index dc6da3d06..000000000
--- a/stylesheets/lfs-xsl/docbook-xsl-1.78.1/params/insert.olink.page.number.xml
+++ /dev/null
@@ -1,83 +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="insert.olink.page.number">
-<refmeta>
-<refentrytitle>insert.olink.page.number</refentrytitle>
-<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo> 
-<refmiscinfo class="other" otherclass="value">no</refmiscinfo>
-<refmiscinfo class="other" otherclass="value">yes</refmiscinfo>
-<refmiscinfo class="other" otherclass="value">maybe</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>insert.olink.page.number</refname>
-<refpurpose>Turns page numbers in olinks on and off</refpurpose>
-</refnamediv>
-
-<refsynopsisdiv>
-<src:fragment xml:id="insert.olink.page.number.frag">
-<xsl:param name="insert.olink.page.number">no</xsl:param>
-</src:fragment>
-</refsynopsisdiv>
-
-<refsection><info><title>Description</title></info>
-
-<para>The value of this parameter determines if
-cross references made between documents with
-<tag>olink</tag> will 
-include page number citations.
-In most cases this is only applicable to references in printed output.
-</para>
-<para>The parameter has three possible values.
-</para>
-<variablelist>
-<varlistentry>
-<term>no</term>
-<listitem><para>No page number references will be generated for olinks.
-</para></listitem>
-</varlistentry>
-<varlistentry>
-<term>yes</term>
-<listitem><para>Page number references will be generated
-for all <tag>olink</tag> references.
-The style of page reference may be changed
-if an <tag class="attribute">xrefstyle</tag>
-attribute is used.
-</para></listitem>
-</varlistentry>
-<varlistentry>
-<term>maybe</term>
-<listitem><para>Page number references will not be generated
-for an <tag>olink</tag> element unless 
-it has an
-<tag class="attribute">xrefstyle</tag>
-attribute whose value specifies a page reference.
-</para></listitem>
-</varlistentry>
-</variablelist>
-<para>Olinks that point to targets within the same document
-are treated as <tag>xref</tag>s, and controlled by
-the <parameter>insert.xref.page.number</parameter> parameter.
-</para>
-
-<para>Page number references for olinks to
-external documents can only be inserted if the 
-information exists in the olink database. 
-This means each olink target element 
-(<tag>div</tag> or <tag>obj</tag>)
-must have a <tag class="attribute">page</tag> attribute
-whose value is its page number in the target document.
-The XSL stylesheets are not able to extract that information
-during processing because pages have not yet been created in
-XSLT transformation.  Only the XSL-FO processor knows what
-page each element is placed on.
-Therefore some postprocessing must take place to populate
-page numbers in the olink database.
-</para>
-
-
-
-</refsection>
-</refentry>