gestalt-users — Using Gestalt

[Gestalt-users] xsl:result-document cannot open a file

[Florent G. <dar...@ya...>]

  Hi

  I tried to use xsl:result-document, and I give a trange
error:

    Fatal error:
http://www.gobosoft.com/eiffel/gobo/gexslt/extension#OUTPUT_RESOLVER_ERROR:
Unable to open file://localhost/c%3A/some path/gexslt-result-doc.xml

  My stylesheet is:

    <xsl:transform
        xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
        version="2.0">

      <xsl:template name="main">
        <xsl:result-document href="gexslt-result-doc.xml">
          <yo/>
        </xsl:result-document>
      </xsl:template>

    </xsl:transform>

  I tried the following URIs:

    - gexslt-result-doc.xml
    - C:/some path/gexslt-result-doc.xml
    - file://localhost/c%3A/some path/gexslt-result-doc.xml
    - file://localhost/c%3A/some+path/gexslt-result-doc.xml
    - file://localhost/c%3A/some%20path/gexslt-result-doc.xml

with lowcase and upcase "C:", all gave the same error.  If
you confirm it is a bug, I'll open a ticket on the tracker.

  Regards,

--drkm






















	

	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com 

Re: [Gestalt-users] [gestalt-Bugs-1563054]gexslt:transformation()and namespace

[Florent G. <dar...@ya...>]

Colin Adams wrote:

  Hi

> I did raise one, and Mike proposed some wording changes.

  Thanks.  Here is the link for the archives:

    http://www.w3.org/Bugs/Public/show_bug.cgi?id=3772

> I assume the bug will be closed by the time I get back from
> China, so I will be able to implement a fix then.

  I think the proposition of Mike is perfect, in a user point of view. 
As he is an implementor, I guess the implementation side is OK too with
this.

  Perfect!  Thanks,

--drkm























	

	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com 

Re: [Gestalt-users] [gestalt-Bugs-1563054]gexslt:transformation()and namespace

[Colin A. <col...@ho...>]

I did raise one, and Mike proposed some wording changes.
I assume the bug will be closed by the time I get back from China, so I will 
be able to implement a fix then.


>From: Florent Georges <dar...@ya...>
>Reply-To: ges...@li...
>To: ges...@li...
>Subject: Re: [Gestalt-users] 
>[gestalt-Bugs-1563054]gexslt:transformation()and namespace
>Date: Thu, 28 Sep 2006 01:17:44 +0200 (CEST)
>
>Colin Adams wrote:
>
>   Hi Colin
>
> > I am going to raise this on the W3C list, to check.
>
>   Did you do so, or do you want I open an issue on the W3C Bugzilla?
>
>   Regards,
>
>--drkm
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>___________________________________________________________________________
>Découvrez un nouveau moyen de poser toutes vos questions quelque soit le 
>sujet !
>Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et 
>vos expériences.
>http://fr.answers.yahoo.com
>
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share 
>your
>opinions on IT & business topics through brief surveys -- and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>Gestalt-users mailing list
>Ges...@li...
>https://lists.sourceforge.net/lists/listinfo/gestalt-users

_________________________________________________________________
Be the first to hear what's new at MSN - sign up to our free newsletters! 
http://www.msn.co.uk/newsletters

Re: [Gestalt-users] [ gestalt-Bugs-1563054]gexslt:transformation()and namespace

[Florent G. <dar...@ya...>]

Colin Adams wrote:

  Hi Colin

> I am going to raise this on the W3C list, to check.

  Did you do so, or do you want I open an issue on the W3C Bugzilla?

  Regards,

--drkm























	

	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com 

Re: [Gestalt-users] OUTPUT_RESOLVER_ERROR: Invalid stdout: URI

[Florent G. <dar...@ya...>]

Colin Adams wrote:

  Hi

> It's a BUG, as the program should report the error, so
> raise a report on the tracker.

  Ok, done.

  Regards,

