xslt-process-users

Re: Resolver

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

Hi Wilfred,

On 08 Apr 2002 08:13:03 +0200, wilfred springer <wil...@su...> wrote:

> I really like the tool you crafted, but I still need to do XSLT
> processing by hand, since that's the only that way I'm able to specify
> my own resolver. I'm not always on-line, and I want to be able to build
> my documents any time I like. Therefore, I need a dedicated resolver
> that maps public and system id's to local resources. I use Norman
> Walsh's resolver (http://www.sun.com/xml/developers/resolver/article/).
> The great thing about it is that it uses catalogs. I'm not an Emacs
> expert, but I guess it will not be very hard to pass the name of the
> catalog that I specified in my PSGML settings. 
> 
> What do you think?

I think this would be a great addition!

It would be great if you could add support for the resolver to the
Java part of XSLT-process, so I can focus on the Emacs integration
only. Right now I'm busy working on other projects, and I don't have
enough spare time to look at it. Please let me know if you plan to do
it.

Best regards,
-- 
Ovidiu Predescu <ov...@cu...>
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)

Xemacs XSLT menu not showing

[<he...@wk...>]

Hi all

I have searched the mailing list regarding the problem I have with the XSLT
menu not displaying in Xemacs.  Regarding Ovidiu's questions in that post

"Do you see an XSLT indicator in the modeline?"

Yes I can see an XSLT indicator in the modeline. What I actually see is:

(XSL XSLT Font)

I have loaded an XSL file but no XSLT menu appears.

TIA

Heidi

Re:Variable Display Problem

[<A.M...@sa...>]

I have found the "problem" with my xslt-process setup. Some other 
developments had caused me to add saxon.jar to my lib/ext directory. This 
was being found before the saxon-6.3.jar file in the emacs setup. The 
debugger no longer hangs.

However, the duplication of local variable values caused by the speedbar 
not updating correctly is present in the official version now. Has that 
been seen by other users, or have I got another setup problem?  At least 
my Saxon 6.5.1 changes haven't caused this :-)
Tony Addyman
----------------------------------
Eur Ing A.M.Addyman
Computer Science
School of Sciences
Newton Building
University of Salford
Salford
M5 4WT
Tel: 0161-295-5067
Fax: 0161-295-5559

Variable display problem

[<A.M...@sa...>]

1. The test files that come with xslt-process work as advertised.
2. My own stylesheets hang if there are variables or params.
3. This is with W2K and GNU Emacs 21.1.1, Speedbar 0.13 or 0.14b4, and 
Saxon 6.3
I don't think I have messed up anything with the installation, and I don't 
recall any other users mentioning similar problems. Can anyone else either
a) confirm that they have problems with variables or params in the 
debugger, or
b) confirm that they DON'T have problems with variables or params their 
own stylesheets and the debugger.

I am interested for two reasons:
1. My students are likely to be using the debugger seriously in the coming 
weeks
2. I am working on support for Saxon 6.5.1 and my code currently has a 
different problem with variable display in the debugger - the values 
display, but the speedbar is not correct unless manually updated to remove 
duplicated entries. If others have experienced problems when Saxon 6.3 is 
being used, I need to look towards Saxon; otherwise I need to look at the 
Speedbar, etc.

Thanks for any input, comments, etc.
Tony Addyman
----------------------------------
Eur Ing A.M.Addyman
Computer Science
School of Sciences
Newton Building
University of Salford
Salford
M5 4WT
Tel: 0161-295-5067
Fax: 0161-295-5559

Resolver

[wilfred s. <wil...@su...>]

Hi,

I really like the tool you crafted, but I still need to do XSLT
processing by hand, since that's the only that way I'm able to specify
my own resolver. I'm not always on-line, and I want to be able to build
my documents any time I like. Therefore, I need a dedicated resolver
that maps public and system id's to local resources. I use Norman
Walsh's resolver (http://www.sun.com/xml/developers/resolver/article/).
The great thing about it is that it uses catalogs. I'm not an Emacs
expert, but I guess it will not be very hard to pass the name of the
catalog that I specified in my PSGML settings. 

What do you think?

Cheers,

Wilfred



-- 
Wilfred Springer
Java Consultant - Sun Java Center
Sun Microsystems Nederland BV
Tel: +31 (0)6 2295 7321
E-mail: wil...@su...

Re: caching imported stylesheet?

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

Hi Pepe,

On Thu, 21 Mar 2002 11:55:55 -0800, "Pepe Kubon" <pe...@re...> wrote:

