more doc

doc/texinfo/gmsh.texi

@@ -3811,7 +3811,7 @@ $EndElements
 <$EndInterpolationScheme>
 @end example
 
-@code{elementType} is e.g.:
+In the format description above, @code{elementType} is e.g.:
 @table @code
 @item 1
 2-node line.
@@ -3910,21 +3910,36 @@ All the currently supported elements in the format are defined in
 @url{https://gitlab.onelab.info/gmsh/gmsh/blob/master/Common/GmshDefines.h,GmshDefines.h}.
 See below for the ordering of the nodes.
 
-The post-processing sections are identical to the ones in the version 2
-file format (@pxref{MSH file format version 2}). These sections will be
-reworked in a future minor revision of the version 4 format
-(e.g. version 4.1 or 4.2).
+In the post-processing sections (@code{$NodeData}, @code{$ElementData},
+@code{$ElementNodeData}) generated by Gmsh:
+@table @code
+@item numStringTags
+is 1 or 2. The first @code{stringTag} is interpreted as the name of the
+post-processing view and the second as the name of the interpolation
+scheme, as provided in the @code{$InterpolationScheme} section.
+@item numRealTags
+is 1 and is interpreted as a time value associated with the dataset.
+@item numIntegerTags
+is 3 or 4. The first @var{integerTag} is interpreted as a time step
+index (starting at 0), the second as the number of field components of
+the data in the view (1, 3 or 9), the third as the number of entities
+(nodes or elements) in the view, and the fourth as the partition index
+for the view data (0 for no partition).
+@end table
 
-Below is a small example (a mesh consisting of two quadrangles with an
-associated nodal scalar dataset; the comments are not part of the actual
-file!):
+The @code{$InterpolationScheme} is defined as in MSH2 (@pxref{MSH file
+format version 2}).
+
+Below is a small example of a minimal ASCII MSH4.1 file, with a mesh
+consisting of two quadrangles and an associated nodal scalar
+dataset. (The comments are not part of the actual file!)
 
 @smallexample
 $MeshFormat
 4.1 0 8          @emph{MSH4.1, ASCII}
 $EndMeshFormat
 $Nodes
-1 6 1 6          @emph{1 entity, 6 nodes, min/max node tags: 1 and 6}
+1 6 1 6          @emph{1 bloc, 6 nodes total, min/max node tags: 1 and 6}
 2 1 0 6          @emph{surface 1, no parametric coordinates, 6 nodes}
 1 0. 0. 0.       @emph{  node #1: coordinates (0., 0., 0.)}
 2 1. 0. 0.       @emph{  node #2: coordinates (1., 0., 0.)}
@@ -3934,20 +3949,20 @@ $Nodes
 6 2. 1. 0.
 $EndNodes
 $Elements
-1 2 1 2          @emph{1 entity, 2 elements, min/max element tags: 1 and 2}
+1 2 1 2          @emph{1 bloc, 2 elements total, min/max element tags: 1 and 2}
 2 1 3 2          @emph{surface 1, element type 3 (4-node quad), 2 elements}
 1 1 2 3 4        @emph{  quad #1: nodes 1 2 3 4}
 2 2 5 6 3        @emph{  quad #2: nodes 2 5 6 3}
 $EndElements
 $NodeData
-1                @emph{one string tag:}
+1                @emph{1 string tag:}
 "A scalar view"  @emph{  the name of the view ("A scalar view")}
-1                @emph{one real tag:}
+1                @emph{1 real tag:}
 0.0              @emph{  the time value (0.0)}
-3                @emph{three integer tags:}
+3                @emph{3 integer tags:}
 0                @emph{  the time step (0; time steps always start at 0)}
 1                @emph{  1-component (scalar) field}
-6                @emph{  six associated nodal values}
+6                @emph{  6 associated nodal values}
 1 0.0            @emph{value associated with node #1 (0.0)}
 2 0.1            @emph{value associated with node #2 (0.1)}
 3 0.2            @emph{etc.}