RE: Standard Date/Time Publication Functions in XSL??

Hi Michael,

I'm trying to implement some pre-written XSL extension modules,
specifically the date Function (http://www.exslt.org/date/index.html) I
think the javascript was just one other method of applying Date data to
the XML file. I could be wrong... you would know more than I would.

I just want to print the date in an XSL output :)

Thanks for your help,

John

    -------------------------
John Bruso
Web Developer
ph  307.674-6446-2608







-----Original Message-----
From: Michael Kay [mailto:mike@xxxxxxxxxxxx]
Sent: Tuesday, August 02, 2005 4:34 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE:  Standard Date/Time Publication Functions in XSL??

EXSLT is a set of function specifications; there are different
implementations of the functions for different processors. Saxon 6.5.4
contains native implementations of many of the EXSLT functions within
the
product: for a list, see
http://saxon.sourceforge.net/saxon6.5.4/extensions.html#EXSLT

It looks as if you're trying to use a Javascript implementation: these
will
work only with XSLT processors such as MSXML that support Javascript
extensions.

Michael Kay
http://www.saxonica.com/


> -----Original Message-----
> From: Bruso, John [mailto:jbruso@xxxxxxxxxxxx]
> Sent: 02 August 2005 22:18
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE:  Standard Date/Time Publication Functions in XSL??
>
> Hi James,
>
> Thanks for the reference. I'm trying to implement the
> extension, but I'm
> afraid my XSL knowledge is at it's glass ceiling at the moment.
>
> I'm working from this reference doc:
> http://www.exslt.org/date/functions/month-in-year/index.html
>
> So far, I've downloaded and installed the Date-Time Functions.
>
> I want to insert a date-time into an existing XSL sheet called
> InlineCustomization.xsl
>
> At the top of the page, I've added:
>
> <xsl:stylesheet
> 	xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"
> 	xmlns:encoder="xalan://java.net.URLEncoder"
> exclude-result-prefixes="encoder"
> 	xmlns:date="http://exslt.org/date"
> 	xmlns:func="http://exslt.org/functions"
> 	extension-element-prefixes="date func">
> 	<xsl:import
> href="http://www-dev.sheridan.edu:8080/uPortal/media/edu/vt/po
> rtal/layou
> t/TabPageColumn/InlineCustomization/XSL/functions/month-in-yea
> r/date.mon
> th-in-year.xsl" />
> 	<xsl:import
> href="http://www-dev.sheridan.edu:8080/uPortal/media/edu/vt/po
> rtal/layou
> t/TabPageColumn/InlineCustomization/XSL/functions/month-in-yea
> r/date.mon
> th-in-year.function.xsl" />
>
>
> I'm getting this error when I try to do a local transform in Oxygen
> using Saxon Transformer 6.5.4:
>
> "Error: Unknown Saxon extension element script"
>
>
>     -------------------------
> John Bruso
> Web Developer
> ph  307.674-6446-2608
>
>
>
>
>
>
>
> -----Original Message-----
> From: James Fuller [mailto:jim.fuller@xxxxxxxxxxxxxx]
> Sent: Tuesday, August 02, 2005 11:17 AM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re:  Standard Date/Time Publication Functions in XSL??
>
> Bruso, John wrote:
>
> >Is there a way to publish the Date in XSL?
> >
> >Like: Wednesday, July 23 2005
> >
> >
> >
>
> check out www.exslt.org datetime functions.
>
> gl, Jim Fuller
>
> >    -------------------------
> >John Bruso
> >Web Developer
> >ph  307.674-6446-2608
> >
> >
> >
> >
> >
> >
> >
> >-----Original Message-----
> >From: Michael Kay [mailto:mike@xxxxxxxxxxxx]
> >Sent: Tuesday, August 02, 2005 10:24 AM
> >To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> >Subject: RE:  Transformation of hierarchy, changing
> levels, and...
> >back
> >
> >It looks to me as if what you're trying to describe is
> >
> >"group Tuv element by their @Lang value"
> >
> >So you need to look up Muenchian grouping (or XSLT 2.0
> >xsl:for-each-group if
> >you can use 2.0). See http://www.jenitennison.com/xslt/grouping.
> >
> >But I may have misunderstood your requirement completely - I don't
> >understand the notations in your problem description.
> >
> >Michael Kay
> >http://www.saxonica.com/
> >
> >
> >
> >
> >>-----Original Message-----
> >>From: Marcin Milkowski [mailto:milek_pl@xxxxx]
> >>Sent: 02 August 2005 16:13
> >>To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> >>Subject:  Transformation of hierarchy, changing levels,
> >>and... back
> >>
> >>hi,
> >>
> >>I've been trying to make some transformation from a structure:
> >>
> >><Tu>
> >>	<Tuv>
> >>		@Lang
> >>		some text1
> >>		<df>some text2</df>
> >>		<ut>some optional text</ut>
> >>		some text
> >>		<ut>some more text</ut>
> >>		and some text
> >>	</Tuv>
> >>	<Tuv>
> >>		@Lang
> >>		some text
> >>		<df>
> >>		some text
> >>		</df>
> >>		<ut>some optional text</ut>
> >>		some text
> >>		<ut>some more text</ut>
> >>		and some text
> >>	</Tuv>
> >></Tu>
> >>
> >>to a structure
> >>
> >><trans-unit>	(=Tu)
> >>	@id
> >>	<source> (=Tu/Tuv@Lang=$blabla)
> >>
> >>		some text1
> >>		<g@id@barfoo/>	(<df>)
> >>		some text2
> >>		<g@id@foobar/>	(</df>)
> >>		<ph@id>some optional text</ph>(=ut)
> >>		some text
> >>		<ph@id>some more text</ut>
> >>		and some text
> >>  	</source>
> >>
> >>	<target> (=Tu/Tuv@Lang=$foobar)
> >>		some text1
> >>		<g@id@barfoo/>	(<df>)
> >>		some text2
> >>		<g@id@foobar/>	(</df>)
> >>		<ph@id>some optional text</ph>(=ut)
> >>		some text
> >>		<ph@id>some more text</ut>
> >>		and some text
> >>	</target>
> >></trans-unit>
> >>
> >>I tried to match //Tu, and then use for-each to match all
> >>Tuv[1]/ut and
> >>Tuv[2]/ut. This approach turned quite difficult because I had
> >>to insert
> >>ut at exactly the same position in source as it was in
> >>Tuv[1]. Probably
> >>   I should use more templates and match //Tu/Tuv or something like
> >>that, but I wouldn't know how to close the trans-unit tag
> (is there a
> >>way to check if this Tuv is Tu/Tuv[1] or Tu/Tuv[2]?).
> Additionally, I
> >>would need to produce a second file with ids replacing all
> >>text between
> >>tags in Tu/Tuv[1]@Lang=foobar and Tu/Tuv[2]@lLang=barfoo. (So
> >>the text
> >>must be uniquely numbered, or indexed in the other file). The
> >>third step
> >>would be to backconvert the transformed files into a source one.
> >>
> >>Any ideas what method would be the best in this case? All help very
> >>appreciated.
> >>
> >>Best regards,
> >>	Marcin Milkowski