The LinKT Manual: File formats

## Fileformats

This is a list of all file belonging to LinKT and their format.
Global versions are located at `$KDEBIN/share/apps/linkt/`. Each user can save its personal version at `~/.kde/share/apps/linkt/`. If no local version can be found, the global one will be used.

The following files may contain Makros.

### ctext

The connect-text is sent to a station whenever it connects us from outside.

### <callsign>.ctext

You can assign an individual connect text to every callsign by creating a file <callsign&grM.ctext (e.g. dh1pn.ctext) at the userdatabase (`~/.kde/share/apps/linkt/userdb/dh1.../dh1pn.ctext`)

### qtext

This text will be sent before the disconnect after `//Q` has been received.

### help.linkt

If the remote station enters `//H`, this text will be sent. It should contain a description of all available remote commands.

### info.linkt

Information about your station. It is common to put information about your rig, hardware, qth and so on into this file.

### news.linkt

News, readable using the `//NE` remote command.

### cookies

"Cookies" are short humouristic phrases (better translation anyone?) which are randomly selected and sent to the remote station. They can be included in the above texts using the macro `%o`.

The format of the cookies file is quite simple:
At the top and bottom of the file and between each two quotes there have to be `@@`. e.g.:

>     @@
>     I'm a cookie
>     @@
>     At night it is colder than outside.
>     @@

### boxcheck.dat

This file contains information about the format of the bbs list command's output. This will be used by the BoxCheck feature. Using this specifications LinKT will extract the different fields of a (list|check)-line. In many cases you will be able to use the definitions which ship with LinKT. If your BBS has a different output LinKT doesn't recognise, you have to adopt boxcheck.dat to support your BBS. If you have a new, working definition, please mail it to Jochen so it can be included in the next LinKT version.

Each line starts with an identifying character followed by a space and the corresponding information (see below). Lines startig with a # will be ignored. One definition is a block of about 10-15 lines of information. The first line starts with `-` (minus) - the identifying character -, the mentioned whitespace followed by a string describing the definition. eg.

>     - FBB 8.12xx (english language)

Next is the description of the header. LinKT scans for this string and will recognize everything following this header as list-data. Identifier for this definition is ":"-

>     :     # Call     File     Nr.  Datum   @MBX   Bytes #LT Titel

Jetzt erfolgen die Definitonen der einzelnen Felder. Diese sind: Now the definitions for the particular fields follow:

Field | Description
--- | ---
s | Sender
r | To-Field (Board)
n | Message number
d | Date
v | Designator (@WW, ...)
b | Size (Bytes)
l | Lifetime (Diebox only, define l 0,0 for fbb
t | Subject
f | fixed string

Given the case that the sender-field is at the seventh column spans over 6 columns, the definition will be `s 7,6`. A "fixed string" is one or more characters which are in every line at the same position. They are used to check the plausibility of the data.

Another example:

>     ## Sender
>     s 7,6
>     ## To-field
>     r 16,8
>     ## Mailnumber
>     n 24,4
>     ## Date
>     d 29,8
>     ## Designator/Adress
>     v 38,6
>     ## Bytes
>     b 44,6
>     ## Lifetime
>     l 51,3
>     ## Subject
>     t 55,25
>     ## fixed strings
>     f 14,>
>     f 31,.
>     f 34,.