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
The <egXML> tagdoc has an example of <egXML> (itself, of course, encoded as an <egXML>) that purports to be a slide (from a lecture about TEI) that explains <egXML>. It contains the bullet point
<item>The <att>rend</att> attribute in the TEI namespace can be
used for recording how parts of the example was rendered</item>
This is a possible solution to the general problem of highlighting within examples (see at least #1632 and #1928, probably others). But it is one that, to my knowledge, has neither been agreed to nor implemented. The prose in the <remarks> spoke of it until 2018-01-19, at which time @jamescummings removed it “until [a] real mechanism [is] agreed [to]”, probably because this runs smack into the fact that attributes, by default, are in no namespace.
My instinct is to just change that last <item> to something entirely different, like
<item>The <att>source</att> attribute can (and should) be used to
point to a bibliographic citation for the example.</item>
The text was updated successfully, but these errors were encountered:
Assigning to @jamescummings to approve or disapprove or shed light on why this is not a problem or some such. If he and I agree on a solution, assigned to myself to implement. (Unless you want to @jamescummings, in which case go right ahead. :-)
sydb
changed the title
example example discusses the a possible future feature
example example discusses a possible future feature
Jun 25, 2022
The
<egXML>
tagdoc has an example of<egXML>
(itself, of course, encoded as an<egXML>
) that purports to be a slide (from a lecture about TEI) that explains<egXML>
. It contains the bullet pointThis is a possible solution to the general problem of highlighting within examples (see at least #1632 and #1928, probably others). But it is one that, to my knowledge, has neither been agreed to nor implemented. The prose in the
<remarks>
spoke of it until 2018-01-19, at which time @jamescummings removed it “until [a] real mechanism [is] agreed [to]”, probably because this runs smack into the fact that attributes, by default, are in no namespace.My instinct is to just change that last
<item>
to something entirely different, likeThe text was updated successfully, but these errors were encountered: