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 February 2016, it was thought important to highlight the use of the <material> element in the support description.
Display of the <material> tag had been suppressed in 2014 at direction of @rla2118 because it was judged to be redundant in the HTML transform. Said transform presents the entire textual contents of the <support> element (within which <material> appears) as a single string under the rubric "Support/Dimensions".
If the current display of material information in HTML as described above is acceptable, then no further XSLT work is required.
If the editor currently supports the insertion of <material> into XML files, then no further coding work is required.
If no further work is required, this ticket should be closed.
If work is required, then this ticket should be properly labeled, prioritized, and if necessary, added to an appropriate milestone.
The redundancy is probably with Format and Layout. Nevertheless, I would leave as is for now, and close this ticket. I'm not sure this is really a problem.
In February 2016, it was thought important to highlight the use of the
<material>
element in the support description.Display of the
<material>
tag had been suppressed in 2014 at direction of @rla2118 because it was judged to be redundant in the HTML transform. Said transform presents the entire textual contents of the<support>
element (within which<material>
appears) as a single string under the rubric "Support/Dimensions".If the current display of material information in HTML as described above is acceptable, then no further XSLT work is required.
If the editor currently supports the insertion of
<material>
into XML files, then no further coding work is required.If no further work is required, this ticket should be closed.
If work is required, then this ticket should be properly labeled, prioritized, and if necessary, added to an appropriate milestone.
Over to @rla2118 @HolgerEssler and/or @jcowey to make said determinations.
The text was updated successfully, but these errors were encountered: