* several example files. If the reader does not grok your files, it should be
* fairly simple to extend it.
*
- * <li> <tt>Gmsh 1.0 mesh</tt> format: this format is used by the @p GMSH mesh
- * generator (see http://www.geuz.org/gmsh/). The documentation in the @p GMSH
+ * <li> <tt>Gmsh 1.0 mesh</tt> format: this format is used by the @p Gmsh mesh
+ * generator (see http://www.geuz.org/gmsh/). The documentation in the @p Gmsh
* manual explains how to generate meshes compatible with the deal.II library
* (i.e. quads rather than triangles). In order to use this format, Gmsh has
* to output the file in the old format 1.0. This is done adding the line
/**
* Read grid data from an msh file, either version 1 or version 2 of that
- * file format. The GMSH formats are documented at
+ * file format. The Gmsh formats are documented at
* http://www.geuz.org/gmsh/.
*
* @note The input function of deal.II does not distinguish between newline
/**
* Write the triangulation in the msh format.
*
- * Msh is the format used by Gmsh and it is described in the gmsh user's
+ * Msh is the format used by Gmsh and it is described in the Gmsh user's
* guide. Besides the usual output of the grid only, you can decide through
* additional flags (see below, and the documentation of the
* GridOutFlags::Msh() class) whether boundary faces with non-zero boundary
void set_flags (const GridOutFlags::DX &flags);
/**
- * Set flags for GMSH output
+ * Set flags for Gmsh output
*/
void set_flags (const GridOutFlags::Msh &flags);
GridOutFlags::DX dx_flags;
/**
- * Flags for GMSH output. Can be changed by using the set_flags(const
+ * Flags for Gmsh output. Can be changed by using the set_flags(const
* GridOutFlags::Msh&) function.
*/
GridOutFlags::Msh msh_flags;
* printed which are on the boundary and which have a boundary indicator not
* equal to zero, since the latter is the default for boundary faces.
*
- * Since, in GMSH, geometric elements are continuously numbered, this
+ * Since, in Gmsh, geometric elements are continuously numbered, this
* function requires a parameter @p next_element_index providing the next
* geometric element number. This index should have a numerical value equal
* to one more than the index previously used to write a geometric element
*
* @warning @p next_element_index should be (at least) one larger than the
* current number of triangulation elements (lines, cells, faces) that have
- * been written to @p out. GMSH will not load the saved file correctly if
+ * been written to @p out. Gmsh will not load the saved file correctly if
* there are repeated indices.
*
* This function unfortunately can not be included in the regular @p
* printed which are on the boundary and which have a boundary indicator not
* equal to zero, since the latter is the default for boundary faces.
*
- * Since, in GMSH, geometric elements are continuously numbered, this
+ * Since, in Gmsh, geometric elements are continuously numbered, this
* function requires a parameter @p next_element_index providing the next
* geometric element number. This index should have a numerical value equal
* to one more than the index previously used to write a geometric element
*
* @warning @p next_element_index should be (at least) one larger than the
* current number of triangulation elements (lines, cells, faces) that have
- * been written to @p out. GMSH will not load the saved file correctly if
+ * been written to @p out. Gmsh will not load the saved file correctly if
* there are repeated indices.
*
* This function unfortunately can not be included in the regular @p