- Tei-council - lists.tei-c.org

Re: [tei-council] weird validation problem
by Elisa Beshero-Bondar 07 May '17

07 May '17

Dear Council-- The weird validation problem is solved: I needed to purge my system of DS_Store files (and this time I set up a proper "cron job" to keep removing them every day). My project's schema needs to check files within a collection, and the presence of a pesky DS_Store file was interfering (sigh). I feel pretty silly, but since errors generated by such things tend to be pretty dramatic, maybe it's worth filing away in future. Elisa On Sat, May 6, 2017 at 2:00 AM, Elisa Beshero-Bondar <ebb8(a)pitt.edu> wrote: > Dear Council-- > I'm seeing a weird schema validation problem since our Stylesheets meeting > on Thursday, just on my Mac OS X installation of oXygen version 19 (current > one). It's weird because I can't duplicate the problem on my (also current) > Linux installation of oXygen. I see it on my Mac only when I try to > validate the TEI files in one project, with an ODD-generated schema. On the > Mac, validation is interrupted with an error that seems to indicate a > problem with the .rng file: Here is the error message: > > Engine name: ISO Schematron > Severity: fatal > Description: Required item type of result of call to collection is node(); > supplied value has item type xs:base64Binary > Start location: 2620:10 > > Clicking on the error message opens my RNG schema file to line 2620, which > is simply: > <define name="model.choicePart"> > <choice> > <ref name="sic"/> > <ref name="corr"/> > <ref name="reg"/> > <ref name="orig"/> > <ref name="unclear"/> > <ref name="abbr"/> > <ref name="expan"/> > <ref name="supplied"/> > <ref name="seg"/> > </choice> > </define> > This is a standard TEI schema rule, and I see no reason why it would be > failing. > > On my Linux computer, I've checked to see that it is running the same > version of oXygen as my Mac, and validation of the same files is performing > with no problems there. So something is wrong on my Mac, but I can't figure > out what. > > The only possibly event I can think of is that I installed Apache Ant on > my Mac using homebrew in my terminal two days ago during our Stylesheets > session, so that I could get the Stylesheets to properly run in their > sequence from our bin directory. But I don't know why that would interfere > with oXygen! > > Has anyone seen something similar or can advise? I've also written to > oXygen support. > > Thanks--and sorry to bug our group with this, but I wonder if it's an > ODD-related thing that we're likely to see more here than elsewhere... > > Elisa > > -- > 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(a)pitt.edu <ebb8(a)pitt.edu> > Development site: http://newtfire.org > -- 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(a)pitt.edu <ebb8(a)pitt.edu> Development site: http://newtfire.org

1 0

weird validation problem
by Elisa Beshero-Bondar 06 May '17

06 May '17

Dear Council-- I'm seeing a weird schema validation problem since our Stylesheets meeting on Thursday, just on my Mac OS X installation of oXygen version 19 (current one). It's weird because I can't duplicate the problem on my (also current) Linux installation of oXygen. I see it on my Mac only when I try to validate the TEI files in one project, with an ODD-generated schema. On the Mac, validation is interrupted with an error that seems to indicate a problem with the .rng file: Here is the error message: Engine name: ISO Schematron Severity: fatal Description: Required item type of result of call to collection is node(); supplied value has item type xs:base64Binary Start location: 2620:10 Clicking on the error message opens my RNG schema file to line 2620, which is simply: <define name="model.choicePart"> <choice> <ref name="sic"/> <ref name="corr"/> <ref name="reg"/> <ref name="orig"/> <ref name="unclear"/> <ref name="abbr"/> <ref name="expan"/> <ref name="supplied"/> <ref name="seg"/> </choice> </define> This is a standard TEI schema rule, and I see no reason why it would be failing. On my Linux computer, I've checked to see that it is running the same version of oXygen as my Mac, and validation of the same files is performing with no problems there. So something is wrong on my Mac, but I can't figure out what. The only possibly event I can think of is that I installed Apache Ant on my Mac using homebrew in my terminal two days ago during our Stylesheets session, so that I could get the Stylesheets to properly run in their sequence from our bin directory. But I don't know why that would interfere with oXygen! Has anyone seen something similar or can advise? I've also written to oXygen support. Thanks--and sorry to bug our group with this, but I wonder if it's an ODD-related thing that we're likely to see more here than elsewhere... Elisa -- 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(a)pitt.edu <ebb8(a)pitt.edu> Development site: http://newtfire.org

1 0

Re: [tei-council] co-operative stylesheet education session #9
by Alejandro Bia 04 May '17

04 May '17

How can I connect to the Google hangout? At 14:46 04/05/2017, 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 <s.bauman(a)northeastern.edu> >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(a)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(a)pitt.edu <ebb8(a)pitt.edu> >Development site: http://newtfire.org >-- >tei-council mailing list >tei-council(a)lists.tei-c.org >http://lists.lists.tei-c.org/mailman/listinfo/tei-council > >PLEASE NOTE: postings to this list are publicly archived --------------------------------------------------------- ALEJANDRO BIA e-mail: abia(a)umh.es CIO - DEMI Centro de Investigación Operativa Departamento de Estadística, Matemáticas e Informática Área de Lenguajes y Sistemas Informáticos Universidad Miguel Hernández Ed. Torretamarit, Av. Universidad s/n, CP:03202, Elche, ESPAÑA Web: http://dhw.umh.es/alex-bia/ Tel: +34 966658973 Móvil: +34 644447008 Skype: alex-bia Twitter: @alex_bia --------------------------------------------------------- --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

4 4

co-operative stylesheet education session #9
by Syd Bauman 04 May '17

04 May '17

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/.

5 4

tei down again?
by Mylonas, Elli 04 May '17

04 May '17

Can't reach it from Athens, trying to look things up in a workshop... --elli

2 1

Re: [tei-council] co-operative stylesheet education session #9
by Alejandro Bia 03 May '17

03 May '17

A few thoughts on the ticket #261 problem: As can be read in several placed on the Web: "the html:address element is ONLY for contact information for its nearest html:article or html:body ancestor" (article only exists in HTML5). In https://developer.mozilla.org/en/docs/Web/HTML/Element/address it also recommends that "to represent an arbitrary address, one that is not related to the contact information, use a html:p element rather than the html:address element." So html:p is a good candidate for the conversion, and a general-purpose one. INLINE vs BLOCK: So at this point my doubt is whether there are cases in TEI where a tei:address should be rendered "inline" (e.g. within a paragraph), instead of the perhaps more common "block" rendering (starting in a new line). If both renderings are expected in TEI, then we need an attribute to encode such difference and choose one option as the default (probably block). So we would have something like (I will use "rend" for the examples, buy can be any other attribute): TEI: Mary moved to <address rend="inline">32nd Moo street<address>, but before, she lived in <address rend="inline">23ed Miou street<address>. And for block rendered addresses, just use rend="block", or nothing if "block" is the default rendering. So a simple HTML rendering solution could be: In the case of inline-rendered addresses: HTML: Mary moved to 32nd Moo street, but before, she lived in 23ed Miou street. And for block-rendered addresses: TEI source: <address> <addrLine>110 Southmoor Road,</addrLine> <addrLine>Oxford OX2 6RB,</addrLine> <addrLine>UK</addrLine> </address> Should simply be converted to HTML like this: 110 Southmoor Road, Oxford OX2 6RB, UK And, when using more specific elements like tei:street, tei:name, etc., just the same thing: TEI source: <address> <street>110 Southmoor Road</street> <name type="city">Oxford</name> <postCode>OX2 6RB</postCode> <name type="country">United Kingdom</name> </address> Would be converted to HTML like this: 110 Southmoor Road Oxford OX2 6RB United Kingdom We could have differentiated renderings for street, name, postCode, etc., but I think this should be customized by projects themselves, and not be part of a general-purpose TEI stylesheet. Anyway, the output for differentiated rendering should be something like this: 110 Southmoor Road Oxford OX2 6RB United Kingdom Which is a very ugly HTML code (but better than using the HTML style attribute and have the CSS code embedded in the HTML target). "span" should be used since there are no HTML elements for street, postcode, city, country, etc. Once we have decided which will the HTML target solution be, the rest is coding an xsl:template and minimally modifying a CSS stylesheet. Alex.- At 22:18 03/05/2017, you wrote: >I've created a test file in case we still need one: >https://gist.github.com/raffazizzi/6b57a9c0016e46aebd249d5041ca4ae4 > >Raff > >On Wed, Apr 26, 2017 at 12:20 PM, Syd Bauman <s.bauman(a)northeastern.edu> >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(a)lists.tei-c.org > > http://lists.lists.tei-c.org/mailman/listinfo/tei-council > > > > PLEASE NOTE: postings to this list are publicly archived > > >-- >tei-council mailing list >tei-council(a)lists.tei-c.org >http://lists.lists.tei-c.org/mailman/listinfo/tei-council > >PLEASE NOTE: postings to this list are publicly archived --------------------------------------------------------- ALEJANDRO BIA e-mail: abia(a)umh.es CIO - DEMI Centro de Investigación Operativa Departamento de Estadística, Matemáticas e Informática Área de Lenguajes y Sistemas Informáticos Universidad Miguel Hernández Ed. Torretamarit, Av. Universidad s/n, CP:03202, Elche, ESPAÑA Web: http://dhw.umh.es/alex-bia/ Tel: +34 966658973 Móvil: +34 644447008 Skype: alex-bia Twitter: @alex_bia --------------------------------------------------------- --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0

Build failed in Jenkins: TEIP5-Test-dev #3327
by Victoria TEI Jenkins 03 May '17

03 May '17

See <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/3327/display/redirect?pag…> Changes: [lou.burnard] close 1538 ------------------------------------------ [...truncated 3.25 KB...] fi if [ git = "git" ] ; \ then \ git log --max-count=1 --pretty=format:"<info type=\"git\"><entry><commit revision=\"%h\"><date>%ai</date></commit></entry></info>" > repodate.xml ; \ fi BUILD: Generate modular DTDs, Schemas, Schematron and miscellaneous outputs ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -lib Utilities/lib/jing.jar:Utilities/lib/saxon9he.jar -f antbuilder.xml -DXSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/../../../Stylesheet…> -DDRIVER=Source/guidelines-en.xml base subset outputs BUILD FAILED <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/antbuilder.xml>:39: ; SystemID: <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Utilities/expand.xsl;> Line#: 68; Column#: 21 net.sf.saxon.trans.XPathException: org.xml.sax.SAXParseException; systemId: <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Source/Specs/att.gl…;> lineNumber: 265; columnNumber: 11; The element type "attDef" must be terminated by the matching end-tag "</attDef>". at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:471) at net.sf.saxon.event.Sender.send(Sender.java:153) at net.sf.saxon.functions.DocumentFn.makeDoc(DocumentFn.java:330) at net.sf.saxon.functions.Doc.call(Doc.java:138) at net.sf.saxon.functions.Doc.call(Doc.java:24) at net.sf.saxon.expr.FunctionCall.iterate(FunctionCall.java:546) at net.sf.saxon.expr.Expression.evaluateItem(Expression.java:763) at net.sf.saxon.expr.SimpleStepExpression.iterate(SimpleStepExpression.java:108) at net.sf.saxon.value.Closure.iterate(Closure.java:189) at net.sf.saxon.expr.instruct.ApplyTemplates$ApplyTemplatesPackage.processLeavingTail(ApplyTemplates.java:566) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:387) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates$ApplyTemplatesPackage.processLeavingTail(ApplyTemplates.java:569) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:387) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.DocumentInstr.evaluateItem(DocumentInstr.java:330) at net.sf.saxon.expr.instruct.DocumentInstr.evaluateItem(DocumentInstr.java:54) at net.sf.saxon.expr.parser.ExpressionTool.evaluate(ExpressionTool.java:313) at net.sf.saxon.expr.LetExpression.eval(LetExpression.java:500) at net.sf.saxon.expr.LetExpression.processLeavingTail(LetExpression.java:702) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.Controller.transformDocument(Controller.java:2291) at net.sf.saxon.Controller.transform(Controller.java:1863) at net.sf.saxon.s9api.XsltTransformer.transform(XsltTransformer.java:579) at net.sf.saxon.jaxp.TransformerImpl.transform(TransformerImpl.java:185) at org.apache.tools.ant.taskdefs.optional.TraXLiaison.transform(TraXLiaison.java:195) at org.apache.tools.ant.taskdefs.XSLTProcess.process(XSLTProcess.java:876) at org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:414) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.Project.executeTarget(Project.java:1364) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at org.apache.tools.ant.Main.runBuild(Main.java:851) at org.apache.tools.ant.Main.startAnt(Main.java:235) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) Caused by: org.xml.sax.SAXParseException; systemId: <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Source/Specs/att.gl…;> lineNumber: 265; columnNumber: 11; The element type "attDef" must be terminated by the matching end-tag "</attDef>". at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:451) ... 99 more --------- org.xml.sax.SAXParseException; systemId: <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Source/Specs/att.gl…;> lineNumber: 265; columnNumber: 11; The element type "attDef" must be terminated by the matching end-tag "</attDef>". at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:451) at net.sf.saxon.event.Sender.send(Sender.java:153) at net.sf.saxon.functions.DocumentFn.makeDoc(DocumentFn.java:330) at net.sf.saxon.functions.Doc.call(Doc.java:138) at net.sf.saxon.functions.Doc.call(Doc.java:24) at net.sf.saxon.expr.FunctionCall.iterate(FunctionCall.java:546) at net.sf.saxon.expr.Expression.evaluateItem(Expression.java:763) at net.sf.saxon.expr.SimpleStepExpression.iterate(SimpleStepExpression.java:108) at net.sf.saxon.value.Closure.iterate(Closure.java:189) at net.sf.saxon.expr.instruct.ApplyTemplates$ApplyTemplatesPackage.processLeavingTail(ApplyTemplates.java:566) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:387) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates$ApplyTemplatesPackage.processLeavingTail(ApplyTemplates.java:569) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:387) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.ElementCreator.processLeavingTail(ElementCreator.java:364) at net.sf.saxon.expr.instruct.Copy.processLeavingTail(Copy.java:432) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.expr.instruct.ApplyTemplates.apply(ApplyTemplates.java:298) at net.sf.saxon.expr.instruct.ApplyTemplates.process(ApplyTemplates.java:251) at net.sf.saxon.expr.instruct.DocumentInstr.evaluateItem(DocumentInstr.java:330) at net.sf.saxon.expr.instruct.DocumentInstr.evaluateItem(DocumentInstr.java:54) at net.sf.saxon.expr.parser.ExpressionTool.evaluate(ExpressionTool.java:313) at net.sf.saxon.expr.LetExpression.eval(LetExpression.java:500) at net.sf.saxon.expr.LetExpression.processLeavingTail(LetExpression.java:702) at net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353) at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456) at net.sf.saxon.Controller.transformDocument(Controller.java:2291) at net.sf.saxon.Controller.transform(Controller.java:1863) at net.sf.saxon.s9api.XsltTransformer.transform(XsltTransformer.java:579) at net.sf.saxon.jaxp.TransformerImpl.transform(TransformerImpl.java:185) at org.apache.tools.ant.taskdefs.optional.TraXLiaison.transform(TraXLiaison.java:195) at org.apache.tools.ant.taskdefs.XSLTProcess.process(XSLTProcess.java:876) at org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:414) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.Project.executeTarget(Project.java:1364) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at org.apache.tools.ant.Main.runBuild(Main.java:851) at org.apache.tools.ant.Main.startAnt(Main.java:235) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) Total time: 3 seconds make: *** [p5.xml] Error 1 Build step 'Execute shell' marked build as failure Not sending mail to unregistered user lou.burnard(a)retired.ox.ac.uk

1 1

Build failed in Jenkins: TEIP5-Test-dev #3325
by Victoria TEI Jenkins 03 May '17

03 May '17

See <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/3325/display/redirect?pag…> Changes: [lou.burnard] add empty element per issues 1596 ------------------------------------------ Started by an SCM change Building in workspace <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/TEIC/TEI.git # timeout=10 Fetching upstream changes from https://github.com/TEIC/TEI.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/TEIC/TEI.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/dev^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/dev^{commit} # timeout=10 Checking out Revision fddde73b3adebc41869a2c0e4de89c90d2359615 (refs/remotes/origin/dev) > git config core.sparsecheckout # timeout=10 > git checkout -f fddde73b3adebc41869a2c0e4de89c90d2359615 > git rev-list ff9875fde94f380064f38fbed1ad644adb340369 # timeout=10 [workspace] $ /bin/bash -xe /tmp/jenkins3763677745448053142.sh + cd P5 ++ pwd + make VCS=git INJENKINS=true XSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/../../../Stylesheet…> clean validate test (cd Exemplars; make clean) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Exemplars'> mv tei_lite_fr.nvdl tei_lite_fr.nvdl.bak rm -f *.processed *.xsd *.dtd *.doc.* *.rnc tei*.xsl tei*.rng *.compiled* *~ *.xi *.isosch *.epub *.pdf *.html *.nvdl *-teix* mv tei_lite_fr.nvdl.bak tei_lite_fr.nvdl rm -f exnames.xml rm -f enrich.rng isofs.rng rm -f names.xml *properties rm -f [A-Z]*xml make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Exemplars'> (cd Test; make clean) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Test'> rm -f test*.doc.xml test*.rnc test*.dtd test*.compiled.* test*.xsd test*.rnc test*.rng test*.xsl test*.isosch rm -rf LOG *~ *.xsd Schema RomaResults DTD rm -rf *.doc.* rm -f detest.log detest.log.all rm -f *-examples.rng *-examples.rnc *test*.nvdl *-ex.odd rm -f detest.rnc detest.rng detest.dtd detest.isosch make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Test'> rm -rf release Guidelines Guidelines-web Schema DTD dtd Split rm -rf Guidelines.??? Guidelines-* rm -f *.isosch.xsl rm -f *.stamp rm -f *.xsd rm -f Exemplars/stdout rm -f Test/*.isosch rm -f Test/detest.dtd Test/detest.rnc Test/detest.rng Test/detest.xsl rm -f Test/stdout rm -f Utilities/guidelines.xsl rm -f anything buildweb.xml rm -f p5.sch p5.isosch p5.xml p5subset.xml p5subset.json p5subset.js rm -f p5attlist.txt rm -f p5odds-examples.rng p5odds-examples.rnc p5odds.rng p5odds.rnc p5odds.isosch rm -f pdfbuild.log rm -f stripspace.xsl.model rm -f tei-*.zip rm -f tei-p5-*_*build rm -f tei-p5-*_*changes rm -f tei-p5-*_*deb rm -f teiwebsiteguidelines.zip rm -rf FASC-* rm -rf catalogue.* modList rm -rf valid v.xml ValidatorLog.xml Utilities/pointerattributes.xsl graphics.sh missfont.log v.body v.header Schematron1.xml Schematron2.xml Checking you have running XML tools and Perl before trying to run transform... Ant:/usr/bin/ant Perl:/usr/bin/perl Java:/usr/bin/java xmllint:/usr/bin/xmllint touch check.stamp get latest date: VCS is git if [ "git" = "svn" ] ; \ then \ if [ true = "true" ] ; \ then svn info --xml svn://svn.code.sf.net/p/tei/code/trunk/P5 ; \ else svn info --xml ; \ fi > repodate.xml ; \ fi if [ git = "git" ] ; \ then \ git log --max-count=1 --pretty=format:"<info type=\"git\"><entry><commit revision=\"%h\"><date>%ai</date></commit></entry></info>" > repodate.xml ; \ fi BUILD: Generate modular DTDs, Schemas, Schematron and miscellaneous outputs ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -lib Utilities/lib/jing.jar:Utilities/lib/saxon9he.jar -f antbuilder.xml -DXSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/../../../Stylesheet…> -DDRIVER=Source/guidelines-en.xml base subset outputs BUILD FAILED <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/antbuilder.xml>:39: Fatal error during transformation using <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Utilities/expand.xsl>: I/O error reported by XML parser processing <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Source/Specs/empty.…>: <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Source/Specs/empty.…> (No such file or directory); SystemID: <http://teijenkins.hcmc.uvic.ca/job/TEIP5-Test-dev/ws/P5/Utilities/expand.xsl;> Line#: 68; Column#: 21 Total time: 13 seconds make: *** [p5.xml] Error 1 Build step 'Execute shell' marked build as failure Not sending mail to unregistered user lou.burnard(a)retired.ox.ac.uk

1 1

RomaJS development update
by Raffaele Viglianti 02 May '17

02 May '17

Dear council members, I've completed a first phase of development of RomaJS (a placeholder name) and I would like to both give you an update and seek volunteers for the next phase of work. *The prompts for your contributions are highlighted in bold below (bring friends!).* The code is on GitHub: https://github.com/raffazizzi/romajs 1. Summary of work: I've have been writing this Redux / React <http://redux.js.org/docs/basics/UsageWithReact.html> application by focusing on data operations first, user interface second. Briefly, the application is now capable of: - reading in an ODD file from the web or from disk - reading in a source file (ie p5 subset in JSON format) - add and remove modules - add and remove elements - write an updated ODD to disk (This is actually only mocked for user testing at the moment.) - provide basic UI components for these operations (working towards what's been sketched in the wireframes <https://docs.google.com/presentation/d/1sUESuY9pF3DkHoQMJJjrVMV2SPFQYE1YqmG…> ) 2. Tests Each operation is comprehensively tested. I've aimed at creating a solid testing infrastructure that is at the core of the application development. I have created two wiki pages to help understanding and developing tests: - a list of test scenarios <https://github.com/raffazizzi/romajs/wiki/Test-scenarios> - a short guide on how to write tests <https://github.com/raffazizzi/romajs/wiki/How-to-write-tests> *Please look at the list of test scenarios: have I not tested something?* You'll see that the list includes different ways of including/excluding modules and elements in ODD. *Have I covered all the mechanisms for doing so? What's missing?* We could discuss this on this email or on the wiki. It would be awesome if then someone besides me would write new tests that result from the discussion! 3. Parsing ODD In order to avoid using a heavy DOM processor, and to make it possible to include ODD directly in the application state, I've opted to convert ODD to JSON. At first I was using an off the shelf library that served me very well until I had to serialize back to XML and realized that mixed content was all screwy... So I wrote my own library here: https://github.com/raffazizzi/squash-xml-json The library is quite central to the success of RomaJS and while it has some tests, it needs more extensive testing. *Would anyone like to help test and develop it? Or perhaps know of viable alternatives I've overlooked?* 4. Getting started with the UI I've created basic UI components to do the operations described above. Here is the current very bare version: https://raffazizzi.github.io/romajs/ *Please try it out with as many (canonicalized) ODD files that you have lying around. Does it do what you expect? Do you get back XML that matched what you wanted? **Please break it (hopefully it will take a few hits first).* 5. Next steps I think I may focus more on UI development now (as per wireframes <https://docs.google.com/presentation/d/1sUESuY9pF3DkHoQMJJjrVMV2SPFQYE1YqmG…>). Getting started with a CSS framework library and nail down general functionality up to the point where we are now. At the same time, I'd like to get started on operations to change elements (basically creating elementSpec[@mode="change"]). *This would be a good time for others to step in the development process: others could start writing operations and tests for changing elements while I focus on UI. Or viceversa. The current module/element operations and tests provide examples of how this all works (and of course I'd be happy to explain stuff).* 6. Finally: decision tree At the F2F we started talking about a possible "decision tree" as a way into RomaJS. I started a document <https://docs.google.com/document/d/1r33QbY7O0HqOHvTxZtOq_-MrYqtIE572YqPEY3J…> with a list of possible questions to the user; James commented on it. *Please comment and add your additions if you can. I would be thrilled if others would want to explore this further as a mind map, etc. so that it's nicely planned out before starting development on a decision tree feature.* As development gains momentum, I hope to write similar reports to this one at least once monthly. Raff

5 10

Doodle Poll: Ticket Triage
by Hugh Cayless 01 May '17

01 May '17

Dear all, As we decided on Thursday, we're going to try out having one volunteer a month triage new tickets. That is, read them, decide whether they're valid (not invalid, duplicates, etc.), and assign someone to investigate each one, taking into account skillsets and workloads. We'll try it for the next few months and see if we like it, https://doodle.com/poll/2wq9wtq6f69wfxc3 I will take May, and try to clean up the backlog as much as I can now that the semester is over. I'd appreciate it if you could all take a look at the unassigned tickets we have now and grab any that suit you. That would be most helpful. Thanks, Hugh

1 0