> Hi:
> 
> I have a following problem - I'm running a transformation in 2 modes,
> each in a separate stylesheet. The 1st stylesheet imports the
> 2nd. 
> 
> If I make changes in the 2nd stylesheet and run it independently,
> the result reflects the changes. But if I run the 1st stylesheet
> that imports the 2nd, those same changes don't seem to have any effect.
> 
> Finally, if I kill Emacs and load the files again and then run the 1st
> stylesheet, the changes are applied.
> 
> I'm wondering if xslt-process is caching the imported stylesheet
> for better performance and doesn't notice that the file was
> changed. Can I force reloading if that's the case?

Yes indeed, XSLT-process caches the stylesheet for performance reasons
(running DocBook would be just a pain without this!).

To get the correct behavior when imported stylesheets are being used,
it would have to check for them. Unfortunately, the JAXP API doesn't
have any provision for this, and doing it at the processor layer is
very cumbersome and non-portable.

I'll think of an Emacs-based solution, something that looks for
imports in a stylesheet, and builds a dependency graph to be able to
correctly detect a modified imported stylesheet. If you see a better
solution please let me know.

In the meantime, you don't have to kill Emacs, just kill the *xslt*
buffer, or even better, touch the master stylesheet by saving it as
well.

Regards,
-- 
Ovidiu Predescu <ov...@cu...>
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)

caching imported stylesheet?

[Pepe K. <pe...@re...>]

Hi:

I have a following problem - I'm running a transformation in 2 modes,
each in a separate stylesheet. The 1st stylesheet imports the
2nd. 

If I make changes in the 2nd stylesheet and run it independently,
the result reflects the changes. But if I run the 1st stylesheet
that imports the 2nd, those same changes don't seem to have any effect.

Finally, if I kill Emacs and load the files again and then run the 1st
stylesheet, the changes are applied.

I'm wondering if xslt-process is caching the imported stylesheet
for better performance and doesn't notice that the file was
changed. Can I force reloading if that's the case?

Thanks a lot,

Pepe

Re: Version

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

On Mon, 25 Feb 2002 08:53:01 -0800, aq...@da... wrote:

> Hi Ovidiu,
> Thanks for your reply. I installed XSLT Process 2.1 and added 
> following to my init.el.
> Now I get the XSLT Menu on the top. But I lost the font-lock for .el 
> files.

Hm, this should not have happened. Are you sure you didn't do anything
else that might have caused this?

> Also it does not syntax highlight any of the xslt buffers. Do I 
> have to do anything special to get syntax highlight for XSL files?

Have you tried to fontify the buffer after it's been created? Try
running M-x font-lock-mode on the XSLT buffer.

If this works, you may want to add something like:

(add-hook 'xml-mode-hook (lambda () (font-lock-mode 1)))

I assume you're using the PSGML mode to display the XSLT file. If
you're using xslide, you may need to add the lambda function to hook
for xslide (sorry, but I don't know what that is).

> Is there no way of finding out the version of individual package in 
> XEmacs?

Usually packages have a variable <mode-name>-version. This is only a
convention, so you may find packages that don't respect it. The safest
bet is to look in the source code of the package directly, and try to
identify the version from there.

Regards,
Ovidiu

Re: Version

[<aq...@da...>]

Hi Ovidiu,
Thanks for your reply. I installed XSLT Process 2.1 and added 
following to my init.el.
Now I get the XSLT Menu on the top. But I lost the font-lock for .el 
files. Also it does not syntax highlight any of the xslt buffers. Do I 
have to do anything special to get syntax highlight for XSL files?
Is there no way of finding out the version of individual package in 
XEmacs?
I appriciate your help.

Anup!!

;;XEmacs Version 21.4 patch 6
;; Added following to init.el 

(require 'cl)

(defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version))

; Turn on font lock
(if running-xemacs
(setq font-lock-auto-fontify t)
(global-font-lock-mode))

;; Set syntax coloring for PSGML
(setq-default sgml-set-face t)

(pushnew (expand-file-name 
"~/Progra~1/XEmacs/xemacs-packages/xslt-process-2.1/lisp") load-path)

(add-hook 'sgml-mode-hook 'xslt-process-mode)
(add-hook 'xml-mode-hook 'xslt-process-mode)

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

(require 'xslt-process)

(setq auto-mode-alist
(union '(("\\.html$" . html-mode)
	       ("\\.shtml$" . html-mode)
	       ("\\.xml$" . sgml-mode)
	       ("\\.xsl$" . sgml-mode)
	       ("\\.xmap$" . sgml-mode)
	       ("\\.xconf$" . sgml-mode)
	       ) auto-mode-alist))


---------Included Message----------
>Date: Fri, 22 Feb 2002 13:44:08 -0800
>From: "Ovidiu Predescu" <ov...@xe...>
>Reply-To: "Ovidiu Predescu" <ov...@xe...>
>To: <aq...@da...>
>Cc: <xsl...@li...>
>Subject: Re: Version 
>
>Hi,
>
>If you installed the latest sumo package for XEmacs, then you probably
>got XSLT-process version 1.2.1, which is very old.
>
>I'd suggest you to install the 2.1 version and see if that works for
>you with the setup described on the Web site.
>
>Regards,
>Ovidiu
>
>On Fri, 22 Feb 2002 11:17:21 -0800, aq...@da... wrote:
>
>> Hi
>> I just got the XEmacs Version 21.4 (patch 6), I have the following 
>> questions:
>> 1) How do I find out which version of xslt-process came with Xemacs. 
(is 
>> there any command/variable which I can look at?)
>> 2) I copied the settings from 
>> http://xslt-process.sourceforge.net/setup.php to install/run xslt 
mode. 
>> But I do not get the syntax highligting and menu items for XSLT mode. 
I 
>> do see XSLT minor mode getting invoked though..
>> I'd appriciate any co-operation in this regard.
>> Thanks
>> Anup!!
>
---------End of Included Message----------
_____________________________________________________________

Re: Version

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

Hi,

If you installed the latest sumo package for XEmacs, then you probably
got XSLT-process version 1.2.1, which is very old.

I'd suggest you to install the 2.1 version and see if that works for
you with the setup described on the Web site.

Regards,
Ovidiu

On Fri, 22 Feb 2002 11:17:21 -0800, aq...@da... wrote:

> Hi
> I just got the XEmacs Version 21.4 (patch 6), I have the following 
> questions:
> 1) How do I find out which version of xslt-process came with Xemacs. (is 
> there any command/variable which I can look at?)
> 2) I copied the settings from 
> http://xslt-process.sourceforge.net/setup.php to install/run xslt mode. 
> But I do not get the syntax highligting and menu items for XSLT mode. I 
> do see XSLT minor mode getting invoked though..
> I'd appriciate any co-operation in this regard.
> Thanks
> Anup!!

Version

[<aq...@da...>]

Hi
I just got the XEmacs Version 21.4 (patch 6), I have the following 
questions:
1) How do I find out which version of xslt-process came with Xemacs. (is 
there any command/variable which I can look at?)
2) I copied the settings from 
http://xslt-process.sourceforge.net/setup.php to install/run xslt mode. 
But I do not get the syntax highligting and menu items for XSLT mode. I 
do see XSLT minor mode getting invoked though..
I'd appriciate any co-operation in this regard.
Thanks
Anup!!
_____________________________________________________________

Y O U Can Too ! Fire your boss NOW !! (7778clvg2-253FrYU4@17)

[<cas...@ao...>]

