Spelling correction

Spelling correction due to updated dictionary.
(dictionary was updated after the previous spelling correction :-( )
This commit is contained in:
albert-github 2024-06-11 10:12:12 +02:00
parent f858554657
commit c35a0a7f11
9 changed files with 10 additions and 10 deletions

View File

@ -1191,7 +1191,7 @@ private:
if(refining) if(refining)
{ {
// If we are re-using the triangulation, change the label of the extra elements // If we are reusing the triangulation, change the label of the extra elements
// that we have added to ensure a manifold result back to external ("manifold" -> "outside") // that we have added to ensure a manifold result back to external ("manifold" -> "outside")
reset_manifold_labels(); reset_manifold_labels();

View File

@ -3716,7 +3716,7 @@ namespace CGAL {
/** Create an edge. /** Create an edge.
* if closed==true, the edge has no 2-free dart. * if closed==true, the edge has no 2-free dart.
* (note that for CMap there is no differente between true and false, but * (note that for CMap there is no difference between true and false, but
* this is not the case for GMap) * this is not the case for GMap)
* @return a dart of the new edge. * @return a dart of the new edge.
*/ */
@ -3733,7 +3733,7 @@ namespace CGAL {
* @param h0 the first vertex descriptor. * @param h0 the first vertex descriptor.
* @param h1 the second vertex descriptor. * @param h1 the second vertex descriptor.
* if closed==true, the edge has no 2-free dart. * if closed==true, the edge has no 2-free dart.
* (note that for CMap there is no differente between true and false, but * (note that for CMap there is no difference between true and false, but
* this is not the case for GMap) * this is not the case for GMap)
* @return the dart of the new edge incident to h0. * @return the dart of the new edge incident to h0.
*/ */

View File

@ -172,7 +172,7 @@ in a consistent, i.e., <I>valid</I>, state.
\subsection HalfedgeDSExampleAddingColortoFaces Example Adding Color to Faces \subsection HalfedgeDSExampleAddingColortoFaces Example Adding Color to Faces
This example re-uses the base class available for faces and adds a This example reuses the base class available for faces and adds a
member variable `color`. member variable `color`.
\cgalExample{HalfedgeDS/hds_prog_color.cpp} \cgalExample{HalfedgeDS/hds_prog_color.cpp}

View File

@ -22,7 +22,7 @@ as a gradient red/green corresponding to close/far from the source vertices.
The heat method is highly efficient, since the algorithm The heat method is highly efficient, since the algorithm
boils down to two standard sparse linear algebra problems. It is especially boils down to two standard sparse linear algebra problems. It is especially
useful in situations where one wishes to perform repeated distance queries useful in situations where one wishes to perform repeated distance queries
on a fixed domain, since precomputation done for the first query can be re-used. on a fixed domain, since precomputation done for the first query can be reused.
As a rule of thumb, the method works well on triangle meshes, which are As a rule of thumb, the method works well on triangle meshes, which are
Delaunay, though in practice may also work fine for meshes that are far from Delaunay, though in practice may also work fine for meshes that are far from

View File

@ -3364,7 +3364,7 @@ Release date: October 2013
#### CGAL and Boost Property Maps #### CGAL and Boost Property Maps
- The `key_type` of the property maps provided by CGAL used to be an - The `key_type` of the property maps provided by CGAL used to be an
iterator. In order to be more easily re-used, the `key_type` has iterator. In order to be more easily reused, the `key_type` has
been changed to be the `value_type` of the iterator. The packages been changed to be the `value_type` of the iterator. The packages
that have been updated to match these changes are **Point Set that have been updated to match these changes are **Point Set
Processing** and **Surface Reconstruction from Point Sets**. Processing** and **Surface Reconstruction from Point Sets**.

View File

@ -2614,7 +2614,7 @@ update_mesh_topo_change(const Vertex_handle& old_vertex,
std::cerr << "update_mesh_topo_change: revert move to " << old_position << "\n"; std::cerr << "update_mesh_topo_change: revert move to " << old_position << "\n";
#endif #endif
//reset caches in case cells are re-used by the compact container //reset caches in case cells are reused by the compact container
reset_circumcenter_cache(outdated_cells); reset_circumcenter_cache(outdated_cells);
reset_sliver_cache(outdated_cells); reset_sliver_cache(outdated_cells);
outdated_cells.clear(); outdated_cells.clear();

View File

@ -2185,7 +2185,7 @@ remove_self_intersections_one_step(std::set<typename boost::graph_traits<Triangl
// If smoothing fails, the face patch is restored to its pre-smoothing state. // If smoothing fails, the face patch is restored to its pre-smoothing state.
// //
// There is no need to update the working range because smoothing doesn`t change // There is no need to update the working range because smoothing doesn`t change
// the number of faces (and old faces are re-used). // the number of faces (and old faces are reused).
// //
// Do not smooth if there are no self-intersections within the patch: this means the intersection // Do not smooth if there are no self-intersections within the patch: this means the intersection
// is with another CC and smoothing is unlikely to move the surface sufficiently // is with another CC and smoothing is unlikely to move the surface sufficiently

View File

@ -42,7 +42,7 @@ struct Time_stamper
pt->set_time_stamp(new_ts); pt->set_time_stamp(new_ts);
} }
else { else {
// else: the time stamp is re-used // else: the time stamp is reused
// Enforces that the time stamp is greater than the current value. // Enforces that the time stamp is greater than the current value.
// That is used when a TDS_3 is copied: in that case, the // That is used when a TDS_3 is copied: in that case, the

View File

@ -333,7 +333,7 @@ Prior to \cgal 3.6, this functionality was available through the
In order to satisfy as many uses as possible, a design has been selected that In order to satisfy as many uses as possible, a design has been selected that
allows to exchange different parts to meet the users' needs, while still allows to exchange different parts to meet the users' needs, while still
re-using a maximum of the provided functionalities. We have already seen that reusing a maximum of the provided functionalities. We have already seen that
the main triangulation classes are parameterized by a geometric traits class the main triangulation classes are parameterized by a geometric traits class
and a triangulation data structure (TDS), so that each of them can be and a triangulation data structure (TDS), so that each of them can be
interchanged with alternate implementations. interchanged with alternate implementations.