diff --git a/doc/texinfo/gmsh.texi b/doc/texinfo/gmsh.texi
index 117ad3c0f7593f8ec5a704bb158277af00a75f0a..8e8321c5716dfcfc6811a71b7bf8b207c1bcd4ea 100644
--- a/doc/texinfo/gmsh.texi
+++ b/doc/texinfo/gmsh.texi
@@ -1,5 +1,5 @@
 \input texinfo.tex @c -*-texinfo-*-
-@c $Id: gmsh.texi,v 1.145 2004-10-27 20:37:10 geuzaine Exp $
+@c $Id: gmsh.texi,v 1.146 2004-10-30 16:03:34 geuzaine Exp $
 @c
 @c Copyright (C) 1997-2004 C. Geuzaine, J.-F. Remacle
 @c
@@ -3020,7 +3020,8 @@ parser, which makes loading a view in parsed format slower than loading a
 view in ASCII or binary format. This is only a disadvantage for very large
 data sets, tough.
 
-The format of the parsed post-processing file is the following:
+A post-processing view in parsed format is defined as follows (there can be
+one or more views in the same file):
 
 @example
 @group
diff --git a/doc/texinfo/opt_plugin.texi b/doc/texinfo/opt_plugin.texi
index ea5d2caa9430a32059366df69aaacce298da261b..4d30469c968367e09b0ec1f65913475e2ddb8fef 100644
--- a/doc/texinfo/opt_plugin.texi
+++ b/doc/texinfo/opt_plugin.texi
@@ -240,6 +240,30 @@ Numeric options:
 Default value: @code{-1}
 @end table
 
+@item Plugin(HarmonicToTime)
+Plugin(HarmonicToTime) takes the values in the
+time steps `realPart' and `imaginaryPart' of
+the view `iView', and creates a new view
+containing (`iView'[`realPart'] * cos(p) -
+`iView'[`imaginaryPart'] * sin(p)), with
+p = 2*Pi*k/`nSteps', k = 0, ..., `nSteps'-1.
+If `iView' < 0, the plugin is run on the
+current view.
+
+Plugin(HarmonicToTime) creates one new view.
+
+Numeric options:
+@table @code
+@item realPart
+Default value: @code{0}
+@item imaginaryPart
+Default value: @code{1}
+@item nSteps
+Default value: @code{20}
+@item iView
+Default value: @code{-1}
+@end table
+
 @item Plugin(Skin)
 Plugin(Skin) extracts the skin (the boundary) of
 the view `iView'. If `iView' < 0, the plugin is run