--drkm























	

	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com 

Re: [Gestalt-users] OUTPUT_RESOLVER_ERROR: Invalid stdout: URI

[Colin A. <col...@ho...>]

>From: Florent Georges <dar...@ya...>

>Following is the set of recorded exceptions:
>
>-------------------------------------------------------------------------------
>Class / Object      Routine                Nature of exception
>  Effect
>-------------------------------------------------------------------------------
>UT_URI              make @9                a_reference_valid:
><00000000035253A4>                         Precondition violated.
>  Fail
>-------------------------------------------------------------------------------

>   It seems that a URI-related precondition is not meet.  Any
>thought?
>

This indicates that there are invalid characters in the URI.

It's a BUG, as the program should report the error, so raise a report on the 
tracker.

It's also a bug because all the characters in your relative URI are valid, 
so there must be a windows-realted problem in creating the base URI. I shall 
have to debug it.

_________________________________________________________________
Windows Live™ Messenger has arrived. Click here to download it for free! 
http://imagine-msn.com/messenger/launch80/?locale=en-gb

Re: [Gestalt-users] OUTPUT_RESOLVER_ERROR: Invalid stdout: URI

[Florent G. <dar...@ya...>]

Colin Adams wrote:

  Hi

> So if you are going to use relative URIs in
> xsl:result-document, you must change the principal output
> destination

  Ok, thanks for the answer.  I tried the following:

    > cat gexslt-crash-2.xsl
    <xsl:transform
        xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
        version="2.0">

      <xsl:template name="main">
        <xsl:result-document href="gexslt-crash-2.xml">
          <out/>
        </xsl:result-document>
      </xsl:template>

    </xsl:transform>

    > gexslt gexslt-crash-2.xsl --template=main --output=dummy.xml
gexslt: system execution failed.
Following is the set of recorded exceptions:

-------------------------------------------------------------------------------
Class / Object      Routine                Nature of exception         
 Effect
-------------------------------------------------------------------------------
UT_URI              make @9                a_reference_valid:
<00000000035253A4>                         Precondition violated.      
 Fail
-------------------------------------------------------------------------------
GEXSLT              perform_transformation @27
<000000000335003C>                         Routine failure.            
 Fail
-------------------------------------------------------------------------------
GEXSLT              execute @44
<000000000335003C>                         Routine failure.            
 Fail
-------------------------------------------------------------------------------
GEXSLT              root's creation
<000000000335003C>                         Routine failure.            
 Exit
-------------------------------------------------------------------------------

  It seems that a URI-related precondition is not meet.  Any
thought?

  Regards,

--drkm
























	

	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com 

Re: [Gestalt-users] OUTPUT_RESOLVER_ERROR: Invalid stdout: URI

[Colin A. <col...@ho...>]

It isn't a bug.

You have specified a relative URI within href attribute of 
xsl:result-document.

This is treated as relative to the URI of the principal output destination.

This is stdout: by default, which is a gexslt-specific URI scheme that only 
has 1 valid lexical form: "stdout:".

So if you are going to use relative URIs in xsl:result-document, you must 
change the principal output destination - from the command line this can 
only be a file name - check the documentation - I think the optiion is 
called --output=<file-name>.


