anchor.diff:  // limitations under the License.
   
   [[sect_webannotsv]]
  -== WebAnno TSV 3 File format
  -
  -In this section, we will discuss the WebAnno TSV (Tab Separated Value) file format version 3. The format is similar to the CoNNL file formats with specialized additions to the header and column representations. The file format inhabits a header and a body section. The *header* section present information about the different types of annotation layers and features used in the file. While importing the WebAnno TSV file, the specified headers should be first created in to the running WebAnno project. Otherwise, the importing of the file will not be possible.
  -
  -The *body* section of the TSV file presents the document and all the associated annotations including sentence and token annotations.
  +== WebAnno TSV 3.2 File format
  +
  +In this section, we will discuss the WebAnno TSV (Tab Separated Value) file format version 3.2. 
  +The format is similar to the CoNNL file formats with specialized additions to the header and column
  +representations. The file format inhabits a header and a body section. The *header* section
  +present information about the different types of annotation layers and features used in the file.
  +While importing the WebAnno TSV file, the specified headers should be first created in to the
  +running WebAnno project. Otherwise, the importing of the file will not be possible.
  +
  +The *body* section of the TSV file presents the document and all the associated annotations
  +including sentence and token annotations.
  +
  +=== Encoding and Offsets
  +
  +TSV files are always encoded in UTF-8. However, the offsets used in the TSV file are based on
  +UTF-16. This is important when using TSV files with texts containing e.g. Emojis or some modern
  +non-latin Asian, Middle-eastern and African scripts.
  +
  +WebAnno is implemented in Java. The Java platform internally uses a UTF-16 representation for
  +text. For this reason, the offsets used in the TSV format currently represent offsets of the 16bit
  +units in UTF-16 strings. This is important if your text contains Unicode characters that cannot
  +be represented din 16bit and which thus require two 16bit units. For example a token represented
  +by the Unicode character 😊 (U+1F60A) requires two 16bit units. Hence, the offset count increased
  +by 2 for this character. So Unicode characters starting at U+10000 increase the offset count by 2.
  +
  +.Example: TSV sentence containing a Unicode character from the Supplementary Planes
  +[source,text]
  +----
  +#Text=I like it 😊 .
  +1-1 0-1 I _ 
  +1-2 2-6 like  _ 
  +1-3 7-9 it  _ 
  +1-4 10-12 😊  * 
  +1-5 13-14 . _ 
  +----
  +
  +NOTE: Since the character offsets are based on UTF-16 and the TSV file itself is encoded in UTF-8,
  +      first the text contained in the file needs to be transcoded from UTF-8 into UTF-16 before the offsets
  +      can be applied. The offsets cannot be used for random access to characters directly in the TSV file.
   
   === File Header
   
  -WebAnno TSV 3 file starts with the following header marker
  +WebAnno TSV 3.2 file starts with the following header marker
   
   .Example: format in file header
   [source,text]
   ----
  -#FORMAT=WebAnno TSV 3
  +#FORMAT=WebAnno TSV 3.2
   ----
   
   Layers are marked by the `#` character followed by `T_SP=` for *span types* (including *slot features*), `T_CH=` for *chain layers*, and `T_RL=` for *relation layers*. Every layer is written in new line, followed by the features in the layer.
  
positive.code: 
  ==== Sentence Representation
  
  Sentence annotations are presented following the text marker `#Text=`, before the token annotations. All text given here is inside the sentence boundaries.
  
  .Example: Original text sections
  [source,text]
  
negative.code: 1-2	4-8	Haag
  ----
  
  Here `1` indicates the sentence number, `2` indicates the token number (here, the second token
  in the first sentence) and `4` is the begin offset of the token and `8` is the end offset of the
  token while `Haag` is the token.
  
  Sub-token representations are affixed with a `.` and a number starts from 1 to N. 
  
  