DQpZIE8gVSBSICBsYXN0IGNoYW5jZSBmb3IgDQoNClkgTyBVIFIgJDMwMDAu
MDAgSU5DT01FIHBlciBXRUVLIQ0KDQoNCkdpdmUgTWUgNSBNaW51dGVzLCBB
bmQgSSdsbCBTaG93IFlvdQ0KSG93IFRvIEZsb29kIFlvdXIgQmFuayBBY2Nv
dW50IFdpdGggU2VyaW91cyBDYXNoLA0KIA0KRElEIFlPVSBNQUtFICQxMiww
MDAgTEFTVCBNT05USA0KSUYgTk9ULCBZT1UgTkVFRCBUTyBKT0lOIFVTIFRP
REFZIQ0KDQotIEZSRUUgVHVybmtleSBNYXJrZXRpbmcgU3lzdGVtIChhICQy
NTAwIFZhbHVlKQ0KLSBGUkVFIFJlYWR5LXRvLVVzZSAiT3JkZXItUHVsbGlu
ZyIgQWRzICYgU2FsZXMgTGV0dGVycw0KLSBFYXJuICQxLDAwMCBDQVNIIG9u
IEVhY2ggYW5kIEV2ZXJ5IFNhbGUgdG8gSW5maW5pdHkhDQotIFdvcmsgRnJv
bSBIb21lIGFuZCBMaXZlIHRoZSAiMS1NaW51dGUiIENvbW11dGUNCi0gUGx1
ZyBJbnRvIE91ciBEdXBsaWNhdGUtYWJsZSAzLVN0ZXAgU3VjY2VzcyBTeXN0
ZW0NCi0gWU9VIHJlY2VpdmUgRlVMTCBsaXZlIFNVUFBPUlQhIEZvciBmcmVl
IQ0KLSBTZWN1cmUgWW91ciBGaW5hbmNpYWwgRnJlZWRvbSBTdGFydGluZyBU
b2RheQ0KLSBCdXkgWW91ciBEcmVhbSBIb3VzZSBhbmQgRHJlYW0gQ2FyISAN
Ci0gQW1hemluZyBTdXBwb3J0IFN5c3RlbSBndWFyYW50ZWVzIFlPVSB0byBT
VUNDRUVEIQ0KLSBFVkVSWUJPRFkgaXMgYSBQcm9zcGVjdCAtIDEwMCUgQ2Fz
aCBNYWNoaW5lICENCi0gRVZFUllCT0RZIGNhbiBkbyBpdCENCg0KTk8gaHlw
ZSAhIEFsbCBsZWdhbCAhDQpJIHdpbGwgZXZlbiBmYXggeW91IG15IEJBTksg
U1RBVEVNRU5UIHRvIHByb3ZlIGl0IQ0KDQogDQpQUk9HUkFNIGF2YWlsYWJs
ZSBpbiBVUyBhbmQgQ2FuYWRhIE9OTFkgIQ0KDQoNClJlcXVlc3QgbW9yZSBm
cmVlIGluZm8gTk9XISANCnNlbmQgYW4gZW1haWwgdG86ICAgICAgZ2VydW5u
aW5nbWVAeWFob28uY29tICANCg0Kd2l0aCAiU0VORCBJTkZPIiBpbiB0aGUg
c3ViamVjdCBsaW5lISENCihkbyBOT1QgY2xpY2sgUkVQTFkhKQ0KDQoNCg0K
DQpUbyByZW1vdmUsIHBsZWFzZSBzZW5kIGFuIGVtYWlsIHdpdGggIlJFTU9W
RSIgDQppbiB0aGUgc3ViamVjdCBsaW5lIHRvOiAgZ2VydW5uaW5nbWVAeWFo
b28uY29tIA0KWzUwODhtc2dWMy02ODhLcEd0NTY1OUxiR28zLTE4MlFCdVow
NTE4eWpvRDUtMjE1WVZnaTIyMTVQUkxhOC01NjhWeVJZMjg2Mmd2Z2IxLTI5
MU5DQDc4XQ0K

Re: standalone stylesheet

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

On Sun, 10 Feb 2002 15:14:33 -0800, "John Menke" <jo...@ea...> wrote:

> I have some "standalone stylesheets" that have both the xml and xsl content
> included in the xsl sheet.  Can I get xslt-process-mode to parse these?

Unfortunately, no :-) XSLT-process assumes you have the XML document
and stylesheet as separate files.

Regards,
Ovidiu

standalone stylesheet

[John M. <jo...@ea...>]

I have some "standalone stylesheets" that have both the xml and xsl content
included in the xsl sheet.  Can I get xslt-process-mode to parse these?

-john

xslt menu not appearing in Xemacs install on Win2000

[John M. <jo...@ea...>]

I have installed XEmacs on Win2000 with the included XSLT-process-mode
package.  I can M-x xslt-process-mode and it shows "XSLT" in the status bar
so I think the package is loaded... I don't get any error, just no toolbar.

Has anyone had the same problems?

-john

How to get xsl-process work

[Massimo I. <mi...@al...>]

I have recentry installed XEmacs 21.4 on Windows 2000 and  I am=20
very interested to xsl-process bat it seems that I'am not able to get it =
work.
The version of xsl-process that I found with XEmas by default is
the 1.2.1 and, typing C-C, C-X, C-V in a buffer with an xml inside it =
says:=20
"Could not process file, most probably Saxon could not be found"

I have also downloaded the version 2.1 already precompiled fo XEmacs,
they said, but i have not understood how install it - yes i read te docs =

but it seem to much difficult for me ;) when uncompressed the package=20
i do not know where to put the files in the directory system of XEmacs
(i suppose that lisp, java, and doc directories fit different sites).

Please help me, the package seems very interesting, powerfull and=20
concrete like many others under Emacs.

And I am very sorry for my orrible english :(=20

Re: More FO drivers

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

On Tue, 08 Jan 2002 09:06:17 -0800, Ovidiu Predescu <ov...@xe...> wrote:

> Hi,
> 
> On Tue, 08 Jan 2002 14:05:36 +0100, "Greger Sernemar" <gre...@ho...> wrote:
> 
> > Is there any plans to implement FO drivers ?
> > For example one or several of the following:
> > 
> > XEP
> > http://www.renderx.com/FO2PDF.html
> > 
> > XSL Formatter from Antenna House
> > http://www.antennahouse.com/xslformatter.html
> > 
> > Unicorn Formatting Objects (UFO)
> > http://www.unicorn-enterprises.com/
> 
> There is little incentive for a free software developer to support
> commercial packages, unless free versions are provided by the
> developer, and they add sufficient value to the package to be worth

  ^^^^^^^^^

Sorry, I guess I was confusing here. I meant the developer of the
comercial package.

> spending the time developing them.

Greetings,
Ovidiu

Re: More FO drivers

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

Hi,

On Tue, 08 Jan 2002 14:05:36 +0100, "Greger Sernemar" <gre...@ho...> wrote:

> Is there any plans to implement FO drivers ?
> For example one or several of the following:
> 
> XEP
> http://www.renderx.com/FO2PDF.html
> 
> XSL Formatter from Antenna House
> http://www.antennahouse.com/xslformatter.html
> 
> Unicorn Formatting Objects (UFO)
> http://www.unicorn-enterprises.com/

There is little incentive for a free software developer to support
commercial packages, unless free versions are provided by the
developer, and they add sufficient value to the package to be worth
spending the time developing them.

However, if you have time to develop drivers for them, I can
incorporate them in the official releases.

> PassiveTeX
> http://users.ox.ac.uk/~rahtz/passivetex/

This is an excellent package! However PassiveTeX uses plain TeX to do
the processing, so you can use normal Emacs packages for TeX
processing to use PassiveTeX. XSLT-process is of no help here.

> REXP
> http://www.esng.dibe.unige.it/REXP

Sorry, I'm not familiar with this project, and I don't use it. As I
said, I'm willing to incorporate changes to support them, if you
provide them.

Best 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)

More FO drivers

[Greger S. <gre...@ho...>]

Is there any plans to implement FO drivers ?
For example one or several of the following:

XEP
http://www.renderx.com/FO2PDF.html

XSL Formatter from Antenna House
http://www.antennahouse.com/xslformatter.html

Unicorn Formatting Objects (UFO)
http://www.unicorn-enterprises.com/

PassiveTeX
http://users.ox.ac.uk/~rahtz/passivetex/

REXP
http://www.esng.dibe.unige.it/REXP

Regards,
Greger


_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx

xslt-process: Debugger ignoring breakpoints

[<A.M...@sa...>]

I, too, couldn't get breakpoints to work on my examples. I am using Win2K 
and Emacs 21.1.
Your test5 worked! My examples worked in your test directory, and your 
test5 didn't work in my examples directory.
Then I noticed something: one of the steps on the path to my folder has a 
space in the name, i.e. Teaching\XML Development\Examples. When I renamed 
the XML Development to XMLDevelopment (no space) the breakpoints are now 
effective.

Hope this helps other users. I don't know if the problem is Java or el 
related.
Tony Addyman
----------------------------------
Eur Ing A.M.Addyman
Computer Science
School of Sciences
Newton Building
University of Salford
Salford
M5 4WT
Tel: 0161-295-5067
Fax: 0161-295-5559

Re: debugger ignores breakpoints / psgml starts in read only (debugger) mode

[Patrick D. <pd...@gm...>]

Hello Ovidiu,

> > Any ideas why XSLT-process is not stopping at my breakpoints?
> 
> Are you sure the breakpoints are reached? You can try playing
> with the test5.xml and test5.xsl from the distribution and 
> see if it works.

It workes now. 

The problem was that either emacs or XSLT-process does not like spaces in
path names. Is this reproducable for you as well? I put my files into the
directory "c:\xml". After that it worked perfect! The former path name was 
"D:\Dokumente und Einstellungen\Administrator\Eigene Dateien". 
This is a standard "home" directory for the user "Administrator" on a 
german Windows XP or Windows 2000 installation.

> There's a bug in the xml mode of PSGML. Add the following in
> 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))

I have this in my .emacs already. Maybe I put it at the wrong position? I
attached my .emacs to this mail. Maybe you can spot the error. 
But this is not really important. 
The debugger is the feature a newby like me really needs :-)

