## Summary of Changes
Octree doc states requirement of RandomAccessIterator for point range
added missing _object types for functors in traits
## Release Management
* Affected package(s): Orthtree
In a number of cases the command `@{` (or `\{`) is not closed by a
corresponding closing command (`@}`). For the `\=name` command this is
apparently not necessary but it is better to have corresponding open and
close commands.
(also corrected a split in a line that I noticed in
Arrangement_on_surface_2/doc/Arrangement_on_surface_2/CGAL/Arr_conic_traits_2.h)
Due to an incompatibility change in doxygen (see
2a62c19755 (commitcomment-150534822))
it is necessary to add the setting for `FULL_SIDEBAR` to the setup of
the CGAL documentation.
Spelling correction
Note: we also have a similar spelling error in:
```
Surface_mesh_skeletonization/benchmark/Surface_mesh_skeletonization/mcf_scale_invariance.cpp:104: output.open("correspondance.cgal");
Surface_mesh_skeletonization/examples/Surface_mesh_skeletonization/MCF_Skeleton_example.cpp:68: output.open("correspondance-poly.polylines.txt");
Surface_mesh_skeletonization/examples/Surface_mesh_skeletonization/MCF_Skeleton_LCC_example.cpp:66: output.open("correspondance-lcc.polylines.txt");
Surface_mesh_skeletonization/examples/Surface_mesh_skeletonization/MCF_Skeleton_om_example.cpp:75: output.open("correspondance-sm.polylines.txt");
Surface_mesh_skeletonization/examples/Surface_mesh_skeletonization/MCF_Skeleton_sm_example.cpp:67: output.open("correspondance-sm.polylines.txt");
Surface_mesh_skeletonization/examples/Surface_mesh_skeletonization/simple_mcfskel_example.cpp:72: output.open("correspondance-poly.polylines.txt");
Surface_mesh_skeletonization/examples/Surface_mesh_skeletonization/simple_mcfskel_LCC_example.cpp:72: output.open("correspondance-lcc.polylines.txt");
Surface_mesh_skeletonization/examples/Surface_mesh_skeletonization/simple_mcfskel_sm_example.cpp:51: output.open("correspondance-sm.polylines.txt");
```
but as this in filenames I didn't change it.
Due to an incompatibility change in doxygen (see 2a62c19755 (commitcomment-150534822)) it is necessary to add the setting for `FULL_SIDEBAR` to the setup of the CGAL documentation.
Spelling correction
Note: we also have a similar spelling error in:
```
Surface_mesh_skeletonization/benchmark/Surface_mesh_skeletonization/mcf_scale_invariance.cpp:104: output.open("correspondance.cgal");
Surface_mesh_skeletonization/examples/Surface_mesh_skeletonization/MCF_Skeleton_example.cpp:68: output.open("correspondance-poly.polylines.txt");
Surface_mesh_skeletonization/examples/Surface_mesh_skeletonization/MCF_Skeleton_LCC_example.cpp:66: output.open("correspondance-lcc.polylines.txt");
Surface_mesh_skeletonization/examples/Surface_mesh_skeletonization/MCF_Skeleton_om_example.cpp:75: output.open("correspondance-sm.polylines.txt");
Surface_mesh_skeletonization/examples/Surface_mesh_skeletonization/MCF_Skeleton_sm_example.cpp:67: output.open("correspondance-sm.polylines.txt");
Surface_mesh_skeletonization/examples/Surface_mesh_skeletonization/simple_mcfskel_example.cpp:72: output.open("correspondance-poly.polylines.txt");
Surface_mesh_skeletonization/examples/Surface_mesh_skeletonization/simple_mcfskel_LCC_example.cpp:72: output.open("correspondance-lcc.polylines.txt");
Surface_mesh_skeletonization/examples/Surface_mesh_skeletonization/simple_mcfskel_sm_example.cpp:51: output.open("correspondance-sm.polylines.txt");
```
but as this in filenames I didn't change it.
if a needle is also a cap, it will be handled as a needle only. But if
we can't collapse the edge, a flip will not be tried. Try the flip too.
Note that this will slow down the method as the status of a triangle is
tested twice.
Fix#8605
## Summary of Changes
For no reason, these examples where present but not available from the
documentation web pages.
## Release Management
* Affected package(s): PMP
* License and copyright ownership: unchanged
## Summary of Changes
Update Perl scripts to support custom platform display names through
CGAL_SUMMARY_NAME variable.
This PR is the companion of
[PR166](https://github.com/CGAL/cgal-testsuite-dockerfiles/pull/166)
(cgal-testsuite-dockerfiles) that introduces this variable.
Correction of incorrect usage of LaTeX in formulas and bibliography
altough MatHJax and bibtex.pl doesn't always signal it.
- Incorrect biblio entry (missing `,` and `}`)
- Documentation/doc/biblio/geom.bib
- ` ` is not correct LaTeX has to be `~`
-
Arrangement_on_surface_2/doc/Arrangement_on_surface_2/Arrangement_on_surface_2.txt
- Documentation/doc/Documentation/Developer_manual/Chapter_intro.txt
- Incorrect formula regarding usage of `\left` and `\right` (also
signaled by MathJax
-
Arrangement_on_surface_2/doc/Arrangement_on_surface_2/Arrangement_on_surface_2.txt
- `DeclareMathOperator` is a command that should be in the preamble,
alternatively the command `\operatorname` can be used explicitly (as
done here as it is only used once)
-
Kinetic_surface_reconstruction/doc/Kinetic_surface_reconstruction/Kinetic_surface_reconstruction.txt
- Latex has problems with `_` in a `text...` command so it should be
escaped though this gives problems with MathJax hence the extra hook.
MathJax reference:
https://groups.google.com/g/mathjax-users/c/wSh6-hSIUpQ/m/KmzZhQQGslgJ
- Documentation/doc/resources/1.10.0/CGAL_mathjax.js
- Documentation/doc/resources/1.8.13/CGAL_mathjax.js
- Documentation/doc/resources/1.9.6/CGAL_mathjax.js
- Weights/include/CGAL/Weights/authalic_weights.h
The new node propagation status only needs to be done the first time the
node is seen, the classification will always be the same and propagation
is already done.
## Summary of Changes
Turn several copies into `const&` to avoid allocation of data members of
traits object with multiprecision coordinates. In release mode the gain
is around 10%..
To address the timeouts in the testsuite in Debug mode, I also changed
cell size and approximation error.
## Release Management
* Affected package(s): Periodic_triangulation_3_mesh_3
* License and copyright ownership: unchanged
_Please use the following template to help us managing pull requests._
## Summary of Changes
There are 4 examples in Nef_2 package: three use Exact_integer, and one
uses a bounded kernel (which is undocumented).
Update one example to show how to use Exact_rational (wich requires to
change the kernel).
## Release Management
* Affected package(s): Nef_2