Fix references to user profile directory.

1 files changed, 8 insertions, 8 deletions

diff --git a/doc/en/index.docbook b/doc/en/index.docbook
index 8715720..c942781 100644
--- a/doc/en/index.docbook
+++ b/doc/en/index.docbook
@@ -134,7 +134,7 @@ category and playings starts at the clicked item position.
 <title>Storage format</title>
 <para>
 The data is stored in
-<filename>~/.kde/share/apps/kmplayer/playlist.xml</filename>, and its format
+<filename>~/.trinity/share/apps/kmplayer/playlist.xml</filename>, and its format
 is like this example. See <link linkend="XML-editing">here</link> for 
 manipulating this data directly.
 <programlisting>
@@ -173,7 +173,7 @@ The current, <guilabel>Television</guilabel> and
 <guilabel>Persistent Playlists</guilabel> categories can also be manipulated
 by editing their <acronym>XML</acronym> storage. Of course one can do that
 when &kmplayer; is not running and editing the various files in
-<filename>~/.kde/share/apps/kmplayer/</filename>, but also in the application
+<filename>~/.trinity/share/apps/kmplayer/</filename>, but also in the application
 itself. Simply click on a catergory label, then choose <guimenu>View</guimenu>
 and next <guimenu>Edit mode</guimenu>. You can also click on a child branch
 and will then see only the <acronym>XML</acronym> contents of the branch.
@@ -197,7 +197,7 @@ enabled by editing the XML.
 <section>
     <title>Intro/exit animation</title>
     <para>
-        Disabling the starting/ending animation can be configured by editing <filename>~/.kde/share/config/kmplayerrc</filename> and modify
+        Disabling the starting/ending animation can be configured by editing <filename>~/.trinity/share/config/kmplayerrc</filename> and modify
         <programlisting>
 [General Options]
   No Intro=0
@@ -205,7 +205,7 @@ enabled by editing the XML.
     the above option to '1'. Just add this option if it's not there yet.
 </para>
 <para>
-    It's also possible to set an alternative animation. &kmplayer; will look at resp. <filename>~/.kde/share/apps/kmplayer/intro.xml</filename> and <filename>~/.kde/share/apps/kmplayer/exit.xml</filename>. The format has to be a supported <acronym>XML</acronym> file.
+    It's also possible to set an alternative animation. &kmplayer; will look at resp. <filename>~/.trinity/share/apps/kmplayer/intro.xml</filename> and <filename>~/.trinity/share/apps/kmplayer/exit.xml</filename>. The format has to be a supported <acronym>XML</acronym> file.
 </para>
 <para>
     The intro animation doesn't have to be a short one, because it will automatically end when another source is opened. Of course for the exit animation this would be a bit annoying, however the user can always end the application twice.
@@ -302,7 +302,7 @@ Basically the same way as trouble shooting
 <para>
 There is no configuration tab for this player in &kmplayer;'s config dialog. 
 Everything must be configured by manually editing the
-<filename>~/.kde/share/config/kmplayerrc</filename> like with configuring the
+<filename>~/.trinity/share/config/kmplayerrc</filename> like with configuring the
 <link linkend="backend-mimetype">backend per mimetype</link>. This is an
 example how to let flash be played with the swfdec-mozilla plugin:
 <programlisting>
@@ -344,7 +344,7 @@ from the popup menu).
 <para>
 To configure to always use a given backend for a particular mimetype
 (if detected of course) can be done by manually editing the
-<filename>~/.kde/share/config/kmplayerrc</filename>. For example, let xine play
+<filename>~/.trinity/share/config/kmplayerrc</filename>. For example, let xine play
 all ogg files:
 <programlisting>
 [audio/ogg]
@@ -365,7 +365,7 @@ player=xine
 </para>
 <para>
 The config file for TV settings is a <acronym>XML</acronym> file, located
-<filename>~/.kde/share/apps/kmplayer/tv.xml</filename>. See
+<filename>~/.trinity/share/apps/kmplayer/tv.xml</filename>. See
 <link linkend="XML-editing">here</link> for manipulating this data directly.
 The <acronym>XML</acronym> format is like this example:
 <programlisting>
@@ -462,7 +462,7 @@ dcop kmplayer-$PID KMediaPlayer toggleFullScreen
             <para>
                 Note the answer below is outdated. <application>kxineplayer</application> saves it automatically to last value, so only the first time xine will do the CPU test.
             </para>
-            <para>The <application>Xine</application> frontend for &kmplayer;, <application>kxineplayer</application>, uses <filename>~/.kde/share/apps/kmplayer/xine_config</filename> for its configuration. Settings for <application>Xine</application> are found in the configuration dialog <quote>General Options</quote>|<quote>Xine</quote>. (If you change an option here and save it, <filename>~/.kde/share/apps/kmplayer/xine_config</filename> will contain some explainations too). The CPU benchmarking is caused by the option <computeroutput>misc.memcpy_method</computeroutput> set to <computeroutput>probe</computeroutput>. To see which memcpy version works the fastest for you, enable <quote>Show Console Output</quote> from the <quote>View</quote> menu and look at the results from this benchmarking when you play something with Xine. Configure <computeroutput>misc.memcpy_method</computeroutput> with the method with the lowest time.</para>
+            <para>The <application>Xine</application> frontend for &kmplayer;, <application>kxineplayer</application>, uses <filename>~/.trinity/share/apps/kmplayer/xine_config</filename> for its configuration. Settings for <application>Xine</application> are found in the configuration dialog <quote>General Options</quote>|<quote>Xine</quote>. (If you change an option here and save it, <filename>~/.trinity/share/apps/kmplayer/xine_config</filename> will contain some explainations too). The CPU benchmarking is caused by the option <computeroutput>misc.memcpy_method</computeroutput> set to <computeroutput>probe</computeroutput>. To see which memcpy version works the fastest for you, enable <quote>Show Console Output</quote> from the <quote>View</quote> menu and look at the results from this benchmarking when you play something with Xine. Configure <computeroutput>misc.memcpy_method</computeroutput> with the method with the lowest time.</para>
         </answer>
       </qandaentry>
       <qandaentry>