>In &kappname; is een Prognose een prognose van de saldi van rekeningen gedurende een gespecificeerde toekomstige tijdsperiode.</para>
<para
>Prognoses kunnen gemaakt worden met een van twee methoden. </para>
<variablelist>
<varlistentry>
<term
>Geplande en toekomstige transacties</term>
<listitem>
<para
>&kappname; gebruikt een combinatie van toekomstige transacties die al zijn ingevoerd in de kasboeken en de items in de planning.</para>
</listitem>
</varlistentry>
<varlistentry>
<term
>Historie-gebaseerd</term>
<listitem>
<para
>&kappname; gebruikt waarden uit eerdere transacties in de kasboeken om toekomstige transacties te voorspellen.</para>
</listitem>
</varlistentry>
</variablelist>
<para
>De methode van prognosticeren en periode hiervan kan in de instellingen van &kappname; worden geconfigureerd in het paneel Prognose. </para>
<para
>Begroting in &kappname; biedt een samenvatting, die de voorspelde balansen op cyclusdatums van rekeningen en het verwachte verschil tussen het begin- en eindsaldo. De lengte van de cyclus in de rekening kan ingesteld worden door de gebruiker. De samenvatting toont ook berichten over significante voorspelde wijzigingen aan de rekeningen gedurende de begrotingsperiode. </para>
<para
>Evenals de samenvatting staat Begroting van &kappname; u ook in staat om dagelijkse saldo's en de minimale en maximale saldo's voor elke rekeningcyclus van de rekening te bekijken. </para>
<para
>Standaard wordt de Begroting aangemaakt voor 90 dagen, met een 30 dagen rekeningcyclus met gebruik van geplande en toekomstige transacties. </para>
</sect1>
<sect1 id="details.forecast.view">
<title
>Begroting bekijken</title>
<para
>U kunt een begroting bekijken door op het toepasselijke pictogram in het navigatiepaneel aan de linkerkant van uw &kappname;-venster te klikken. </para>
<para
>Het venster Begroting is in vijf tabbladen gesplitst </para>
<sect2>
<title
>Tabblad Samenvatting</title>
<para
>Het tabblad Samenvatting is verticaal gesplitst in twee helften. </para>
<sect3>
<title
>Rekeningsamenvatting</title>
<para
>De rekeningsamenvatting bevat een raster die een rij informatie toont voor elk Vermogen en Verplichtingen. </para>
<para
>De volgende kolommen worden getoond: </para>
<variablelist>
<varlistentry>
<term
>Rekening</term>
<listitem>
<para
>De naam van de rekening met Vermogen of Verplichting</para>
</listitem>
</varlistentry>
<varlistentry>
<term
>Huidig saldo (huidig)</term>
<listitem>
<para
>Het huidige saldo van de rekening wordt getoond.</para>
</listitem>
</varlistentry>
<varlistentry>
<term
>Saldo in rekeningcyclus</term>
<listitem>
<para
>De begrotingsperiode is in rekeningcycli gesplitst. De standaard lengte van de rekeningcyclus is 30 dagen, maar kan door de gebruiker worden ingesteld.</para>
<para
>De eerste datum in de rekeningcyclus is de eerste begrotingsdatum. Dit is standaard de huidige datum plus één rekeningcyclus, maar kan afhankelijk van de instelling "Dag van de maand voor start begroting".</para>
<para
>Overblijvende datums van rekeningcycli worden bepaald door de lengte van de rekeningcyclus op te tellen bij de vorige datum van de rekeningcyclus. Dit gaat verder totdat de berekende datum van de rekeningcyclus verder is dan de begrotingsperiode.</para>
<para
>Voor elke datum van de rekeningcyclus wordt het voorspelde saldo getoond.</para>
</listitem>
</varlistentry>
<varlistentry>
<term
>Totale variantie</term>
<listitem>
<para
>De meest rechtse kolom toont het voorspelde verschil in waarde tussen de saldi aan het begin en einde van de begroting. Als de voorspelde eindwaarde van de rekening (in termen van netto waarde) kleiner is dan de beginwaarde zal de gehele rij met rood geaccentueerd worden.</para>
</listitem>
</varlistentry>
</variablelist>
</sect3>
<sect3>
<title
->Key Summary Information</title>
+>Samenvatting sleutelinformatie</title>
<para
->The bottom half of the Summary tab displays noteworthy information about accounts. This includes: </para>
+>De onderste helft van het tabblad Samenvatting toont vermeldenswaardige informatie over rekeningen. Dit omvat: </para>
<variablelist>
<varlistentry>
<term
->Assets below zero</term>
+>Bezittingen onder nul</term>
<listitem>
<para
->A message is displayed for any asset for which the value starts or will drop below zero during the forecast period.</para>
+>Er wordt een bericht getoond voor elke bezitting waarvan de waarde gedurende de begrotingsperiode onder nul begint of zal komen.</para>
</listitem>
</varlistentry>
<varlistentry>
<term
->Liabilities above zero</term>
+>Verplichtingen boven nul</term>
<listitem>
<para
>A message is displayed for any liability for which the value starts or will rise above zero during the forecast period. Note that the value of a liability is the negative of its ledger balance, since a positive balance indicates money owed.</para>
</listitem>
</varlistentry>
</variablelist>
</sect3>
</sect2>
<sect2>
<title
>Tabblad Details</title>
<para
>The Details tab contains a grid displaying a row of information for each Asset and Liability. </para>
<variablelist>
<varlistentry>
<term
>Rekening</term>
<listitem>
<para
>De naam van de rekening met Vermogen of Verplichting</para>
</listitem>
</varlistentry>
<varlistentry>
<term
>Datums</term>
<listitem>
<para
>For each date in the Forecast period a column displays the predicted balance of the account on that date. The date columns are in ascending order from left to right.</para>
</listitem>
</varlistentry>
<varlistentry>
<term
>Totale variantie</term>
<listitem>
<para
>De meest rechtse kolom toont het voorspelde verschil in waarde tussen de saldi aan het begin en einde van de begroting. Als de voorspelde eindwaarde van de rekening (in termen van netto waarde) kleiner is dan de beginwaarde zal de gehele rij met rood geaccentueerd worden.</para>
</listitem>
</varlistentry>
</variablelist>
</sect2>
<sect2>
<title
>Het tabblad Gevorderd</title>
<para
>The Advanced tab contains a grid displaying a row of information for each Asset and Liability. The information is split into columns as follows: </para>
<variablelist>
<varlistentry>
<term
>Rekening</term>
<listitem>
<para
>De naam van de rekening met Vermogen of Verplichting</para>
</listitem>
</varlistentry>
<varlistentry>
<term
>Minimum saldo in rekeningcyclus</term>
<listitem>
<para
>For each account cycle number <n> in the Forecast period the following columns are displayed:</para>
<variablelist>
<varlistentry>
<term
>Minimum saldo (Min sal <n>)</term>
<listitem>
<para
>Het minimale voorspelde saldo gedurende de rekeningcyclus</para>
</listitem>
</varlistentry>
<varlistentry>
<term
>Datum Minimaal saldo (Min Dat <n>)</term>
<listitem>
<para
>The date on which the balance reaches its predicted minimum.</para>
</listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
<varlistentry>
<term
>Maximum Account Cycle Balance</term>
<listitem>
<para
>For each account cycle number <n> in the Forecast period the following columns are displayed:</para>
<variablelist>
<varlistentry>
<term
>Maximum Balance (Max Bal <n>)</term>
<listitem>
<para
>The maximum predicted balance during the account cycle</para>
</listitem>
</varlistentry>
<varlistentry>
<term
>Maximum Balance Date (Max Date <n>)</term>
<listitem>
<para
>The date on which the balance reaches its predicted maximum.</para>
</listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
<varlistentry>
<term
>Gemiddeld</term>
<listitem>
<para
>The average balance of the account during the forecast period</para>
</listitem>
</varlistentry>
</variablelist>
</sect2>
<sect2>
<title
>Budget Forecast Tab</title>
<para
>The Budget tab displays a forecast calculation for the Income and Expense categories. The columns are similar to the Summary and Detailed tabs. </para>
</sect2>
<sect2>
<title
>Grafiek Tabblad</title>
<para
>It displays a chart showing the forecast. The level of detail varies depending on the detail level selected on the option above. </para>
>In de geest van Vrije Software bent u welkom om &appname; te hacken zoveel u wilt. U zou in staat moeten zijn om scripts te schrijven om gegevens gemakkelijk te importeren, te exporteren of te wijzigen. Dit hoofdstuk geeft u meer informatie over hoe dat te doen. </para>
<sect1 id="file-format">
<title
>Bestandsformaat</title>
<para
>The default &appname; data file is a zip archive, normally with a <literal role="extension"
>.tc</literal
> file extension. Inside the archive is a top-level <filename
>tellico.xml</filename
> file. Images may be included inside the <filename
>images/</filename
> folder in the archive, or they may be included in the &XML; data directly in a base64 encoding. Images may also be saved inside the application data folder, in which case, they are not in the data file at all. &appname; can also load the &XML; file, by itself, uncompressed. </para>
<sect2 id="xml-format">
<title
->&XML; Data</title>
+>&XML;-gegevens</title>
<sect3 id="coll-xml-data">
<title
>Collectie</title>
<programlisting
><![CDATA[
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE tellico PUBLIC "-//Robby Stephenson/DTD Tellico V11.0//EN" "http://periapsis.org/tellico/dtd/v11/tellico.dtd">
>The file begins with the required &XML; declaration and encoding, followed by the doctype. When a new field type is added or additional properties are set on the default fields, the doctype DTD version is incremented. &appname; is always able to open and read any previous DTD version, but will save files in the current version. The DTD location does point to an actual DTD file. </para>
<para
>The top-level element is a <markup
><tellico></markup
> element, containing the default namespace declaration and the syntax version of the file, which should always match the DTD. </para>
<para
>The <markup
><tellico></markup
> element contains one <markup
><collection></markup
> element. Multiple collections are ignored, for now. The <markup
>title</markup
> attribute contains the collection title, while the <markup
>type</markup
> specifies what kinds of entries are contained in the collection. The allowable types are in <link linkend="collection-type-values"
>listed in a later section</link
>. An optional <markup
>entryTitle</markup
> attribute may be used to specify the title of the entries for a custom collection, and should be plural. </para>
> element, of which there can be only one. All of the information for a field, except for any properties, are included as attributes of the <markup
><field></markup
> element. The allowable values for the <markup
>flags</markup
>, <markup
>format</markup
>, and <markup
>type</markup
> attributes are given in a <link linkend="field-type-values"
>following section</link
>. </para>
<para
>Field properties are used for setting default field values, rating value ranges, derived value templates, etc. The examples above include a default value, a maximum rating value, and a template for a derived ID field. </para>
> may contain an element whose name is identical to the field name. If multiple values are allowed for the field, then the letter <emphasis
>s</emphasis
> is added to the field name to create an element, and each value is added as a child of the element, as in the case of the author, genre, and keyword fields above. </para>
<para
>As a result, if additional fields are added to the collection, the data file will no longer conform to the DTD. However, &appname; uses a non-validating &XML; parser, so additional fields do not cause problems. </para>
> element, each image referenced by an entry is listed, along with attributes describing the image's size, format, and id. If the image is contained inside the Zip file, the element is empty. Otherwise, the image data may be contained in the &XML; stream as base64-encoded text. </para>
</sect3>
</sect2>
</sect1>
<sect1 id="collection-type-values">
<title
->Collection Type Values</title>
+>Waarden van typen van verzamelingen</title>
<para
->The type of collection is given in the type attribute of the collection element. The value is equal to the <type
+>Het type verzameling is gegeven in het type-attribuut van het verzamelingselement. De waarde is gelijk aan het <type
>Type</type
-> enum value in <filename
+> enum-waarde in <filename
>src/collection.h</filename
>. </para>
<table>
<title
->Collection Type Values</title>
+>Waarden van typen van verzamelingen</title>
<tgroup cols="2">
<thead>
<row>
<entry
>Type collectie</entry>
<entry
>Waarde</entry>
</row>
</thead>
<tbody>
<row
><entry
>Eigen verzameling</entry
><entry
>1</entry
></row>
<row
><entry
>Boekenverzameling</entry
><entry
>2</entry
></row>
<row
><entry
>Filmverzameling</entry
><entry
>3</entry
></row>
<row
><entry
>Muziekverzameling</entry
><entry
>4</entry
></row>
<row
><entry
>Bibliografie</entry
><entry
>5</entry
></row>
<row
><entry
>Stripverzameling</entry
><entry
>6</entry
></row>
<row
><entry
>Wijnverzameling</entry
><entry
>7</entry
></row>
<row
><entry
>Muntverzameling</entry
><entry
>8</entry
></row>
<row
><entry
>Postverzameling</entry
><entry
>9</entry
></row>
<row
><entry
>Trading Card Collection</entry
><entry
>10</entry
></row>
<row
><entry
>Video Game Collection</entry
><entry
>11</entry
></row>
<row
><entry
>Bestandencatalogus</entry
><entry
>12</entry
></row>
<row
><entry
>Bordspellenverzameling</entry
><entry
>13</entry
></row>
</tbody>
</tgroup>
</table>
</sect1>
<sect1 id="field-type-values">
<title
>Field Type Values</title>
<para
>&appname; will include all the default fields for a collection if the first field element has the name <emphasis
>_default</emphasis
>. For <emphasis
>Paragraph</emphasis
>, <emphasis
>Table</emphasis
>, or <emphasis
>Image</emphasis
> fields, the field category should be identical to the field title. </para>
<para
>The type of field is given in the type attribute of the field element. The value is equal to the <type
>FieldType</type
> enum value in <filename
>src/field.h</filename
>. </para>
<table>
<title
>Field Type Values</title>
<tgroup cols="2">
<thead>
<row>
<entry
>Veldtype</entry>
<entry
>Waarde</entry>
</row>
</thead>
<tbody>
<row
><entry
>Eenvoudige tekst</entry
><entry
>1</entry
></row>
<row
><entry
>Paragraaf</entry
><entry
>2</entry
></row>
<row
><entry
>Keuze</entry
><entry
>3</entry
></row>
<row
><entry
>Keuzevakje</entry
><entry
>4</entry
></row>
<row
><entry
>Cijfers</entry
><entry
>6</entry
></row>
<row
><entry
>&URL;</entry
><entry
>7</entry
></row>
<row
><entry
>Single-Column Table</entry
><entry
>8</entry
></row>
<row
><entry
>Afbeelding</entry
><entry
>10</entry
></row>
<row
><entry
>Datum</entry
><entry
>12</entry
></row>
<row
><entry
>Waardering</entry
><entry
>14</entry
></row>
</tbody>
</tgroup>
</table>
<para
>The field may have different flags set, given as a bitwise OR'd value in the flags attribute on the field element. The flag for preventing the user from deleting a field is intended for such things as the citation key for bibliographic entries. </para>
<table>
<title
>Field Flag Values</title>
<tgroup cols="2">
<thead>
<row>
<entry
>Field Flags</entry>
<entry
>Waarde</entry>
</row>
</thead>
<tbody>
<row
><entry
>Meerdere waarden toestaan</entry
><entry
><constant
>0x01</constant
></entry
></row>
<row
><entry
>Groepering toestaan</entry
><entry
><constant
>0x02</constant
></entry
></row>
<row
><entry
>Allow Completion</entry
><entry
><constant
>0x04</constant
></entry
></row>
<row
><entry
><emphasis
>Verwijderen weigeren</emphasis
></entry
><entry
><constant
>0x08</constant
></entry
></row>
<row
><entry
><emphasis
>Bewerken weigeren</emphasis
></entry
><entry
><constant
>0x10</constant
></entry
></row>
<row
><entry
>Afgeleide waarde</entry
><entry
><constant
>0x20</constant
></entry
></row>
</tbody>
</tgroup>
</table>
<para
>The format of the field is given in the format attribute on the field element. <emphasis
>Date Formatting</emphasis
> is not currently used. Grouping by <emphasis
>People</emphasis
> uses all the fields which use <emphasis
>Name Formatting</emphasis
>. Setting the <emphasis
>Derived Value</emphasis
> flag implies the value for the field is generated from the template property from other field values. </para>
<table>
<title
>Waarden van veldformaten</title>
<tgroup cols="2">
<thead>
<row>
<entry
>Veldformaat</entry>
<entry
>Waarde</entry>
</row>
</thead>
<tbody>
<row
><entry
>Capitalization Only</entry
><entry
>0</entry
></row>
<row
><entry
>Title Formatting</entry
><entry
>1</entry
></row>
<row
><entry
>Name Formatting</entry
><entry
>2</entry
></row>
<row
><entry
><emphasis
>Date Formatting</emphasis
></entry
><entry
>3</entry
></row>
<row
><entry
>Geen opmaak</entry
><entry
>4</entry
></row>
</tbody>
</tgroup>
</table>
</sect1>
<sect1 id="hidden-options">
<title
>Hidden Configuration Options</title>
<para
>&appname; has some additional configuration options that are not visible in the <interface
>Configuration Dialog</interface
>. They are not important enough to warrant cluttering the dialog with more settings, but as they represent options which may appeal to various users, the application does read them from the configuration file. </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. </para>
<sect2 id="hidden-general-options">
<title
>[Algemene opties]</title>
<para
>These settings should be placed in the <emphasis
>General Options</emphasis
> group. </para>
<sect3>
<title
>Max Icon Size</title>
<para
>The maximum size of the icons in the <interface
>Icon View</interface
> may be changed with this setting. The default value is 96. The size must be in the range of 32 to 512. </para>
</sect3>
<sect3>
<title
>Voorbeeld</title>
<informalexample>
<para
><userinput
>Max Icon Size=128</userinput
></para>
</informalexample>
</sect3>
<sect3>
<title
>Icon Cache Size</title>
<para
>The maximum numbers of icons cached in memory may be changed with this setting. The default value is 1000. </para>
</sect3>
<sect3>
<title
>Voorbeeld</title>
<informalexample>
<para
><userinput
>Icon Cache Size=100</userinput
></para>
</informalexample>
</sect3>
<sect3>
<title
>Voorbeeld</title>
<informalexample>
<para
><userinput
>Max Icon Size=128</userinput
></para>
</informalexample>
</sect3>
<sect3>
<title
>Image Cache Size</title>
<para
>The maximum amount of memory in bytes used for caching all the images may be changed with this setting. The default value is 67108864. </para>
</sect3>
<sect3>
<title
>Voorbeeld</title>
<informalexample>
<para
><userinput
>Image Cache Size=256000000</userinput
></para>
</informalexample>
</sect3>
</sect2>
<sect2 id="hidden-bibtex-options">
<title
>[Options - bibtex]</title>
<para
>These settings should be placed in the <emphasis
>Options - bibtex</emphasis
> group. </para>
<sect3>
<title
>lyxpipe</title>
<para
>This setting is for the location of the lyxpipe for sending bibliographic citations. It should not include the <literal role="extension"
>.in</literal
> suffix. </para>
</sect3>
<sect3>
<title
>Voorbeeld</title>
<informalexample>
<para
><userinput
>lyxpipe=$HOME/.lyx/lyxpipe</userinput
></para>
</informalexample>
</sect3>
</sect2>
</sect1>
<sect1 id="bibtex-translation">
<title
>Bibtex Character Translation</title>
<para
>When bibtex files are imported or exported, certain characters are translated between their TeX equivalents and the Unicode characters. Those character mappings are contained in the <filename
>bibtex-translation.xml</filename
> file, located in the installation data directory. The mappings can be modified, as desired. The key element contains the Unicode character, and the string elements within contain the TeX equivalents, which may be a one-to-many mapping. The first one is the one used when exporting to bibtex. </para>
<programlisting
><![CDATA[
<key char="À">
<string>{\`A}</string>
<string>\`{A}</string>
</key>
]]>
</programlisting>
</sect1>
<sect1 id="xslt-tricks">
<title
>XSLT Tricks</title>
<para
>Here are some tips for writing XSLT to parse &appname; &XML; data: (TBD). </para>
>In de geest van Vrije Software bent u welkom om &appname; te hacken zoveel u wilt. U zou in staat moeten zijn om scripts te schrijven om gegevens gemakkelijk te importeren, te exporteren of te wijzigen. Dit hoofdstuk geeft u meer informatie over hoe dat te doen. </para>
<sect1 id="file-format">
<title
>Bestandsformaat</title>
<para
>The default &appname; data file is a zip archive, normally with a <literal role="extension"
>.tc</literal
> file extension. Inside the archive is a top-level <filename
>tellico.xml</filename
> file. Images may be included inside the <filename
>images/</filename
> folder in the archive, or they may be included in the &XML; data directly in a base64 encoding. Images may also be saved inside the application data folder, in which case, they are not in the data file at all. &appname; can also load the &XML; file, by itself, uncompressed. </para>
<sect2 id="xml-format">
<title
->&XML; Data</title>
+>&XML;-gegevens</title>
<sect3 id="coll-xml-data">
<title
>Collectie</title>
<programlisting
><![CDATA[
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE tellico PUBLIC "-//Robby Stephenson/DTD Tellico V11.0//EN" "http://periapsis.org/tellico/dtd/v11/tellico.dtd">
>The file begins with the required &XML; declaration and encoding, followed by the doctype. When a new field type is added or additional properties are set on the default fields, the doctype DTD version is incremented. &appname; is always able to open and read any previous DTD version, but will save files in the current version. The DTD location does point to an actual DTD file. </para>
<para
>The top-level element is a <markup
><tellico></markup
> element, containing the default namespace declaration and the syntax version of the file, which should always match the DTD. </para>
<para
>The <markup
><tellico></markup
> element contains one <markup
><collection></markup
> element. Multiple collections are ignored, for now. The <markup
>title</markup
> attribute contains the collection title, while the <markup
>type</markup
> specifies what kinds of entries are contained in the collection. The allowable types are in <link linkend="collection-type-values"
>listed in a later section</link
>. An optional <markup
>entryTitle</markup
> attribute may be used to specify the title of the entries for a custom collection, and should be plural. </para>
> element, of which there can be only one. All of the information for a field, except for any properties, are included as attributes of the <markup
><field></markup
> element. The allowable values for the <markup
>flags</markup
>, <markup
>format</markup
>, and <markup
>type</markup
> attributes are given in a <link linkend="field-type-values"
>following section</link
>. </para>
<para
>Field properties are used for setting default field values, rating value ranges, derived value templates, etc. The examples above include a default value, a maximum rating value, and a template for a derived ID field. </para>
> may contain an element whose name is identical to the field name. If multiple values are allowed for the field, then the letter <emphasis
>s</emphasis
> is added to the field name to create an element, and each value is added as a child of the element, as in the case of the author, genre, and keyword fields above. </para>
<para
>As a result, if additional fields are added to the collection, the data file will no longer conform to the DTD. However, &appname; uses a non-validating &XML; parser, so additional fields do not cause problems. </para>
> element, each image referenced by an entry is listed, along with attributes describing the image's size, format, and id. If the image is contained inside the Zip file, the element is empty. Otherwise, the image data may be contained in the &XML; stream as base64-encoded text. </para>
</sect3>
</sect2>
</sect1>
<sect1 id="collection-type-values">
<title
->Collection Type Values</title>
+>Waarden van typen van verzamelingen</title>
<para
->The type of collection is given in the type attribute of the collection element. The value is equal to the <type
+>Het type verzameling is gegeven in het type-attribuut van het verzamelingselement. De waarde is gelijk aan het <type
>Type</type
-> enum value in <filename
+> enum-waarde in <filename
>src/collection.h</filename
>. </para>
<table>
<title
->Collection Type Values</title>
+>Waarden van typen van verzamelingen</title>
<tgroup cols="2">
<thead>
<row>
<entry
>Type collectie</entry>
<entry
>Waarde</entry>
</row>
</thead>
<tbody>
<row
><entry
>Eigen verzameling</entry
><entry
>1</entry
></row>
<row
><entry
>Boekenverzameling</entry
><entry
>2</entry
></row>
<row
><entry
>Filmverzameling</entry
><entry
>3</entry
></row>
<row
><entry
>Muziekverzameling</entry
><entry
>4</entry
></row>
<row
><entry
>Bibliografie</entry
><entry
>5</entry
></row>
<row
><entry
>Stripverzameling</entry
><entry
>6</entry
></row>
<row
><entry
>Wijnverzameling</entry
><entry
>7</entry
></row>
<row
><entry
>Muntverzameling</entry
><entry
>8</entry
></row>
<row
><entry
>Postverzameling</entry
><entry
>9</entry
></row>
<row
><entry
>Trading Card Collection</entry
><entry
>10</entry
></row>
<row
><entry
>Video Game Collection</entry
><entry
>11</entry
></row>
<row
><entry
>Bestandencatalogus</entry
><entry
>12</entry
></row>
<row
><entry
>Bordspellenverzameling</entry
><entry
>13</entry
></row>
</tbody>
</tgroup>
</table>
</sect1>
<sect1 id="field-type-values">
<title
>Field Type Values</title>
<para
>&appname; will include all the default fields for a collection if the first field element has the name <emphasis
>_default</emphasis
>. For <emphasis
>Paragraph</emphasis
>, <emphasis
>Table</emphasis
>, or <emphasis
>Image</emphasis
> fields, the field category should be identical to the field title. </para>
<para
>The type of field is given in the type attribute of the field element. The value is equal to the <type
>FieldType</type
> enum value in <filename
>src/field.h</filename
>. </para>
<table>
<title
>Field Type Values</title>
<tgroup cols="2">
<thead>
<row>
<entry
>Veldtype</entry>
<entry
>Waarde</entry>
</row>
</thead>
<tbody>
<row
><entry
>Eenvoudige tekst</entry
><entry
>1</entry
></row>
<row
><entry
>Paragraaf</entry
><entry
>2</entry
></row>
<row
><entry
>Keuze</entry
><entry
>3</entry
></row>
<row
><entry
>Keuzevakje</entry
><entry
>4</entry
></row>
<row
><entry
>Cijfers</entry
><entry
>6</entry
></row>
<row
><entry
>&URL;</entry
><entry
>7</entry
></row>
<row
><entry
>Single-Column Table</entry
><entry
>8</entry
></row>
<row
><entry
>Afbeelding</entry
><entry
>10</entry
></row>
<row
><entry
>Datum</entry
><entry
>12</entry
></row>
<row
><entry
>Waardering</entry
><entry
>14</entry
></row>
</tbody>
</tgroup>
</table>
<para
>The field may have different flags set, given as a bitwise OR'd value in the flags attribute on the field element. The flag for preventing the user from deleting a field is intended for such things as the citation key for bibliographic entries. </para>
<table>
<title
>Field Flag Values</title>
<tgroup cols="2">
<thead>
<row>
<entry
>Field Flags</entry>
<entry
>Waarde</entry>
</row>
</thead>
<tbody>
<row
><entry
>Meerdere waarden toestaan</entry
><entry
><constant
>0x01</constant
></entry
></row>
<row
><entry
>Groepering toestaan</entry
><entry
><constant
>0x02</constant
></entry
></row>
<row
><entry
>Allow Completion</entry
><entry
><constant
>0x04</constant
></entry
></row>
<row
><entry
><emphasis
>Verwijderen weigeren</emphasis
></entry
><entry
><constant
>0x08</constant
></entry
></row>
<row
><entry
><emphasis
>Bewerken weigeren</emphasis
></entry
><entry
><constant
>0x10</constant
></entry
></row>
<row
><entry
>Afgeleide waarde</entry
><entry
><constant
>0x20</constant
></entry
></row>
</tbody>
</tgroup>
</table>
<para
>The format of the field is given in the format attribute on the field element. <emphasis
>Date Formatting</emphasis
> is not currently used. Grouping by <emphasis
>People</emphasis
> uses all the fields which use <emphasis
>Name Formatting</emphasis
>. Setting the <emphasis
>Derived Value</emphasis
> flag implies the value for the field is generated from the template property from other field values. </para>
<table>
<title
>Waarden van veldformaten</title>
<tgroup cols="2">
<thead>
<row>
<entry
>Veldformaat</entry>
<entry
>Waarde</entry>
</row>
</thead>
<tbody>
<row
><entry
>Capitalization Only</entry
><entry
>0</entry
></row>
<row
><entry
>Title Formatting</entry
><entry
>1</entry
></row>
<row
><entry
>Name Formatting</entry
><entry
>2</entry
></row>
<row
><entry
><emphasis
>Date Formatting</emphasis
></entry
><entry
>3</entry
></row>
<row
><entry
>Geen opmaak</entry
><entry
>4</entry
></row>
</tbody>
</tgroup>
</table>
</sect1>
<sect1 id="hidden-options">
<title
>Hidden Configuration Options</title>
<para
>&appname; has some additional configuration options that are not visible in the <interface
>Configuration Dialog</interface
>. They are not important enough to warrant cluttering the dialog with more settings, but as they represent options which may appeal to various users, the application does read them from the configuration file. </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. </para>
<sect2 id="hidden-general-options">
<title
>[Algemene opties]</title>
<para
>These settings should be placed in the <emphasis
>General Options</emphasis
> group. </para>
<sect3>
<title
>Max Icon Size</title>
<para
>The maximum size of the icons in the <interface
>Icon View</interface
> may be changed with this setting. The default value is 96. The size must be in the range of 32 to 512. </para>
</sect3>
<sect3>
<title
>Voorbeeld</title>
<informalexample>
<para
><userinput
>Max Icon Size=128</userinput
></para>
</informalexample>
</sect3>
<sect3>
<title
>Icon Cache Size</title>
<para
>The maximum numbers of icons cached in memory may be changed with this setting. The default value is 1000. </para>
</sect3>
<sect3>
<title
>Voorbeeld</title>
<informalexample>
<para
><userinput
>Icon Cache Size=100</userinput
></para>
</informalexample>
</sect3>
<sect3>
<title
>Voorbeeld</title>
<informalexample>
<para
><userinput
>Max Icon Size=128</userinput
></para>
</informalexample>
</sect3>
<sect3>
<title
>Image Cache Size</title>
<para
>The maximum amount of memory in bytes used for caching all the images may be changed with this setting. The default value is 67108864. </para>
</sect3>
<sect3>
<title
>Voorbeeld</title>
<informalexample>
<para
><userinput
>Image Cache Size=256000000</userinput
></para>
</informalexample>
</sect3>
</sect2>
<sect2 id="hidden-bibtex-options">
<title
>[Options - bibtex]</title>
<para
>These settings should be placed in the <emphasis
>Options - bibtex</emphasis
> group. </para>
<sect3>
<title
>lyxpipe</title>
<para
>This setting is for the location of the lyxpipe for sending bibliographic citations. It should not include the <literal role="extension"
>.in</literal
> suffix. </para>
</sect3>
<sect3>
<title
>Voorbeeld</title>
<informalexample>
<para
><userinput
>lyxpipe=$HOME/.lyx/lyxpipe</userinput
></para>
</informalexample>
</sect3>
</sect2>
</sect1>
<sect1 id="bibtex-translation">
<title
>Bibtex Character Translation</title>
<para
>When bibtex files are imported or exported, certain characters are translated between their TeX equivalents and the Unicode characters. Those character mappings are contained in the <filename
>bibtex-translation.xml</filename
> file, located in the installation data directory. The mappings can be modified, as desired. The key element contains the Unicode character, and the string elements within contain the TeX equivalents, which may be a one-to-many mapping. The first one is the one used when exporting to bibtex. </para>
<programlisting
><![CDATA[
<key char="À">
<string>{\`A}</string>
<string>\`{A}</string>
</key>
]]>
</programlisting>
</sect1>
<sect1 id="xslt-tricks">
<title
>XSLT Tricks</title>
<para
>Here are some tips for writing XSLT to parse &appname; &XML; data: (TBD). </para>
#. i18nc("Who made the profile?","Manufacturer: ") + currentColorSpace()->profile()->manufacturer() + "</p>"); //This would work if people actually wrote the manufacturer into the manufacturer fiedl...