>From: Florent Georges <dar...@ya...>
>Reply-To: ges...@li...
>To: Gestalt ML <ges...@li...>
>Subject: [Gestalt-users] OUTPUT_RESOLVER_ERROR: Invalid stdout: URI
>Date: Wed, 27 Sep 2006 09:48:20 +0200 (CEST)
>
>   Hi
>
>   I found an other error, related to xsl:result-document.
>Here is the test case:
>
>     > cat gexslt-crash-2.xsl
>     <xsl:transform
>         xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>         version="2.0">
>
>       <xsl:template name="main">
>         <xsl:result-document href="gexslt-crash-2.xml">
>           <out/>
>         </xsl:result-document>
>       </xsl:template>
>
>     </xsl:transform>
>
>     > gexslt gexslt-crash-2.xsl --template=main
>     At line 6 in
>file://localhost/c%3A/Documents+and+Settings/Florent+Georges/My+Documents/xslt/xslt-unit/misc/gexslt-crash-2.xsl:
>     Fatal error:
>http://www.gobosoft.com/eiffel/gobo/gexslt/extension#OUTPUT_RESOLVER_ERROR:
>Invalid stdout: URI
>
>   It seems to be clearly a bug, so I guess I can open an issue?
>
>   Regards,
>
>--drkm
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>___________________________________________________________________________
>Découvrez un nouveau moyen de poser toutes vos questions quelque soit le 
>sujet !
>Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et 
>vos expériences.
>http://fr.answers.yahoo.com
>
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share 
>your
>opinions on IT & business topics through brief surveys -- and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>Gestalt-users mailing list
>Ges...@li...
>https://lists.sourceforge.net/lists/listinfo/gestalt-users

_________________________________________________________________
Windows Live™ Messenger has arrived. Click here to download it for free! 
http://imagine-msn.com/messenger/launch80/?locale=en-gb

[Gestalt-users] OUTPUT_RESOLVER_ERROR: Invalid stdout: URI

[Florent G. <dar...@ya...>]

  Hi

  I found an other error, related to xsl:result-document.
Here is the test case:

    > cat gexslt-crash-2.xsl
    <xsl:transform
        xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
        version="2.0">

      <xsl:template name="main">
        <xsl:result-document href="gexslt-crash-2.xml">
          <out/>
        </xsl:result-document>
      </xsl:template>

    </xsl:transform>

    > gexslt gexslt-crash-2.xsl --template=main
    At line 6 in
file://localhost/c%3A/Documents+and+Settings/Florent+Georges/My+Documents/xslt/xslt-unit/misc/gexslt-crash-2.xsl:
    Fatal error:
http://www.gobosoft.com/eiffel/gobo/gexslt/extension#OUTPUT_RESOLVER_ERROR:
Invalid stdout: URI

  It seems to be clearly a bug, so I guess I can open an issue?

  Regards,

--drkm
























	

	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com 

Re: [Gestalt-users] [ gestalt-Bugs-1563054]gexslt:transformation()and namespace

[Florent G. <dar...@ya...>]

Colin Adams wrote:

  Hi

> Now the question is, does the spec allow me to return true
> for my extension functions, and yet still disallow them
> within use-when?

  Good question.

  §5.4.1 makes clear extension functions have to be in the static
context.  §3.12 says what part of the static context is available in
@use-when.  In particular, the "in scope functions" contains an
"implementation-defined set of extension functions".

  But it is not clear the two set of functions have to be equal or no. 
My guess is that the set of known extension functions within @use-when
is a subset of the known extension functions in the static context, but
I think the CR is ambiguous.

  And it could maybe be a note telling: "Implementations are encouraged
to register extension functions as soon as possible".

  Regards,

--drkm






















	

	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com 

Re: [Gestalt-users] [ gestalt-Bugs-1563054]gexslt:transformation()and namespace

[Colin A. <col...@ho...>]

>From: Florent Georges <dar...@ya...>

>   But I think it is a feature, not a bug.  Or say a design
>choice: it is not possible to test the availability of a
>stylesheet function.  I guess it is to simplify
>implementations, to give them a possibility of optimization.
>
>   Because at the compile time, when the processor treat the
>@use-when, it has not already seen all stylesheet functions.
>So it'd have to perform a second pass to compile or not the
>branches depending on function-available().  But I said I
>guess; you know that better than me.

I guess you are right.

Now the question is, does the spec allow me to return true for my extension 
functions, and yet still disallow them within use-when?

It seems not.
I am going to raise this on the W3C list, to check.

