Find the file tellico-printing.xsl which should be in the $KDEDIR/share/apps/tellico/ directory. You can copy that to $KDEHOME/share/apps/tellico/ for personal modifications. You’ll have to know XSLT, but modifying that file is how you change the printing layout. HTML is generated from the file, and the easiest way to change the appearance of the printout is to modify the CSS in the top portion.
Be aware that the tellico-printing.xsl references another file, tellico-common.xsl, that contains some common XSLT templates. If you copy tellico-printing.xsl to $KDEHOME, you must either modify the element to point to the actual location of the tellico-common.xsl file or copy the common file as well.
Internally, the checkbox fields in Tellico are saved as “true“, so if you’d like to filter to show only the science fiction books which you’ve not read, for example, then you have two rules. Make sure the “Match all of the following” button is checked. Set the first rule to have “Genre” “contains” “Science Fiction” (no quotes) and the second rule to have “Read” “does not contain” “true” (no quotes).
Also, the quick filter in the toolbar will match any field, and if there is a non-word character, the text is interpreted as a regular expression. So if you quickly want to filter your books to show those by Weber or Bujold, then you can type “weber|bujold” (no quotes) in the toolbar.
Tellico uses the bibtex property to know how to export bibtex fields. If you want to add additional fields to export, such as an abstract, open up the Collection Fields dialog, and click the Set Properties button. Add a bibtex property with value abstract. Then, when you export to bibtex or bibtexml, that property will be used for the bibtex field name.
To allow grouping by a field which doesn’t allow grouping by default, check the Allow Grouping box for that particular field in the Collection Fields dialog.
Right-click on the header bar. You can also drag the headers to re-order the columns, and click on them to sort by that field.
Nearly 20 years ago, part of the reason I started Tellico was to learn C++. I didn’t know SQL at the time, and at the moment, I still only have a faint knowledge of how to use it. Simply put, Tellico didn’t start out as a relational database, and that won’t change until sometime in the future when I get around to learning SQL and have the time and motivation to change the data model. If that bothers you, well, don’t use Tellico then.
Of course, anyone is welcome to make any changes they want to with the source code.
I thought about several other names, a few of which were connected with book collections. However, Tellico can handle more than just books, and besides, this is a hobby, so I chose a neat-sounding (to me) name, one taken from a town close to where I grew up.
Tellico is developed on the Linux platform so compilation and functionality on Windows is rarely verified or tested. Using the craft build system, there is some development on a github branch for running Tellico.
For further information, please see the KDE Community Wiki pages.
Tellico is able to query the FreeDB (CDDB) interface for information about audio CDs.
In the File menu, select the Import Audio CD Data item. Select where you want to replace, import, or merge the CD information to your current collection. Then select the device location for the CD drive. You can also import the entire CDDB cache, which likely includes all the CDs that have been read previously.
Your version of Tellico must be compiled with support reading CDDB information. If it is not, then the menu option is disabled.
Author names should be separated by a semi-colon, like so: Brian W. Kernighan; Dennis M. Ritchie. Don’t include the word “and” or anything similar, even if you have 20 authors. If you have the auto-format option checked, then the last name will automatically be shown first for each author.
Other properties which allow multiple values, like “genre” and “keywords”, are entered in the same way, with a semi-colon (;) separating each value.