Remove DOCS/xml

This contained _some_ documentation, but it was all old, crappy,
barely maintained. Even if it was maintained, uau hasn't merged
back changes for years.
This commit is contained in:
wm4
2012-07-28 20:44:58 +02:00
parent 6dc1249625
commit f606bb6d97
19 changed files with 0 additions and 3757 deletions
-54
View File
@@ -1,54 +0,0 @@
# Makefile for generating the HTML documentation
include ../../config.mak
include xml.mak
# Generated HTML files go here.
HTML = ../HTML
MAIN_XML_ALL = $(foreach lang,$(DOC_LANG_ALL),$(lang)/main.xml)
CONFIGURE_GENERATED = html-chunk.xsl html-single.xsl xml.mak
all: html-chunked html-single
html-chunked: $(addprefix html-chunked-,$(DOC_LANGS))
html-single: $(addprefix html-single-,$(DOC_LANGS))
xmllint: $(addprefix xmllint-,$(DOC_LANGS))
$(CONFIGURE_GENERATED) $(MAIN_XML_ALL):
./configure
define lang-def
html-chunked-$(lang): $(HTML)/$(lang)/dummy.html
html-single-$(lang): $(HTML)/$(lang)/MPlayer.html
$(HTML)/$(lang)/dummy.html $(HTML)/$(lang)/MPlayer.html: $(lang)/main.xml $(wildcard $(lang)/*.xml) html-common.xsl $(HTML)/$(lang)/default.css
$(HTML)/$(lang)/default.css:
mkdir -p $$(@D)
cp -f default.css $$(@D)
$(HTML)/$(lang)/dummy.html:
SGML_CATALOG_FILES=$(CATALOG) $(XSLT_COMMAND) $$@ html-chunk.xsl $$<
$(HTML)/$(lang)/MPlayer.html:
SGML_CATALOG_FILES=$(CATALOG) $(XSLT_COMMAND) $$@ html-single.xsl $$<
xmllint-$(lang):
SGML_CATALOG_FILES=$(CATALOG) $(XMLLINT_COMMAND) $(lang)/main.xml
endef
$(foreach lang, $(DOC_LANG_ALL),$(eval $(lang-def)))
clean:
-rm -rf $(HTML)
# Remove generated files but keep the HTML (for release tarballs).
releaseclean:
-rm -f $(CONFIGURE_GENERATED)
-rm -f $(MAIN_XML_ALL)
distclean: clean releaseclean
.PHONY: all html-chunked html-single xmllint
.PHONY: html-chunked-* html-single-* xmllint-* *clean
-84
View File
@@ -1,84 +0,0 @@
Tools required for building the documentation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* GNU make 3.80 or later
* DocBook 4.1.2 or later
* The DocBook XML DTD (also known as DocBk XML)
* DocBook XSL stylesheets -- version 1.50.0 or later is recommended.
I am not quite sure which tools work, but I used the following
ones successfully, so they are required:
* xmllint (part of libxml2) is used for validation.
* xsltproc (part of libxslt1) is used for transforming XML files into HTML
files. Version 1.0.18 or later is recommended.
On Red Hat systems you need the following packages:
libxml2, libxslt, docbook-dtds, docbook-style-xsl
On Debian you will need these packages:
docbook-xml, docbook-xsl, xsltproc, libxml2-utils
Building the documentation
~~~~~~~~~~~~~~~~~~~~~~~~~~
Before trying to build the documentation, run
make help
to see all available build targets and make your choice. If something goes
wrong, check the Configuration section of the toplevel Makefile and adjust
the variables.
The documentation and its translations reside in subdirectories.
When building the documentation, the generated HTML files are
placed in subdirectories of the 'HTML' directory.
IMPORTANT: Do NOT place sensitive files under 'HTML'!
It is for generated documentation only.
The whole directory tree is wiped out by the Makefile
when running 'make distclean' or 'make clean'.
Adding new translations
~~~~~~~~~~~~~~~~~~~~~~~
1) Create a new subdirectory and copy the XML files there. main.xml must not be
copied, it is autogenerated.
2) In each translated file after the <?xml ... ?> tag you must put a note
like <!-- synced with r2 -->, where 2 is the revision of corresponding
English file (see comment at the top of file).
That's all, in theory.
A few words about SGML catalog files
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
As far as I know, the document type declaration in XML files requires
both a public and a system identifier. For example:
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"/usr/share/sgml/docbook/dtd/xml/4.1.2/docbookx.dtd">
where
"-//OASIS//DTD DocBook XML V4.1.2//EN"
is the public, and
"/usr/share/sgml/docbook/dtd/xml/4.1.2/docbookx.dtd"
is the system identifier.
The problem is that the system identifier is most probably system-dependent.
To avoid the need to manually fix the system identifiers before building the
documentation, I've decided to use SGML catalogs. If you have your catalogs
set up correctly, xmllint and xsltproc will use them to find the DTDs
based on the public identifiers.
Note that this works only if public identifiers override system identifiers
(i.e. the catalog file must contain 'OVERRIDE YES'). (I had no problem with
these on my system, since the Debian people took care of everything. ;-))
-184
View File
@@ -1,184 +0,0 @@
#!/bin/sh
# Script to check for catalogs, stylesheets, XSL processors and all
# the other stuff necessary to convert the XML documentation.
echo "Searching for XML catalogs..."
for try_catalog in \
/etc/sgml/catalog \
/usr/share/xml/docbook/*/catalog.xml \
/opt/local/share/xml/docbook-xml/*/catalog.xml \
/opt/local/share/xml/docbook/*/catalog.xml \
/usr/share/sgml/docbook/*/*catalog \
/usr/share/apps/ksgmltools2/customization/en/catalog \
/usr/share/sgml/catalog \
/usr/local/share/sgml/catalog \
/usr/lib/sgml/catalog \
/usr/local/lib/sgml/catalog \
/usr/share/docbook-xml42/catalog.xml \
/usr/share/sgml/docbook/xmlcatalog
do
if test -f "$try_catalog"; then
catalog=$try_catalog
break
fi
done
if test -n "$catalog"; then
echo "Found SGML catalog at $catalog"
catalog_opts=--catalogs
else
echo "No SGML catalog found."
fi
echo "Searching for stylesheets..."
echo "Searching for html/chunk.xsl..."
for try_chunk_xsl in \
/usr/share/xml/docbook/*/html/chunk.xsl \
/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/html/chunk.xsl \
/usr/share/sgml/docbook/yelp/docbook/html/chunk.xsl \
/usr/local/share/sgml/docbook/stylesheet/xsl/nwalsh/html/chunk.xsl \
/usr/local/share/sgml/docbook/yelp/docbook/html/chunk.xsl \
/usr/share/docbook-xsl/html/chunk.xsl \
/usr/share/sgml/docbook/xsl-stylesheets*/html/chunk.xsl \
/usr/share/xml/docbook/stylesheet/nwalsh/current/html/chunk.xsl \
/opt/local/share/xsl/docbook-xsl/html/chunk.xsl \
do
if test -f "$try_chunk_xsl"; then
chunk_xsl=$try_chunk_xsl
break
fi
done
if test -z "$chunk_xsl"; then
chunk_xsl=/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/html/chunk.xsl
echo "Not found. Using default ($chunk_xsl)"
fake_chunk_xsl=yes
else
echo "Found chunk.xsl at $chunk_xsl"
fi
echo "Searching for html/docbook.xsl..."
for try_docbook_xsl in \
/usr/share/xml/docbook/*/html/docbook.xsl \
/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/html/docbook.xsl \
/usr/share/sgml/docbook/yelp/docbook/html/docbook.xsl \
/usr/local/share/sgml/docbook/stylesheet/xsl/nwalsh/html/docbook.xsl \
/usr/local/share/sgml/docbook/yelp/docbook/html/docbook.xsl \
/usr/share/docbook-xsl/html/docbook.xsl \
/usr/share/sgml/docbook/xsl-stylesheets*/html/docbook.xsl \
/usr/share/xml/docbook/stylesheet/nwalsh/current/html/docbook.xsl \
/opt/local/share/xsl/docbook-xsl/html/docbook.xsl \
do
if test -f "$try_docbook_xsl"; then
docbook_xsl=$try_docbook_xsl
break
fi
done
if test -z "$docbook_xsl"; then
docbook_xsl=/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/html/docbook.xsl
echo "Not found. Using default ($docbook_xsl)"
else
echo "Found docbook.xsl at $docbook_xsl"
fi
cat > html-chunk.xsl << EOF
<?xml version="1.0" encoding="utf-8"?>
<!-- **************************************************
This file is generated automatically. DO NOT EDIT.
************************************************** -->
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0">
<xsl:import href="$chunk_xsl"/>
<xsl:include href="html-common.xsl"/>
</xsl:stylesheet>
EOF
cat > html-single.xsl << EOF
<?xml version="1.0" encoding="utf-8"?>
<!-- **************************************************
This file is generated automatically. DO NOT EDIT.
************************************************** -->
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0">
<xsl:import href="$docbook_xsl"/>
<xsl:include href="html-common.xsl"/>
</xsl:stylesheet>
EOF
echo "Searching for DTD..."
#FIXME: This should prefer higher version numbers, not the other way around ..
for try_dtd in \
/usr/share/xml/docbook/*/dtd/4*/docbookx.dtd \
/usr/share/xml/docbook/*/docbookx.dtd \
/usr/share/sgml/docbook/*/docbookx.dtd \
/usr/share/sgml/docbook/dtd/*/docbookx.dtd \
/usr/share/sgml/docbook/dtd/xml/*/docbookx.dtd \
/usr/share/docbook-xml*/docbookx.dtd \
/opt/local/share/xml/docbook*/*/docbookx.dtd \
/usr/share/apps/ksgmltools2/docbook/*/docbookx.dtd
do
if test -f "$try_dtd"; then
dtd=$try_dtd
break
fi
done
if test -z "$dtd"; then
dtd=/usr/share/sgml/docbook/dtd/xml/4.1.2/docbookx.dtd
echo "Not found. Using default ($dtd)."
else
echo "Found docbookx.dtd at $dtd"
fi
for lang in `grep 'DOC_LANGS =' ../../config.mak|cut -d= -f2`; do
cat > $lang/main.xml << EOF
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!-- **************************************************
This file is generated automatically. DO NOT EDIT.
************************************************** -->
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"$dtd"
[
EOF
for file in $(find en -name \*.xml -exec basename \{\} \;); do
echo '<!ENTITY '$file' SYSTEM "'$file'">' >> $lang/main.xml
done
cat >> $lang/main.xml << EOF
]>
<book id="index" lang="$lang">
&documentation.xml;
</book>
EOF
done
echo "Looking for a valid XSLT processor..."
if xsltproc --version > /dev/null 2>&1; then
if test -z "$fake_chunk_xsl"; then
echo "Found xsltproc. If it works, it's probably the best choice."
xsltcommand="xsltproc $catalog_opts -o \$\$1 \$\$2 \$\$3"
else
echo "Found xsltproc but no stylesheets on your system."
echo "xsltproc is unusable without stylesheets."
fi
fi
cat > xml.mak << EOF
CATALOG = $catalog
XMLLINT_COMMAND = xmllint --noout --noent --postvalid $catalog_opts \$*
XSLT_COMMAND = $xsltcommand
EOF
-83
View File
@@ -1,83 +0,0 @@
body {
color: black;
background: white;
font-family: Arial, Helvetica, sans-serif;
/*
* It's a Bad Idea(tm) to use fixed font sizes.
* Uncomment it if you _really_ want
*/
font-size: 14px;
}
div.table table, div.informaltable table {
background: #333366;
border-collapse: separate;
border: solid 1px #333366;
border-spacing: 1px;
}
div.table th, div.informaltable th {
color: white;
background: #4488cc;
border: 0px;
padding: 2px;
}
div.table td, div.informaltable td {
background: #fffff8;
border: 0px;
padding: 2px;
}
pre.screen {
padding: 4px;
background: #e0e0e0;
}
pre.programlisting {
padding: 4px;
background: #e0e8f0;
}
/*
span.application {
}
*/
span.keycap {
background: #ddd;
border: solid 1px #aaa;
white-space: nowrap;
font-family: Arial, Helvetica, sans-serif;
}
span.guimenu, span.guisubmenu, span.guimenuitem {
background: #dddddd;
}
tt.filename {
color: maroon;
white-space: nowrap;
}
tt.option {
color: #066;
white-space: nowrap;
}
div.example {
padding-left: 0.5em;
border-left: solid 2px black;
}
div.important .title, div.caution .title, div.warning .title {
color: #c00;
}
/*
div.important, div.warning, div.caution {
padding-left: 0.5em;
border-left: solid 2px maroon;
}
*/
-255
View File
@@ -1,255 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<!-- $Revision$ -->
<appendix id="bugreports">
<title>How to report bugs</title>
<para>
Good bug reports are a very valuable contribution to the development of any
software project. But just like writing good software, good problem reports
involve some work. Please realize that most developers are extremely busy and
receive obscene amounts of email. So while your feedback is crucial in improving
<application>MPlayer</application> and very much appreciated, please understand
that you have to provide <emphasis role="bold">all</emphasis> of the information
we request and follow the instructions in this document closely.
</para>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<sect1 id="bugreports_security">
<title>Report security related bugs</title>
<para>
In case you have found an exploitable bug and you would like to do the
right thing and let us fix it before you disclose it, we would be happy
to get your security advisory at
<ulink url="mailto:&#115;&#101;&#99;&#117;&#114;&#105;&#116;&#121;&#64;&#109;&#112;&#108;&#97;&#121;&#101;&#114;&#104;&#113;&#46;&#104;&#117;">&#115;&#101;&#99;&#117;&#114;&#105;&#116;&#121;&#64;&#109;&#112;&#108;&#97;&#121;&#101;&#114;&#104;&#113;&#46;&#104;&#117;</ulink>.
Please add [SECURITY] or [ADVISORY] in the subject.
Be sure that your report contains complete and detailed analysis of the bug.
Sending a fix is highly appreciated.
Please don't delay your report to write proof-of-concept exploit, you can
send that one with another mail.
</para>
</sect1>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<sect1 id="bugreports_fix">
<title>How to fix bugs</title>
<para>
OUTDATED CONTENT REMOVED
</para>
</sect1>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<sect1 id="bugreports_regression_test">
<title>How to do regression testing using Subversion</title>
<para>
OUTDATED CONTENT REMOVED
</para>
</sect1>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<sect1 id="bugreports_report">
<title>How to report bugs</title>
<para>
OUTDATED CONTENT REMOVED
</para>
</sect1>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<sect1 id="bugreports_where">
<title>Where to report bugs</title>
<para>
OUTDATED CONTENT REMOVED
</para>
<para>
The language of this list is <emphasis role="bold">English</emphasis>.
Please follow the standard
<ulink url="http://www.ietf.org/rfc/rfc1855.txt">Netiquette Guidelines</ulink>
and <emphasis role="bold">do not send HTML mail</emphasis> to any of our
mailing lists. You will only get ignored or
banned. If you do not know what HTML mail is or why it is evil, read this
<ulink url="http://efn.no/html-bad.html">fine document</ulink>.
It explains all the details and has instructions for turning HTML off. Also
note that we will not individually CC (carbon-copy) people so it is a good idea
to subscribe to actually receive your answer.
</para>
</sect1>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<sect1 id="bugreports_what">
<title>What to report</title>
<para>
OUTDATED CONTENT REMOVED
</para>
<!-- ********** -->
<sect2 id="bugreports_system">
<title>System Information</title>
<para>
OUTDATED CONTENT REMOVED
</para>
</sect2>
<!-- ********** -->
<sect2 id="bugreports_hardware">
<title>Hardware and drivers</title>
<para>
OUTDATED CONTENT REMOVED
</para>
</sect2>
<!-- ********** -->
<sect2 id="bugreports_configure">
<title>Configure problems</title>
<para>
If you get errors while running <command>./configure</command>, or autodetection
of something fails, read <filename>config.log</filename>. You may find the
answer there, for example multiple versions of the same library mixed on your
system, or you forgot to install the development package (those with the -dev
suffix). If you think there is a bug, include <filename>config.log</filename>
in your bug report.
</para>
</sect2>
<sect2 id="bugreports_compilation">
<title>Compilation problems</title>
<para>
Please include these files:
<itemizedlist>
<listitem><para>config.h</para></listitem>
<listitem><para>config.mak</para></listitem>
</itemizedlist>
</para>
</sect2>
<!-- ********** -->
<sect2 id="bugreports_playback">
<title>Playback problems</title>
<para>
Please include the output of <application>MPlayer</application> at verbosity
level 1, but remember to
<emphasis role="bold">not truncate the output</emphasis> when
you paste it into your mail. The developers need all of the messages to properly
diagnose a problem. You can direct the output into a file like this:
<screen>
mplayer -v <replaceable>options</replaceable> <replaceable>filename</replaceable> &gt; mplayer.log 2&gt;&amp;1
</screen>
</para>
<para>
If your problem is specific to one or more files,
then please upload the offender(s) to:
<ulink url="ftp://upload.mplayerhq.hu/MPlayer/incoming/"/>
</para>
<para>
Also upload a small text file having the same base name as your file with a .txt
extension. Describe the problem you are having with the particular file there
and include your email address as well as the output of
<application>MPlayer</application> at verbosity level 1.
Usually the first 1-5 MB of a file are enough to reproduce
the problem, but to be sure we ask you to:
<screen>
dd if=<replaceable>yourfile</replaceable> of=<replaceable>smallfile</replaceable> bs=1024k count=5
</screen>
It will take the first five megabytes of
'<emphasis role="bold">your-file</emphasis>' and write it to
'<emphasis role="bold">small-file</emphasis>'. Then try again on
this small file and if the bug still shows up your sample is sufficient for us.
Please <emphasis role="bold">do not ever</emphasis> send such files via mail!
Upload it, and send only the path/filename of the file on the FTP-server. If the
file is accessible on the net, then sending the
<emphasis role="bold">exact</emphasis> URL is sufficient.
</para>
</sect2>
<!-- ********** -->
<sect2 id="bugreports_crash">
<title>Crashes</title>
<para>
You have to run <application>MPlayer</application> inside <command>gdb</command>
and send us the complete output or if you have a <filename>core</filename> dump
of the crash you can extract useful information from the Core file. Here's how:
</para>
<sect3 id="bugreports_debug">
<title>How to conserve information about a reproducible crash</title>
<para>
Recompile <application>MPlayer</application> with debugging code enabled:
<screen>
./configure --enable-debug=3
make
</screen>
and then run <application>MPlayer</application> within gdb using:
<screen>gdb ./mplayer</screen>
You are now within gdb. Type:
<screen>
run -v <replaceable>options-to-mplayer</replaceable> <replaceable>filename</replaceable>
</screen>
and reproduce your crash. As soon as you did it, gdb will return you to the
command line prompt where you have to enter
<screen>
bt
disass $pc-32 $pc+32
info all-registers
</screen>
</para>
</sect3>
<sect3 id="bugreports_core">
<title>How to extract meaningful information from a core dump</title>
<para>
Create the following command file:
<screen>
bt
disass $pc-32 $pc+32
info all-registers
</screen>
Then simply execute this command:
<screen>
gdb mplayer --core=core -batch --command=command_file &gt; mplayer.bug
</screen>
</para>
</sect3>
</sect2>
</sect1>
</appendix>
-76
View File
@@ -1,76 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<!-- $Revision$ -->
<bookinfo id="toc">
<title><application>MPlayer</application> - The Movie Player</title>
<subtitle><ulink url="http://www.mplayer2.org/"></ulink></subtitle>
<date>March 24, 2003</date>
<copyright>
<year>2000</year>
<year>2001</year>
<year>2002</year>
<year>2003</year>
<year>2004</year>
<year>2005</year>
<year>2006</year>
<year>2007</year>
<year>2008</year>
<year>2009</year>
<year>2010</year>
<year>2011</year>
<holder>MPlayer team</holder>
</copyright>
<legalnotice>
<title>License</title>
<para>MPlayer is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License version 2 as
published by the Free Software Foundation.</para>
<para>MPlayer is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
for more details.</para>
<para>You should have received a copy of the GNU General Public License
along with MPlayer; if not, write to the Free Software Foundation,
Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.</para>
</legalnotice>
</bookinfo>
<preface id="howtoread">
<title>How to read this documentation</title>
<para>
If you are a first-time installer: be sure to read everything from here to
the end of the Installation section, and follow the links you will find. If
you have any other questions, return to the <link linkend="toc">Table of
Contents</link> and search for the topic, read the <xref linkend="faq"/>,
or try grepping through the files.
</para>
</preface>
<chapter id="intro">
<title>Introduction</title>
OUTDATED CONTENT REMOVED
<para>
</para>
<!-- FIXME: the license should be in bookinfo -->
<para>
<application>MPlayer</application> and <application>MEncoder</application>
can be distributed under the terms of the GNU General Public License Version 2.
</para>
</chapter>
&install.xml;
&usage.xml;
&video.xml;
&ports.xml;
&mencoder.xml;
&encoding-guide.xml;
&faq.xml;
&bugreports.xml;
-9
View File
@@ -1,9 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<!-- $Revision$ -->
<chapter id="encoding-guide">
<title>Encoding with <application>MEncoder</application></title>
<para>
OUTDATED CONTENT REMOVED
</para>
</chapter>
-626
View File
@@ -1,626 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<!-- $Revision$ -->
<chapter id="faq" xreflabel="FAQ">
<title>Frequently Asked Questions</title>
<qandaset defaultlabel="qanda">
<qandadiv id="faq-development">
<title>Development</title>
<qandaentry>
<question><para>
How do I create a proper patch for <application>MPlayer</application>?
</para></question>
<answer><para>
OUTDATED CONTENT REMOVED
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
How do I translate <application>MPlayer</application> to a new language?
</para></question>
<answer><para>
OUTDATED CONTENT REMOVED
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
How can I support <application>MPlayer</application> development?
</para></question>
<answer><para>
OUTDATED CONTENT REMOVED
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
How can I become an <application>MPlayer</application> developer?
</para></question>
<answer><para>
OUTDATED CONTENT REMOVED
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
Why don't you use autoconf/automake?
</para></question>
<answer><para>
We have a modular, handwritten build system. It does a reasonably good
job, so why change? Besides, we dislike the auto* tools, just like
<ulink url="http://freshmeat.net/articles/view/889/">other people</ulink>.
</para></answer>
</qandaentry>
</qandadiv>
<!-- ********** -->
<qandadiv id="faq-compilation-installation">
<title>Compilation and installation</title>
<qandaentry>
<question><para>
Compilation fails with an error and <application>gcc</application> bails out
with some cryptic message containing the phrase
<systemitem>internal compiler error</systemitem> or
<systemitem>unable to find a register to spill</systemitem> or
<systemitem>can't find a register in class `GENERAL_REGS'
while reloading `asm'</systemitem>.
</para></question>
<answer><para>
You have stumbled over a bug in <application>gcc</application>. Please
<ulink url="http://gcc.gnu.org/bugs.html">report it to the gcc team</ulink>
but not to us. For some reason <application>MPlayer</application> seems to
trigger compiler bugs frequently. Nevertheless we cannot fix them and do not
add workarounds for compiler bugs to our sources. To avoid this problem,
either stick with a compiler version that is known to be reliable and
stable, or upgrade frequently.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
Are there binary (RPM/Debian) packages of <application>MPlayer</application>?
</para></question>
<answer><para>
OUTDATED CONTENT REMOVED
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
How can I build a 32 bit <application>MPlayer</application> on a 64 bit Athlon?
</para></question>
<answer><para>
OUTDATED CONTENT REMOVED
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
During 'make', <application>MPlayer</application> complains about
missing X11 libraries. I don't understand, I <emphasis>do</emphasis>
have X11 installed!?
</para></question>
<answer><para>
... but you don't have the X11 development package installed. Or not correctly.
It's called <filename>XFree86-devel*</filename> under Red Hat,
<filename>xlibs-dev</filename> under Debian Woody and
<filename>libx11-dev</filename> under Debian Sarge. Also check if the
<filename class="directory">/usr/X11</filename> and
<filename class="directory">/usr/include/X11</filename> symlinks exist.
</para></answer>
</qandaentry>
</qandadiv>
<!-- ********** -->
<qandadiv id="faq-general">
<title>General questions</title>
<qandaentry>
<question><para>
Are there any mailing lists on <application>MPlayer</application>?
</para></question>
<answer><para>
OUTDATED CONTENT REMOVED
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
I've found a nasty bug when I tried to play my favorite video!
Who should I inform?
</para></question>
<answer><para>
OUTDATED CONTENT REMOVED
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
How can I make a screenshot?
</para></question>
<answer><para>
You have to use a video output driver that does not employ an overlay to be
able to take a screenshot. Under X11, <option>-vo x11</option> will do, under
Windows <option>-vo directx:noaccel</option> works.
</para>
<para>
Alternatively you can run <application>MPlayer</application> with the
<systemitem>screenshot</systemitem> video filter
(<option>-vf screenshot</option>), and press the <keycap>s</keycap>
key to grab a screenshot.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
What is the meaning of the numbers on the status line?
</para></question>
<answer><para>
Example:
<screen>
A: 2.1 V: 2.2 A-V: -0.167 ct: 0.042 57/57 41% 0% 2.6% 0 4 49% 1.00x
</screen>
<variablelist>
<varlistentry>
<term><systemitem>A: 2.1</systemitem></term>
<listitem><para>audio position in seconds</para></listitem>
</varlistentry>
<varlistentry>
<term><systemitem>V: 2.2</systemitem></term>
<listitem><para>video position in seconds</para></listitem>
</varlistentry>
<varlistentry>
<term><systemitem>A-V: -0.167</systemitem></term>
<listitem><para>audio-video difference in seconds (delay)</para></listitem>
</varlistentry>
<varlistentry>
<term><systemitem>ct: 0.042</systemitem></term>
<listitem><para>total A-V sync correction done</para></listitem>
</varlistentry>
<varlistentry>
<term><systemitem>57/57</systemitem></term>
<listitem><para>
frames played/decoded (counting from last seek)
</para></listitem>
</varlistentry>
<varlistentry>
<term><systemitem>41%</systemitem></term>
<listitem><para>
video codec CPU usage in percent
(for slice rendering and direct rendering this includes video_out)
</para></listitem>
</varlistentry>
<varlistentry>
<term><systemitem>0%</systemitem></term>
<listitem><para>video_out CPU usage</para></listitem>
</varlistentry>
<varlistentry>
<term><systemitem>2.6%</systemitem></term>
<listitem><para>audio codec CPU usage in percent</para></listitem>
</varlistentry>
<varlistentry>
<term><systemitem>0</systemitem></term>
<listitem><para>frames dropped to maintain A-V sync</para></listitem>
</varlistentry>
<varlistentry>
<term><systemitem>4</systemitem></term>
<listitem><para>
current level of image postprocessing (when using <option>-autoq</option>)
</para></listitem>
</varlistentry>
<varlistentry>
<term><systemitem>49%</systemitem></term>
<listitem><para>
current cache size used (around 50% is normal)
</para></listitem>
</varlistentry>
<varlistentry>
<term><systemitem>1.00x</systemitem></term>
<listitem><para>playback speed as a factor of original speed</para></listitem>
</varlistentry>
</variablelist>
Most of them are for debug purposes, use the <option>-quiet</option>
option to make them disappear.
You might notice that video_out CPU usage is zero (0%) for some files.
This is because it is called directly from the codec and thus cannot
be measured separately. If you wish to know the video_out speed, compare
the difference when playing the file with <option>-vo null</option> and
your usual video output driver.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
There are error messages about file not found
<filename>/usr/local/lib/codecs/</filename> ...
</para></question>
<answer><para>
OUTDATED CONTENT REMOVED
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
How can I make <application>MPlayer</application> remember the options I
use for a particular file, e.g. <filename>movie.avi</filename>?
</para></question>
<answer><para>
Create a file named <filename>movie.avi.conf</filename> with the file-specific
options in it and put it in <filename class="directory">~/.mplayer</filename>.
Also see the manpage about <option>-use-filedir-conf</option>.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
How can I run <application>MPlayer</application> in the background?
</para></question>
<answer><para>
Use:
<screen>
OUTDATED CONTENT REMOVED
</screen>
</para></answer>
</qandaentry>
</qandadiv>
<!-- ********** -->
<qandadiv id="faq-playback">
<title>Playback problems</title>
<qandaentry>
<question><para>
I cannot pinpoint the cause of some strange playback problem.
</para></question>
<answer><para>
Do you have a stray <filename>codecs.conf</filename> file in
<filename>~/.mplayer/</filename>, <filename>/etc/</filename>,
<filename>/usr/local/etc/</filename> or a similar location? Remove it,
an outdated <filename>codecs.conf</filename> file can cause obscure
problems and is intended for use only by developers working on codec
support. It overrides <application>MPlayer</application>'s internal
codec settings, which will wreak havoc if incompatible changes are
made in newer program versions. Unless used by experts it is a recipe
for disaster in the form of seemingly random and very hard to localize
crashes and playback problems. If you still have it somewhere on your
system, you should remove it now.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
How can I get subtitles to appear on the black margins around a movie?
</para></question>
<answer><para>
OUTDATED CONTENT REMOVED
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
How can I select audio/subtitle tracks from a DVD, OGM, Matroska or NUT file?
</para></question>
<answer><para>
You have to use <option>-aid</option> (audio ID) or <option>-alang</option>
(audio language), <option>-sid</option>(subtitle ID) or <option>-slang</option>
(subtitle language), for example:
<screen>
mplayer -alang eng -slang eng <replaceable>example.mkv</replaceable>
mplayer -aid 1 -sid 1 <replaceable>example.mkv</replaceable>
</screen>
To see which ones are available:
<screen>
mplayer -vo null -ao null -frames 0 -v <replaceable>filename</replaceable> | grep sid
mplayer -vo null -ao null -frames 0 -v <replaceable>filename</replaceable> | grep aid
</screen>
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
I downloaded a movie off a P2P network and it doesn't work!
</para></question>
<answer><para>
Your file is most probably broken or a fake file. If you got it from
a friend, and he says it works, try comparing
<application>md5sum</application> hashes.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
I'm having trouble getting my subtitles to display, help!!
</para></question>
<answer><para>
OUTDATED CONTENT REMOVED
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
<application>MPlayer</application> dies with
<screen>MPlayer interrupted by signal 4 in module: decode_video</screen>
</para></question>
<answer><para>
Don't use <application>MPlayer</application> on a CPU different from the one
it was compiled on or recompile with runtime CPU detection
OUTDATED CONTENT REMOVED
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
When I try to grab from my tuner, it works, but colors are strange.
It's OK with other applications.
</para></question>
<answer><para>
Your card probably reports some colorspaces as supported when in fact
it does not support them. Try with YUY2 instead of the
default YV12 (see the <link linkend="tv-input">TV</link> section).
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
While playing a movie it suddenly gets jerky and I get the following message:
<screen>Badly interleaved AVI file detected - switching to -ni mode...</screen>
</para></question>
<answer><para>
Badly interleaved files and <option>-cache</option> don't work well together.
Try <option>-nocache</option>.
</para></answer>
</qandaentry>
</qandadiv>
<!-- ********** -->
<qandadiv id="faq-driver">
<title>Video/audio driver problems (vo/ao)</title>
<qandaentry>
<question><para>
When I go into fullscreen mode I just get black borders around the image
and no real scaling to fullscreen mode.
</para></question>
<answer><para>
Your video output driver does not support scaling in hardware and since
scaling in software can be incredibly slow <application>MPlayer</application>
does not automatically enable it. Most likely you are using the
<systemitem>x11</systemitem> instead of the <systemitem>xv</systemitem>
video output driver. Try adding <option>-vo xv</option> to the command
line or read the <link linkend="video">video section</link> to find out
about alternative video output drivers. The <option>-zoom</option>
option explicitly enables software scaling.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
I've just installed <application>MPlayer</application>. When I want to
open a video file it causes a fatal error:
<screen>Error opening/initializing the selected video_out (-vo) device.</screen>
How can I solve my problem?
</para></question>
<answer><para>
Just change your video output device. Issue the following command to get
a list of available video output drivers:
<screen>mplayer -vo help</screen>
After you've chosen the correct video output driver, add it to
your configuration file. Add
<programlisting>
vo = <replaceable>selected_vo</replaceable>
</programlisting>
to <filename>~/.mplayer/config</filename>
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
I have problems with <replaceable>[your window manager]</replaceable>
and fullscreen xv/xmga/sdl/x11 modes ...
</para></question>
<answer><para>
Read the <link linkend="bugreports">bug reporting guidelines</link> and send us
a proper bug report.
Also try experimenting with the <option>-fstype</option> option.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
How can I use <application>dmix</application> with
<application>MPlayer</application>?
</para></question>
<answer><para>
After setting up your
<ulink url="http://alsa.opensrc.org/index.php?page=DmixPlugin">asoundrc</ulink>
you have to use <option>-ao alsa:device=dmix</option>.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
I have no sound when playing a video and get error messages similar to this one:
<screen>
AO: [oss] 44100Hz 2ch Signed 16-bit (Little-Endian)
[AO OSS] audio_setup: Can't open audio device /dev/dsp: Device or resource busy
Could not open/initialize audio device -> no sound.
Audio: no sound
Starting playback...
</screen>
</para></question>
<answer><para>
Are you running KDE or GNOME with the aRts or ESD sound daemon? Try disabling
the sound daemon or use the <option>-ao arts</option> or
<option>-ao esd</option> option to make <application>MPlayer</application> use
aRts or ESD.
You might also be running ALSA without OSS emulation, try loading the ALSA OSS
kernel modules or add <option>-ao alsa</option> to your command line to
directly use the ALSA audio output driver.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
When starting <application>MPlayer</application> under KDE I just get a black
screen and nothing happens. After about one minute the video starts playing.
</para></question>
<answer><para>
The KDE aRts sound daemon is blocking the sound device. Either wait until the
video starts or disable the aRts daemon in control center. If you want to use
aRts sound, specify audio output via our native aRts audio driver
(<option>-ao arts</option>). If it fails or isn't compiled in, try SDL
(<option>-ao sdl</option>) and make sure your SDL can handle aRts sound. Yet
another option is to start <application>MPlayer</application> with artsdsp.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
I have A/V sync problems.
Some of my AVIs play fine, but some play with double speed!
</para></question>
<answer><para>
You have a buggy sound card/driver. Most likely it's fixed at 44100Hz, and you
try to play a file which has 22050Hz audio. Try the
<systemitem>resample</systemitem> audio filter.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
How can I get rid of A/V desynchronization
while seeking through RealMedia streams?
</para></question>
<answer><para>
<option>-mc 0.1</option> can help.
</para></answer>
</qandaentry>
</qandadiv>
<!-- ********** -->
<qandadiv id="faq-dvd">
<title>DVD playback</title>
<qandaentry>
<question><para>
What about DVD navigation/menus?
</para></question>
<answer><para>
<application>MPlayer</application> should support DVD menus nowadays.
Your mileage may vary.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
What about subtitles? Can <application>MPlayer</application> display them?
</para></question>
<answer><para>
Yes. See the <link linkend="dvd">DVD chapter</link>.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
How can I set the region code of my DVD-drive? I don't have Windows!
</para></question>
<answer><para>
Use the
<ulink url="http://linvdr.org/projects/regionset/">regionset tool</ulink>.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
I can't play a DVD, MPlayer hangs or outputs "Encrypted VOB file!" errors.
</para></question>
<answer><para>
CSS decryption code does not work with some DVD drives unless you set
the region code appropriately. See the answer to the previous question.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
Do I need to be (setuid) root to be able to play a DVD?
</para></question>
<answer><para>
No. However you must have the proper rights
on the DVD device entry (in <filename class="directory">/dev/</filename>).
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
Is it possible to play/encode only selected chapters?
</para></question>
<answer><para>
Yes, try the <option>-chapter</option> option.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
My DVD playback is sluggish!
</para></question>
<answer><para>
Use the <option>-cache</option> option (described in the man page) and try
enabling DMA for the DVD drive with the <command>hdparm</command> tool.
</para></answer>
</qandaentry>
<qandaentry>
<question><para>
I copied a DVD using vobcopy. How do I play/encode it from my hard disk?
</para></question>
<answer><para>
Use the <option>-dvd-device</option> option to refer to the directory
that contains the files:
<screen>
mplayer dvd://1 -dvd-device <replaceable>/path/to/directory</replaceable>
</screen>
</para></answer>
</qandaentry>
</qandadiv>
<qandadiv id="faq-features">
<title>Feature requests</title>
<qandaentry>
<question><para>
I'd like to seek +/- 1 frame instead of 10 seconds.
</para></question>
<answer><para>
You can step forward one frame by pressing <keycap>.</keycap>.
If the movie was not paused it will be paused afterwards
(see the man page for details).
Stepping backwards is not currently implemented, but note that you can make
small seeks using the <option>-hr-seek</option> functionality.
</para></answer>
</qandaentry>
</qandadiv>
<!-- ********** -->
<qandadiv id="faq-encoding">
<title>Encoding</title>
<para>
OUTDATED CONTENT REMOVED
</para>
</qandadiv>
</qandaset>
</chapter>
-96
View File
@@ -1,96 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<!-- $Revision$ -->
<chapter id="install">
<title>Installation</title>
<para>
A quick installation guide can be found in the <filename>README</filename>
file. Please read it first and then come back here for the rest of the gory
details.
</para>
<para>
In this section you will be guided through the compilation and configuration
process of <application>MPlayer</application>. It's not easy, but it won't
necessarily be hard. If you experience a behavior different from this
description, please search through this documentation and you'll find your
answers.
</para>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<sect1 id="softreq">
<title>Software requirements</title>
<para>
OUTDATED CONTENT REMOVED
</para>
</sect1>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<sect1 id="features">
<title>Features</title>
<para>
OUTDATED CONTENT REMOVED
</para>
</sect1>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<sect1 id="gui">
<title>What about the GUI?</title>
<para>
MPlayer used to have an internal GUI, but it was removed because it was
buggy, unmaintained and there are much better alternatives. See <ulink
url="http://www.mplayerhq.hu/design7/projects.html#mplayer_frontends">the
frontends page</ulink> for a list of existing GUIs.
</para>
</sect1>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<sect1 id="fonts-osd">
<title>Fonts and OSD</title>
<para>
OUTDATED CONTENT REMOVED
</para>
</sect1>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<sect1 id="codec-installation">
<title>Codec installation</title>
<para>
OUTDATED CONTENT REMOVED
</para>
</sect1>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<sect1 id="rtc">
<title>RTC</title>
<para>
OUTDATED CONTENT REMOVED
</para>
</sect1>
</chapter>
-10
View File
@@ -1,10 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<!-- $Revision$ -->
<chapter id="mencoder">
<title>Basic usage of <application>MEncoder</application></title>
<para>
OUTDATED CONTENT REMOVED
</para>
</chapter>
-10
View File
@@ -1,10 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<!-- $Revision$ -->
<chapter id="ports" xreflabel="Ports">
<title>Ports</title>
<para>
OUTDATED CONTENT REMOVED
</para>
</chapter>
File diff suppressed because it is too large Load Diff
-10
View File
@@ -1,10 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<!-- $Revision$ -->
<chapter id="video">
<title>Video output devices</title>
<para>
OUTDATED CONTENT REMOVED
</para>
</chapter>
-95
View File
@@ -1,95 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0">
<xsl:output method="html" indent="no"
doctype-system="http://www.w3.org/TR/html4/loose.dtd"
doctype-public="-//W3C//DTD HTML 4.01 Transitional//EN"/>
<!-- **************
Set parameters
************** -->
<xsl:param name="chunker.output.encoding" select="'utf-8'"/>
<xsl:output encoding="utf-8"/>
<xsl:param name="toc.section.depth" select="'4'"/>
<xsl:param name="html.stylesheet" select="'default.css'"/>
<xsl:param name="html.stylesheet.type" select="'text/css'"/>
<xsl:param name="html.cleanup" select="'1'"/>
<xsl:param name="make.valid.html" select="'1'"/>
<xsl:param name="make.single.year.ranges" select="'1'"/>
<xsl:param name="make.year.ranges" select="'1'"/>
<!-- Use ID value for generated filenames -->
<xsl:param name="use.id.as.filename" select="'1'"/>
<!-- Depth to which sections are chunked -->
<xsl:param name="chunk.section.depth" select="'1'"/>
<!-- Create a chunk for the 1st top-level section too -->
<xsl:param name="chunk.first.sections" select="'1'"/>
<xsl:param name="admon.graphics" select="'0'"/>
<xsl:param name="navig.graphics" select="'0'"/>
<xsl:param name="navig.showtitles" select="'1'"/>
<!-- Generate more links for Site Navigation Bar -->
<xsl:param name="html.extra.head.links" select="1"/>
<!-- Label sections too (eg. 2.1, 2.1.1) -->
<xsl:param name="section.autolabel" select="'1'"/>
<xsl:param name="section.label.includes.component.label" select="'1'"/>
<!-- Use informal procedures; no need to number them -->
<xsl:param name="formal.procedures" select="'0'"/>
<xsl:param name="generate.toc">
appendix toc
article toc
book toc
chapter toc
part toc
preface toc
qandadiv toc
qandaset toc
reference toc
section toc
set toc
</xsl:param>
<!-- *********
Templates
********* -->
<xsl:template match="application">
<span class="application"><xsl:apply-templates/></span>
</xsl:template>
<xsl:template match="option">
<tt class="option"><xsl:apply-templates/></tt>
</xsl:template>
<xsl:template match="filename">
<tt class="filename"><xsl:apply-templates/></tt>
</xsl:template>
<xsl:template match="keycap">
<span class="keycap"><b><xsl:apply-templates/></b></span>
</xsl:template>
<xsl:template match="guimenu">
<span class="guimenu"><xsl:apply-templates/></span>
</xsl:template>
<xsl:template match="guisubmenu">
<span class="guisubmenu"><xsl:apply-templates/></span>
</xsl:template>
<xsl:template match="guimenuitem">
<span class="guimenuitem"><xsl:apply-templates/></span>
</xsl:template>
</xsl:stylesheet>
-364
View File
@@ -1,364 +0,0 @@
<!DOCTYPE style-sheet PUBLIC
"-//James Clark//DTD DSSSL Style Sheet//EN" [
<!ENTITY % html "IGNORE">
<![%html;[
<!ENTITY % print "IGNORE">
<!ENTITY docbook.dsl PUBLIC
"-//Norman Walsh//DOCUMENT DocBook HTML Stylesheet//EN"
CDATA dsssl>
]]>
<!ENTITY % print "INCLUDE">
<![%print;[
<!ENTITY docbook.dsl PUBLIC
"-//Norman Walsh//DOCUMENT DocBook Print Stylesheet//EN"
CDATA dsssl>
]]>
]>
<style-sheet>
;; ------------------------------------------------------------------------
;; ldp.dsl - LDP Customized DSSSL Stylesheet
;; v1.11, 2003-02-03
;; Copyright (C) 2000-2003
;;
;; This program is free software; you can redistribute it and/or modify
;; it under the terms of the GNU General Public License as published by
;; the Free Software Foundation; either version 2 of the License, or
;; (at your option) any later version.
;;
;; This program is distributed in the hope that it will be useful,
;; but WITHOUT ANY WARRANTY; without even the implied warranty of
;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
;; GNU General Public License for more details.
;;
;; You should have received a copy of the GNU General Public License
;; along with this program; if not, write to the Free Software
;; Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
;; ------------------------------------------------------------------------
<style-specification id="print" use="docbook">
<style-specification-body>
;; customize the print stylesheet
(declare-characteristic preserve-sdata?
;; this is necessary because right now jadetex does not understand
;; symbolic entities, whereas things work well with numeric entities.
"UNREGISTERED::James Clark//Characteristic::preserve-sdata?"
#f)
(define %generate-article-toc%
;; Should a Table of Contents be produced for Articles?
#t)
(define (toc-depth nd)
4)
(define %generate-article-titlepage-on-separate-page%
;; Should the article title page be on a separate page?
#t)
(define %section-autolabel%
;; Are sections enumerated?
#t)
(define %footnote-ulinks%
;; Generate footnotes for ULinks?
#f)
(define %bop-footnotes%
;; Make "bottom-of-page" footnotes?
#f)
(define %body-start-indent%
;; Default indent of body text
0pi)
(define %para-indent-firstpara%
;; First line start-indent for the first paragraph
0pt)
(define %para-indent%
;; First line start-indent for paragraphs (other than the first)
0pt)
(define %block-start-indent%
;; Extra start-indent for block-elements
0pt)
(define formal-object-float
;; Do formal objects float?
#t)
(define %hyphenation%
;; Allow automatic hyphenation?
#t)
(define %admon-graphics%
;; Use graphics in admonitions?
#f)
(define %default-quadding%
;; Full justification.
'justify)
(define (book-titlepage-verso-elements)
;;added publisher, releaseinfo to the default list
(list (normalize "title")
(normalize "subtitle")
(normalize "corpauthor")
(normalize "authorgroup")
(normalize "author")
(normalize "publisher")
(normalize "releaseinfo")
(normalize "editor")
(normalize "edition")
(normalize "pubdate")
(normalize "copyright")
(normalize "abstract")
(normalize "legalnotice")
(normalize "revhistory")))
</style-specification-body>
</style-specification>
<!--
;; customize the html stylesheet; parts borrowed from
;; Cygnus at http://sourceware.cygnus.com/ (cygnus-both.dsl)
-->
<style-specification id="html" use="docbook">
<style-specification-body>
(declare-characteristic preserve-sdata?
;; this is necessary because right now jadetex does not understand
;; symbolic entities, whereas things work well with numeric entities.
"UNREGISTERED::James Clark//Characteristic::preserve-sdata?"
#f)
(declare-flow-object-class element
;; for redhat
"UNREGISTERED::James Clark//Flow Object Class::element")
(define %generate-legalnotice-link%
;; put the legal notice in a separate file
#t)
(define %admon-graphics-path%
;; use graphics in admonitions, set their
"../images/")
(define %admon-graphics%
#t)
(define %funcsynopsis-decoration%
;; make funcsynopsis look pretty
#t)
(define %html-ext%
;; when producing HTML files, use this extension
".html")
(define %generate-book-toc%
;; Should a Table of Contents be produced for books?
#t)
(define %generate-article-toc%
;; Should a Table of Contents be produced for articles?
#t)
(define %generate-part-toc%
;; Should a Table of Contents be produced for parts?
#t)
(define %generate-book-titlepage%
;; produce a title page for books
#t)
(define %generate-article-titlepage%
;; produce a title page for articles
#t)
(define (chunk-skip-first-element-list)
;; forces the Table of Contents on separate page
'())
(define (list-element-list)
;; fixes bug in Table of Contents generation
'())
(define %root-filename%
;; The filename of the root HTML document (e.g, "index").
"index")
(define %shade-verbatim%
;; verbatim sections will be shaded if t(rue)
#t)
(define %use-id-as-filename%
;; Use ID attributes as name for component HTML files?
#t)
(define %graphic-extensions%
;; graphic extensions allowed
'("gif" "png" "jpg" "jpeg" "tif" "tiff" "eps" "epsf" ))
(define %graphic-default-extension%
"gif")
(define %section-autolabel%
;; For enumerated sections (1.1, 1.1.1, 1.2, etc.)
#t)
(define (toc-depth nd)
;; more depth (2 levels) to toc; instead of flat hierarchy
2)
(element emphasis
;; make role=strong equate to bold for emphasis tag
(if (equal? (attribute-string "role") "strong")
(make element gi: "STRONG" (process-children))
(make element gi: "EM" (process-children))))
(define (book-titlepage-recto-elements)
;; elements on a book's titlepage
(list (normalize "title")
(normalize "subtitle")
(normalize "graphic")
(normalize "mediaobject")
(normalize "corpauthor")
(normalize "authorgroup")
(normalize "author")
(normalize "othercredit")
(normalize "edition")
(normalize "releaseinfo")
(normalize "publisher")
(normalize "editor")
(normalize "copyright")
(normalize "pubdate")
(normalize "revhistory")
(normalize "abstract")
(normalize "legalnotice")))
(define (article-titlepage-recto-elements)
;; elements on an article's titlepage
(list (normalize "title")
(normalize "subtitle")
(normalize "authorgroup")
(normalize "author")
(normalize "othercredit")
(normalize "releaseinfo")
(normalize "copyright")
(normalize "pubdate")
(normalize "revhistory")
(normalize "abstract")
(normalize "legalnotice")))
(define (process-contrib #!optional (sosofo (process-children)))
;; print out with othercredit information; for translators, etc.
(make sequence
(make element gi: "SPAN"
attributes: (list (list "CLASS" (gi)))
(process-children))))
(define (process-othercredit #!optional (sosofo (process-children)))
;; print out othercredit information; for translators, etc.
(let ((author-name (author-string))
(author-contrib (select-elements (children (current-node))
(normalize "contrib"))))
(make element gi: "P"
attributes: (list (list "CLASS" (gi)))
(make element gi: "B"
(literal author-name)
(literal " - "))
(process-node-list author-contrib))))
(mode article-titlepage-recto-mode
(element contrib (process-contrib))
(element othercredit (process-othercredit))
)
(mode book-titlepage-recto-mode
(element contrib (process-contrib))
(element othercredit (process-othercredit))
)
(define (article-title nd)
(let* ((artchild (children nd))
(artheader (select-elements artchild (normalize "artheader")))
(artinfo (select-elements artchild (normalize "articleinfo")))
(ahdr (if (node-list-empty? artheader)
artinfo
artheader))
(ahtitles (select-elements (children ahdr)
(normalize "title")))
(artitles (select-elements artchild (normalize "title")))
(titles (if (node-list-empty? artitles)
ahtitles
artitles)))
(if (node-list-empty? titles)
""
(node-list-first titles))))
(mode subtitle-mode
;; do not print subtitle on subsequent pages
(element subtitle (empty-sosofo)))
;; Redefinition of $verbatim-display$
;; Origin: dbverb.dsl
;; Different foreground and background colors for verbatim elements
;; Author: Philippe Martin (feloy@free.fr) 2001-04-07
(define ($verbatim-display$ indent line-numbers?)
(let ((verbatim-element (gi))
(content (make element gi: "PRE"
attributes: (list
(list "CLASS" (gi)))
(if (or indent line-numbers?)
($verbatim-line-by-line$ indent line-numbers?)
(process-children)))))
(if %shade-verbatim%
(make element gi: "TABLE"
attributes: (shade-verbatim-attr-element verbatim-element)
(make element gi: "TR"
(make element gi: "TD"
(make element gi: "FONT"
attributes: (list
(list "COLOR" (car (shade-verbatim-element-colors
verbatim-element))))
content))))
content)))
;;
;; Customize this function
;; to change the foreground and background colors
;; of the different verbatim elements
;; Return (list "foreground color" "background color")
;;
(define (shade-verbatim-element-colors element)
(case element
(("SYNOPSIS") (list "#000000" "#6495ED"))
;; ...
;; Add your verbatim elements here
;; ...
(else (list "#000000" "#E0E0E0"))))
(define (shade-verbatim-attr-element element)
(list
(list "BORDER"
(cond
((equal? element (normalize "SCREEN")) "1")
(else "0")))
(list "BGCOLOR" (car (cdr (shade-verbatim-element-colors element))))
(list "WIDTH" ($table-width$))))
;; End of $verbatim-display$ redefinition
</style-specification-body>
</style-specification>
<external-specification id="docbook" document="docbook.dsl">
</style-sheet>
-27
View File
@@ -1,27 +0,0 @@
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version='1.0'
xmlns="http://www.w3.org/TR/xhtml1/transitional"
exclude-result-prefixes="#default">
<!-- $Id$ -->
<!-- This stylesheet calls Norman Walsh's 'docbook.xsl' stylesheet
and therefore generates MULTIPLE HTML FILES as output. -->
<!-- Note the the *order* of the import statements below is important and
should not be changed. -->
<!-- Change this to the path to where you have installed Norman
Walsh's XSL stylesheets -->
<xsl:import href="/usr/share/sgml/docbook/xsl-stylesheets-1.60.1/html/chunk.xsl"/>
<!-- Imports the common LDP customization layer. -->
<xsl:import href="ldp-html-common.xsl"/>
<!-- If there was some reason to override 'ldp-html-common.xsl' or to
perform any other customizations that affect *only* the generation
of multiple HTML files, those templates or parameters could be
entered here. -->
</xsl:stylesheet>
-228
View File
@@ -1,228 +0,0 @@
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version='1.0'
xmlns="http://www.w3.org/TR/xhtml1/transitional"
exclude-result-prefixes="#default">
<!-- $Id -->
<!-- Experimental stylesheet by Dan York
This is an attempt to replicate the customizations done in ldp.dsl
Each customization in ldp.dsl is listed in the order in which it
appears (in ldp.dsl) with the corresponding XSLT template or setting
below it. Where there is no XSLT code below an item, that particular
customization of ldp.dsl is not yet supported here. Some additional
options and features have been added and are noted as not being in
ldp.dsl. The work on this stylesheet began 5 Jul 2001. -->
<!-- Note that this file, 'ldp-html-common.xsl', is NOT intended to be
called directly. Instead, you should call either of two stylesheets:
'ldp-html.xsl' or 'ldp-html-chunk.xsl'. The former generates a SINGLE
HTML file, while the latter performs "chunking" to generate MULTIPLE
HTML files. Both of those files import the appropriate Norman Walsh
stylesheet and then import this customization layer. -->
<!-- NOT IN LDP.DSL - This stylesheet supports the additional use of the
"role" and "condition" attributes to the <author> tag. The XSLT template
is listed later in the stylesheet, but the text lables are listed
here in order to make localization of the stylesheet easier. Note
that spaces *are* significant in the value, so you should have a
space after the colon. -->
<xsl:variable name="maintainerlabel">Maintainer: </xsl:variable>
<xsl:variable name="authorlabel">Author: </xsl:variable>
<!-- NOT IN LDP.DSL
Creates header content in all generated HTML files -->
<xsl:template name="user.head.content">
<xsl:param name="node" select="."/>
<meta name="generator" content="Experimental LDP.XSL $Revision$"/>
<xsl:text>
</xsl:text>
<xsl:comment> Generated by LDP XSLT customization layer
based on Norman Walsh's DocBook XSL stylesheets.
More information at http://www.linuxdoc.org/ </xsl:comment>
<xsl:text>
</xsl:text>
</xsl:template>
<!-- declare-characteristic preserve-sdata?
No longer appears necessary as it is a JadeTex issue. -->
<!-- generate-legalnotice-link?
Not currently supported in Norm's XSL stylesheets. Logged
at SourceForge as a bug. -->
<!-- Should graphics be used for admonitions (notes, warnings)? 0 or 1 -->
<xsl:param name="admon.graphics" select="0"/>
<!-- If using admon graphics (1 above), what is path to graphics?
Should be the path relative to your document and MUST end with
a trailing slash. Also, this parameter needs to be on a
single line. -->
<xsl:param name="admon.graphics.path">images/</xsl:param>
<!-- Make funcsynopsis look pretty -->
<xsl:param name="funcsynopsis.decoration" select="1" doc:type="boolean"/>
<!-- Extension for HTML files -->
<xsl:param name="html.ext" select="'.html'"/>
<!-- Generate TOCs for book, article, part -->
<xsl:param name="generate.book.toc" select="1" doc:type="boolean"/>
<xsl:param name="generate.article.toc" select="1" doc:type="boolean"/>
<xsl:param name="generate.part.toc" select="1" doc:type="boolean"/>
<!-- generate-book-titlepage -->
<!-- generate-article-titlepage -->
<!-- Equivalent to chunk-skip-first-element-list - forces TOC on separate page
If 0, first sect is on page for chapter or article -->
<xsl:param name="chunk.first.sections" select="'1'"/>
<!-- NOT IN LDP.DSL -->
<!-- Create chunks for top-level sections. If 0, chunks will only be
created for chapters/appendixes, and NOT for sectx elements -->
<xsl:param name="chunk.sections" select="'1'"/>
<!-- list-element-list - NO LONGER NEEDED - bug fix -->
<!-- Filename for the root chunk -->
<xsl:param name="root.filename" select="'index'"/>
<!-- shade-verbatim
I have created a function below that shades the verbatim sections.
logic would need to be added to check if this is set.
Norm has added parameters to his 1.44 stylesheets that support
shading verbatim sections. However, it looks like it requires
an attribute to a table to have verbatim shading. Needs to be
explored further. -->
<!-- When chunking, use id attribute as filename? 0 or 1 -->
<xsl:param name="use.id.as.filename" select="1"/>
<!-- graphic-extensions - NO LONGER NEEDED?? -->
<!-- default graphic filename extension -->
<xsl:param name="graphic.default.extension" select="'.gif'" doc:type="string"/>
<!-- Should chapters be labeled? 0 or 1 -->
<xsl:param name="chapter.autolabel" select="1"/>
<!-- Should sections be labeled? 0 or 1 -->
<xsl:param name="section.autolabel" select="1"/>
<!-- Related to section labels, should those labels include the chapter
number in them (i.e., 1.1, 1.2, 1.3, 1.4 )-->
<xsl:param name="section.label.includes.component.label" select="1" doc:type="boolean"/>
<!-- To what depth (in sections) should the TOC go? -->
<xsl:param name="toc.section.depth" select="2"/>
<!-- Custom 'emphasis' template to allow 'role="strong"' to
also produce a bold item. -->
<xsl:template match="emphasis">
<xsl:choose>
<xsl:when test="(@role='strong') or (@role='bold')">
<xsl:call-template name="inline.boldseq"/>
</xsl:when>
<xsl:otherwise>
<xsl:call-template name="inline.italicseq"/>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
<!-- book-titlepage-recto-elements
article-titlepage-recto-elements
article-titlepage-recto-mode
article-title
- Customizing these elements (for instance, to list what is on the
title page) involves writing a layer for html/titlepage.templates.xml and the
other files html/titlepage.xsl and html/titlepage.templates.xsl - Norm
is doing something funky here and I haven't fully figured it out. -->
<!-- The remainder of ldp.dsl deals with changing the foreground and
background colors of verbatim elements although in reading through the
DSSSL it doesn't look like it actually changed the foreground colors.
The changing of the background shading can be done at two locations
(one numbered, one not) in the template below. -->
<!-- Custom template for programlisting, screen and synopsis to generate a gray
background to the item. -->
<xsl:template match="programlisting|screen|synopsis">
<xsl:param name="suppress-numbers" select="'0'"/>
<xsl:variable name="vendor" select="system-property('xsl:vendor')"/>
<xsl:variable name="id"><xsl:call-template name="object.id"/></xsl:variable>
<xsl:if test="@id">
<a href="{$id}"/>
</xsl:if>
<xsl:choose>
<xsl:when test="$suppress-numbers = '0'
and @linenumbering = 'numbered'
and $use.extensions != '0'
and $linenumbering.extension != '0'">
<xsl:variable name="rtf">
<xsl:apply-templates/>
</xsl:variable>
<!-- Change the color bacground color in the line below. -->
<table border="0" bgcolor="#E0E0E0" width="90%">
<tr><td>
<pre class="{name(.)}">
<xsl:call-template name="number.rtf.lines">
<xsl:with-param name="rtf" select="$rtf"/>
</xsl:call-template>
</pre>
</td></tr></table>
</xsl:when>
<xsl:otherwise>
<!-- Change the color bacground color in the line below. -->
<table border="0" bgcolor="#E0E0E0" width="90%">
<tr><td>
<pre class="{name(.)}">
<xsl:apply-templates/>
</pre>
</td></tr></table>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
<!-- NOT IN LDP.DSL. Custom template to allow Maintainer to be a role in
the Author element. It also checks for a "condition" attribute
to the <author> element. If it finds the condition attribute, it
copies VERBATIM the value of the attribute to be in front of the
word Author or Maintainer. This is done to allow maximum flexibility.
Note that an <xsl:text> element was necessary to put the space
between the condition and the word Author or Maintainer. -->
<xsl:template match="author" mode="titlepage.mode">
<h3 class="{name(.)}">
<!-- If there is a condition attribute, print it VERBATIM first -->
<xsl:if test="@condition"><i><xsl:value-of select="@condition"/></i>
<xsl:text> </xsl:text></xsl:if>
<!-- Test to see if there is a role. If maintainer, print that. If not,
assume it is an author. -->
<xsl:choose>
<xsl:when test="@role='maintainer'">
<i><xsl:value-of select="$maintainerlabel"/></i>
</xsl:when>
<xsl:otherwise>
<i><xsl:value-of select="$authorlabel"/></i>
</xsl:otherwise>
</xsl:choose>
<xsl:call-template name="person.name"/>
</h3>
<xsl:apply-templates mode="titlepage.mode" select="./contrib"/>
<xsl:apply-templates mode="titlepage.mode" select="./affiliation"/>
</xsl:template>
</xsl:stylesheet>
-27
View File
@@ -1,27 +0,0 @@
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version='1.0'
xmlns="http://www.w3.org/TR/xhtml1/transitional"
exclude-result-prefixes="#default">
<!-- $Id$ -->
<!-- This stylesheet calls Norman Walsh's 'docbook.xsl' stylesheet
and therefore generates a SINGLE HTML FILE as output. -->
<!-- Note the the *order* of the import statements below is important and
should not be changed. -->
<!-- Change this to the path to where you have installed Norman
Walsh's XSL stylesheets. -->
<xsl:import href="/usr/share/sgml/docbook/xsl-stylesheets-1.60.1/html/docbook.xsl"/>
<!-- Imports the common LDP customization layer. -->
<xsl:import href="/home/n/xml/xsl/ldp-html-common.xsl"/>
<!-- If there was some reason to override 'ldp-html-common.xsl' or to
perform any other customizations that affect *only* the generation
of a single HTML file, those templates or parameters could be
entered here. -->
</xsl:stylesheet>
-18
View File
@@ -1,18 +0,0 @@
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version='1.0'
xmlns="http://www.w3.org/TR/xhtml1/transitional"
exclude-result-prefixes="#default">
<!-- $Id$ -->
<!-- This stylesheet will eventually include print customizations
from LDP.DSL. At the current time, it has not been developed.-->
<!-- Change this to the path to where you have installed Norman
Walsh's XSL stylesheets. -->
<xsl:import href="/usr/share/sgml/docbook/docbook-xsl-1.41/fo/docbook.xsl"/>
<!-- Customized parameters and templates go here. -->
</xsl:stylesheet>