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
With this new value you can control how elements in the tooltip are rendered.
If the entity is part of the list (for example list of glosses),
<listtype="glossary">
<itemxml:id="kalendy">
<labeltype="main">Kalendy</label>
<glossxml:lang="cs">název prvního dne v měsíci v římském kalendáři. <hirendition="italic">Jani Calendae </hi>jsou tedy lednové Kalendy, začátek roku.</gloss>
<glossxml:lang="en">the name of the first day of the month in the Roman calendar. <hirendition="italic">Jani Calendae</hi> is thus the January Calendae, the beginning of the year.</gloss>
<note />
</item>
</list>
the <item> element can be rendered as the block element:
<elementSpecident="item"mode="change">
<modelpredicate="$parameters?mode='register-entry' and parent::list"behaviour="block" />
<modelbehaviour="listItem"/>
</elementSpec>
Another example: if the <hi> element is part of the anotation, it can be rendered with desired rendition but not as an annotation:
I suggest to introduce new mode value (within
$parameters
variable) to control HTML generated (in the tooltip, for example) for annotated elements.Suggested parameter's value, for instance
register-entry
should be used inreapi:register-entry()
function in theregisters.xql
module.On the line 435 change
to
With this new value you can control how elements in the tooltip are rendered.
If the entity is part of the list (for example list of glosses),
the
<item>
element can be rendered as the block element:Another example: if the
<hi>
element is part of the anotation, it can be rendered with desired rendition but not as an annotation:The text was updated successfully, but these errors were encountered: