xslt-process-users

xslt-process and saxon 6.5

[Benjamin P. <bp...@ze...>]

Hi,

is there a way to get xslt-process to work with anything else than saxon 
6.3? Well, apart from the debugger, everything is ok, but then that's 
what's great about xslt-process ;-)

To be more detailed: saxon 6.3, which is supplied with xslt-process ahs 
a show-stopper bug for me. It will return true on a test for a 
non-existant attribute.

I have dropped in saxon 6.5 by simply changing the classpath list in 
xslt-process.el (and of course placed the jar file in the java dir).

(defvar xslt-process-external-java-libraries
   (mapcar (lambda (f)
	    (concat (xslt-process-find-xslt-data-directory)
		      "java" xslt-process-dir-separator f))
	  '("bsf.jar" "xerces.jar" "xalan-2.1.0.jar" "saxon-6.5.jar"
	    "xalanj1compat.jar" "batik.jar" "fop-0.20.1.jar"
	    "jimi-1.0.jar" "xslt.jar"))
   "Defines the classpath to the XSLT processors thyat do the real work
of processing an XML document. Be sure you know what you're doing when
you modify this.")

The debugger will then produce the following stack trace:

java.lang.NoClassDefFoundError: com/icl/saxon/om/ElementInfo
	at 
xslt.debugger.saxon.SaxonTraceListener.leaveNode(SaxonTraceListener.java:184)
	at xslt.debugger.saxon.SaxonTraceListener.leave(SaxonTraceListener.java:302)
	at com.icl.saxon.style.XSLStyleSheet.process(XSLStyleSheet.java:624)
	at com.icl.saxon.Controller.transformDocument(Controller.java:1065)
	at com.icl.saxon.Controller.transform(Controller.java:939)
	at xslt.debugger.AbstractXSLTDebugger.run(AbstractXSLTDebugger.java:188)
	at java.lang.Thread.run(Thread.java:484)


Any help is appreciated.

Cheers,
Ben

Re: psgml and xslt-process

[Ovidiu P. <ov...@xe...>]

Christian,

There is also a problem with PSGML if you set it up in XML mode. To
solve that add the following to your .emacs:

(defadvice xml-mode (after run-xml-mode-hooks act)
                   "Invoke `xml-mode-hook' hooks in the XML mode."
                   (run-hooks 'xml-mode-hook))

Best regards,
Ovidiu

P.S. I will be off until next Monday, please be patient if you don't
see any reply from me.

--=20
Ovidiu Predescu <ov...@cu...>
http://orion.nsr.hp.com/ (inside HP's firewall only)
http://sourceforge.net/users/ovidiu/ (my SourceForge page)
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other s=
tuff)


On Thu, 22 Nov 2001 10:24:00 +0100, "Kaiser Christian (SV SC RS T33)" <Ch=
ris...@at...> wrote:

> Sorry for the stupid question,
>=20
> it is in deed my fault. I have had activated the
> debug mode.
>=20
> I should make it a habit to read the manual befor
> starting to work, i'm really sorry :-)
>=20
> best regards,
>=20
> (-:hris
>=20
>=20
> > -----Original Message-----
> > From: Kaiser Christian (SV SC RS T33)=20
> > Sent: Donnerstag, 22. November 2001 09:23
> > To: 'xsl...@li...'
> > Subject: psgml and xslt-process
> >=20
> >=20
> >=20
> > Here is what i have included in my .emacs:
> >  <<docbook.el>>=20
> >=20
> > regards
> >=20
> > Christian Kaiser    =20
> >=20
> > SiemensVDO Automotive AG                            =20
> > SV SC RS T33                               =20
> > Osterhofener Stra=DFe 19 - O19
> > 93055 Regensburg
> > Germany
> >=20
> > Tel: ++49 (0)941-790-6689
> >=20
> >=20

RE: psgml and xslt-process

[Kaiser C. (SV SC RS T33) <Chr...@at...>]

Sorry for the stupid question,

it is in deed my fault. I have had activated the
debug mode.

I should make it a habit to read the manual befor
starting to work, i'm really sorry :-)

best regards,

(-:hris


> -----Original Message-----
> From: Kaiser Christian (SV SC RS T33)=20
> Sent: Donnerstag, 22. November 2001 09:23
> To: 'xsl...@li...'
> Subject: psgml and xslt-process
>=20
>=20
>=20
> Here is what i have included in my .emacs:
>  <<docbook.el>>=20
>=20
> regards
>=20
> Christian Kaiser    =20
>=20
> SiemensVDO Automotive AG                            =20
> SV SC RS T33                               =20
> Osterhofener Stra=DFe 19 - O19
> 93055 Regensburg
> Germany
>=20
> Tel: ++49 (0)941-790-6689
>=20
>=20

psgml and xslt-process

[Kaiser C. (SV SC RS T33) <Chr...@at...>]

Here is what i have included in my .emacs:
 <<docbook.el>>=20

regards

Christian Kaiser    =20

SiemensVDO Automotive AG                            =20
SV SC RS T33                               =20
Osterhofener Stra=DFe 19 - O19
93055 Regensburg
Germany

Tel: ++49 (0)941-790-6689

read-only buffer

[Kaiser C. (SV SC RS T33) <Chr...@at...>]

Hello Ovidiu,

just one more question:

I use the PSGML mode and XML DocBook with your XSLT-process.

Why is it not possible to edit any buffer?
I'm quite sure it's just a matter of adjustment, i might have missed
something?


My PSGML xml mode looks like this:

;; ----- load xml-mode -----
;; this derives a XML mode from PSGML

(setq auto-mode-alist
        (append (list (cons "\\.xml\\'" 'xml-mode))
                auto-mode-alist))
(autoload 'xml-mode "psgml" nil t)


and i had to change following section,
because the XML DTDs appared to be
problematic using sgml-mode:

(setq auto-mode-alist
      (union '(("\\.xml$" . xml-mode)
	       ("\\.xsl$" . xml-mode)
	       ) auto-mode-alist))

but supposedly this has nothing to do with the=20
read-only problem.

best regards,

Christian Kaiser    =20

SiemensVDO Automotive AG                            =20
SV SC RS T33                               =20
Osterhofener Stra=DFe 19 - O19
93055 Regensburg
Germany

Tel: ++49 (0)941-790-6689

Re: Speedbar 0.11

[Ovidiu P. <ov...@xe...>]

Christian,

I've created a ready-to-go distribution of XSLT-process at

http://sourceforge.net/project/showfiles.php?group_id=23425

Please get the version you're interested in, and install it in your
home directory. Be careful that your ~/.emacs file may be overwritten,
so if you have one, make a copy of it before.

Please let me know if this works for you.

Thanks,
Ovidiu

On Tue, 20 Nov 2001 18:20:58 +0100, "Kaiser Christian (SV SC RS T33)" <Chr...@at...> wrote:

> Hi Ovidiu,
> 
> oh, I'm sorry, yes it's NTEmacs
> 
> GNU Emacs 20.5.1 (i386-*-nt4.0.1381) of Sun Dec 26 1999 on WSAMD400
> 
> Thank you very much for your trouble,
> I'm looking forward to the precompiled version,
> 
> best regards,
> 
> (-:hris
> 
> 
> > -----Original Message-----
> > From: Ovidiu Predescu [mailto:ov...@xe...]
> > Sent: Dienstag, 20. November 2001 17:49
> > To: Kaiser Christian (SV SC RS T33)
> > Cc: 'Ovidiu Predescu'
> > Subject: Re: Speedbar 0.11 
> > 
> > 
> > Christian,
> > 
> > Could you please tell me what emacs version are you using? Is it
> > XEmacs or NTEmacs? From the logs you sent it appears you're running
> > NTEmacs. Can you tell me what version?
> > 
> > I'll try to come up with a precompiled version of the files and put
> > them on the Web site.
> > 
> > Thanks,
> > Ovidiu
> > 
> > On Tue, 20 Nov 2001 15:44:13 +0100, "Kaiser Christian (SV SC 
> > RS T33)" <Chr...@at...> wrote:
> > 
> > > Thank you for the response Ovidiu,
> > > 
> > > but I'm afraid it still doesn't work.
> > > 
> > > I've done what you wrote, but there was a chain of problems
> > > resulting.
> > > Since I usually do not use CygWin, i had to adapt the
> > > paths within the makefile, at least within elips makefile.
> > > 
> > > 
> > > I would really be glad to get a compiled version including
> > > speedbar and elib. It would be great.
> > > I terribly sorry not to have time left for solving this
> > > problem, and i admit i don't have the insight which would
> > > be necessary.
> > > 
> > > Here is some output:
> > > 
> > > 
> > > 
> > > while executing makefile of ELIB:
> > > 
> > > nt_admin@RBGV72001061D ~/site-lisp/elib-1.0
> > > $ make
> > > emacs -batch -l elib-compile-all.el -f compile-elib
> > > Byte-compiling stack-f.el...
> > > Wrote d:/progs/emacs/site-lisp/elib-1.0/stack-f.elc
> > > Byte-compiling stack-m.el...
> > > Wrote d:/progs/emacs/site-lisp/elib-1.0/stack-m.elc
> > > Byte-compiling queue-f.el...
> > > Wrote d:/progs/emacs/site-lisp/elib-1.0/queue-f.elc
> > > Byte-compiling queue-m.el...
> > > Wrote d:/progs/emacs/site-lisp/elib-1.0/queue-m.elc
> > > Byte-compiling elib-node.el...
> > > Wrote d:/progs/emacs/site-lisp/elib-1.0/elib-node.elc
> > > Byte-compiling dll.el...
> > > Wrote d:/progs/emacs/site-lisp/elib-1.0/dll.elc
> > > Byte-compiling dll-debug.el...
> > > Wrote d:/progs/emacs/site-lisp/elib-1.0/dll-debug.elc
> > > Byte-compiling bintree.el...
> > > While compiling the end of the data in file
> > > d:/progs/emacs/site-lisp/elib-1.0/bi
> > > ntree.el:
> > >   ** The following functions are not known to be defined:
> > >     elib-stack-create, elib-stack-push, elib-stack-pop
> > > Wrote d:/progs/emacs/site-lisp/elib-1.0/bintree.elc
> > > Byte-compiling avltree.el...
> > > While compiling the end of the data in file
> > > d:/progs/emacs/site-lisp/elib-1.0/av
> > > ltree.el:
> > >   ** The following functions are not known to be defined:
> > >     elib-stack-create, elib-stack-push, elib-stack-pop
> > > Wrote d:/progs/emacs/site-lisp/elib-1.0/avltree.elc
> > > Byte-compiling cookie.el...
> > > While compiling elib-refresh-tin in file
> > > d:/progs/emacs/site-lisp/elib-1.0/cooki
> > > e.el:
> > >   ** reference to free variable dll
> > > Wrote d:/progs/emacs/site-lisp/elib-1.0/cookie.elc
> > > Byte-compiling string.el...
> > > While compiling elib-string-expand-newtext in file
> > > d:/progs/emacs/site-lisp/elib
> > > -1.0/string.el:
> > >   ** reference to free variable newtext
> > >   ** reference to free variable string
> > > Wrote d:/progs/emacs/site-lisp/elib-1.0/string.elc
> > > Byte-compiling read.el...
> > > Wrote d:/progs/emacs/site-lisp/elib-1.0/read.elc
> > > 
> > > 
> > > 
> > > while executing makefile of speedbar:
> > > 
> > > nt_admin@RBGV72001061D ~/site-lisp/speedbar-0.13a
> > > $ make
> > > emacs -batch -l speedbar-compile-script -f 
> > batch-byte-compile dframe.el
> > > speedbar
> > > .el
> > > While compiling dframe-frame-mode in file
> > > d:/progs/emacs/site-lisp/speedbar-0.13
> > > a/dframe.el:
> > >   ** reference to free variable x-pointer-top-left-arrow
> > >   ** reference to free variable x-pointer-hand2
> > > While compiling dframe-emacs-popup-kludge:
> > >   ** mouse-major-mode-menu called with 1 argument, but requires 2
> > > While compiling the end of the data:
> > >   ** The following functions are not known to be defined:
> > >     display-graphic-p, face-height, delete-itimer, start-itimer,
> > >     event-closest-point, popup-mode-menu, misc-user-event-p,
> > >     next-event, dispatch-event, event-over-glyph-p,
> > >     event-glyph-extent, extent-end-position
> > > Wrote d:/progs/emacs/site-lisp/speedbar-0.13a/dframe.elc
> > > While compiling speedbar-current-frame in file
> > > d:/progs/emacs/site-lisp/speedbar
> > > -0.13a/speedbar.el:
> > >   ** function speedbar-current-frame defined multiple times 
> > in this file
> > > While compiling speedbar-mode:
> > >   ** assignment to free variable font-lock-keywords
> > > While compiling speedbar-set-mode-line-format:
> > >   ** reference to free variable has-modeline-p
> > > While compiling speedbar-check-vc:
> > >   ** reference to free variable ange-ftp-path-format
> > >   ** reference to free variable efs-path-regexp
> > > While compiling the end of the data:
> > >   ** The following functions are not known to be defined:
> > >     display-graphic-p, specifier-instance, set-buffer-menubar,
> > >     semantic-token-p, semantic-summerize-nonterminal,
> > >     semantic-token-name, copy-tree
> > > Wrote d:/progs/emacs/site-lisp/speedbar-0.13a/speedbar.elc
> > > Done
> > > 
> > > 
> > > 
> > > while executing makefile of XSLT-Process:
> > > 
> > > nt_admin@RBGV72001061D ~/site-lisp/xslt-process-2.1
> > > $ make
> > > for d in java etc doc; do \
> > >   (cd $d; make VERSION="2.1" all); \
> > > done
> > > make[1]: Entering directory
> > > `/cygdrive/d/progs/emacs/site-lisp/xslt-process-2.1/
> > > java'
> > > javac -classpath
> > > 'xalan-2.1.0.jar;xalanj1compat.jar;xerces.jar;bsf.jar;saxon-6.3
> > > .jar;fop-0.20.1.jar' xslt/debugger/AbstractXSLTDebugger.java
> > > xslt/debugger/Break
> > > point.java xslt/debugger/cmdline/CmdLineObserver.java
> > > xslt/debugger/cmdline/Cont
> > > roller.java xslt/debugger/cmdline/EmacsObserver.java
> > > xslt/debugger/FOPMessageLis
> > > tener.java xslt/debugger/Manager.java xslt/debugger/Observer.java
> > > xslt/debugger/
> > > saxon/SaxonSAXParserErrorHandler.java
> > > xslt/debugger/saxon/SaxonStyleFrame.java x
> > > slt/debugger/saxon/SaxonTraceListener.java
> > > xslt/debugger/saxon/SaxonType.java xs
> > > lt/debugger/saxon/SaxonValue.java 
> > xslt/debugger/saxon/SaxonVariable.java
> > > xslt/de
> > > bugger/saxon/XSLTDebugger.java 
> > xslt/debugger/SAXParserErrorHandler.java
> > > xslt/deb
> > > ugger/SourceFrame.java xslt/debugger/StyleFrame.java
> > > xslt/debugger/TrAXErrorList
> > > ener.java xslt/debugger/Type.java xslt/debugger/Utils.java
> > > xslt/debugger/Value.j
> > > ava xslt/debugger/Variable.java
> > > xslt/debugger/xalan/XalanSAXParserErrorHandler.j
> > > ava xslt/debugger/xalan/XalanTraceListener.java
> > > xslt/debugger/xalan/XSLTDebugger
> > > .java
> > > jar cf xslt.jar xslt
> > > make[1]: Leaving directory
> > > `/cygdrive/d/progs/emacs/site-lisp/xslt-process-2.1/j
> > > ava'
> > > make[1]: Entering directory
> > > `/cygdrive/d/progs/emacs/site-lisp/xslt-process-2.1/
> > > etc'
> > > make[1]: Nothing to be done for `all'.
> > > make[1]: Leaving directory
> > > `/cygdrive/d/progs/emacs/site-lisp/xslt-process-2.1/e
> > > tc'
> > > make[1]: Entering directory
> > > `/cygdrive/d/progs/emacs/site-lisp/xslt-process-2.1/
> > > doc'
> > > (scale=0.75; \
> > >  for f in apply-xslt.png assoc-stylesheet.png boolean.png
> > > menu-comparison.png nu
> > > mber.png object.png processors.png sflogo.png speedbar.png 
> > string.png
> > > tree.png t
> > > ype.png xslt-errors.png xslt-menu.png xslt-mode.png 
> > xslt-registry.png
> > > xsltd-menu
> > > .png xsltd-mode.png xsltd-stopped.png; do \
> > >   width=`identify $f | awk '{print $2}' | awk -F x '{print $1}'`; \
> > >   height=`identify $f | awk '{print $2}' | awk -F x '{print $2}'`; \
> > >   scalew=`echo $scale '*' $width | bc | awk '{printf "%d", $0}'`; \
> > >   scaleh=`echo $scale '*' $height | bc | awk '{printf "%d", $0}'`; \
> > >   var=`echo $f | sed 's/.png//g'`; \
> > >   echo "s/@image{$var}/@image{$var,${scalew}pt,${scaleh}pt}/g"; \
> > >  done) > sizes.sed
> > > identify: not found
> > > identify: not found
> > > bc: not found
> > > bc: not found
> > > identify: not found
> > > identify: not found
> > > bc: not found
> > > bc: not found
> > > identify: not found
> > > identify: not found
> > > bc: not found
> > > bc: not found
> > > identify: not found
> > > identify: not found
> > > bc: not found
> > > bc: not found
> > > identify: not found
> > > identify: not found
> > > bc: not found
> > > bc: not found
> > > identify: not found
> > > identify: not found
> > > bc: not found
> > > bc: not found
> > > identify: not found
> > > identify: not found
> > > bc: not found
> > > bc: not found
> > > identify: not found
> > > identify: not found
> > > bc: not found
> > > bc: not found
> > > identify: not found
> > > identify: not found
> > > bc: not found
> > > bc: not found
> > > make[1]: *** Deleting file `sizes.sed'
> > > identify: not found
> > > identify: not found
> > > bc: not found
> > > bc: not found
> > > identify: not found
> > > identify: not found
> > > bc: not found
> > > bc: not found
> > > make[1]: *** [sizes.sed] Interrupt
> > > make: *** [all] Interrupt
> > > 
> > > 
> > > I stopped that after a while.
> > > 
> > > 
> > > 
> > > 
> > > Best regards,
> > > 
> > > (-:hris
> > > 
> > 
> 

Re: Speedbar 0.11

[Ovidiu P. <ov...@xe...>]

Hi Christian,

Are you using NTEmacs or XEmacs? What version?

If you're using NTEmacs, you probably need to download another
package, elib. You can get this package from:

ftp://ftp.lysator.liu.se/pub/emacs/elib-1.0.tar.gz

Please place this package in the same directory where speedbar is,
like this:

emacs/
  elib-1.0/
  speedbar-0.14/

Then go to the elib-1.0 directory and compile the code. After this
compiles fine, go to the speedbar directory and compile it using the
instructions on speedbar's Web site.

I am thinking to provide an already pre-compiled package which
contains elib, speedbar and xslt-process, if you think this would be
useful.

Regards,
-- 
Ovidiu Predescu <ov...@cu...>
http://orion.rgv.hp.com/ (inside HP's firewall only)
http://sourceforge.net/users/ovidiu/ (my SourceForge page)
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)

On Mon, 19 Nov 2001 12:59:02 +0100, "Kaiser Christian (SV SC RS T33)" <Chr...@at...> wrote:

> Hello,
> 
> I have some trouble with getting xslt-process running
> 
> I've tried to start the minor mode via ...
> 
>     M-x xslt-process-mode
> 
> 
> but there is the message:
> 
>     Speedbar 0.11 or newer is required to use xslt-speedbar.
> 
> I renamed the old speedbar.el to something else.
> After i had downoaded speedbar 0.13a and 
> included the correct load-path to the new speedbar dir, the 
> problem still was the same.
> 
> I also tried to execute the makefile of the new speedbar. But 
> there was following output:
> 
> 
> nt_admin@RBGV72001061D ~/site-lisp/speedbar-0.13a
> $ make
> emacs -batch -l speedbar-compile-script -f batch-byte-compile dframe.el
> speedbar
> .el
> While compiling dframe-frame-mode in file
> d:/progs/emacs/site-lisp/speedbar-0.13
> a/dframe.el:
>   ** reference to free variable x-pointer-top-left-arrow
>   ** reference to free variable x-pointer-hand2
> While compiling dframe-emacs-popup-kludge:
>   ** mouse-major-mode-menu called with 1 argument, but requires 2
> While compiling the end of the data:
>   ** The following functions are not known to be defined:
>     display-graphic-p, face-height, delete-itimer, start-itimer,
>     event-closest-point, popup-mode-menu, misc-user-event-p,
>     next-event, dispatch-event, event-over-glyph-p,
>     event-glyph-extent, extent-end-position
> Wrote d:/progs/emacs/site-lisp/speedbar-0.13a/dframe.elc
> While compiling speedbar-current-frame in file
> d:/progs/emacs/site-lisp/speedbar
> -0.13a/speedbar.el:
>   ** function speedbar-current-frame defined multiple times in this file
> While compiling speedbar-mode:
>   ** assignment to free variable font-lock-keywords
> While compiling speedbar-set-mode-line-format:
>   ** reference to free variable has-modeline-p
> While compiling speedbar-check-vc:
>   ** reference to free variable ange-ftp-path-format
>   ** reference to free variable efs-path-regexp
> While compiling the end of the data:
>   ** The following functions are not known to be defined:
>     display-graphic-p, specifier-instance, set-buffer-menubar,
>     semantic-token-p, semantic-summerize-nonterminal,
>     semantic-token-name, copy-tree
> Wrote d:/progs/emacs/site-lisp/speedbar-0.13a/speedbar.elc
> Done
> 
> 
> and i really couldn't find out where these functions are.
> (e.g. display-graphic-p). They are not within my emacs directory.
> 
> 
> Any kind of possible solution would be highly appreciated.
> 
> 
> 
> 
> Christian Kaiser     
> 
> SiemensVDO Automotive AG                             
> SV SC RS T33                                
> Osterhofener Straße 19 - O19
> 93055 Regensburg
> Germany
> 
> Tel: ++49 (0)941-790-6689

Speedbar 0.11

[Kaiser C. (SV SC RS T33) <Chr...@at...>]

Hello,

I have some trouble with getting xslt-process running

I've tried to start the minor mode via ...

    M-x xslt-process-mode


but there is the message:

    Speedbar 0.11 or newer is required to use xslt-speedbar.

I renamed the old speedbar.el to something else.
After i had downoaded speedbar 0.13a and=20
included the correct load-path to the new speedbar dir, the=20
problem still was the same.

I also tried to execute the makefile of the new speedbar. But=20
there was following output:


nt_admin@RBGV72001061D ~/site-lisp/speedbar-0.13a
$ make
emacs -batch -l speedbar-compile-script -f batch-byte-compile dframe.el
speedbar
.el
While compiling dframe-frame-mode in file
d:/progs/emacs/site-lisp/speedbar-0.13
a/dframe.el:
  ** reference to free variable x-pointer-top-left-arrow
  ** reference to free variable x-pointer-hand2
While compiling dframe-emacs-popup-kludge:
  ** mouse-major-mode-menu called with 1 argument, but requires 2
While compiling the end of the data:
  ** The following functions are not known to be defined:
    display-graphic-p, face-height, delete-itimer, start-itimer,
    event-closest-point, popup-mode-menu, misc-user-event-p,
    next-event, dispatch-event, event-over-glyph-p,
    event-glyph-extent, extent-end-position
Wrote d:/progs/emacs/site-lisp/speedbar-0.13a/dframe.elc
While compiling speedbar-current-frame in file
d:/progs/emacs/site-lisp/speedbar
-0.13a/speedbar.el:
  ** function speedbar-current-frame defined multiple times in this =
file
While compiling speedbar-mode:
  ** assignment to free variable font-lock-keywords
While compiling speedbar-set-mode-line-format:
  ** reference to free variable has-modeline-p
While compiling speedbar-check-vc:
  ** reference to free variable ange-ftp-path-format
  ** reference to free variable efs-path-regexp
While compiling the end of the data:
  ** The following functions are not known to be defined:
    display-graphic-p, specifier-instance, set-buffer-menubar,
    semantic-token-p, semantic-summerize-nonterminal,
    semantic-token-name, copy-tree
Wrote d:/progs/emacs/site-lisp/speedbar-0.13a/speedbar.elc
Done


and i really couldn't find out where these functions are.
(e.g. display-graphic-p). They are not within my emacs directory.


Any kind of possible solution would be highly appreciated.




Christian Kaiser    =20

SiemensVDO Automotive AG                            =20
SV SC RS T33                               =20
Osterhofener Stra=DFe 19 - O19
93055 Regensburg
Germany

Tel: ++49 (0)941-790-6689

XSLT processor implemented in Emacs Lisp?

[Ovidiu P. <ov...@cu...>]

Hi,

I was lately investigating the usage of Lisp/Scheme in building Web
applications, and it dawned on me how easy is to build a fully fledged
Web/XML application using Lisp.

As a proof of this concept, I was lately toying with the idea of
implementing an XSLT processor in Lisp. If you look at XSLT, it is
nothing else than a functional language with an XML syntax. It should
be possible to take an XSLT program and generate an equivalent Lisp
program that performs the equivalent transformation.

Is there any interest in having such a pure Emacs Lisp implementation
of an XSLT processor? I can see it being very useful for doing in
editor transformations, and using normal Java/C/C++ based XSLT
processors in normal applications. It would probably be a lot easier
to have a reliable debugger when the XSLT engine is written in
Lisp. On the other hand things like extension functions in foreign
languages will be more difficult to do.

How many of you would actually need or use such a feature?

Thanks,
-- 
Ovidiu Predescu <ov...@cu...>
http://orion.rgv.hp.com/ (inside HP's firewall only)
http://sourceforge.net/users/ovidiu/ (my SourceForge page)
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)

Re: view in browser

[Ovidiu P. <ov...@xe...>]

Gerrit,

Do you have an H: drive and H:\temp directory on your machine? It
appears that the value of TEMPDIR or TMPDIR is setup to h:\temp on
your machine; you can try changing this value to an existing temporary
directory.

Greetings,
Ovidiu

On 30 Aug 2001 17:50:17 +0200, Gerrit Niestijl <g.n...@rr...> wrote:

> Hi,
> 
> I recently installed xslt-process 2.1 on xemacs (version 21.4.0 for win32) under
> Windows NT. It works fine if I view the results in a buffer, but if I want to
> view the results in a browser an error occurs with the warning:
> 
> (error/warning) Error in process filter: (error file not found
> file:h:\TEMP\xslt-process-output.html)
> 
> and no output is generated. Trying to view PDF output gives a similar warning.
> Does anyone know why this error occurs and how it can be solved?
> 
> -- 
> Met vriendelijke groet,
> Gerrit Niestijl
> Revalidatiecentrum Rijndam Adriaanstichting
> Westersingel 300, 3015 LJ Rotterdam
> Postbus 23181, 3001 KD Rotterdam
> Tel (010) 2412439
> Fax (010) 2412400
> 
> 
> _______________________________________________
> Xslt-process-users mailing list
> Xsl...@li...
> http://lists.sourceforge.net/lists/listinfo/xslt-process-users
> 

Won't display PDF

[Jeff R. <jef...@so...>]

Here are the errors I see in the *Messages* buffer:

Starting XSLT process...
Running the Xalan processor...
Starting XSLT process...done
Done invoking Xalan; no output generated.
XSLT processing finished, running FOP processor...
building formatting object tree

setting up fonts

Done invoking Xalan; no output generated.
Starting 'xslt-process-win32-open-file'  PDF viewer...
Starting PDF viewer 'xslt-process-win32-open-file'...done.

This seems to work on some XML files, but not others?

Jeff


Also,  I still can't change to Saxon.  I click on it in the menu, but
nothing happens.

NTEmacs 20.7 on Windows 2000
XSLT-Process 2.1

Re: view in browser

[Ovidiu P. <ov...@cu...>]

Gerrit,

Do you have an H: drive and H:\temp directory on your machine? It
appears that the value of TEMPDIR or TMPDIR is setup to h:\temp on
your machine; you can try changing this value to an existing temporary
directory.

Greetings,
Ovidiu

On 30 Aug 2001 17:50:17 +0200, Gerrit Niestijl <g.n...@rr...> wrote:

> Hi,
> 
> I recently installed xslt-process 2.1 on xemacs (version 21.4.0 for win32) under
> Windows NT. It works fine if I view the results in a buffer, but if I want to
> view the results in a browser an error occurs with the warning:
> 
> (error/warning) Error in process filter: (error file not found
> file:h:\TEMP\xslt-process-output.html)
> 
> and no output is generated. Trying to view PDF output gives a similar warning.
> Does anyone know why this error occurs and how it can be solved?
> 
> -- 
> Met vriendelijke groet,
> Gerrit Niestijl
> Revalidatiecentrum Rijndam Adriaanstichting
> Westersingel 300, 3015 LJ Rotterdam
> Postbus 23181, 3001 KD Rotterdam
> Tel (010) 2412439
> Fax (010) 2412400

view in browser

[Gerrit N. <g.n...@rr...>]

Hi,

I recently installed xslt-process 2.1 on xemacs (version 21.4.0 for win32) under
Windows NT. It works fine if I view the results in a buffer, but if I want to
view the results in a browser an error occurs with the warning:

(error/warning) Error in process filter: (error file not found
file:h:\TEMP\xslt-process-output.html)

and no output is generated. Trying to view PDF output gives a similar warning.
Does anyone know why this error occurs and how it can be solved?

-- 
Met vriendelijke groet,
Gerrit Niestijl
Revalidatiecentrum Rijndam Adriaanstichting
Westersingel 300, 3015 LJ Rotterdam
Postbus 23181, 3001 KD Rotterdam
Tel (010) 2412439
Fax (010) 2412400

Re: [ANNOUNCE] XSLT-process 2.1 available

[Ovidiu P. <ov...@xe...>]

On Thu, 23 Aug 2001 07:56:22 -0700, "T. V. Raman" <tv...@al...> wrote:

> I'm running xslt-process with emacspeak
> --http://emacspeak.sf.net --works pretty well for the most
> par.

Yes, I'm familiar with this one. Although I'm not a user of it, I was
quite intrigued by this technology, especially since it has been
around for such a long time.

> The one thing I noticed  is that if you turn off auto update
> of the speedbar, and then try to manually update the source
> and xsl frames dont always update correctly.

I'll take a look into this.

> Also, I'm still a bit confused about  knowing whether the
> debugger is running from the start or is somewhere in the
> middle of a run --but all in all this is a great tool!

That's a good point, there is no indication of what the background
process is doing. Since the processing in the Java background process
is asynchronous, I was thinking to add some visual clue in the
modeline to indicate what's going on. Would this be a helpful
indication in conjunction with emacspeak?

> While on the topic, have you tried csltproc as an
> alternative xslt processor on Linux-- it runs blazingly fast
> compared to either saxon or xalan.

I assume you're referring to xsltproc, the XSLT C library for Gnome; I
couldn't find anything on 'csltproc'. My tool was primarily designed
to work with Java processors that use the JAXP APIs, but nothing stops
it from working with a C/C++ implementation as well.

I looked at xsltproc, and it seems to be a fairly complete
implementation of the XSLT spec. I might add support for it in a later
release, as this requires some work for the background process that
runs the XSLT processor and debugger.

Do you know if the tool also compiles outside the Gnome environment? I
would like to have a solution that works on all the platforms, not
only on Linux/Gnome.

Thanks for the hint, though!

> Best Regards,
> --raman
> ------------------------------------------------------------
> 
> IBM Research: Human Language Technologies
> Phone:        1 (408) 927 2608
> Fax:        1 (408) 927 3012
> Email:        tv...@us...
> WWW:      http://www.cs.cornell.edu/home/raman
> PGP:          http://emacspeak.sf.net/raman.asc
> Snail:        IBM Almaden Research Center,
>               650 Harry Road
>               San Jose 95120

Best regards,
-- 
Ovidiu Predescu <ov...@cu...>
http://orion.nsr.hp.com/ (inside HP's firewall only)
http://sourceforge.net/users/ovidiu/ (my SourceForge page)
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)

Re: problem running java

[Ovidiu P. <ov...@xe...>]

Michael,

On Thu, 23 Aug 2001 14:27:21 +0200, Michael Rose <ro...@te...> wrote:

> whenever I try to invoke the XSLT processor (Saxon or Xalan) I get the 
> following error
> 
> (1) (error/warning) Error in process filter: (file-error connection failed 
> Connection refused localhost xslt results)
> 
> It's trying to open a socket somewhere, but I can't see what the problem is 
> (Xemacs 21.4.3 on MacOSX).

Emacs uses two socket connections to communicate with the Java process
it spawns off. It looks like in your case is not able to create the
socket connection.

I can't think of what could be wrong in your case. One thing might be
that localhost doesn't resolve to an IP address. Do you have an entry
for localhost in your /etc/hosts file? I'm not familiar with MacOSX,
but if it's similar with the old NeXTSTEP/OPENSTEP, where this file
was not used, you might need to run

nidump hosts

in a terminal and see what's the result. If this still doesn't work,
you might want to replace "localhost" with "127.0.0.1" in the
xslt-process-set-output-port function, in file lisp/xslt-process.el.

Greetings,
-- 
Ovidiu Predescu <ov...@cu...>
http://orion.nsr.hp.com/ (inside HP's firewall only)
http://sourceforge.net/users/ovidiu/ (my SourceForge page)
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)

problem running java

[Michael R. <ro...@te...>]

Hi,

whenever I try to invoke the XSLT processor (Saxon or Xalan) I get the 
following error

(1) (error/warning) Error in process filter: (file-error connection failed 
Connection refused localhost xslt results)

It's trying to open a socket somewhere, but I can't see what the problem is 
(Xemacs 21.4.3 on MacOSX).

ideas?

thanks

Michael

************************************************
Assoc. Prof. Michael Rose
Center for Tele-Information,    Technical University of Denmark
(45) 45 25 51 72                mailto:ro...@te...
Off the Desktop - http://converge.cti.dtu.dk/news
'and what is the use of a computer' thought Alice 'without pictures or
conversation'     with apologies to Lewis Carroll
*************************************************

Re: xslt-process-2.0 on emacs 20.3.1

[Ovidiu P. <ov...@xe...>]

Carsten,

On Mon, 30 Jul 2001 09:44:42 -0700, Ovidiu Predescu <ov...@xe...> wrote:

> > I'm trying to get xslt-process to run on emacs 20.3.1
> > (linux). Installed elib 1.0 and speedbar 0.13a, then xslt-process 2.0.
> > 
> > When opening an XML file, apparently while loading xslt-speedbar.el I
> > get the message
> > 
> >  File mode specification error: (void-variable xslt-process-boolean-type-image)
> > 
> > and xslt-process-mode is not started. Looks like there's a problem
> > defining xslt-process-boolean-type-image. When trying to start
> > xslt-process by hand, I get
> > 
> >  Symbol's value as variable is void: xslt-process-boolean-type-image
> > 
> > again in xslt-speedbar.el. 
> > 
> > Since know little about elisp, I'm not sure what's going on here. I
> > looked at the speedbar code, and found that 'defimage-speedbar' should
> > be defined as a dummy macro in sb-image.el and thus not look for an
> > image file at all. So why the 'File mode specification error'?
> 
> Actually on older versions of emacs without image support,
> defimage-speedbar should only define the variable, using the
> definition between the lines 60-67 in speedbar-0.13a/sb-image.el. I'm
> not sure why in your case this doesn't happen.
> 
> > I'm confused. Can anybody help me?
> 
> This looks like a problem with the combination between speebar 0.13a
> and your emacs version. I've tested it on emacs 20.7.1 and it seems to
> be working fine.
> 
> You may want to post a message on the speedbar forum at:
> 
> http://sourceforge.net/projects/cedet/

Did you find out what the problem was with the error message you got?

Somebody else hit the same problem, but I can't reproduce it here with
GNU Emacs or XEmacs.


Thanks,
-- 
Ovidiu Predescu <ov...@cu...>
http://orion.nsr.hp.com/ (inside HP's firewall only)
http://sourceforge.net/users/ovidiu/ (my SourceForge page)
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)

RE: Xslt-process-users digest, Vol 1 #27 - 3 msgs

[Jeff R. <jef...@so...>]

What I was referring to was in the README file:

For more information on the how to setup and use XSLT-process, please
refer to the documentation in the doc/ directory.

Jeff

-----Original Message-----
From: xsl...@li...
[mailto:xsl...@li...]On Behalf Of
xsl...@li...
Sent: Saturday, August 18, 2001 3:12 PM
To: xsl...@li...
Subject: Xslt-process-users digest, Vol 1 #27 - 3 msgs


Send Xslt-process-users mailing list submissions to
	xsl...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.sourceforge.net/lists/listinfo/xslt-process-users
or, via email, send a message with subject or body 'help' to
	xsl...@li...

You can reach the person managing the list at
	xsl...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Xslt-process-users digest..."


Today's Topics:

   1. Re: support for PDF viewing of XML documents (Ovidiu Predescu)
   2. new package with PDF support for Windows (Ovidiu Predescu)
   3. Re: new package with PDF support for Windows (Ovidiu Predescu)

--__--__--

Message: 1
From: Ovidiu Predescu <ov...@xe...>
To: "Jeff Rancier" <jef...@so...>
Cc: xsl...@li...
Subject: Re: support for PDF viewing of XML documents
Date: Fri, 17 Aug 2001 19:19:47 -0700

Jeff,

There is no file in the doc/ directory you need to
open/print. Instead, take a look in the tests/fo/ directory. You have
a greetings.xml file which is a regular XML file containing some
data. There's a greetings.xsl file, which operates on greetings.xml
and generates an XML FO file.

If you apply the XSLT processor on the XML file in the usual way, you
would get the XML FO document. But now you can choose "Apply XSLT,
view PDF" which will run the resulting XML FO document through the FOP
processor, obtain a PDF file, and pass this file to a PDF viewer.

This is the understanding of the question/request for feature you made
a while ago on this mailing list. Was I right in the approach to solve
the problem?

Regards,
Ovidiu

On Fri, 17 Aug 2001 14:11:33 -0400, "Jeff Rancier"
<jef...@so...> wrote:

> I'm anxious to try what you've done.  Silly question:  in the doc
directory,
> which file do I print?  How?
> Jeff
>
> -----Original Message-----
> From: ov...@cu... [mailto:ov...@cu...]On Behalf Of Ovidiu
> Predescu
> Sent: Friday, August 17, 2001 3:01 AM
> To: Jeff Rancier
> Cc: xsl...@li...
> Subject: support for PDF viewing of XML documents
>
>
> Jeff,
>
> I finally had some time to work on the PDF viewing support (I was
> really busy at work with a deadline on the project I work on).
>
> There is now a new menu item in the top level XSLT menu, "Apply XSLT,
> View PDF". The action applies an XSLT transformation on the input XML
> document, then calls the Apache FOP processor on it to generate a PDF
> document. After the PDF document is generated, a PDF viewer of choice
> is invoked to show the results. You can specify your favorite PDF
> viewer through customization. By default xpdf is setup, but
> AcrobatReader is another choice. If you have a different viewer than
> these two, you can still enter it in the customization.
>
> Everything you need to generate PDFs is included in the package, you
> don't need anything additional. I placed an build package at
>
>
ftp://xslt-process.sourceforge.net/pub/xslt-process/xslt-process-20010816.ta
> r.gz
>
> I have tested this on Linux, with xpdf and AcrobatReader and it works
> fine for me. I've tested with the two files in the tests/fo/
> directory, an XML and an XSLT file taken from the FOP 0.20.1
> distribution. To test, associate the XML with the XSLT file, and
> invoke C-c C-x p.
>
> The testing I've done is minimal, so please let me know if this works
> for you with some more complex files. I would also be interested in
> somebody testing this on Windows too, I will test it anyway sometime
> these days, but more testers are better than one. If everything works
> fine, I will make a new release with this functionality over the
> week-end.
>
> Regards,
> --
> Ovidiu Predescu <ov...@cu...>
> http://orion.nsr.hp.com/ (inside HP's firewall only)
> http://sourceforge.net/users/ovidiu/ (my SourceForge page)
> http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other
> stuff)
>


--__--__--

Message: 2
From: Ovidiu Predescu <ov...@xe...>
To: Jeff Rancier <jef...@so...>
Cc: xsl...@li...
Subject: new package with PDF support for Windows
Date: Fri, 17 Aug 2001 21:03:08 -0700

Hi,

Right now I'm uploading a new version that contains support for
viewing the generated PDF file on Windows as well. If you're running
on Windows, please try it out and let me know if it works for
you. I've tested this package on Win2k, with both GNU Emacs 20.7.1 and
XEmacs 21.4.3; they both work fine.

Greetings,
--
Ovidiu Predescu <ov...@cu...>
http://orion.nsr.hp.com/ (inside HP's firewall only)
http://sourceforge.net/users/ovidiu/ (my SourceForge page)
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other
stuff)


--__--__--

Message: 3
From: Ovidiu Predescu <ov...@xe...>
To: Ovidiu Predescu <ov...@xe...>
Cc: Jeff Rancier <jef...@so...>,
   xsl...@li...
Subject: Re: new package with PDF support for Windows
Date: Fri, 17 Aug 2001 21:15:23 -0700

On Fri, 17 Aug 2001 21:03:08 -0700, Ovidiu Predescu <ov...@xe...>
wrote:

> Right now I'm uploading a new version that contains support for
> viewing the generated PDF file on Windows as well. If you're running
> on Windows, please try it out and let me know if it works for
> you. I've tested this package on Win2k, with both GNU Emacs 20.7.1 and
> XEmacs 21.4.3; they both work fine.

Oops, I forgot to mention the location:

ftp://xslt-process.sourceforge.net/pub/xslt-process/xslt-process-20010817.ta
r.gz

Greetings,
--
Ovidiu Predescu <ov...@cu...>
http://orion.nsr.hp.com/ (inside HP's firewall only)
http://sourceforge.net/users/ovidiu/ (my SourceForge page)
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other
stuff)



--__--__--

_______________________________________________
Xslt-process-users mailing list
Xsl...@li...
http://lists.sourceforge.net/lists/listinfo/xslt-process-users


End of Xslt-process-users Digest

[ANNOUNCE] XSLT-process 2.1 available

[Ovidiu P. <ov...@cu...>]

What's new?
===========

This release adds few improvements to the previous release:

- the ability to process the result of an XSLT transformation through
the Apache FOP processor.

- initial integration with the DocBook-XSL project; HTML and PDF
generation and viewing from within Emacs of DocBook documents is
supported.

- support for specifying proxies and additional arguments to the
supporting Java VM.


What is it?
===========

XSLT-process is a minor mode for GNU Emacs/XEmacs which transforms it
into a powerful editor with XSLT processing and debugging
capabilities. With this mode you can:

- run an XSLT processor on the Emacs buffer you edit, and view the
results either in another Emacs buffer or in a browser.

- run an XSLT processor in debug mode and view what happens during the
XSLT transformation. You can set breakpoints, run step by step into
your stylesheet, view global and local XSLT variables and many
more. In this mode you effectively use GNU Emacs/XEmacs as an XSLT
debugger.

- when used with the DocBook-XSL package, GNU Emacs/XEmacs becomes a
powerful DocBook processing system.

Currently the Saxon and Xalan Java XSLT processors, and Apache FOP are
supported, and the mode comes out of the box configured to use them.

The package has been tested on XEmacs, versions 21.1.14 and 21.4.3,
and GNU Emacs 20.7.1, under both Linux and Windows 2000.

The package is free software and is distributed under GPL. The home
page of XSLT-process is located at:

http://xslt-process.sourceforge.net/

Enjoy,

-- 
Ovidiu Predescu <ov...@cu...>
http://orion.nsr.hp.com/ (inside HP's firewall only)
http://sourceforge.net/users/ovidiu/ (my SourceForge page)
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)

Re: new package with PDF support for Windows

[Ovidiu P. <ov...@xe...>]

On Fri, 17 Aug 2001 21:03:08 -0700, Ovidiu Predescu <ov...@xe...> wrote:

> Right now I'm uploading a new version that contains support for
> viewing the generated PDF file on Windows as well. If you're running
> on Windows, please try it out and let me know if it works for
> you. I've tested this package on Win2k, with both GNU Emacs 20.7.1 and
> XEmacs 21.4.3; they both work fine.

Oops, I forgot to mention the location:

ftp://xslt-process.sourceforge.net/pub/xslt-process/xslt-process-20010817.tar.gz

Greetings,
-- 
Ovidiu Predescu <ov...@cu...>
http://orion.nsr.hp.com/ (inside HP's firewall only)
http://sourceforge.net/users/ovidiu/ (my SourceForge page)
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)

new package with PDF support for Windows

[Ovidiu P. <ov...@xe...>]

Hi,

Right now I'm uploading a new version that contains support for
viewing the generated PDF file on Windows as well. If you're running
on Windows, please try it out and let me know if it works for
you. I've tested this package on Win2k, with both GNU Emacs 20.7.1 and
XEmacs 21.4.3; they both work fine.

Greetings,
-- 
Ovidiu Predescu <ov...@cu...>
http://orion.nsr.hp.com/ (inside HP's firewall only)
http://sourceforge.net/users/ovidiu/ (my SourceForge page)
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)

Re: support for PDF viewing of XML documents

[Ovidiu P. <ov...@xe...>]

Jeff,

There is no file in the doc/ directory you need to
open/print. Instead, take a look in the tests/fo/ directory. You have
a greetings.xml file which is a regular XML file containing some
data. There's a greetings.xsl file, which operates on greetings.xml
and generates an XML FO file.

If you apply the XSLT processor on the XML file in the usual way, you
would get the XML FO document. But now you can choose "Apply XSLT,
view PDF" which will run the resulting XML FO document through the FOP
processor, obtain a PDF file, and pass this file to a PDF viewer.

This is the understanding of the question/request for feature you made
a while ago on this mailing list. Was I right in the approach to solve
the problem?

Regards,
Ovidiu

On Fri, 17 Aug 2001 14:11:33 -0400, "Jeff Rancier" <jef...@so...> wrote:

> I'm anxious to try what you've done.  Silly question:  in the doc directory,
> which file do I print?  How?
> Jeff
> 
> -----Original Message-----
> From: ov...@cu... [mailto:ov...@cu...]On Behalf Of Ovidiu
> Predescu
> Sent: Friday, August 17, 2001 3:01 AM
> To: Jeff Rancier
> Cc: xsl...@li...
> Subject: support for PDF viewing of XML documents
> 
> 
> Jeff,
> 
> I finally had some time to work on the PDF viewing support (I was
> really busy at work with a deadline on the project I work on).
> 
> There is now a new menu item in the top level XSLT menu, "Apply XSLT,
> View PDF". The action applies an XSLT transformation on the input XML
> document, then calls the Apache FOP processor on it to generate a PDF
> document. After the PDF document is generated, a PDF viewer of choice
> is invoked to show the results. You can specify your favorite PDF
> viewer through customization. By default xpdf is setup, but
> AcrobatReader is another choice. If you have a different viewer than
> these two, you can still enter it in the customization.
> 
> Everything you need to generate PDFs is included in the package, you
> don't need anything additional. I placed an build package at
> 
> ftp://xslt-process.sourceforge.net/pub/xslt-process/xslt-process-20010816.ta
> r.gz
> 
> I have tested this on Linux, with xpdf and AcrobatReader and it works
> fine for me. I've tested with the two files in the tests/fo/
> directory, an XML and an XSLT file taken from the FOP 0.20.1
> distribution. To test, associate the XML with the XSLT file, and
> invoke C-c C-x p.
> 
> The testing I've done is minimal, so please let me know if this works
> for you with some more complex files. I would also be interested in
> somebody testing this on Windows too, I will test it anyway sometime
> these days, but more testers are better than one. If everything works
> fine, I will make a new release with this functionality over the
> week-end.
> 
> Regards,
> --
> Ovidiu Predescu <ov...@cu...>
> http://orion.nsr.hp.com/ (inside HP's firewall only)
> http://sourceforge.net/users/ovidiu/ (my SourceForge page)
> http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other
> stuff)
> 

support for PDF viewing of XML documents

[Ovidiu P. <ov...@xe...>]

Jeff,

I finally had some time to work on the PDF viewing support (I was
really busy at work with a deadline on the project I work on).

There is now a new menu item in the top level XSLT menu, "Apply XSLT,
View PDF". The action applies an XSLT transformation on the input XML
document, then calls the Apache FOP processor on it to generate a PDF
document. After the PDF document is generated, a PDF viewer of choice
is invoked to show the results. You can specify your favorite PDF
viewer through customization. By default xpdf is setup, but
AcrobatReader is another choice. If you have a different viewer than
these two, you can still enter it in the customization.

Everything you need to generate PDFs is included in the package, you
don't need anything additional. I placed an build package at

ftp://xslt-process.sourceforge.net/pub/xslt-process/xslt-process-20010816.tar.gz

I have tested this on Linux, with xpdf and AcrobatReader and it works
fine for me. I've tested with the two files in the tests/fo/
directory, an XML and an XSLT file taken from the FOP 0.20.1
distribution. To test, associate the XML with the XSLT file, and
invoke C-c C-x p.

The testing I've done is minimal, so please let me know if this works
for you with some more complex files. I would also be interested in
somebody testing this on Windows too, I will test it anyway sometime
these days, but more testers are better than one. If everything works
fine, I will make a new release with this functionality over the
week-end.

Regards,
-- 
Ovidiu Predescu <ov...@cu...>
http://orion.nsr.hp.com/ (inside HP's firewall only)
http://sourceforge.net/users/ovidiu/ (my SourceForge page)
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)

Re: XSLT-process 2.0; XSLT menu shows debug mode on startup.

[Ovidiu P. <ov...@xe...>]

Hi Eugene,

On Wed, 8 Aug 2001 17:49:06 -0400, "Eugene Gross" <eug...@em...> wrote:

> When I initially load my XML file so that xslt-process gets invoked,
> XSLT menu looks like debug mode is ON, and the read-only mode is on
> for the buffer, however the xslt-process-debug-mode variable is nil.

There must be something wrong, when you load an XML file the first
time, you should not be in debug mode. Also it should not happen that
you're in debug mode and xslt-process-debug-mode is nil.

Something is wrong with your setup or with the code somewhere, but I
don't see this behavior here on any of my machines. Could you please
send me your .emacs file?

> Being far from a lisp guru, I just moved the
> '(xslt-process-toggle-debug-mode 0)' call right after
> the if statement in xslt-process.el; that fixed the problem.
> 
>   (interactive "P")
>   (setq xslt-process-mode
> 	(if (null arg)
> 	    (not xslt-process-mode)
> 	  (> (prefix-numeric-value arg) 0)))
>   (if xslt-process-mode
>       (xslt-process-toggle-debug-mode 0)
>       ----------------------------------
>     (progn
>       (easy-menu-add xslt-process-menu)
>       (xslt-process-setup-minor-mode xslt-process-mode-map
>                                      xslt-process-mode-line-string)
>       )
>     (setq minor-mode-alist (remassoc 'xslt-process-mode minor-mode-alist))
>     (setq minor-mode-map-alist
> 	  (remassoc 'xslt-process-mode minor-mode-map-alist))
>     (easy-menu-remove '("XSLT")))
>   ;; Force modeline to redisplay
>   (force-mode-line-update))

This doesn't look like the right thing. The if statement in my
original code was setting up the mode if the value of
`xslt-process-mode' is non-nil, and disabled it otherwise. In your
code you effectively disable the debug mode, but the code doesn't
setup the menus and the rest. Moreover, on the "else" clause, your
version adds and then removes the menus, which is not a good thing.

Could you explain the intent of the change?

> PS: I'm an old NeXT veteran, too ;)

Glad to see NeXT still lives on through its users ;-) I'm dreaming of
going back to Mac OS X some time, but I'm not sure I want to shell out
quite a bit of money to buy their proprietary hardware. The OS looks
great, I'd love to see it running on PCs, as the old OpenStep did.

Greetings,
-- 
Ovidiu Predescu <ov...@cu...>
http://orion.nsr.hp.com/ (inside HP's firewall only)
http://sourceforge.net/users/ovidiu/ (my SourceForge page)
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)

XSLT-process 2.0; XSLT menu shows debug mode on startup.

[Eugene G. <eug...@em...>]

Ovidiu,

When I initially load my XML file so that xslt-process gets invoked,
XSLT menu looks like debug mode is ON, and the read-only mode is on
for the buffer, however the xslt-process-debug-mode variable is nil.

Being far from a lisp guru, I just moved the
'(xslt-process-toggle-debug-mode 0)' call right after
the if statement in xslt-process.el; that fixed the problem.

  (interactive "P")
  (setq xslt-process-mode
	(if (null arg)
	    (not xslt-process-mode)
	  (> (prefix-numeric-value arg) 0)))
  (if xslt-process-mode
      (xslt-process-toggle-debug-mode 0)
      ----------------------------------
    (progn
      (easy-menu-add xslt-process-menu)
      (xslt-process-setup-minor-mode xslt-process-mode-map
                                     xslt-process-mode-line-string)
      )
    (setq minor-mode-alist (remassoc 'xslt-process-mode minor-mode-alist))
    (setq minor-mode-map-alist
	  (remassoc 'xslt-process-mode minor-mode-map-alist))
    (easy-menu-remove '("XSLT")))
  ;; Force modeline to redisplay
  (force-mode-line-update))

---------
Eugene

PS: I'm an old NeXT veteran, too ;)


Emacs  : GNU Emacs 20.7.1 (i386-*-nt4.0.1381)
 of Tue Jun 13 2000 on buffy
Package: XSLT-process 2.0

current state:
==============
(setq
 xslt-process-breakpoints (hash table, 0 entries:)
 xslt-process-comint-process #<process xslt>
 xslt-process-comint-buffer #<buffer *xslt*>
 xslt-process-selected-position [nil nil nil nil nil nil]
 xslt-process-debugger-process-started t
 xslt-process-process-state 'not-running
 xslt-process-debugger-running nil
 xslt-process-source-frames-stack nil
 xslt-process-style-frames-stack nil
 xslt-process-local-variables nil
 xslt-process-global-variables nil
xslt-process-breakpoint-extents (hash table, 0 entries:)
xslt-process-execution-context-error-function nil
xslt-process-results-process #<process xslt results>
xslt-process-current-processor "Saxon"
xslt-process-default-processor '(Saxon)
xslt-process-external-java-libraries '("d:/usr/site-lisp/xslt-process-2.0/java\\bsf.jar" "d:/usr/site-lisp/xslt-process-2.0/java\\xerces.jar" "d:/usr/site-lisp/xslt-process-2.0/java\\xalan-2.1.0.jar" "d:/usr/site-lisp/xslt-process-2.0/java\\saxon-6.3.jar" "d:/usr/site-lisp/xslt-process-2.0/java\\xalanj1compat.jar" "d:/usr/site-lisp/xslt-process-2.0/java\\xslt.jar")
xslt-process-error-messages nil
xslt-process-registered-stylesheets '("d:/usr/dtd/docbook-xsl/html/docbook.xsl")
xslt-process-xml-xslt-associations '(("d:/home/evg/projects/evg/tech-doc/tsd/tsd.xml" . "d:/usr/dtd/docbook-xsl/html/docbook.xsl")
                                     ("d:/home/evg/projects/evg/tech-doc/tsd/test.xml" . "d:/usr/dtd/docbook-xsl/html/docbook.xsl")
                                     )
)