> I haven't tested on emacs 21.1.1, and I have no experience
> with it. It would help knowing whether test5.{xml,xsl} work on it.

It works great as long as there are no spaces in path names.

Best regards,

Patrick

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net

Re: debugger ignores breakpoints / psgml starts in read only (debugger) mode

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

On Thu, 13 Dec 2001 00:43:44 +0100 (MET), Patrick Dehne <pd...@gm...> wrote:

> Hello,
> 
> I am trying to setup XSLT-process 2.1 under emacs 21.1.1 running on Windows
> XP. I have discovered two problems:
> 
> 1.
> When I try to run Saxon on the current buffer everything works, XSLT-process
> processes the xml file and the xsl file and shows the resulting output in
> the *xslt results* buffer. If I try to use the debugger my breakpoints are
> ignored and XSLT-process simply does exactly the same as described above. It does
> not stop at any breakpoint. I try to start the debugger like this:
> - I load the xml file and xsl file
> - I toggle the buffer with the xsl file into debug mode
> - I set a few breakpoints in the xsl file with the "b" command.
> - I switch into the buffer with the xml file
> - I toggle this buffer into debug mode
> - I start the debugger with the "r" command.
> Any ideas why XSLT-process is not stopping at my breakpoints?

Are you sure the breakpoints are reached? You can try playing with the
test5.xml and test5.xsl from the distribution and see if it works.

> 2.  I have another problem when using psgml 1.2.3 for xml
> editing. After opening a xml file, the buffer is read-only and the
> XSLT-process menu is in "debugger-mode". The modeline still shows
> XSLT though, not XSLTd. If I am using the standard xml (sgml) mode
> that is coming with emacs the behavior is ok, so it must be a
> problem with psgml and XSLT-process. I have seen Eugene Gross
> describing the same problem on this mailing list in a mail from
> 08/08/2001 but there was no resolution posted.

There's a bug in the xml mode of PSGML. Add the following in 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))

> XSLT-process is a very good tool despite these problems, but with xslt
> debugging working it would be really great!

I haven't tested on emacs 21.1.1, and I have no experience with it. It
would help knowing whether test5.{xml,xsl} work on it.

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)

debugger ignores breakpoints / psgml starts in read only (debugger) mode

[Patrick D. <pd...@gm...>]

Hello,

I am trying to setup XSLT-process 2.1 under emacs 21.1.1 running on Windows
XP. I have discovered two problems:

1.
When I try to run Saxon on the current buffer everything works, XSLT-process
processes the xml file and the xsl file and shows the resulting output in
the *xslt results* buffer. If I try to use the debugger my breakpoints are
ignored and XSLT-process simply does exactly the same as described above. It does
not stop at any breakpoint. I try to start the debugger like this:
- I load the xml file and xsl file
- I toggle the buffer with the xsl file into debug mode
- I set a few breakpoints in the xsl file with the "b" command.
- I switch into the buffer with the xml file
- I toggle this buffer into debug mode
- I start the debugger with the "r" command.
Any ideas why XSLT-process is not stopping at my breakpoints?

2.
I have another problem when using psgml 1.2.3 for xml editing. After opening
a xml file, the buffer is read-only and the XSLT-process menu is in
"debugger-mode". The modeline still shows XSLT though, not XSLTd. If I am using the
standard xml (sgml) mode that is coming with emacs the behavior is ok, so it
must be a problem with psgml and XSLT-process. I have seen Eugene Gross
describing the same problem on this mailing list in a mail from 08/08/2001 but
there was no resolution posted.

XSLT-process is a very good tool despite these problems, but with xslt
debugging working it would be really great!

Patrick

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net

(no subject)

[xiangw <xi...@an...>]

Re: xslt-process and saxon 6.5

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

Hi Ben,

Unfortunately Saxon's internal APIs keep changing quite often, with no
backward compatibility. Which is OK, as a normal program is not
supposed to use those low-level, processor specific, APIs, but instead
use the JAXP API. However XSLT-process is no usual program, and relies
on very intimate details of the processor. When these change, the code
breaks or doesn't work anymore.

I noticed the problem starting with 6.4, but didn't have time to
investigate more. Any suggestion of what has changed is welcome. Of
course, a patch would really be great ;-)

Regards,
Ovidiu

On Tue, 04 Dec 2001 09:43:44 +0100, Benjamin Peter <bp...@ze...> wrote:

> 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
> 
> 
> _______________________________________________
> Xslt-process-users mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xslt-process-users
>