Re: [tei-council] teidata.point

Good morning, from Lisbon! I like the idea of helpful comments turning up to guide the customizer, so I think it is good to see this. Only the phrasing is a little awkward, and I would amend to: I.e., if you have added or changed an attribute or element to use teidata.pointer Hope that helps, Elisa -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text Associate Professor of English University of Pittsburgh at Greensburg 150 Finoli Drive, Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu | Development site: http://newtfire.org Typeset by hand on my iPad

On Feb 27, 2018, at 7:09 AM, Syd Bauman wrote:

Hope y'all are having uneventful trips back home. If you look at the "Schematron" section of http://jenkins2.tei-c.org/job/TEIP5-dev/lastSuccessfulBuild/artifact/P5/rele... or equivalent, you will see that the comments I left in the tagdoc file, intended more for Council than end users, has been copied over to the output.

This is not a bug in the stylesheets, IMHO it is a feature -- if I really want the comment not to show up in the output I just move it to be a sibling of <constraint> instead of a child of <constraint>. No big deal.

But I forgot about that, and so we have a big ugly comment showing up. But taking a look at it, I wonder whether it should be left there for users or not?

Also, just so y'all know, I am planning to add a <remarks> indicating exactly what is deprecated. -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived