RE: [dev] xslt filters as extensions - swext

2009-03-31 Thread Emmanuel Bégué 
Hello Mikhail,

Thank you very much for this answer -- but I don't know
how to browse cws though?

I did find this:
http://svn.services.openoffice.org/opengrok/xref/OOO310_m5/swext/mediawiki/

which does not contain xslt files and is probably not what you
were mentionning?

Regards,
EB



 -Original Message-
 From: mikhail.voyte...@sun.com [mailto:mikhail.voyte...@sun.com]
 Sent: Tuesday, March 31, 2009 5:58 PM
 To: dev@openoffice.org
 Subject: Re: [dev] filters as extensions -- still no luck -- looking for
 one working example
 
 The new version of Sun Wiki Publisher extension in mav46 
 childworkspace does it. Actually the MediaWiki filter will no more be 
 installed as a part of OOo installation starting from OOo3.2, the 
 extension will install it. So you could try to checkout swext module 
 from this cws and investigate it.
 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

RE: [dev] xslt filters as extensions - swext

2009-03-31 Thread Emmanuel Bégué 
 -Original Message-
 From: Ariel Constenla-Haile
   The new version of Sun Wiki Publisher extension in mav46
 http://svn.services.openoffice.org/ooo/cws/mav46/

Ariel,
Much thanks for the link.

Mikhail,
This does not appear to be a filter based on XSLT?

Regards,
EB



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

[dev] RE: XSLT Export filter, result-document path

2009-03-05 Thread Emmanuel Bégué 
Hello,

In fact, the answer to this question is simply to use
the targetBaseURL parameter, which contains the full
name and path of the target file, and use the path in
result-document (after having stripped the name from
the path).

This has indirectly been already discussed before,
sorry for asking again.

Regards,
EB


 -Original Message-
 From: Emmanuel Bégué [mailto:e...@medusis.fr]
 Sent: Monday, February 23, 2009 6:34 PM
 To: dev@openoffice.org
 Subject: XSLT Export filter, result-document path
 
 
 Hello,
 
 I'm writing an export filter for Writer that needs to produce
 TWO files:
 - the transformation itself
 - a list of errors / problems found in the source document.
 
 To produce the second file I use the function xsl:result-document.
 
 When used with no path information, this function produces a
 file in the directory
   {OOo-install-dir}/program
 
 (where the end user is unlikely to go find it ;-)
 
 Of course, I would like for this file to be written in the
 same directory as the result of main transformation, which
 is chosen by the user when running the filter.
  
 Is there a way to know what this directory is from within
 the XSLT? (runtime parameter?)
 
 Thanks,
 Regards,
 EB

[dev] XSLT Export filter, result-document path

2009-02-23 Thread Emmanuel Bégué 
Hello,

I'm writing an export filter for Writer that needs to produce
TWO files:
- the transformation itself
- a list of errors / problems found in the source document.

To produce the second file I use the function xsl:result-document.

When used with no path information, this function produces a
file in the directory
{OOo-install-dir}/program

(where the end user is unlikely to go find it ;-)

Of course, I would like for this file to be written in the
same directory as the result of main transformation, which
is chosen by the user when running the filter.
 
Is there a way to know what this directory is from within
the XSLT? (runtime parameter?)

Thanks,
Regards,
EB

[dev] xml filter - result-document

2009-02-23 Thread Emmanuel Bégué 
Hello,

In an XSLT Filter using the function xsl:result-document,
the filter works fine the first time it is launched; but,
starting at the second time, it fails.

It works again (just one time) if one closes OpenOffice.org
and then restarts it.

It would seem xsl:result-document refuses to overwrite
an existing file, but it would be strange since it is
not the usual behavior of the function (outside of OOo);
and the transformation works again if OOo is restarted,
even if the target file of result-document is still there
(it then gets overwritten).

BUT, if the name of the target file for result-document
changes at every execution (by appending the time in seconds
to the filename, for example), the transformation succeeds
every time, with no need to restart OOo.

A possible explanation for this behavior would be that
XSLT files are precompiled / cached in some way, and
that every sucessive execution is in fact just one continuous
execution: then, the transformation would refuse to
write twice to the same file in the same execution.

Is this interpretation correct?

Is it possible to somehow circumvent it, for example by
resetting the compiled XSLT, or preventing precompilation
altogether?

I'm using OOo 3.0 and Saxon 9.

Regards,
EB