_________________________________________________________________
Add fun gadgets and colorful themes to express yourself on Windows Live 
Spaces   
http://clk.atdmt.com/MSN/go/msnnkwsp0070000001msn/direct/01/?href=http://www.get.live.com/spaces/features

Re: [Gestalt-users] [ gestalt-Bugs-1563054 ]gexslt:transformation()and namespace

[Florent G. <dar...@ya...>]

Colin Adams wrote:

  Hi

> For clarity, then, let us talk only about stylesheet
> functions.  These are NOT available at use-when processing
> time.

  Yes.

> But they ARE available at run time.  So
> function-available, within a use-when attribute, should
> return true (this is what you want to know - will the
> function be available at runtime?). But the spec says
> explicitly that function-available should return false.

> this is what is wrong with the spec, in my opinion.

  But I think it is a feature, not a bug.  Or say a design
choice: it is not possible to test the availability of a
stylesheet function.  I guess it is to simplify
implementations, to give them a possibility of optimization.

  Because at the compile time, when the processor treat the
@use-when, it has not already seen all stylesheet functions.
So it'd have to perform a second pass to compile or not the
branches depending on function-available().  But I said I
guess; you know that better than me.

  Maybe I could post the question on XSL List?

  Regards,

--drkm






















	

	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com 

Re: [Gestalt-users] [ gestalt-Bugs-1563054 ]gexslt:transformation()and namespace

[Colin A. <col...@ho...>]

>From: Florent Georges <dar...@ya...>
>
> > This is required behaviour.
>
>   Do you mean function-available('gexslt:transformation') is
>required to evaluate to false when used in @use-when?  On the
>contrary, I think the intention behind §3.12 is to have such
>functions included in the static context:
>
>     - standard functions have to be in the static context;
>
>     - stylesheet functions (that is, XPath functions defined
>       by the user with the help of the xsl:function
>       instruction) must not be in the static context;
>
>     - extension functions (as gexslt:transformation() or
>       saxon:serialize()) may be in the static context.  This
>       is implementation-defined.
>
>   I think that earlier an extension function can be
>registered in the static context, better it is for
>everybody.
>
>   This is my understanding, maybe it is wrong?  I'm not sure
>that you think function-available('gexslt:transformation')
>is required to evaluate to false, but if you do so, I don't
>see how you deduce that from the CR.

Implementation-defined extension functions may be in the static context.

But if they are not (as is the case for gexslt), then the situation is the 
same for stylesheet functions.

For clarity, then, let us talk only about stylesheet functions.
These are NOT available at use-when processing time.

But they ARE available at run time.
So function-available, within a use-when attribute, should return true (this 
is what you want to know - will the function be available at runtime?). But 
the spec says explicitly that function-available should return false.

this is what is wrong with the spec, in my opinion.
>   Regards,
>
>--drkm
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>___________________________________________________________________________
>Découvrez un nouveau moyen de poser toutes vos questions quelque soit le 
>sujet !
>Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et 
>vos expériences.
>http://fr.answers.yahoo.com
>
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share 
>your
>opinions on IT & business topics through brief surveys -- and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>Gestalt-users mailing list
>Ges...@li...
>https://lists.sourceforge.net/lists/listinfo/gestalt-users

_________________________________________________________________
The new Windows Live Toolbar helps you guard against viruses 
http://toolbar.live.com/?mkt=en-gb

Re: [Gestalt-users] [ gestalt-Bugs-1563054 ]gexslt:transformation() and namespace bindings

[Florent G. <dar...@ya...>]

Colin Adams wrote:

  Hi

> It is absolutely correct for
> function-available(gexslt:transformation) to return false
> for use-when processing.

  Yes.

> This is required behaviour.

  Do you mean function-available('gexslt:transformation') is
required to evaluate to false when used in @use-when?  On the
contrary, I think the intention behind §3.12 is to have such
functions included in the static context:

    - standard functions have to be in the static context;

    - stylesheet functions (that is, XPath functions defined
      by the user with the help of the xsl:function
      instruction) must not be in the static context;

    - extension functions (as gexslt:transformation() or
      saxon:serialize()) may be in the static context.  This
      is implementation-defined.

  I think that earlier an extension function can be
registered in the static context, better it is for
everybody.

  This is my understanding, maybe it is wrong?  I'm not sure
that you think function-available('gexslt:transformation')
is required to evaluate to false, but if you do so, I don't
see how you deduce that from the CR.

  Regards,

--drkm



















	

	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com 

Re: [Gestalt-users] [ gestalt-Bugs-1563054 ]gexslt:transformation() and namespace bindings

[Colin A. <col...@ho...>]

It is absolutely correct for function-available(gexslt:transformation) to 
return false for use-when processing. This is required behaviour.

It is also correct for the function to be available at run time (though not 
required).

So, no bug, just a user error.

At least, I think this is the case. In XSLT 2.0 section 3.12, it says:

"In scope functions The core functions defined in [Functions and Operators], 
together with the functions element-available, function-available, and 
system-property defined in this specification, plus an 
implementation-defined set of extension functions. Note that stylesheet 
functions are not included in the context, which means that the function 
function-available will return false in respect of such functions. "

But this doesn't seem to be useful to me. function-available ought to 
indicate which functions are unavailable at runtime, for it to be useful to 
call it in a use-when attribute.
So I think this is a bug in the spec.

If you agree with this, then please raise a bug on the W3C bugzilla.

>From: Florent Georges <dar...@ya...>
>
>   <xsl:template name="main" use-when="
>       function-available('gexslt:transformation')">
>     <main available="true">
>       <xsl:sequence select="
>           gexslt:transformation('#test', doc(''))"/>
>     </main>
>   </xsl:template>
>
>   <xsl:template name="main" use-when="
>       not(function-available('gexslt:transformation'))">
>     <main available="false">
>       <xsl:sequence select="
>           gexslt:transformation('#test', doc(''))"/>
>     </main>
>   </xsl:template>
>
>the last template rule will be compiled and will run correctly.  So the
>function is available, and works fine, but seems to not be in the
>static context (as if it was registered too late in the context
>library).
>
>   HTH.  Regards,
>
>--drkm
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>___________________________________________________________________________
>Découvrez un nouveau moyen de poser toutes vos questions quelque soit le 
>sujet !
>Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et 
>vos expériences.
>http://fr.answers.yahoo.com
>
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share 
>your
>opinions on IT & business topics through brief surveys -- and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>Gestalt-users mailing list
>Ges...@li...
>https://lists.sourceforge.net/lists/listinfo/gestalt-users

_________________________________________________________________
Be the first to hear what's new at MSN - sign up to our free newsletters! 
http://www.msn.co.uk/newsletters

Re: [Gestalt-users] [ gestalt-Bugs-1563054 ] gexslt:transformation() and namespace bindings

[Florent G. <dar...@ya...>]

"SourceForge.net" wrote:

> Fixed and comitted to CVS

  Yes, it works, thanks.  But I found a strange behaviour in modifying
the use case, related to @use-when.  If you change:

  <xsl:template name="main">
    <xsl:sequence select="
        gexslt:transformation('#test', doc(''))"/>
  </xsl:template>

in:

  <xsl:template name="main" use-when="
      function-available('gexslt:transformation')">
    <main available="true">
      <xsl:sequence select="
          gexslt:transformation('#test', doc(''))"/>
    </main>
  </xsl:template>

  <xsl:template name="main" use-when="
      not(function-available('gexslt:transformation'))">
    <main available="false">
      <xsl:sequence select="
          gexslt:transformation('#test', doc(''))"/>
    </main>
  </xsl:template>

