diff options
Diffstat (limited to 'doc/faq/faq.sgml')
| -rw-r--r-- | doc/faq/faq.sgml | 76 |
1 files changed, 38 insertions, 38 deletions
diff --git a/doc/faq/faq.sgml b/doc/faq/faq.sgml index 5a713e306..23ff8ebb8 100644 --- a/doc/faq/faq.sgml +++ b/doc/faq/faq.sgml @@ -43,7 +43,7 @@ </sect2> <sect2 id="wheretogethelp"> - <title>My question is not yet covered here - where can I ask for help?</title> + <title>My question is not yet covered here – where can I ask for help?</title> <para> First of all be sure that your question is really not covered here and that you haven't just been a bit too lazy to read through all of this @@ -52,7 +52,7 @@ <command>totem</command>). </para> <para> - That said - you are welcome to mail to our user mailing list: + That said – you are welcome to mail to our user mailing list: <email>xine-user@lists.sourceforge.net</email> Please provide some info about your setup so people have a chance to help you, e.g. include information about your audio/video hardware @@ -75,7 +75,7 @@ </sect2> <sect2 id="modules"> - <title>What are those xine-lib, xine-ui, gnome-xine, ... modules in cvs for?</title> + <title>What are those xine-lib, xine-ui, gnome-xine, … modules in cvs for?</title> <para> Some time ago xine just became too complex to be just one big program. Therefore it was split into two major parts. @@ -86,7 +86,7 @@ is covered in this FAQ.) </para> <para> - Then there are frontends - applications that use xine. The most + Then there are frontends – applications that use xine. The most common frontend is that of a media player. There are currently two frontends being developed in the xine project, xine-ui (skinned dvd-player style frontend directly based on xlib) and gxine, @@ -152,7 +152,7 @@ <para> First, make sure that you're using a current development version (see above) or at least the current release version. Then, once you're - ready to send the patch... + ready to send the patch… </para> <para> Generate your patch using either <command>cvs diff -u > @@ -162,17 +162,17 @@ patch. Your patch should be applicable using <command>patch -p0 -i my.patch</command> or, preferably, <command>patch -p1 -i my.patch</command> from the top-level directory in the source tree - (i.e. where configure.ac is) - this is fairly important for our + (i.e. where configure.ac is) – this is fairly important for our Mercurial-based repositories since it makes importing your patch that much easier (hg import defaults to -p1). </para> <para> Alternatively, if you've been hacking away at a module which is - maintained using mercurial, you can make them available as diffs - use + maintained using mercurial, you can make them available as diffs – use <command>hg export</command> or, if you have several patches, you could use <command>hg bundle</command> instead (both require extra parameters; <command>hg help export</command> and <command>hg help - bundle</command> for more details) - or via HTTP by using <command>hg + bundle</command> for more details) – or via HTTP by using <command>hg serve</command>. In the latter case, you'll need to post a URL from which a developer can pull the changes. </para> @@ -194,8 +194,8 @@ <para> The xine project does not provide pre-compiled binaries for legal reasons (some parts of xine may be covered by patents in some countries). - Some OS projects/vendors (e.g. debian, freebsd, ...) offer binaries - for their distributions - please contact them or use their package search + Some OS projects/vendors (e.g. Debian, FreeBSD, …) offer binaries + for their distributions – please contact them or use their package search tools for further info. You can also find links to third parties providing xine RPMs on the xine homepage at @@ -221,13 +221,13 @@ </para> <para> Furthermore you'll have to use GNU make to compile xine. On most GNU/Linux - systems "make" is GNU make - on other platforms use "gmake" instead. + systems "make" is GNU make – on other platforms use "gmake" instead. Also, zlib is required (including the appropriate header files, which are often found in a package called zlib-devel or similar.) </para> <para> If you want to compile xine from CVS, you'll need to have the autobuild tools - installed (automake, autoconf and libtool - in recent versions). + installed (automake, autoconf and libtool – in recent versions). </para> <para> Frontends might need additional libraries, e.g. for gxine you'll need to have @@ -274,7 +274,7 @@ <screen> <command>ldconfig</command></screen> </para> <para> - Now unpack your frontend (gxine or xine-ui or ...), then: + Now unpack your frontend (gxine or xine-ui or …), then: <screen> <command>./configure</command> <command>make install</command></screen> @@ -292,7 +292,7 @@ <para> If you have installed xine-lib to a non-standard prefix, make sure that you have <filename>$prefix/bin</filename> in your PATH and that your linker finds - libs in <filename>$prefix/lib</filename> - otherwise trying to build modules that + libs in <filename>$prefix/lib</filename> – otherwise trying to build modules that rely on xine-lib will fail with configure complaining about not finding certain parts of libxine. Using bash you can do something like: <screen> @@ -304,7 +304,7 @@ Last but not least. Here the build instructions. As stated earlier, those are the same for every xine module. <screen> - <command>./autogen.sh</command> [-> *only* if you checked your sources out of CVS] + <command>./autogen.sh</command> [→ <emphasis>only</emphasis> if you checked your sources out of CVS] <command>./configure</command> <command>make</command> <command>make install</command></screen> @@ -477,7 +477,7 @@ </sect2> <sect2> - <title>Build problems in frontends (gxine/xine-ui/...)</title> + <title>Build problems in frontends (gxine/xine-ui/…)</title> <sect3 id="xinelibnotfound"> <title>I have installed xine-lib but the frontend complains about not finding it!</title> <para> @@ -504,7 +504,7 @@ <screen> <command>mkdir ~/xine</command></screen> </para> <para> - Then you have to set a few environment variables - it's probably a good + Then you have to set a few environment variables – it's probably a good idea to add this to your <filename>~/.bashrc</filename> (or somewhere similar): <screen> <command>export PATH="$HOME/xine/bin:$PATH"</command> @@ -561,7 +561,7 @@ check out you boot/kernel logs (or run <command>cdrecord -scanbus</command>) to find out which device it got mapped to and set the symlink accordingly (should be something like <filename>/dev/scd0</filename>, - <filename>/dev/scd1</filename>, ... in that case). + <filename>/dev/scd1</filename>, … in that case). Also make sure you (as a user) have sufficient (read and write) permissions on your DVD drive. This could mean you either have to change the device permissions or add your user to a special group @@ -954,7 +954,7 @@ <title>Running xine</title> <sect2 id="speedup"> - <title>I have a lot of dropped frames - what can I do?</title> + <title>I have a lot of dropped frames – what can I do?</title> <para> Your hardware might be too slow for xine. Make sure you turn on all speed optimizing options. A few things you should check (in order of @@ -1062,7 +1062,7 @@ be enough (use a recent kernel!). </para> <para> - Try a <command>cat /proc/mtrr</command> - if the file exists and you find an entry + Try a <command>cat /proc/mtrr</command> – if the file exists and you find an entry corresponding to the amount of graphics memory you have, everything should be fine. </para> @@ -1077,7 +1077,7 @@ <para> Use the "top" utility and verify under the "NI" column if the X process has a negative value, this indicates a higher priority. - See "The X Window User HOWTO - Performance considerations" for + See "The X Window User HOWTO – Performance considerations" for further instructions <ulink url="http://www.tldp.org/HOWTO/XWindow-User-HOWTO/performance.html"> http://www.tldp.org/HOWTO/XWindow-User-HOWTO/performance.html @@ -1194,7 +1194,7 @@ </sect2> <sect2 id="ports"> - <title>I have problems when using xine on FreeBSD, Solaris, ... !</title> + <title>I have problems when using xine on FreeBSD, Solaris, … !</title> <para> Check out the the corresponding README files in the directory <filename>xine-lib/doc</filename>. </para> @@ -1205,7 +1205,7 @@ <para> aalib is an ascii art library. xine comes with an aalib video output plugin so you can watch movies in your xterm, on the console or on your - old vt100 - very cool ;> ... another nice option is to preview movies + old vt100 – very cool ;> … another nice option is to preview movies on a remote server in your shell over ssh. </para> <para> @@ -1240,7 +1240,7 @@ <para> Currently xine support audio output via OSS (kernel audio drivers), ALSA 0.9.x (ALSA 0.5.x is no longer supported), arts (KDE's sound daemon) - and esound (esd, gnome's sound daemon - not recommended because it has + and esound (esd, gnome's sound daemon – not recommended because it has serious issues with a/v sync). </para> </sect2> @@ -1284,7 +1284,7 @@ <para> If this happens with any video, first try a different audio driver (<command>gxine -A oss</command>, <command>gxine -A arts</command>, - <command>xine -A alsa</command> ...). + <command>xine -A alsa</command> …). </para> <para> If this problem only occurs with one specific stream, maybe switching to @@ -1506,8 +1506,8 @@ </para> <para> Another, whole different possibility is that you have some background - process running which is messing with the clock (like some ntp client - - chronny, ntpd, ...). + process running which is messing with the clock (like some ntp client – + chrony, ntpd, …). </para> <para> Occasional messages of "fixing sound card drift" may happen on start and @@ -1545,9 +1545,9 @@ <title>Video related questions</title> <sect2 id="novideo"> - <title>I can hear the audio - but I don't see a picture!</title> + <title>I can hear the audio – but I don't see a picture!</title> <para> - Probably your hardware is simply too slow - see above for some + Probably your hardware is simply too slow – see above for some hints on how to speed things up. </para> <para> @@ -1846,7 +1846,7 @@ </para> <para> Drivers that access hardware directly includes VIDIX (warning: requires - root priviledges or kernel helper) and SyncFB (requires kernel helper - Matrox only). + root priviledges or kernel helper) and SyncFB (requires kernel helper – Matrox only). User may try one of those, but should be warned that with root access they can cause the system to crash hard. The support is also limited to a couple of graphics cards only. @@ -1995,7 +1995,7 @@ <para> The font for text subtitles is selected via config option <parameter>subtitles.separate.font</parameter>. You can specify xine font name - (<parameter>sans</parameter>, <parameter>serif</parameter>, ...) + (<parameter>sans</parameter>, <parameter>serif</parameter>, …) or file name of the TTF font. The directories <filename>$prefix/share/xine/libxine1/fonts</filename> and <filename>~/.xine/fonts</filename> are searched for the fonts, with @@ -2032,7 +2032,7 @@ </para> <para> Syntax is: - <screen> <command>./xine-fontconf font.ttf font_name [encoding1 [encoding2 [...]]]</command></screen> + <screen> <command>./xine-fontconf font.ttf font_name [encoding1 [encoding2 […]]]</command></screen> </para> <para> For example default font <filename>sans</filename> was generated with @@ -2129,9 +2129,9 @@ <title>"Unable to open dvd drive (/dev/dvd)"</title> <para> You probably don't have /dev/dvd (check that). If so, simply create a - link /dev/dvd that points to your DVD device. Something like... + link /dev/dvd that points to your DVD device. Something like… <screen> <command>ln -s hdc /dev/dvd</command></screen> - ...should do the job. Also make sure you have read and write access on + … should do the job. Also make sure you have read and write access on the device the symlink points to. See the <link linkend="dvdplayback">dvd playback section</link> for more information. @@ -2183,7 +2183,7 @@ standby" or just kill it. Then xine will use OSS audio output. The other method is to make xine use ESD for audio output with: <screen> <command>gxine -A esd</command></screen> - This may result in worse playback - exact syncronization is not possible + This may result in worse playback – exact syncronization is not possible with esd, so using oss should be preferred. </para> <para> @@ -2197,7 +2197,7 @@ your aRts control. (recommended) </para> <para> - Newer versions of arts have an auto-suspend mode - this can lead to + Newer versions of arts have an auto-suspend mode – this can lead to some nondeterministic behaviour of xine if it is set up to use the audio device directly. Using arts is recommended in that case; however, you will lose the ability to do four/five channel audio output. @@ -2236,7 +2236,7 @@ </sect2> <sect2 id="xinecrashed"> - <title>xine just crashed on me - i didn't get any error message</title> + <title>xine just crashed on me – i didn't get any error message</title> <para> OK, yes, that shouldn't happen and you're upset. We can understand that. But, to help you and of course to fix this, we need some information. @@ -2290,7 +2290,7 @@ If you write to the <ulink url="http://bugs.xine-project.org/">xine bug tracker</ulink> 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 + 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> |