Fix rendering of example attribute in XMLreference.rst

PiperOrigin-RevId: 481614595
Change-Id: Ie582b2ba0b3fc89e3296337b0d43c492ac0d65fa
This commit is contained in:
Yuval Tassa
2022-10-17 05:28:48 -07:00
committed by Copybara-Service
parent 3aaf94f42c
commit c7c6a870b4
+11 -10
View File
@@ -58,24 +58,25 @@ real(N) An array of N real-valued numbers. If N is omitted it equals 1.
| "..." | The attribute is optional. The internal default is given in quotes. | | "..." | The attribute is optional. The internal default is given in quotes. |
+-------------+--------------------------------------------------------------------------------------------------+ +-------------+--------------------------------------------------------------------------------------------------+
|
| In the reference documentation below the attribute name is shown in boldface, followed by its data type, followed by In the reference documentation below the attribute name is shown in boldface, followed by its data type, followed by the
the required/optional status including the internal default if any. For example, the attribute angle is a keyword required/optional status including the internal default if any. For example, the attribute angle is a keyword attribute
attribute whose value can be "radian" or "degree". It is an optional attribute and has internal default "degree". whose value can be "radian" or "degree". It is an optional attribute and has internal default "degree". Therefore it
Therefore it will appear in the reference documentation as will appear in the reference documentation as
:at:`angle`: :at-val:`[radian, degree], "degree"` :at:`angle`: :at-val:`[radian, degree], "degree"`
|br|
.. _Reference: .. _Reference:
MJCF Reference MJCF Reference
-------------- --------------
| MJCF files have a unique top-level element :ref:`mujoco <mujoco>`. The next-level elements are referred to as MJCF files have a unique top-level element :ref:`mujoco <mujoco>`. The next-level elements are referred to as
*sections*. They are all optional. Some sections are merely used for grouping and have no attributes. Sections can be *sections*. They are all optional. Some sections are merely used for grouping and have no attributes. Sections can be
repeated, to facilitate merging of models via the :ref:`include <include>` element. repeated, to facilitate merging of models via the :ref:`include <include>` element. The *order* of attributes within an
| The *order* of attributes within an element can be arbitrary. The order of child elements within a parent element can element can be arbitrary. The order of child elements within a parent element can also be arbitrary, with four
also be arbitrary, with four exceptions: exceptions:
- The order of :ref:`joint <body-joint>` elements within a :ref:`body <body>` matters because joint transformations are - The order of :ref:`joint <body-joint>` elements within a :ref:`body <body>` matters because joint transformations are
performed in sequence. performed in sequence.