generic-library/opencv
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Used literal blocks instead of the LaTeX verbatim environment

Browse Source
This commit is contained in:
Ilya Lysenkov 2011-06-07 12:54:00 +00:00
parent bdae962e13
commit 9c3c1603b7
2 changed files with 31 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
doc/opencv1/c/core_xml_yaml_persistence.rst
View File

@ -56,30 +56,30 @@ using CXCore functions:
XML:
::
<?xml version="1.0">
<opencv_storage>
<A type_id="opencv-matrix">
<rows>3</rows>
<cols>3</cols>
<dt>f</dt>
<data>1. 0. 0. 0. 1. 0. 0. 0. 1.</data>
</A>
</opencv_storage>
\begin{verbatim}
<?xml version="1.0">
<opencv_storage>
<A type_id="opencv-matrix">
<rows>3</rows>
<cols>3</cols>
<dt>f</dt>
<data>1. 0. 0. 0. 1. 0. 0. 0. 1.</data>
</A>
</opencv_storage>
\end{verbatim}
YAML:
::
A: !!opencv-matrix
rows: 3
cols: 3
dt: f
data: [ 1., 0., 0., 0., 1., 0., 0., 0., 1.]
\begin{verbatim}
A: !!opencv-matrix
rows: 3
cols: 3
dt: f
data: [ 1., 0., 0., 0., 1., 0., 0., 0., 1.]
\end{verbatim}
As it can be seen from the examples, XML uses nested tags to represent
hierarchy, while YAML uses indentation for that purpose (similar
to the Python programming language).

27
doc/opencv1/c/objdetect_cascade_classification.rst
View File

@ -177,22 +177,21 @@ Boosted Haar classifier structures.
All the structures are used for representing a cascaded of boosted Haar classifiers. The cascade has the following hierarchical structure:
::
\begin{verbatim}
Cascade:
Stage,,1,,:
Classifier,,11,,:
Feature,,11,,
Classifier,,12,,:
Feature,,12,,
...
Stage,,2,,:
Classifier,,21,,:
Feature,,21,,
...
...
Cascade:
Stage,,1,,:
Classifier,,11,,:
Feature,,11,,
Classifier,,12,,:
Feature,,12,,
...
Stage,,2,,:
Classifier,,21,,:
Feature,,21,,
...
...
\end{verbatim}
The whole hierarchy can be constructed manually or loaded from a file or an embedded base using the function
:ref:`LoadHaarClassifierCascade`
.