the last template rule will be compiled and will run correctly.  So the
function is available, and works fine, but seems to not be in the
static context (as if it was registered too late in the context
library).

  HTH.  Regards,

--drkm
























	

	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com 

Re: [Gestalt-users] Issue related to starts-with()

[Florent G. <dar...@ya...>]

Colin Paul Adams wrote:

  Hi Colin

> I've implemented starts-with now, so you will no longer
> need the work-round.

  Good news, thanks.  Sorry I can't help in Eiffel, even for simple
tasks :-(

  Regards,

--drkm




















	

	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com 

Re: [Gestalt-users] [ gestalt-Bugs-1563047 ] Gexslt crash

[Florent G. <dar...@ya...>]

"SourceForge.net" wrote:

  Hi Colin

> I've found the source of the error (the difficult bit), and
> fixed it.

  Sorry for the delay, but I had some problem while updating my Gobo
working copy.  I found a modified version of the original use-case
still makes Gexslt crash.

  I reopened the issue on the SF tracker.

  I attach the original complete styelsheet and input (in case you'll
want to test them while fixing the simplified case).

  I guess we'll have to wait you'll come back from China.

  Have a good trip,

--drkm























	

	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com 

Re: [Gestalt-users] Issue related to starts-with()

[Colin P. A. <co...@co...>]

>>>>> "Florent" == Florent Georges <dar...@ya...> writes:

    Florent>   Hi I just found the following issue.  It seems (from
    Florent> the error message) that the implementation for
    Florent> starts-with() is simply not completely written yet.  But
    Florent> just in case...:

    >> cat gexslt-starts-with.xsl
    Florent>     <xsl:transform
    Florent> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    Florent> version="2.0">

    Florent>       <xsl:template name="main"> <res> <xsl:value-of
    Florent> select=" starts-with('Une phrase.', 'Une')"/> </res>
    Florent> </xsl:template>

    Florent>     </xsl:transform>

    >> gexslt gexslt-starts-with.xsl --template=main
    Florent>     TODO: {XM_XPATH_STARTS_WITH}.evaluate-item needs to
    Florent> be written <?xml version="1.0" encoding="UTF-8"?><res/>

I've implemented starts-with now, so you will no longer need the work-round.
-- 
Colin Adams
Preston Lancashire

Re: [Gestalt-users] Copied elements loose the namespace part of theirname

[Florent G. <dar...@ya...>]

Colin Paul Adams wrote:

> >>>>> "Florent" == Florent Georges writes:

>     Florent>   I'm not sure to understand what is the current
>     Florent> behaviour.  You first said "I still have a namespace
>     Florent> declaration being omitted for the xsl prefix", then you
>     Florent> seem to suggest that this declaration is serialised.

> hm. a typo for emitted.

  Ok, a subtle typo :-).  So I think we are in agreement.

  Regards,

--drkm























	

	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com 

Re: [Gestalt-users] Copied elements loose the namespace part of theirname

[Colin P. A. <co...@co...>]

>>>>> "Florent" == Florent Georges <dar...@ya...> writes:

    Florent> Colin Paul Adams wrote: Hi Colin


    Florent>   I'm not sure to understand what is the current
    Florent> behaviour.  You first said "I still have a namespace
    Florent> declaration being omitted for the xsl prefix", then you
    Florent> seem to suggest that this declaration is serialised.

hm. a typo for emitted.

    Florent>   So I don't know what Gexslt is doing now, but I think
    Florent> §11.1.4 makes clear the declaration has to be in the
    Florent> serialised output:

    Florent>     When a literal result element is processed, its
    Florent> namespace nodes are handled as follows:

    Florent>     * A namespace node whose string value is a literal
    Florent> namespace URI is not copied to the result tree.

    Florent>     * A namespace node whose string value is a target
    Florent> namespace URI is copied to the result tree, whether or
    Florent> not the URI identifies an excluded namespace.

    >> If you think otherwise, try raising a bug report against Saxon,
    >> and see what MHK says.

    Florent>   I tried with Saxon, and it outputs the declaration, so
    Florent> I guess Gexslt do so.  If it does, I think it is the
    Florent> mandatory behaviour.

    Florent>   Thanks for the fix,

