From 2e524f93fc03353e6fb05333d8041505948959eb Mon Sep 17 00:00:00 2001 From: Pierre Labastie Date: Fri, 13 Mar 2020 09:20:45 +0000 Subject: 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 --- .../params/webhelp.tree.cookie.id.xml | 38 ---------------------- 1 file changed, 38 deletions(-) delete mode 100644 stylesheets/lfs-xsl/docbook-xsl-1.78.1/params/webhelp.tree.cookie.id.xml (limited to 'stylesheets/lfs-xsl/docbook-xsl-1.78.1/params/webhelp.tree.cookie.id.xml') diff --git a/stylesheets/lfs-xsl/docbook-xsl-1.78.1/params/webhelp.tree.cookie.id.xml b/stylesheets/lfs-xsl/docbook-xsl-1.78.1/params/webhelp.tree.cookie.id.xml deleted file mode 100644 index 8f790be5d..000000000 --- a/stylesheets/lfs-xsl/docbook-xsl-1.78.1/params/webhelp.tree.cookie.id.xml +++ /dev/null @@ -1,38 +0,0 @@ - - -webhelp.tree.cookie.id -string - - -webhelp.tree.cookie.id -Controls how the cookie that stores the webhelp toc state is named. - - - - - - - - -Description -The webhelp output does not use a frameset. Instead, the table of contents is a div on each page. To preserve the state of the table of contents as the user navigates from page to page, webhelp stores the state in a cookie and reads that cookie when you get to the next page. If you've published several webhelp documents on the same domain, it is important that each cookie have a unique id. In lieu of calling on a GUID generator, by default this parameter is just set to the number of nodes in the document on the assumption that it is unlikely that you will have more than one document with the exact number of nodes. A more optimal solution would be for the user to pass in some unique, stable identifier from the build system to use as the webhelp cookie id. For example, if you have safeguards in place to ensure that the xml:id of the root element of each document will be unique on your site, then you could set webhelptree.cookie.id as follows: - - - - - - - - - - ]]> - - - - -- cgit v1.2.3-54-g00ecf