...
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 Bparameter , or its first case in a table;
indicates the end of a document section which is related
to ParName of case CaseNumber. So @END_DOCUMENT_B_1 isto of case . So is the ending tag for the document-value of the list
parameter Bparameter , or its first case in a table;
The DOCUMENT block should always close with
a @END_DOCUMENTS taga tag;
The parameter containing a
document Document$ defined by @DOCUMENT_ParName_CaseNumber Document$ @END_DOCUMENT_ParNam_CaseNumber should have "\DOCUMENT"asdocument 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
ParName
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 { andwith and ends with
}, which should both be provided on a new line:
ListNo%
"ParName"
{
"Text$"
"..."
"Text$"
@DOCUMENT_ParName_CaseNumber
Document$
@END_DOCUMENT_ParName_CaseNumber
@END_DOCUMENTS
ListNo%
"ParName" ParVal
... ...
"ParName" ParVal
TableNo% "ParName" ... "ParName"
"1" ParVal ... ParVal
... ... ... ...
"nr.cases" ParVal ... ParVal
}
...