Skip to content

Commit fa60b47

Browse files
committed
Fixes the display of the annotations code examples
These were simply not displayed due to erroneous syntax.
1 parent 8164355 commit fa60b47

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

text/source/behavior/equations/annotations.rst

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -114,14 +114,14 @@ The syntax of an annotation is the same syntax used for
114114
:ref:`modifications`. This means the annotation will include either
115115
an assignment to a variable in the annotation, *e.g.,*
116116

117-
.. code-block:
117+
.. code-block:: modelica
118118
119119
annotation(Evaluate=true);
120120
121121
or it will include a modification to something **inside** a variable in
122122
the annotation, *e.g.,*
123123

124-
.. code-block:
124+
.. code-block:: modelica
125125
126126
annotation(experiment(StartTime=0,StopTime=8));
127127
@@ -133,7 +133,7 @@ Annotations were designed to allow model developers to attach
133133
associate a part number with a given model definition, they might
134134
introduce a model annotation like this:
135135

136-
.. code-block:
136+
.. code-block:: modelica
137137
138138
annotation(PartNumber="FF78-E4B879");
139139
@@ -149,7 +149,7 @@ Imagine a user wanted to specify **both** a part number and an
149149
experiment annotation. Then they might end up with an annotation like
150150
this one:
151151

152-
.. code-block:
152+
.. code-block:: modelica
153153
154154
annotation(PartNumber="FF78-E4B879",
155155
experiment(StartTime=0,StopTime=8));
@@ -171,7 +171,7 @@ For example, a better approach for including the part number
171171
would be to enclose it in a variable that is more likely to be unique
172172
to your company or application, *e.g.,*:
173173

174-
.. code-block:
174+
.. code-block:: modelica
175175
176176
annotation(XogenyIndustries(PartNumber="FF78-E4B879"),
177177
experiment(StartTime=0,StopTime=8));
@@ -182,7 +182,7 @@ organization came along and wanted to associate a different part
182182
number with the same model, they could do that by establishing their
183183
own separate hierarchy in the annotation, *e.g.,*:
184184

185-
.. code-block:
185+
.. code-block:: modelica
186186
187187
annotation(XogenyIndustries(PartNumber="FF78-E4B879"),
188188
AcmeEquipment(PartNumber="A23335-992"),
@@ -193,7 +193,7 @@ annotations (*e.g.,* in the Modelica Standard Library). By
193193
convention, tool vendors use names that are prefixed by two
194194
underscores, *e.g.,*
195195

196-
.. code-block:
196+
.. code-block:: modelica
197197
198198
annotation(XogenyIndustries(PartNumber="FF78-E4B879"),
199199
__ModelicateTechnologies(enableCoolFeature10=true),

0 commit comments

Comments
 (0)