@ -135,7 +135,7 @@ will honor those settings. However, custom template may choose to ignore them.</
Additional templates may be installed directly, or downloaded from
Additional templates may be installed directly, or downloaded from
<ulink url="http://kde-files.org/index.php?amp;xcontentmode=676">kde-files.org</ulink> by clicking
<ulink url="http://kde-files.org/index.php?amp;xcontentmode=676">kde-files.org</ulink> by clicking
the <guilabel>Download</guilabel> button. Any templates installed by the user may also be deleted.
the <guilabel>Download</guilabel> button. Any templates installed by the user may also be deleted.
Entry templates are saved in <filename class="directory">$<envar>KDEHOME</envar>/share/apps/tellico/entry-templates/</filename>.
Entry templates are saved in <filename class="directory">$<envar>TDEHOME</envar>/share/apps/tellico/entry-templates/</filename>.
</para>
</para>
<para>If you create a new template, please consider submitting it at <ulink url="http://kde-files.org/index.php?amp;xcontentmode=676">kde-files.org</ulink>!</para>
<para>If you create a new template, please consider submitting it at <ulink url="http://kde-files.org/index.php?amp;xcontentmode=676">kde-files.org</ulink>!</para>
<para>Be aware that the <filename>tellico-printing.xsl</filename> references another file, <filename>tellico-common.xsl</filename>, that contains some common &xslt; templates. If you copy
<para>Be aware that the <filename>tellico-printing.xsl</filename> references another file, <filename>tellico-common.xsl</filename>, that contains some common &xslt; templates. If you copy
<filename>tellico-printing.xsl</filename> to $<envar>KDEHOME</envar>, you must either modify the <xsl:import> element to point to the actual location of the <filename>tellico-common.xsl</filename> file or copy the common file as well.
<filename>tellico-printing.xsl</filename> to $<envar>TDEHOME</envar>, you must either modify the <xsl:import> element to point to the actual location of the <filename>tellico-common.xsl</filename> file or copy the common file as well.
for access by everyone. Templates in $<envar>KDEHOME</envar> will
for access by everyone. Templates in $<envar>TDEHOME</envar> will
override any files by the same name in $<envar>KDEDIRS</envar>. The
override any files by the same name in $<envar>TDEDIRS</envar>. The
entry templates can be set on a per collection-type basis in the
entry templates can be set on a per collection-type basis in the
settings dialog.</para>
settings dialog.</para>
<para>Templates for the &report-dialog; are saved in <filename class="directory">$<envar>KDEHOME</envar>/share/apps/tellico/report-templates/</filename>.
<para>Templates for the &report-dialog; are saved in <filename class="directory">$<envar>TDEHOME</envar>/share/apps/tellico/report-templates/</filename>.
</para>
</para>
</answer>
</answer>
</qandaentry>
</qandaentry>
@ -173,14 +173,14 @@ wrong?</para></question>
<answer>
<answer>
<para>KDE programs look for data in the locations defined in the
<para>KDE programs look for data in the locations defined in the
$<envar>KDEDIRS</envar> environmental variable. If you install in
$<envar>TDEDIRS</envar> environmental variable. If you install in
<filename class="directory">/usr/local</filename> for example, but
<filename class="directory">/usr/local</filename> for example, but
$<envar>KDEDIRS</envar> is empty or just <filename class="directory">/usr</filename>,
$<envar>TDEDIRS</envar> is empty or just <filename class="directory">/usr</filename>,
then &appname; won't be able to find the files it needs. This is
then &appname; won't be able to find the files it needs. This is
particularly true for SuSE, for which you should compile with
particularly true for SuSE, for which you should compile with
@ -184,7 +184,7 @@ The edit widget also supports drag-and-drop. Dragging an image file from a file-
<warning>
<warning>
<para>
<para>
By default, the images are stored in the collection data file, keeping everything contained in one location. However, too many images will cause &appname; to slow down significantly as well result in a very large data file. Alternatively, &appname; can save the images separately, either in the <filename class="directory">$<envar>KDEHOME</envar>/share/apps/tellico/data/</filename> directory or in a directory in the same location as the data file. Loading and saving data files is much faster if images are stored separately, but the data files are no longer portable or archivable.
By default, the images are stored in the collection data file, keeping everything contained in one location. However, too many images will cause &appname; to slow down significantly as well result in a very large data file. Alternatively, &appname; can save the images separately, either in the <filename class="directory">$<envar>TDEHOME</envar>/share/apps/tellico/data/</filename> directory or in a directory in the same location as the data file. Loading and saving data files is much faster if images are stored separately, but the data files are no longer portable or archivable.
Self-contained data files can always be created by using the <menuchoice><guimenu>File</guimenu><guimenu>Export</guimenu><guimenuitem>Export to Zip...</guimenuitem></menuchoice> menu item.
Self-contained data files can always be created by using the <menuchoice><guimenu>File</guimenu><guimenu>Export</guimenu><guimenuitem>Export to Zip...</guimenuitem></menuchoice> menu item.
</para>
</para>
</warning>
</warning>
@ -440,7 +440,7 @@ button, set the first rule to <emphasis>Author contains Bujold</emphasis> and th
<sect1 id="report-dialog">
<sect1 id="report-dialog">
<title>Generating Reports</title>
<title>Generating Reports</title>
<para>
<para>
&appname; can generate various reports about your current collection. The &report-dialog; checks for all &xslt; templates in the installation path and in <filename class="directory">$<envar>KDEHOME</envar>/share/apps/tellico/report-templates/</filename>. So you can create new ones, and they're automatically found and included as options in the &report-dialog;. Some complex reports may take a while to generate for large collections.
&appname; can generate various reports about your current collection. The &report-dialog; checks for all &xslt; templates in the installation path and in <filename class="directory">$<envar>TDEHOME</envar>/share/apps/tellico/report-templates/</filename>. So you can create new ones, and they're automatically found and included as options in the &report-dialog;. Some complex reports may take a while to generate for large collections.
@ -258,7 +258,7 @@ The format of the field is given in the format attribute on the field element. <
</para>
</para>
<para>
<para>
The settings for &appname; are saved in a file in the user's home folder, namely <filename>$<envar>KDEHOME</envar>/share/config/tellicorc</filename>. Within that file, settings are put in groups, which appear with bracketed names, such as [General Options]. To add a setting to the <emphasis>General Options</emphasis> group, find the line in the settings file with that group name. If it does not appear, then create it yourself by adding a line saying [General Options]. Then, the setting can be added underneath the group name.
The settings for &appname; are saved in a file in the user's home folder, namely <filename>$<envar>TDEHOME</envar>/share/config/tellicorc</filename>. Within that file, settings are put in groups, which appear with bracketed names, such as [General Options]. To add a setting to the <emphasis>General Options</emphasis> group, find the line in the settings file with that group name. If it does not appear, then create it yourself by adding a line saying [General Options]. Then, the setting can be added underneath the group name.
Timothy Pearson
13 years ago