...
is optional and contains text between quotes for each line. If only DOCUMENT blocks are used, the TeLiTab should start with an empty line;
indicates the start of a document section which is related to of case . So is the starting tag for the document-value of the list parameter , or its first case in a table;
indicates the end of a document section which is related to of case . So is the ending tag for the document-value of the list parameter , or its first case in a table;
The DOCUMENT block should always close with a tag;
The parameter containing a document defined by should have as value in the list or table;
is an integer value indicating the number of parameters in the list;
is the parameter name (between quotes and unique in that level of the TeLiTab. So, although the syntax shows several ParName items, they cannot have the same name!);
is the value of the parameter;
is an integer value indicating the number of parameters in the table, when using a negative value Quaestor expects a transposed TeLiTab with parameter on the rows and cases as columns;
is the parameter name (between quotes and unique in that level of the TeLiTab. So, although the syntax shows several
items, they cannot have the same name!);
is the maximun case row or column number;
is the value of the parameter;
Each nested telitab starts with and ends with , which should both be provided on a new line:
If TeLiTab or OBJECT values have to be included in the table, should be the total number of table parameters, including the TeLiTab or OBJECT parameters. This is not really surprising as the OBJECT or TeLiTab parameters for these values are indeed part of the Table. However, the structure is difference in only blocks with and divide the different values:
Remarks
Parameters can have documents as values, in that case ParVal for this parameter should be replaced with . These document are defined as a block after the text part and prior to the list parameters. If the text part is NOT provided the TeLiTab should start with an empty line. This should be the case on any TeLiTab level. A document is basically a set of strings (text) with character returns;
...
The resulting TeLiTab looks as followed:
Finally you could assume that this information is part of the "Ship" object. In that case on the highest level their is one list parameter "Ship", containing the previous TeLiTab structure as value:
...