You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Modelica.UsersGuide.Conventions.Documentation.Format.Tables the guidelines say that the caption should be defined as:
<caption align="bottom"><strong>Tab 2:</strong> Caption starts with a capital letter</caption>
But this would place the caption at the bottom and not the top. The problem is that Dymola renders the position incorrectly and always displays it on the top. Now the question, should the caption appear at the top of the table or the bottom. If at the top then it needs to be updated and tools need to make sure to get the rendering right.
One additional problem is that align is no longer supported in HTML5, so the guideline should most likely updated anyway.
The text was updated successfully, but these errors were encountered:
dietmarw
changed the title
Conflicting guidelines for HTML documentation convention guidelines for tables
Conflicting guidelines for HTML documentation conventions for tables
Jun 18, 2021
This fixesmodelica#3844 by removing the recommendation and application of `align=\"bottom\"` since tools tend to interpret this differently (e.g., ignore) and the `align` parameter is also deprecated in HTML5. Not using and recommending it makes it more future proof.
In
Modelica.UsersGuide.Conventions.Documentation.Format.Tables
the guidelines say that the caption should be defined as:But this would place the caption at the bottom and not the top. The problem is that Dymola renders the position incorrectly and always displays it on the top. Now the question, should the caption appear at the top of the table or the bottom. If at the top then it needs to be updated and tools need to make sure to get the rendering right.
One additional problem is that
align
is no longer supported in HTML5, so the guideline should most likely updated anyway.The text was updated successfully, but these errors were encountered: