I'm planning on keeping the Stylesheets group in the mode of using work on stylesheets as a self-educational methodology (as opposed to the mission of actually working on stylesheets) for our Dec meeting this coming Thu 12-07. As mentioned at the Council F2F, we would like to re-schedule to Tuesdays at the same time (09:00 ET which is either 13:00Z or 14:00Z) starting with our Jan (or maybe Feb) meeting, and we'll switch our focus then. (Not that it will really mean much. :-) In any case, we are scheduled to meet this Thu 12-07 at 14:00Z (note: time is different than last meeting), i.e.: * 06:00 PST * 09:00 EST * 14:00 GMT <== different than last meeting * 15:00 CET <== different than last meeting I thought it would be useful to try to attack ticket 293 "error showing author etc". Peter will lead us through his suggested fix of 11-10 (which I'm reasonably sure will, in fact, work). Discussion to include the difference between signatures of xs:string, xs:string*, text(), text()*, node(), and node()*. And for extra credit I'll ask what's wrong with the XPath in common/functions.xsl on line 739. :-) Hope all the Americans had a great Thanksgiving, and that everyone else had a great non-holiday Thu 23 Nov. :-)
Finished that little test: yes, <xsl:copy-of> preserved the datatype. --------- <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" version="2.0"> <xsl:output method="text"/> <xsl:template match="/"> <xsl:variable name="arbitraryDate"> <xsl:copy-of select="xs:date('2017-12-07')"/> </xsl:variable> <!-- the variable $D retains the dateness (i.e., the xs:date datatype), else the following would throw an error. --> <xsl:value-of select="format-date( $arbitraryDate,'[FNn] [D01] [MNn] [Y]')"/> <xsl:text> </xsl:text> </xsl:template> </xsl:stylesheet> ---------
We were discussing this a bit during the call, but I thought I’d add here that, from what I’m reading of xsl:sequence, it seems that it’s preferable to use it in the context of functions because it preserves the XPath relationships from the document being processed—makes them part of what the function can process. See https://stackoverflow.com/questions/14361629/xslt-xslsequence-what-is-it-goo... <https://stackoverflow.com/questions/14361629/xslt-xslsequence-what-is-it-good-for> 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@pitt.edu <mailto:ebb8@pitt.edu> Development site: http://newtfire.org <http://newtfire.org/>
On Dec 7, 2017, at 10:28 AM, Syd Bauman <s.bauman@northeastern.edu> wrote:
Finished that little test: yes, <xsl:copy-of> preserved the datatype. --------- <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" version="2.0"> <xsl:output method="text"/> <xsl:template match="/"> <xsl:variable name="arbitraryDate"> <xsl:copy-of select="xs:date('2017-12-07')"/> </xsl:variable> <!-- the variable $D retains the dateness (i.e., the xs:date datatype), else the following would throw an error. --> <xsl:value-of select="format-date( $arbitraryDate,'[FNn] [D01] [MNn] [Y]')"/> <xsl:text> </xsl:text> </xsl:template> </xsl:stylesheet> --------- -- 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
participants (2)
-
Elisa Beshero-Bondar -
Syd Bauman