summaryrefslogtreecommitdiff
path: root/doc/faq/faq.sgml
diff options
context:
space:
mode:
authorGuenter Bartsch <guenter@users.sourceforge.net>2003-01-05 12:33:48 +0000
committerGuenter Bartsch <guenter@users.sourceforge.net>2003-01-05 12:33:48 +0000
commitebf1669d062f8e104323f2c2a3527fcd31f61bd9 (patch)
tree1fb210e01b19b7dc1601bd19d2f87b8081370814 /doc/faq/faq.sgml
parent52cc68f4f3b8839039b8edf9ab0a54f320e78365 (diff)
downloadxine-lib-ebf1669d062f8e104323f2c2a3527fcd31f61bd9.tar.gz
xine-lib-ebf1669d062f8e104323f2c2a3527fcd31f61bd9.tar.bz2
small corrections and do not mention the bug report form anymore
CVS patchset: 3782 CVS date: 2003/01/05 12:33:48
Diffstat (limited to 'doc/faq/faq.sgml')
-rw-r--r--doc/faq/faq.sgml14
1 files changed, 9 insertions, 5 deletions
diff --git a/doc/faq/faq.sgml b/doc/faq/faq.sgml
index 71c76eb67..0b6bd200e 100644
--- a/doc/faq/faq.sgml
+++ b/doc/faq/faq.sgml
@@ -982,7 +982,7 @@
binary named <command>aaxine</command> should get built and installed. You can then use
something like:
<programlisting>
- aacine foo.mpg
+ aaxine foo.mpg
</programlisting>
to use aalib video output.
</para>
@@ -990,7 +990,7 @@
<sect1>
- <title>What do all these ~/.xine/config entries mean?</title>
+ <title>What do all these <filename>~/.xine/config</filename> entries mean?</title>
<para>
You can find information about them in <filename>xine-ui/doc/README.config_en</filename>.
@@ -1450,9 +1450,13 @@
still under heavy development (nice excuse, isn't it? *grin*).
</para>
<para>
- Please take a look at our bug report form which is located in the xine-lib
- package (doc/bug_report_form). Fill it out accordingly and sent it to our
- user mailing list: <email>xine-user@lists.sourceforge.net</email>
+ If you write to the xine user mailing list
+ <email>xine-user@lists.sourceforge.net</email>
+ make sure you include a the above information (when applicable)
+ and also some information about your machine (operating system, cpu type and
+ speed, gfx card, sound card, ...) and please use a meaningfull subject
+ line ("xine bug" is bad, "xine fails to play this quicktime trailer in fullscreen mode"
+ ist much better).
</para>
<para>
Thanks for taking the time to help improve xine.