Re: [tei-council] co-operative stylesheet education session #9

Apologies. I've ended up double- booked this morning. Hugh Sent from my phone.

On May 4, 2017, at 08:46, Elisa Beshero-Bondar wrote:

Hi everyone-- I became very stuck on this homework--in actually attempting to get a fix to *process*--and I'm really stumped. I think I'm learning something about the interdependency of the Stylesheets, but I'm really baffled, ready to explain what I've tried, and I am hoping for enlightenment. I'm especially stumped because I attempted what *looks* from Raff's "gist" to be the same kind of fix he made, and it absolutely didn't work to alter my output. I can see at least two ways, though, that we're processing to output an HTML address element in two different contexts.

Anyway, in case it's my sample file, I wanted to share it with the group. This is a simplified version of a letter from my Digital Mitford project, and the TEI address element is toward the end of the document: https://github.com/ebeshero/Stylesheets/tree/dev/test_ebb The XML file is my input, and the HTML is a stupid tester output that doesn't change anything from the current way the Stylesheets are outputting. During the session I'll share what I tried to change, and hope for enlightenment.

Thanks, and looking forward to our session! Elisa

On Wed, Apr 26, 2017 at 12:20 PM, Syd Bauman wrote:

...

1. Andrew, Marcus, Jure, and Ron -- would you like to continue to receive these e-mails? If so, speak up.

2. We're scheduled to meet on Thu 04 May at 13:00Z on Google Hangouts.

3. Per our previous e-mail discussion, we have HOME WORK to complete before this meeting. Our goal is to address ticket #261.[1]

a) Read the ticket.[1]

b) Make a small test TEI file that uses the tei:address element; if you can do so easily, put it up somewhere to share with the rest of us for step #4, below.

c) Make a fork of the Stylesheets repo.

d) Find the 2 files that generate html:address, and fix the one that is general-purpose, leaving the the one that is used in the footer for later -- extra credit :-)

e) Decide what the HTML output (for tei:address input) should be, and implement a fix.

f) Test and update your fix until it works.[2]

g) Validate the HTML produced.[3]

h) Find any CSS files that may need to be changed accordingly, and change 'em as needed.

i) Share your test file and solution.

4. On the call we will try to run each solution on someone else's test file(s).

Notes ----- [1] https://github.com/TEIC/Stylesheets/issues/261 [2] E.g., by running /path/to/Stylesheets/bin/teitohtml TEST.xml [3] E.g., by opening in oXygen or by uploading to either https://validator.nu/ or http://validator.w3.org/. -- 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

-- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu Development site: http://newtfire.org -- 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