As usual, I shall be comitting fixes Sunday evening or Monday morning.
-- 
Colin Adams
Preston Lancashire

Re: [Gestalt-users] Copied elements loose the namespace part of theirname

[Florent G. <dar...@ya...>]

Colin Paul Adams wrote:

  Hi Colin

> >>>>> "Colin" == Colin Paul Adams <co...@co...> writes:

>     Colin> The fix is trivial (it only took a few minutes
>     Colin> debugging to find the cause of the principal
>     Colin> error).  Although I still have a namespace
>     Colin> declaration being omitted for the xsl prefix.
>     Colin> Not sure why - that may be a seperate bug.  --

> I note that Saxon does the same thing.

> We are both using the same logic - If a namespace
> declaration is excluded, and is not the target of a
> xsl:namespace-alias declaration, then remove it from the
> list of namespaces to be output on the element.

> It is the latter clause that causes a declaration for the
> xsl namespace to be output.

> As far as I can see, this is in strict accordance with the
> spec.

  I'm not sure to understand what is the current behaviour.
You first said "I still have a namespace declaration being
omitted for the xsl prefix", then you seem to suggest that
this declaration is serialised.

  So I don't know what Gexslt is doing now, but I think
§11.1.4 makes clear the declaration has to be in the
serialised output:

    When a literal result element is processed, its
    namespace nodes are handled as follows:

    * A namespace node whose string value is a literal
      namespace URI is not copied to the result tree.

    * A namespace node whose string value is a target
      namespace URI is copied to the result tree, whether or
      not the URI identifies an excluded namespace.

> If you think otherwise, try raising a bug report against
> Saxon, and see what MHK says.

  I tried with Saxon, and it outputs the declaration, so I
guess Gexslt do so.  If it does, I think it is the mandatory
behaviour.

  Thanks for the fix,

--drkm

























	

	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com 

Re: [Gestalt-users] Copied elements loose the namespace part of theirname

[Colin P. A. <co...@co...>]

>>>>> "Colin" == Colin Paul Adams <co...@co...> writes:

    Colin> The fix is trivial (it only took a few minutes debugging to
    Colin> find the cause of the principal error).  Although I still
    Colin> have a namespace declaration being omitted for the xsl
    Colin> prefix.  Not sure why - that may be a seperate bug.  --

I note that Saxon does the same thing.

We are both using the same logic - If a namespace declaration is
excluded, and is not the target of a xsl:namespace-alias declaration,
then remove it from the list of namespaces to be output on the
element.

It is the latter clause that causes a declaration for the xsl
namespace to be output.

As far as I can see, this is in strict accordance with the spec.

If you think otherwise, try raising a bug report against Saxon, and
see what MHK says.
-- 
Colin Adams
Preston Lancashire

Re: [Gestalt-users] Copied elements loose the namespace part of theirname

[Colin P. A. <co...@co...>]

The fix is trivial (it only took a few minutes debugging to find the
cause of the principal error).
Although I still have a namespace declaration being omitted for the
xsl prefix.
Not sure why - that may be a seperate bug.
-- 
Colin Adams
Preston Lancashire

Re: [Gestalt-users] Gexslt crash

[Florent G. <dar...@ya...>]

Colin Adams wrote:

> Your welcome to make use of the tracker.

  Ok, filled in there:

   
https://sourceforge.net/tracker/index.php?func=detail&aid=1563047&group_id=124274&atid=699086

  It will be easier for you to keep track of the bugs after your trip
;-).

  Enjoy,

--drkm






















	

	
		
___________________________________________________________________________ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. 
http://fr.answers.yahoo.com