xslt-process-users

problem with caracteres speciaux

[abbouh <ab...@ra...>]

i use in my FS:

<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="text" version="1.0" encoding="ISO-8859-1"
indent="yes" />
----------
---------
<xsl:value-of select="./para"/>
--------

and in my xml file un have:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE dicodoc PUBLIC "-//ALCATEL//DICODOC 2.0//EN"
 "dicodoc.dtd">
--------
<para>...G&eacute;n&eacute;ralit&eacute;s</para>
------

and in the output file  i have:
...G n ralit s

so the character &eacute; isn't translated.
so which encoding i should have for output,stylsheet,or what the problem

generating a set of output files

[abbouh <ab...@ra...>]

hello,
i want  to creat other output documents in addition to the main output
document
i know that with the xt process ,we use
<xt:document href="{$file}">
------------
-----------
</xt:document>
but with xalan process i have no idea,
thanks.

F I N A L N-O-T-I-C-E! - it's time to respond! 2917e-5

[<dzz...@ho...>]

Li4uIFRoYXQncyBpdCENCg0KVElSRUQgb2YgY2hhc2luZyBwZW9wbGUgdGhh
dCB5b3UgbGlrZSB0byBzZWxsIHlvdXIgc3R1ZmY/DQpTRUxMSU5HIGhhcyBi
ZWNvbWUgc28gbXVjaCBlYXNpZXIhDQpKT0lOIG5vdyBhbmQgeW91IHdpbGwg
TkVWRVIgaGF2ZSB0byBjYWxsIHBlb3BsZSANCmluIG9yZGVyIHRvIHNlbGwg
eW91ciBwcm9kdWN0IG9yIG9wcG9ydHVuaXR5IQ0KDQpGSVJTVCB0aW1lIGlu
IEhJU1RPUlkhDQoNCkhFUkUgcmVhZHkgdG8gam9pbiBwZW9wbGUgQUxXQVlT
IENBTEwgVVMgRklSU1QhDQoNCk5PIGNvbGQgY2FsbGluZw0KTk8gc2VsbGlu
ZyANCk5PIGh1bnRpbmcgZm9yIHByb3NwZWN0cw0KMTAwJSBBdXRvbWF0aW9u
DQpFVkVSWUJPRFkgY2FuIGRvIHRoaXMhDQoNCi4uLndlIGhhdmUgcHJvdmVu
IGl0IG1vcmUgdGhhbiA5MDAwIHRpbWVzIHdpdGhpbiA0IG1vbnRocyENCg0K
QVJFIHlvdSBmaW5hbGx5IFJFQURZIHRvIHJlY2VpdmUgJDM1MDAgY2hlY2tz
IHZpYSBBaXJib3JuZSwgRmVkRXggYW5kIFVQUz8NCg0KDQoNCmFzayBmb3Ig
TU9SRSBJTkZPIGFuZCBzZW5kIHVzIGFuIGVtYWlsIHRvIA0KQnJhZFN1bW1p
dEB0YWxrMjEuY29tDQp3aXRoIFNFTkQgRlJFRSBJTkZPIFBBQ0tBR0UgaW4g
dGhlIFN1YmplY3QgTGluZS4NCg0KUGxlYXNlIGFsc28gTElTVCB5b3VyIFBI
T05FIE5VTUJFUiANCnNvIEkgY2FuIGdpdmUgeW91IGEgcXVpY2sgZm9sbG93
IHVwIGFuZCANCllPVSBjY2FuIGZpbmQgb3V0IHRoYXQgSSBBTSBSRUFMLCB0
b28hDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCi4uLnRvIGJlIHJlbW92
ZWQgZnJvbSBmdXJ0aGVyIG1haWxpbmdzIA0KanVzdCBzZW5kIGFuIGVtYWls
IHRvICAgDQpCcmFkU3VtbWl0QHRhbGsyMS5jb20NCndpdGggUkVNT1ZFIGlu
IHRoZSBzdWJqZWN0IGxpbmUuDQoNCg0KRE8gIE4gTyBUICBDTElDSyBSRVBM
WSEhDQoNCg0KOTQ4MW5LbWgwLTA2NEpkdFY0MzA1cWJ0bTItNzE5ekFRUTM2
MTFkdndFOS0wMjFKSnRSMDY2NkhEa2IwLTgzOGlWbEMyNjg1UkFibDctMzQ0
c2w3Nw==

-- YES, YOU want it all - YOU get it all! VZ

[<ha...@ho...>]

Hi,
Would you like to make an extra $5000. 
per month PART TIME with a success guarantee? 
OR
min. $12,000. per month full time? 
I will show you my bank statement,
after 4 months running this CASH Opportunity 
I am making $30,000 per single month!
JOIN the fastest growing group TODAY!
YOU keep 100% of ALL CASH !

If you have good work ethics and a strong desire to
increase your net worth significantly so you can
PAY OFF YOUR DEBTS within a few weeks!
This Opportunity made it happen for me overnight!


WIN-WIN is our formula for YOUR SUCCESS! 

SPECIAL available LIMITED TIME ONLY! 


Request your F R E E  I N F O R M A T I O N  TODAY! 
Send an email to:                  Fra...@ro...
with        "GIVE INFO NOW"      in the SUBJECT LINE 
Please also LIST your  PHONE NUMBER  in the email
so I can give you a quick follow up and 
YOU can FIND OUT that I am  REAL !

(D o  N O T  click R E P L Y to this email!)





















.. or use the same email address to ask for REMOVAL in the subject line

Re: Disappearing forward slash from files paths

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

Hi George,

Thanks for catching this, I've committed a fix in the repository. You  
can get the new version of xslt-process.el from here:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/xslt-process/ 
xslt-process/lisp/xslt-process.el?rev=HEAD&content-type=text/plain

The fix involved calling 'urlize' on the value of the filename to be  
set to xslt-process-output-to-filename.

Please let me know if this fixes your problem.

Best regards,
Ovidiu

On Sunday, Apr 20, 2003, at 20:11 US/Pacific, George Spelvin wrote:

> Hi,
>
> On W2K, XEmacs 21.4 patch 11, xslt-process2.2,
> Xalan2.4:
>
> The file name that gets written out to the temp dir
> when invoking view in browser, loses all slashes from
> its path, and therefore gets written to the same
> directory as the source XML file, but with a long name
> essentially comprising a whole path without slashes.
> For example: ~/WINNTTEMPXslt-process-output
>
> I hardly know any Lisp, but from mucking around in
> xslt-process.el urlize function, any other character
> besides / was inserted successfully into the string.
> But / simply vanishes from the temp-dir variable which
> tells me there's another regex involved.
>
> My workaround so far is to hard code the file path in
> two places: in xslt-process-do-run, where I set the
> file to "/Xslt-process-out.html", and also in
> xslt-process-invoke-browser-view to the same value.
> Otherwise the file to process will be both named
> incorrectly, and browse-url will not find the file in
> its expected location (and it would still be misnamed
> even in the right location).
>
> For reference, my TEMP var is simply c:\WINNT\TEMP. I
> tried variations on it as c:/WINNT/TEMP, tried other
> directories etc. Under the root dir, there's just no
> extra path so both xalan and browse URL can get to it
> (if I know how to work with variables in Lisp, I'd do
> it better)
>
> I'd be happy to provide more details if necessary.
>
> Advice greatly appreciated.
>
-- 
Ovidiu Predescu <ov...@ap...>
http://www.google.com/search?btnI=&q=ovidiu (I'm feeling lucky)

Disappearing forward slash from files paths

[George S. <g_s...@ya...>]

Hi,

On W2K, XEmacs 21.4 patch 11, xslt-process2.2,
Xalan2.4:

The file name that gets written out to the temp dir
when invoking view in browser, loses all slashes from
its path, and therefore gets written to the same
directory as the source XML file, but with a long name
essentially comprising a whole path without slashes.
For example: ~/WINNTTEMPXslt-process-output

I hardly know any Lisp, but from mucking around in
xslt-process.el urlize function, any other character
besides / was inserted successfully into the string.
But / simply vanishes from the temp-dir variable which
tells me there's another regex involved.

My workaround so far is to hard code the file path in
two places: in xslt-process-do-run, where I set the
file to "/Xslt-process-out.html", and also in
xslt-process-invoke-browser-view to the same value.
Otherwise the file to process will be both named
incorrectly, and browse-url will not find the file in
its expected location (and it would still be misnamed
even in the right location).

For reference, my TEMP var is simply c:\WINNT\TEMP. I
tried variations on it as c:/WINNT/TEMP, tried other
directories etc. Under the root dir, there's just no
extra path so both xalan and browse URL can get to it
(if I know how to work with variables in Lisp, I'd do
it better)

I'd be happy to provide more details if necessary.

Advice greatly appreciated.

__________________________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com

NO HYPE at all ! Voted BEST income Opportunity in the USA ! TYV

[<dl...@ho...>]

TIRED of chasing down people that you like to sell your stuff?
SELLING has become so much easier!
JOIN now and you will NEVER have to call people 
in order to sell your product or opportunity!

FIRST time in HISTORY!

HERE Ready-to-join-People ALWAYS CALL US FIRST!

NO cold calling
NO selling 
NO hunting for prospects
100% A U T O M A T I O N
EVERYBODY can do this!

..we have proven it more than 9000 times within 4 months!

ARE you finally READY to receive $3500 Money Orders via Airborne, FedEx and UPS?



ask for MORE INFO and send us an email to 
Fra...@ta...
with SEND FREE INFO PACKAGE in the Subject Line.



























to be removed from further mailings just send an email to   Fra...@ta...    with REMOVE in the subject line.

-Are You Ready For Serious Cash? UUAETSRS

[<ai...@ho...>]

-- Are you Asking for MORE in your LIFE?
Many great People have proven that today
EVERYTHING is POSSIBLE.

What does it need to be successful over night?
It takes YOUR WILL and POWER to BELIEVE... the rest we provide for you.

We will help you succeed and fulfill your dreams quickly!
I didn't believe it myself, but had no choice...
before filing bankruptcy I just gave this opportunity and my life a last shot!

I received $7000 my first month and I was a slow starter compared to others
but I have managed averaging $20,000 monthly income 
after running for little over than 3 months
I was never in sales, had no exerience, I was shy like a child
If I can do it, 
EVERYBODY can do it!


Interested HOW to make that much money staying HOME?
STOP dreaming, 
CHECK it out NOW!


Ask for "THE CASH WEBSITE" now!
Send an email to:       Pau...@ta...
with  "THE CASH WEBSITE"  in the SUBJECT LINE 
(D o  N O T  click R E P L Y!)








to UNSUBSCRIBE please send an email to   Pau...@ta...    with REMOVE in the subject line

(±¤°í) »ê¼Ò¹æ µé¾î º¸¼Ì³ª¿ä?

[<ev...@ko...>]

<html>
<head>
<title>Mail for potential customers</title>
<body> 
세상에 이런 제품도 있습니다.<br>
산소발생기 들어 보셨나요?<br>
병원 응급실에서만 사용되었던 그 값비산 산소가 <br>
여러분의 안방침실, 아이방, 부모님방, 업소 , 사무실<br>
어떻한 공간에도 설치가능 합니다.<br>
<br>
직장인 단체구입 환영합니다.   080-580-0202<br>
콜센타 단체구입 환영합니다.   02-725-9316~7<br>
※ 고농도 산소 80%   저농도 산소35% 두가지가 있습니다.<br>
http://www.0202.co.kr    ev...@ko...<br>
<br>
수신거부<br>
<br>
<br>
 <br>
<br>

</body></html>

Re: transformation problems

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

It works fine for me on MacOS X.

One thing you might want to do is check the paths. I've spotted for  
example in your stylesheet definition you have a dockbook.dsl instead  
of docbook.xsl.

Also the DOCTYPE definition should include a reference to the DTD file,  
something like this:

<!DOCTYPE article
	  PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
	  "file:/Users/ovidiu/Desktop/docbook-xml-4.2/docbookx.dtd">

Please let me know if you still have problems.

Ovidiu

On Friday, Mar 7, 2003, at 12:15 US/Pacific, Ed Stuart wrote:

> Hi,
>
> I'm using XSLT 2.2 in XEmacs 21.4 (patch 6) that is running on a  
> Wintel box.
> I am able to create a small DocBook document using the XML-Mode (it  
> can find
> the DTD) and successfully validate the document, but when I execute
> 'xslt-process-invoke-buffer-view' using the Saxon 6.5.2 processon my  
> XML
> document:
>
> 	<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN">
> 	<?xml-stylesheet type="text/xsl"
> href="file://E:/Users/Local/Lib/XML/DocBook/docbook-xsl-1.60.1/html/ 
> docbook.
> dsl"?>
> 	<article>
> 	<articleinfo>
> 	<title>Unit Test: <!--FIXME-->
> 	</title>
> 	<releaseinfo role="CVS">$Id: template.xml,v 1.2 2002/01/18 21:06:45  
> nwalsh
> Exp $</releaseinfo>
> 	<author><firstname>Ed</firstname><surname>Stuart</surname>
>
> <affiliation><address><email>blah@blah</email></address></affiliation>
> 	</author>
> 	</articleinfo>
> 	  <para>Hi!</para>
> 	</article>
>
> the *SGML LOG* indicates that the DTD and the associated entity has  
> been
> found
>
> 	  catalog: e:\users\local\lib\XML\SuperCatalog exists
> 	  catalog: e:\users\local\lib\XML\docbook\docbkx412\docbook.cat exists
> 	Start looking for dtd entity ARTICLE public -//OASIS//DTD DocBook XML
> V4.1.2//EN// system nil
> 	  catalog: e:\users\local\lib\XML\SuperCatalog exists
> 	  catalog: e:\users\local\lib\XML\docbook\docbkx412\docbook.cat exists
> 	  >> e:\users\local\lib\XML\docbook\docbkx412\docbookx.dtd [by pubid]
>
> however, the *xslt errors* buffer contains the returned error message:
>
> 	cd
>
> 	E:/Docs/DOCbook/docbook-testdocs-1.1/tests/template.xml:2:63: Fatal  
> error:
> whitespace required (found ">")
>
> Any ideas here?
>
> Thanks,
> Ed Stuart
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Etnus, makers of TotalView, The  
> debugger
> for complex code. Debugging C/C++ programs can leave you feeling lost  
> and
> disoriented. TotalView can help you find your way. Available on major  
> UNIX
> and Linux platforms. Try it free. www.etnus.com
> _______________________________________________
> Xslt-process-users mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xslt-process-users
>

transformation problems

[Ed S. <es...@sg...>]

Hi,

I'm using XSLT 2.2 in XEmacs 21.4 (patch 6) that is running on a Wintel box.
I am able to create a small DocBook document using the XML-Mode (it can find
the DTD) and successfully validate the document, but when I execute
'xslt-process-invoke-buffer-view' using the Saxon 6.5.2 processon my XML
document:

	<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN">
	<?xml-stylesheet type="text/xsl"
href="file://E:/Users/Local/Lib/XML/DocBook/docbook-xsl-1.60.1/html/docbook.
dsl"?>
	<article>
	<articleinfo>
	<title>Unit Test: <!--FIXME-->
	</title>
	<releaseinfo role="CVS">$Id: template.xml,v 1.2 2002/01/18 21:06:45 nwalsh
Exp $</releaseinfo>
	<author><firstname>Ed</firstname><surname>Stuart</surname>

<affiliation><address><email>blah@blah</email></address></affiliation>
	</author>
	</articleinfo>
	  <para>Hi!</para>
	</article>

the *SGML LOG* indicates that the DTD and the associated entity has been
found

	  catalog: e:\users\local\lib\XML\SuperCatalog exists
	  catalog: e:\users\local\lib\XML\docbook\docbkx412\docbook.cat exists
	Start looking for dtd entity ARTICLE public -//OASIS//DTD DocBook XML
V4.1.2//EN// system nil
	  catalog: e:\users\local\lib\XML\SuperCatalog exists
	  catalog: e:\users\local\lib\XML\docbook\docbkx412\docbook.cat exists
	  >> e:\users\local\lib\XML\docbook\docbkx412\docbookx.dtd [by pubid]

however, the *xslt errors* buffer contains the returned error message:

	cd

	E:/Docs/DOCbook/docbook-testdocs-1.1/tests/template.xml:2:63: Fatal error:
whitespace required (found ">")

Any ideas here?

Thanks,
Ed Stuart

re: Xemacs associciate XSLT with XML buffer path problem

[Marty K. <mar...@ya...>]

I've had the best luck when I open the xml file and
stylesheet using full windows paths, like C-x C-f
c:/cygwin/home/me/doc.xml RET, not C-x C-f ~/doc.xml
RET, and insuring that when you set the association
the same full paths are used.

I'm using an earlier version of xslt-process, cygwin
native xemacs, and windows version of java.  I think
this is a difficult configuration to make work, since
xemacs thinks it is on unix, and generates unix paths,
while java expects windows paths.  I've had to do some
tinkering with the lisp code to get paths correct in
some cases.  From your post it looks like cygwin
support might have been beefed up in 2.2.  I'm going
to go give 2.2 a wirl.

Heidi Brannan wrote:
>Hi there
> 
> I am using Xemacs v 21.4 on Windows 2000 withCygwin.
 I am trying to 
> associate an XML doc with a stylesheet but Xemacs
returns an error as the path created is incorrect.
> 
> The error I find in the *XSLT* buffer is


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

Re: xslt-process make failed on cygwin - missing identify

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

This is part of the ImageMagick package. You don't necessarily need it,  
it's used to generate the documentation only.

The package you download should be ready to use, just follow the  
installation instructions.

Regards,
Ovidiu

On Wednesday, Feb 5, 2003, at 08:23 US/Pacific, Marty Kube wrote:

> The make for xslt-process-2.2 is failing for me on
> cygwin.  I seem to be missing "identify".  Any
> suggestions on where to locate this for cygwin?
>
> <tmp> uname -a
> CYGWIN_NT-5.0 MARTY-PC 1.3.19(0.71/3/2) 2003-01-23
> 21:31 i686 unknown unknown Cygwin
> <tmp> tar -xvf xslt-process-2.2.tar
> xslt-process-2.2/
> xslt-process-2.2/bin/
> ....
> <tmp> cd xslt-process-2.2
> <xslt-process-2.2> make
> for d in java etc doc; do \
>   (cd $d; make VERSION="2.2" all); \
> done
> make[1]: Entering directory
> `/tmp/xslt-process-2.2/java'
> javac -classpath
> '.;saxon-6.5.2.jar;xml- 
> apis.jar;xalan.jar;xercesImpl.jar;bsf.jar;batik.jar;jimi- 
> 1.0.jar;fop.jar;avalon-framework-cvs-20020315.jar'
> xslt/debugger/AbstractXSLTDebugger.java
> xslt/debugger/Breakpoint.java
> xslt/debugger/cmdline/CmdLineObserver.java
> xslt/debugger/cmdline/Controller.java
> xslt/debugger/cmdline/EmacsObserver.java
> xslt/debugger/FOPLogger.java
> xslt/debugger/FOPMessageListener.java
> xslt/debugger/Manager.java xslt/debugger/Observer.java
> xslt/debugger/saxon/SaxonSAXParserErrorHandler.java
> xslt/debugger/saxon/SaxonStyleFrame.java
> xslt/debugger/saxon/SaxonTraceListener.java
> xslt/debugger/saxon/SaxonType.java
> xslt/debugger/saxon/SaxonValue.java
> xslt/debugger/saxon/SaxonVariable.java
> xslt/debugger/saxon/XSLTDebugger.java
> xslt/debugger/SAXParserErrorHandler.java
> xslt/debugger/SourceFrame.java
> xslt/debugger/StyleFrame.java
> xslt/debugger/TrAXErrorListener.java
> xslt/debugger/Type.java xslt/debugger/Utils.java
> xslt/debugger/Value.java xslt/debugger/Variable.java
> xslt/debugger/xalan/XalanSAXParserErrorHandler.java
> xslt/debugger/xalan/XalanStyleFrame.java
> xslt/debugger/xalan/XalanTraceListener.java
> xslt/debugger/xalan/XalanType.java
> xslt/debugger/xalan/XalanValue.java
> xslt/debugger/xalan/XalanVariable.java
> xslt/debugger/xalan/XSLTDebugger.java
> jar cf xslt.jar xslt
> make[1]: Leaving directory
> `/tmp/xslt-process-2.2/java'
> make[1]: Entering directory
> `/tmp/xslt-process-2.2/etc'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/tmp/xslt-process-2.2/etc'
> make[1]: Entering directory
> `/tmp/xslt-process-2.2/doc'
> (scale=0.75; \
>  for f in apply-xslt.png assoc-stylesheet.png
> boolean.png menu-comparison.png number.png object.png
> processors.png sflogo.png speedbar.png string.png
> tree.png type.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 $3}' | awk -F x
> '{print $1}'`; \
>   height=`identify $f | awk '{print $3}' | 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
>
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Xslt-process-users mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xslt-process-users
>

xslt-process make failed on cygwin - missing identify

[Marty K. <mar...@ya...>]

The make for xslt-process-2.2 is failing for me on
cygwin.  I seem to be missing "identify".  Any
suggestions on where to locate this for cygwin?

<tmp> uname -a
CYGWIN_NT-5.0 MARTY-PC 1.3.19(0.71/3/2) 2003-01-23
21:31 i686 unknown unknown Cygwin
<tmp> tar -xvf xslt-process-2.2.tar 
xslt-process-2.2/
xslt-process-2.2/bin/
....
<tmp> cd xslt-process-2.2
<xslt-process-2.2> make
for d in java etc doc; do \
  (cd $d; make VERSION="2.2" all); \
done
make[1]: Entering directory
`/tmp/xslt-process-2.2/java'
javac -classpath
'.;saxon-6.5.2.jar;xml-apis.jar;xalan.jar;xercesImpl.jar;bsf.jar;batik.jar;jimi-1.0.jar;fop.jar;avalon-framework-cvs-20020315.jar'
xslt/debugger/AbstractXSLTDebugger.java
xslt/debugger/Breakpoint.java
xslt/debugger/cmdline/CmdLineObserver.java
xslt/debugger/cmdline/Controller.java
xslt/debugger/cmdline/EmacsObserver.java
xslt/debugger/FOPLogger.java
xslt/debugger/FOPMessageListener.java
xslt/debugger/Manager.java xslt/debugger/Observer.java
xslt/debugger/saxon/SaxonSAXParserErrorHandler.java
xslt/debugger/saxon/SaxonStyleFrame.java
xslt/debugger/saxon/SaxonTraceListener.java
xslt/debugger/saxon/SaxonType.java
xslt/debugger/saxon/SaxonValue.java
xslt/debugger/saxon/SaxonVariable.java
xslt/debugger/saxon/XSLTDebugger.java
xslt/debugger/SAXParserErrorHandler.java
xslt/debugger/SourceFrame.java
xslt/debugger/StyleFrame.java
xslt/debugger/TrAXErrorListener.java
xslt/debugger/Type.java xslt/debugger/Utils.java
xslt/debugger/Value.java xslt/debugger/Variable.java
xslt/debugger/xalan/XalanSAXParserErrorHandler.java
xslt/debugger/xalan/XalanStyleFrame.java
xslt/debugger/xalan/XalanTraceListener.java
xslt/debugger/xalan/XalanType.java
xslt/debugger/xalan/XalanValue.java
xslt/debugger/xalan/XalanVariable.java
xslt/debugger/xalan/XSLTDebugger.java
jar cf xslt.jar xslt
make[1]: Leaving directory
`/tmp/xslt-process-2.2/java'
make[1]: Entering directory
`/tmp/xslt-process-2.2/etc'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/tmp/xslt-process-2.2/etc'
make[1]: Entering directory
`/tmp/xslt-process-2.2/doc'
(scale=0.75; \
 for f in apply-xslt.png assoc-stylesheet.png
boolean.png menu-comparison.png number.png object.png
processors.png sflogo.png speedbar.png string.png
tree.png type.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 $3}' | awk -F x
'{print $1}'`; \
  height=`identify $f | awk '{print $3}' | 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


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

Re: So close! Java issues

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

On Monday, Jan 20, 2003, at 14:04 US/Pacific, glaprade wrote:

> Ovidiu,
>
> I fixed it.  The problem was something to do my NT box having dual 
> versions
> of the jre.  I cannot say _exactly_ what fixed it, but I:
>     - uninstalled all jre/jdk related stuff
>     - reinstalled jdk1.4 but got a 'cannot find jvm.cfg' error from
> xslt-process
>     - rebooted, uninstalled jdk1.4
>     - rebooted, reinstalled jdk1.4
>
> Now it works like a champ.

I'm glad it works for you!

> Thanks for the help,
> Greg

Not much help though ;)

Cheers,
Ovidiu

> -----Original Message-----
> From: Ovidiu Predescu [mailto:ov...@ap...]
> Sent: Friday, January 17, 2003 9:57 PM
> To: glaprade
> Cc: 'xsl...@li...'
> Subject: Re: So close! Java issues
>
>
> Hi Greg,
>
> I'm sorry, I don't have much experience on the Windows platform so I
> cannot help you much. Perhaps somebody else that encounters the same
> problem can help you.
>
> Regards,
> Ovidiu
>
> On Friday, Jan 17, 2003, at 08:52 US/Pacific, glaprade wrote:
>
>> OK, I solved problem #1.  I copied and pasted my .emacs entries out of
>> the
>> .pdf file and the character encoding messed up my single quotes.  I am
>> automatically loading up the XSLT minor mode when I load an xsl or xml
>> document.
>>
>> However, I still have the java problems.  I got to the transforms to
>> work
>> by:
>>  - changing my 'Software\JavaSoft\Java Runtime
>> Environment\CurrentVersion'
>> registry entry to: 1.3
>>  - and then added a 'Software\JavaSoft\Java Runtime
>> Environment\1.3\JavaHome' C:\Program Files\JavaSoft\JRE\1.3.1_02 (I've
>> actually got 1.3.1 and not 1.3)
>>
>> However, this is not a good solution as I have other apps that depend
>> on
>> jre1.4.
>>
>> What setting do I need to change to get xslt-process to use jre1.4???
>> I am
>> running xslt-process 2.2.
>>
>> Thanks,
>> greg
>>
>>
>>
>> -----Original Message-----
>> From: glaprade [mailto:gla...@mi...]
>> Sent: Wednesday, January 15, 2003 5:59 PM
>> To: 'xsl...@li...'
>> Subject: So close! Java issues
>>
>>
>> I am using NTEmacs 21.2.
>>
>> I am so very close, but I have 2 problems:
>>
>> 1.  I have to manually load the xslt-process.el file before I use it?
>> The
>> path to this file is in my .emacs load-path, but unless I manually
>> load the
>> file I cannot M-x xslt-process-mode.  This is what I put in my .emacs
>> file
>> as a stop gap, but I'm sure there's a much better way:
>> 	(load-file "c:/emacs-21.2/xslt-process-2.2/lisp/xslt-process.el")
>>
>> 2.  More importantly, I cannot run the Saxon or Xalan processors due
>> to Java
>> errors.  This is what I get in the *xslt* buffer:
>>
>> Registry key 'Software\JavaSoft\Java Runtime
>> Environment\CurrentVersion'
>> has value '1.4', but '1.3' is required.
>> Error: could not find java.dll
>> Error: could not find Java 2 Runtime Environment.
>>
>> I have the j2sdk1.4.0 installed, and c:\j2sdk1.4.0\bin is in my path.
>> I
>> notice in the xslt-process 2.2 announce message that 1.4 is now
>> supported,
>> what do I need to do?
>>
>> Thanks for your help,
>> Greg
>>
>>
>>
>> -------------------------------------------------------
>> This SF.NET email is sponsored by: A Thawte Code Signing Certificate
>> is essential in establishing user confidence by providing assurance of
>> authenticity and code integrity. Download our Free Code Signing guide:
>> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en
>> _______________________________________________
>> Xslt-process-users mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xslt-process-users
>>
>>
>> -------------------------------------------------------
>> This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts
>> will
>> allow you to extend the highest allowed 128 bit encryption to all your
>> clients even if they use browsers that are limited to 40 bit
>> encryption.
>> Get a guide
>> here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
>> _______________________________________________
>> Xslt-process-users mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xslt-process-users
>>
>

RE: So close! Java issues

[glaprade <gla...@mi...>]

Ovidiu,

I fixed it.  The problem was something to do my NT box having dual versions
of the jre.  I cannot say _exactly_ what fixed it, but I:
    - uninstalled all jre/jdk related stuff
    - reinstalled jdk1.4 but got a 'cannot find jvm.cfg' error from
xslt-process
    - rebooted, uninstalled jdk1.4
    - rebooted, reinstalled jdk1.4

Now it works like a champ.

Thanks for the help,
Greg

-----Original Message-----
From: Ovidiu Predescu [mailto:ov...@ap...]
Sent: Friday, January 17, 2003 9:57 PM
To: glaprade
Cc: 'xsl...@li...'
Subject: Re: So close! Java issues


Hi Greg,

I'm sorry, I don't have much experience on the Windows platform so I 
cannot help you much. Perhaps somebody else that encounters the same 
problem can help you.

Regards,
Ovidiu

On Friday, Jan 17, 2003, at 08:52 US/Pacific, glaprade wrote:

> OK, I solved problem #1.  I copied and pasted my .emacs entries out of 
> the
> .pdf file and the character encoding messed up my single quotes.  I am
> automatically loading up the XSLT minor mode when I load an xsl or xml
> document.
>
> However, I still have the java problems.  I got to the transforms to 
> work
> by:
>  - changing my 'Software\JavaSoft\Java Runtime 
> Environment\CurrentVersion'
> registry entry to: 1.3
>  - and then added a 'Software\JavaSoft\Java Runtime
> Environment\1.3\JavaHome' C:\Program Files\JavaSoft\JRE\1.3.1_02 (I've
> actually got 1.3.1 and not 1.3)
>
> However, this is not a good solution as I have other apps that depend 
> on
> jre1.4.
>
> What setting do I need to change to get xslt-process to use jre1.4???  
> I am
> running xslt-process 2.2.
>
> Thanks,
> greg
>
>
>
> -----Original Message-----
> From: glaprade [mailto:gla...@mi...]
> Sent: Wednesday, January 15, 2003 5:59 PM
> To: 'xsl...@li...'
> Subject: So close! Java issues
>
>
> I am using NTEmacs 21.2.
>
> I am so very close, but I have 2 problems:
>
> 1.  I have to manually load the xslt-process.el file before I use it?  
> The
> path to this file is in my .emacs load-path, but unless I manually 
> load the
> file I cannot M-x xslt-process-mode.  This is what I put in my .emacs 
> file
> as a stop gap, but I'm sure there's a much better way:
> 	(load-file "c:/emacs-21.2/xslt-process-2.2/lisp/xslt-process.el")
>
> 2.  More importantly, I cannot run the Saxon or Xalan processors due 
> to Java
> errors.  This is what I get in the *xslt* buffer:
>
> Registry key 'Software\JavaSoft\Java Runtime 
> Environment\CurrentVersion'
> has value '1.4', but '1.3' is required.
> Error: could not find java.dll
> Error: could not find Java 2 Runtime Environment.
>
> I have the j2sdk1.4.0 installed, and c:\j2sdk1.4.0\bin is in my path.  
> I
> notice in the xslt-process 2.2 announce message that 1.4 is now 
> supported,
> what do I need to do?
>
> Thanks for your help,
> Greg
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: A Thawte Code Signing Certificate
> is essential in establishing user confidence by providing assurance of
> authenticity and code integrity. Download our Free Code Signing guide:
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en
> _______________________________________________
> Xslt-process-users mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xslt-process-users
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts 
> will
> allow you to extend the highest allowed 128 bit encryption to all your
> clients even if they use browsers that are limited to 40 bit 
> encryption.
> Get a guide 
> here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
> _______________________________________________
> Xslt-process-users mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xslt-process-users
>

Re: So close! Java issues

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

Hi Greg,

I'm sorry, I don't have much experience on the Windows platform so I 
cannot help you much. Perhaps somebody else that encounters the same 
problem can help you.

Regards,
Ovidiu

On Friday, Jan 17, 2003, at 08:52 US/Pacific, glaprade wrote:

> OK, I solved problem #1.  I copied and pasted my .emacs entries out of 
> the
> .pdf file and the character encoding messed up my single quotes.  I am
> automatically loading up the XSLT minor mode when I load an xsl or xml
> document.
>
> However, I still have the java problems.  I got to the transforms to 
> work
> by:
>  - changing my 'Software\JavaSoft\Java Runtime 
> Environment\CurrentVersion'
> registry entry to: 1.3
>  - and then added a 'Software\JavaSoft\Java Runtime
> Environment\1.3\JavaHome' C:\Program Files\JavaSoft\JRE\1.3.1_02 (I've
> actually got 1.3.1 and not 1.3)
>
> However, this is not a good solution as I have other apps that depend 
> on
> jre1.4.
>
> What setting do I need to change to get xslt-process to use jre1.4???  
> I am
> running xslt-process 2.2.
>
> Thanks,
> greg
>
>
>
> -----Original Message-----
> From: glaprade [mailto:gla...@mi...]
> Sent: Wednesday, January 15, 2003 5:59 PM
> To: 'xsl...@li...'
> Subject: So close! Java issues
>
>
> I am using NTEmacs 21.2.
>
> I am so very close, but I have 2 problems:
>
> 1.  I have to manually load the xslt-process.el file before I use it?  
> The
> path to this file is in my .emacs load-path, but unless I manually 
> load the
> file I cannot M-x xslt-process-mode.  This is what I put in my .emacs 
> file
> as a stop gap, but I'm sure there's a much better way:
> 	(load-file "c:/emacs-21.2/xslt-process-2.2/lisp/xslt-process.el")
>
> 2.  More importantly, I cannot run the Saxon or Xalan processors due 
> to Java
> errors.  This is what I get in the *xslt* buffer:
>
> Registry key 'Software\JavaSoft\Java Runtime 
> Environment\CurrentVersion'
> has value '1.4', but '1.3' is required.
> Error: could not find java.dll
> Error: could not find Java 2 Runtime Environment.
>
> I have the j2sdk1.4.0 installed, and c:\j2sdk1.4.0\bin is in my path.  
> I
> notice in the xslt-process 2.2 announce message that 1.4 is now 
> supported,
> what do I need to do?
>
> Thanks for your help,
> Greg
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: A Thawte Code Signing Certificate
> is essential in establishing user confidence by providing assurance of
> authenticity and code integrity. Download our Free Code Signing guide:
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en
> _______________________________________________
> Xslt-process-users mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xslt-process-users
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts 
> will
> allow you to extend the highest allowed 128 bit encryption to all your
> clients even if they use browsers that are limited to 40 bit 
> encryption.
> Get a guide 
> here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
> _______________________________________________
> Xslt-process-users mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xslt-process-users
>

RE: So close! Java issues

[glaprade <gla...@mi...>]

OK, I solved problem #1.  I copied and pasted my .emacs entries out of the
.pdf file and the character encoding messed up my single quotes.  I am
automatically loading up the XSLT minor mode when I load an xsl or xml
document.

However, I still have the java problems.  I got to the transforms to work
by:
 - changing my 'Software\JavaSoft\Java Runtime Environment\CurrentVersion'
registry entry to: 1.3
 - and then added a 'Software\JavaSoft\Java Runtime
Environment\1.3\JavaHome' C:\Program Files\JavaSoft\JRE\1.3.1_02 (I've
actually got 1.3.1 and not 1.3)

However, this is not a good solution as I have other apps that depend on
jre1.4.

What setting do I need to change to get xslt-process to use jre1.4???  I am
running xslt-process 2.2.

Thanks,
greg



-----Original Message-----
From: glaprade [mailto:gla...@mi...]
Sent: Wednesday, January 15, 2003 5:59 PM
To: 'xsl...@li...'
Subject: So close! Java issues


I am using NTEmacs 21.2.

I am so very close, but I have 2 problems:

1.  I have to manually load the xslt-process.el file before I use it?  The
path to this file is in my .emacs load-path, but unless I manually load the
file I cannot M-x xslt-process-mode.  This is what I put in my .emacs file
as a stop gap, but I'm sure there's a much better way:  
	(load-file "c:/emacs-21.2/xslt-process-2.2/lisp/xslt-process.el")

2.  More importantly, I cannot run the Saxon or Xalan processors due to Java
errors.  This is what I get in the *xslt* buffer:

Registry key 'Software\JavaSoft\Java Runtime Environment\CurrentVersion'
has value '1.4', but '1.3' is required.
Error: could not find java.dll
Error: could not find Java 2 Runtime Environment.

I have the j2sdk1.4.0 installed, and c:\j2sdk1.4.0\bin is in my path.  I
notice in the xslt-process 2.2 announce message that 1.4 is now supported,
what do I need to do?

Thanks for your help,
Greg



-------------------------------------------------------
This SF.NET email is sponsored by: A Thawte Code Signing Certificate 
is essential in establishing user confidence by providing assurance of 
authenticity and code integrity. Download our Free Code Signing guide:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en
_______________________________________________
Xslt-process-users mailing list
Xsl...@li...
https://lists.sourceforge.net/lists/listinfo/xslt-process-users

So close! Java issues

[glaprade <gla...@mi...>]

I am using NTEmacs 21.2.

I am so very close, but I have 2 problems:

1.  I have to manually load the xslt-process.el file before I use it?  The
path to this file is in my .emacs load-path, but unless I manually load the
file I cannot M-x xslt-process-mode.  This is what I put in my .emacs file
as a stop gap, but I'm sure there's a much better way:  
	(load-file "c:/emacs-21.2/xslt-process-2.2/lisp/xslt-process.el")

2.  More importantly, I cannot run the Saxon or Xalan processors due to Java
errors.  This is what I get in the *xslt* buffer:

Registry key 'Software\JavaSoft\Java Runtime Environment\CurrentVersion'
has value '1.4', but '1.3' is required.
Error: could not find java.dll
Error: could not find Java 2 Runtime Environment.

I have the j2sdk1.4.0 installed, and c:\j2sdk1.4.0\bin is in my path.  I
notice in the xslt-process 2.2 announce message that 1.4 is now supported,
what do I need to do?

Thanks for your help,
Greg

[ANNOUNCE] XSLT-process 2.2 available

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

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

XSLT-process is a 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 with various versions of XEmacs and GNU 
Emacs under Linux, Windows 2000 and MacOS X.

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

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

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

This release adds several improvements to the previous release:

- XSLT-process now uses Saxon 6.5.2, Xalan 2.4.1 and FOP 0.20.4

- Debugging using Xalan 2.4.1 is now fully supported.

- Both JDK 1.3 and 1.4 are supported.

- During debugging sessions the output produced by executing the 
stylesheet is serialized immediately, then displayed and incrementally 
updated in an Emacs buffer.

- Added parameter passing to the XSLT processor. These are parameters 
that are specified to all the stylesheets, in addition to any other 
parameters. They are specified through the customization menu.

- Logging output, error messages, etc. generated by the FOP processor 
are displayed in the *Messages* buffer. The level of logging can be 
customized.

- Improvements to the display of information during debugging.

- MacOS X is now a supported platform, in addition to Linux and Windows 
2000.


Enjoy,
-- 
Ovidiu Predescu <ov...@ap...>
http://webweavertech.com/ovidiu/weblog/

AW: Error with XalanJ 2.4.0

[Tolja Z. <zu...@we...>]

Hi,

it's my fault - I am using the latest stable build from Apache
(http://xml.apache.org/dist/xalan-j/xalan-j_2_4_1-bin.zip),
but the same problem I have with the shipped version(2.1) of xalan.
I found a solution for this problem by using JDK1.3 instead of
JDK1.4. So what's wrong with the new JDK ?

Thanks,
Zubow 


Are you using the version from CVS or you have simply replaced the  
Xalan shipped with the 2.1 package with the 2.4.0 version?

I'm traveling away from home, so I may be unavailable in the next few  
days.

Thanks,
Ovidiu

On Wednesday, Nov 20, 2002, at 21:08 Europe/Brussels, Tolja Zubow wrote:

> Hi Ovidiu Predescu,
>
> your xslt-debugger works really fine with saxon, but with xalan 2.4.0
> I have the following problem. Do you know what this could be ???
>
> Thanx from Germany,
> Zubow
>
> C:\j2sdk1.4.1\bin\javaw.exe -classpath
> C:\Projekte\xslt-process- 
> 2.1\classes;C:\j2sdk1.4.1\jre\lib\charsets.jar;C:\j
> 2sdk1.4.1\jre\lib\jaws.jar;C:\j2sdk1.4.1\jre\lib\jce.jar;C:\j2sdk1.4.1\ 
> jre\l
> ib\jsse.jar;C:\j2sdk1.4.1\jre\lib\rt.jar;C:\j2sdk1.4.1\jre\lib\sunrsasi 
> gn.ja
> r;C:\j2sdk1.4.1\jre\lib\ext\dnsns.jar;C:\j2sdk1.4.1\jre\lib\ext\ldapsec 
> .jar;
> C:\j2sdk1.4.1\jre\lib\ext\localedata.jar;C:\j2sdk1.4.1\jre\lib\ext\sunj 
> ce_pr
> ovider.jar;C:\j2sdk1.4.1\jre\lib\ext\Coroutine4Java.jar;C:\Projekte\xsl 
> t-pro
> cess-2.1\java\fop-0.20.1.jar;C:\Projekte\xslt-process-2.1\java\saxon- 
> 6.3.jar
> ;C:\Projekte\xslt-process-2.1\java\batik.jar;C:\Projekte\xslt-process- 
> 2.1\ja
> va\bsf.jar;C:\Projekte\xslt-process-2.1\java\jimi- 
> 1.0.jar;C:\Projekte\xslt-p
> rocess-2.1\java\xerces.jar;C:\Apache\xalan- 
> j_2_4_0\build\xalan.jar;C:\Apache
> \xalan-j_2_4_0\build\xsltctmp\BCEL.jar;C:\Apache\xalan- 
> j_2_4_0\build\xsltctm
> p\xsltc.jar xslt.debugger.cmdline.Controller
> xslt> debug -xml samples/books.xml -xsl samples/books.xsl
> xslt> javax.xml.transform.TransformerException:
> java.util.EmptyStackException
> 	at
> org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(Transfor 
> merFa
> ctoryImpl.java:958)
> 	at
> xslt.debugger.AbstractXSLTDebugger$XSLTSheetInfo.<init>(AbstractXSLTDeb 
> ugger
> .java:406)
> 	at  
> xslt.debugger.AbstractXSLTDebugger.run(AbstractXSLTDebugger.java:174)
> 	at java.lang.Thread.run(Thread.java:536)
> Caused by: java.util.EmptyStackException
> 	at java.util.Stack.peek(Stack.java:79)
> 	at com.icl.saxon.aelfred.SAXDriver.getSystemId(SAXDriver.java:1279)
> 	at
> org.apache.xml.utils.SAXSourceLocator.getSystemId(SAXSourceLocator.java 
> :147)
> 	at  
> xslt.debugger.TrAXErrorListener.reportError(TrAXErrorListener.java:82)
> 	at xslt.debugger.TrAXErrorListener.error(TrAXErrorListener.java:51)
> 	at
> org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.ja 
> va:88
> 7)
> 	at
> org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.ja 
> va:91
> 9)
> 	at
> org.apache.xalan.processor.ProcessorInclude.parse(ProcessorInclude.java 
> :316)
> 	at
> org.apache.xalan.processor.ProcessorInclude.startElement(ProcessorInclu 
> de.ja
> va:189)
> 	at
> org.apache.xalan.processor.StylesheetHandler.startElement(StylesheetHan 
> dler.
> java:656)
> 	at com.icl.saxon.aelfred.SAXDriver.startElement(SAXDriver.java:798)
> 	at com.icl.saxon.aelfred.XmlParser.parseElement(XmlParser.java:1034)
> 	at com.icl.saxon.aelfred.XmlParser.parseContent(XmlParser.java:1210)
> 	at com.icl.saxon.aelfred.XmlParser.parseElement(XmlParser.java:1030)
> 	at com.icl.saxon.aelfred.XmlParser.parseDocument(XmlParser.java:499)
> 	at com.icl.saxon.aelfred.XmlParser.doParse(XmlParser.java:151)
> 	at com.icl.saxon.aelfred.SAXDriver.parse(SAXDriver.java:320)
> 	at
> org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(Transfor 
> merFa
> ctoryImpl.java:934)
> 	... 3 more
> ---------
> java.util.EmptyStackException
> 	at java.util.Stack.peek(Stack.java:79)
> 	at com.icl.saxon.aelfred.SAXDriver.getSystemId(SAXDriver.java:1279)
> 	at
> org.apache.xml.utils.SAXSourceLocator.getSystemId(SAXSourceLocator.java 
> :147)
> 	at  
> xslt.debugger.TrAXErrorListener.reportError(TrAXErrorListener.java:82)
> 	at xslt.debugger.TrAXErrorListener.error(TrAXErrorListener.java:51)
> 	at
> org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.ja 
> va:88
> 7)
> 	at
> org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.ja 
> va:91
> 9)
> 	at
> org.apache.xalan.processor.ProcessorInclude.parse(ProcessorInclude.java 
> :316)
> 	at
> org.apache.xalan.processor.ProcessorInclude.startElement(ProcessorInclu 
> de.ja
> va:189)
> 	at
> org.apache.xalan.processor.StylesheetHandler.startElement(StylesheetHan 
> dler.
> java:656)
> 	at com.icl.saxon.aelfred.SAXDriver.startElement(SAXDriver.java:798)
> 	at com.icl.saxon.aelfred.XmlParser.parseElement(XmlParser.java:1034)
> 	at com.icl.saxon.aelfred.XmlParser.parseContent(XmlParser.java:1210)
> 	at com.icl.saxon.aelfred.XmlParser.parseElement(XmlParser.java:1030)
> 	at com.icl.saxon.aelfred.XmlParser.parseDocument(XmlParser.java:499)
> 	at com.icl.saxon.aelfred.XmlParser.doParse(XmlParser.java:151)
> 	at com.icl.saxon.aelfred.SAXDriver.parse(SAXDriver.java:320)
> 	at
> org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(Transfor 
> merFa
> ctoryImpl.java:934)
> 	at
> xslt.debugger.AbstractXSLTDebugger$XSLTSheetInfo.<init>(AbstractXSLTDeb 
> ugger
> .java:406)
> 	at  
> xslt.debugger.AbstractXSLTDebugger.run(AbstractXSLTDebugger.java:174)
> 	at java.lang.Thread.run(Thread.java:536)
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:
> Battle your brains against the best in the Thawte Crypto
> Challenge. Be the first to crack the code - register now:
> http://www.gothawte.com/rd521.html
> _______________________________________________
> Xslt-process-users mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xslt-process-users
>

Re: Error with XalanJ 2.4.0

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

Are you using the version from CVS or you have simply replaced the  
Xalan shipped with the 2.1 package with the 2.4.0 version?

I'm traveling away from home, so I may be unavailable in the next few  
days.

Thanks,
Ovidiu

On Wednesday, Nov 20, 2002, at 21:08 Europe/Brussels, Tolja Zubow wrote:

> Hi Ovidiu Predescu,
>
> your xslt-debugger works really fine with saxon, but with xalan 2.4.0
> I have the following problem. Do you know what this could be ???
>
> Thanx from Germany,
> Zubow
>
> C:\j2sdk1.4.1\bin\javaw.exe -classpath
> C:\Projekte\xslt-process- 
> 2.1\classes;C:\j2sdk1.4.1\jre\lib\charsets.jar;C:\j
> 2sdk1.4.1\jre\lib\jaws.jar;C:\j2sdk1.4.1\jre\lib\jce.jar;C:\j2sdk1.4.1\ 
> jre\l
> ib\jsse.jar;C:\j2sdk1.4.1\jre\lib\rt.jar;C:\j2sdk1.4.1\jre\lib\sunrsasi 
> gn.ja
> r;C:\j2sdk1.4.1\jre\lib\ext\dnsns.jar;C:\j2sdk1.4.1\jre\lib\ext\ldapsec 
> .jar;
> C:\j2sdk1.4.1\jre\lib\ext\localedata.jar;C:\j2sdk1.4.1\jre\lib\ext\sunj 
> ce_pr
> ovider.jar;C:\j2sdk1.4.1\jre\lib\ext\Coroutine4Java.jar;C:\Projekte\xsl 
> t-pro
> cess-2.1\java\fop-0.20.1.jar;C:\Projekte\xslt-process-2.1\java\saxon- 
> 6.3.jar
> ;C:\Projekte\xslt-process-2.1\java\batik.jar;C:\Projekte\xslt-process- 
> 2.1\ja
> va\bsf.jar;C:\Projekte\xslt-process-2.1\java\jimi- 
> 1.0.jar;C:\Projekte\xslt-p
> rocess-2.1\java\xerces.jar;C:\Apache\xalan- 
> j_2_4_0\build\xalan.jar;C:\Apache
> \xalan-j_2_4_0\build\xsltctmp\BCEL.jar;C:\Apache\xalan- 
> j_2_4_0\build\xsltctm
> p\xsltc.jar xslt.debugger.cmdline.Controller
> xslt> debug -xml samples/books.xml -xsl samples/books.xsl
> xslt> javax.xml.transform.TransformerException:
> java.util.EmptyStackException
> 	at
> org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(Transfor 
> merFa
> ctoryImpl.java:958)
> 	at
> xslt.debugger.AbstractXSLTDebugger$XSLTSheetInfo.<init>(AbstractXSLTDeb 
> ugger
> .java:406)
> 	at  
> xslt.debugger.AbstractXSLTDebugger.run(AbstractXSLTDebugger.java:174)
> 	at java.lang.Thread.run(Thread.java:536)
> Caused by: java.util.EmptyStackException
> 	at java.util.Stack.peek(Stack.java:79)
> 	at com.icl.saxon.aelfred.SAXDriver.getSystemId(SAXDriver.java:1279)
> 	at
> org.apache.xml.utils.SAXSourceLocator.getSystemId(SAXSourceLocator.java 
> :147)
> 	at  
> xslt.debugger.TrAXErrorListener.reportError(TrAXErrorListener.java:82)
> 	at xslt.debugger.TrAXErrorListener.error(TrAXErrorListener.java:51)
> 	at
> org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.ja 
> va:88
> 7)
> 	at
> org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.ja 
> va:91
> 9)
> 	at
> org.apache.xalan.processor.ProcessorInclude.parse(ProcessorInclude.java 
> :316)
> 	at
> org.apache.xalan.processor.ProcessorInclude.startElement(ProcessorInclu 
> de.ja
> va:189)
> 	at
> org.apache.xalan.processor.StylesheetHandler.startElement(StylesheetHan 
> dler.
> java:656)
> 	at com.icl.saxon.aelfred.SAXDriver.startElement(SAXDriver.java:798)
> 	at com.icl.saxon.aelfred.XmlParser.parseElement(XmlParser.java:1034)
> 	at com.icl.saxon.aelfred.XmlParser.parseContent(XmlParser.java:1210)
> 	at com.icl.saxon.aelfred.XmlParser.parseElement(XmlParser.java:1030)
> 	at com.icl.saxon.aelfred.XmlParser.parseDocument(XmlParser.java:499)
> 	at com.icl.saxon.aelfred.XmlParser.doParse(XmlParser.java:151)
> 	at com.icl.saxon.aelfred.SAXDriver.parse(SAXDriver.java:320)
> 	at
> org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(Transfor 
> merFa
> ctoryImpl.java:934)
> 	... 3 more
> ---------
> java.util.EmptyStackException
> 	at java.util.Stack.peek(Stack.java:79)
> 	at com.icl.saxon.aelfred.SAXDriver.getSystemId(SAXDriver.java:1279)
> 	at
> org.apache.xml.utils.SAXSourceLocator.getSystemId(SAXSourceLocator.java 
> :147)
> 	at  
> xslt.debugger.TrAXErrorListener.reportError(TrAXErrorListener.java:82)
> 	at xslt.debugger.TrAXErrorListener.error(TrAXErrorListener.java:51)
> 	at
> org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.ja 
> va:88
> 7)
> 	at
> org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.ja 
> va:91
> 9)
> 	at
> org.apache.xalan.processor.ProcessorInclude.parse(ProcessorInclude.java 
> :316)
> 	at
> org.apache.xalan.processor.ProcessorInclude.startElement(ProcessorInclu 
> de.ja
> va:189)
> 	at
> org.apache.xalan.processor.StylesheetHandler.startElement(StylesheetHan 
> dler.
> java:656)
> 	at com.icl.saxon.aelfred.SAXDriver.startElement(SAXDriver.java:798)
> 	at com.icl.saxon.aelfred.XmlParser.parseElement(XmlParser.java:1034)
> 	at com.icl.saxon.aelfred.XmlParser.parseContent(XmlParser.java:1210)
> 	at com.icl.saxon.aelfred.XmlParser.parseElement(XmlParser.java:1030)
> 	at com.icl.saxon.aelfred.XmlParser.parseDocument(XmlParser.java:499)
> 	at com.icl.saxon.aelfred.XmlParser.doParse(XmlParser.java:151)
> 	at com.icl.saxon.aelfred.SAXDriver.parse(SAXDriver.java:320)
> 	at
> org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(Transfor 
> merFa
> ctoryImpl.java:934)
> 	at
> xslt.debugger.AbstractXSLTDebugger$XSLTSheetInfo.<init>(AbstractXSLTDeb 
> ugger
> .java:406)
> 	at  
> xslt.debugger.AbstractXSLTDebugger.run(AbstractXSLTDebugger.java:174)
> 	at java.lang.Thread.run(Thread.java:536)
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:
> Battle your brains against the best in the Thawte Crypto
> Challenge. Be the first to crack the code - register now:
> http://www.gothawte.com/rd521.html
> _______________________________________________
> Xslt-process-users mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xslt-process-users
>

Error with XalanJ 2.4.0

[Tolja Z. <zu...@we...>]

Hi Ovidiu Predescu,

your xslt-debugger works really fine with saxon, but with xalan 2.4.0
I have the following problem. Do you know what this could be ???

Thanx from Germany,
Zubow

C:\j2sdk1.4.1\bin\javaw.exe -classpath
C:\Projekte\xslt-process-2.1\classes;C:\j2sdk1.4.1\jre\lib\charsets.jar;C:\j
2sdk1.4.1\jre\lib\jaws.jar;C:\j2sdk1.4.1\jre\lib\jce.jar;C:\j2sdk1.4.1\jre\l
ib\jsse.jar;C:\j2sdk1.4.1\jre\lib\rt.jar;C:\j2sdk1.4.1\jre\lib\sunrsasign.ja
r;C:\j2sdk1.4.1\jre\lib\ext\dnsns.jar;C:\j2sdk1.4.1\jre\lib\ext\ldapsec.jar;
C:\j2sdk1.4.1\jre\lib\ext\localedata.jar;C:\j2sdk1.4.1\jre\lib\ext\sunjce_pr
ovider.jar;C:\j2sdk1.4.1\jre\lib\ext\Coroutine4Java.jar;C:\Projekte\xslt-pro
cess-2.1\java\fop-0.20.1.jar;C:\Projekte\xslt-process-2.1\java\saxon-6.3.jar
;C:\Projekte\xslt-process-2.1\java\batik.jar;C:\Projekte\xslt-process-2.1\ja
va\bsf.jar;C:\Projekte\xslt-process-2.1\java\jimi-1.0.jar;C:\Projekte\xslt-p
rocess-2.1\java\xerces.jar;C:\Apache\xalan-j_2_4_0\build\xalan.jar;C:\Apache
\xalan-j_2_4_0\build\xsltctmp\BCEL.jar;C:\Apache\xalan-j_2_4_0\build\xsltctm
p\xsltc.jar xslt.debugger.cmdline.Controller
xslt> debug -xml samples/books.xml -xsl samples/books.xsl
xslt> javax.xml.transform.TransformerException:
java.util.EmptyStackException
	at
org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFa
ctoryImpl.java:958)
	at
xslt.debugger.AbstractXSLTDebugger$XSLTSheetInfo.<init>(AbstractXSLTDebugger
.java:406)
	at xslt.debugger.AbstractXSLTDebugger.run(AbstractXSLTDebugger.java:174)
	at java.lang.Thread.run(Thread.java:536)
Caused by: java.util.EmptyStackException
	at java.util.Stack.peek(Stack.java:79)
	at com.icl.saxon.aelfred.SAXDriver.getSystemId(SAXDriver.java:1279)
	at
org.apache.xml.utils.SAXSourceLocator.getSystemId(SAXSourceLocator.java:147)
	at xslt.debugger.TrAXErrorListener.reportError(TrAXErrorListener.java:82)
	at xslt.debugger.TrAXErrorListener.error(TrAXErrorListener.java:51)
	at
org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.java:88
7)
	at
org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.java:91
9)
	at
org.apache.xalan.processor.ProcessorInclude.parse(ProcessorInclude.java:316)
	at
org.apache.xalan.processor.ProcessorInclude.startElement(ProcessorInclude.ja
va:189)
	at
org.apache.xalan.processor.StylesheetHandler.startElement(StylesheetHandler.
java:656)
	at com.icl.saxon.aelfred.SAXDriver.startElement(SAXDriver.java:798)
	at com.icl.saxon.aelfred.XmlParser.parseElement(XmlParser.java:1034)
	at com.icl.saxon.aelfred.XmlParser.parseContent(XmlParser.java:1210)
	at com.icl.saxon.aelfred.XmlParser.parseElement(XmlParser.java:1030)
	at com.icl.saxon.aelfred.XmlParser.parseDocument(XmlParser.java:499)
	at com.icl.saxon.aelfred.XmlParser.doParse(XmlParser.java:151)
	at com.icl.saxon.aelfred.SAXDriver.parse(SAXDriver.java:320)
	at
org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFa
ctoryImpl.java:934)
	... 3 more
---------
java.util.EmptyStackException
	at java.util.Stack.peek(Stack.java:79)
	at com.icl.saxon.aelfred.SAXDriver.getSystemId(SAXDriver.java:1279)
	at
org.apache.xml.utils.SAXSourceLocator.getSystemId(SAXSourceLocator.java:147)
	at xslt.debugger.TrAXErrorListener.reportError(TrAXErrorListener.java:82)
	at xslt.debugger.TrAXErrorListener.error(TrAXErrorListener.java:51)
	at
org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.java:88
7)
	at
org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.java:91
9)
	at
org.apache.xalan.processor.ProcessorInclude.parse(ProcessorInclude.java:316)
	at
org.apache.xalan.processor.ProcessorInclude.startElement(ProcessorInclude.ja
va:189)
	at
org.apache.xalan.processor.StylesheetHandler.startElement(StylesheetHandler.
java:656)
	at com.icl.saxon.aelfred.SAXDriver.startElement(SAXDriver.java:798)
	at com.icl.saxon.aelfred.XmlParser.parseElement(XmlParser.java:1034)
	at com.icl.saxon.aelfred.XmlParser.parseContent(XmlParser.java:1210)
	at com.icl.saxon.aelfred.XmlParser.parseElement(XmlParser.java:1030)
	at com.icl.saxon.aelfred.XmlParser.parseDocument(XmlParser.java:499)
	at com.icl.saxon.aelfred.XmlParser.doParse(XmlParser.java:151)
	at com.icl.saxon.aelfred.SAXDriver.parse(SAXDriver.java:320)
	at
org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFa
ctoryImpl.java:934)
	at
xslt.debugger.AbstractXSLTDebugger$XSLTSheetInfo.<init>(AbstractXSLTDebugger
.java:406)
	at xslt.debugger.AbstractXSLTDebugger.run(AbstractXSLTDebugger.java:174)
	at java.lang.Thread.run(Thread.java:536)

Re: XSLT Processor and Java, help GREATLY appreciated

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

Wow, this is the first time I see this error.

I guess the reason for this is that Kaffe, the JVM you're using,=20
doesn't come with the essential JDK class libraries. Instead of using=20
Kaffe, just install JDK 1.3 from either Sun or IBM. Don't use JDK 1.4,=20=

the code has not been tested with it, and you may run in other problems.

You don't need to install JDEE to be able to run XSLT-processor.

Regards,
Ovidiu

On Tuesday, October 15, 2002, at 01:05  PM, angel wrote:

> Hi. =A0Can someone please help?
>
> =A0
>
> I=92ve just installed XSLT-processor version 2.1 in emacs and all =
looks=20
> good so far, the XSLT Menus are there, etc.
>
> =A0
>
> But when I try to Apply XSLT to an xml file, I get this in my *xslt*=20=

> buffer:
>
> =A0
>
> =93 Couldn'tfind or load essential class `java/lang/Object'=20
> java.lang.NoClassDefFoundError java/lang/Object =93
>
> =A0
>
> =A0
>
> I=92ve never used java through emacs so I think this is where I need=20=

> help.
>
> Here=92s the version of java on my machine:=A0
>
> =A0
>
> mojave% java -version
>
> KaffeVirtual Machine
>
> Copyright (c) 1996-2000
>
> TransvirtualTechnologies, Inc.=A0All rights reserved
>
> Engine: Just-in-time v3=A0=A0Version: 1.0.6=A0=A0Java Version: 1.1
>
> =A0
>
> I have not installed JDEE - is that what I need?=A0Or do I have to =
just=20
> set some CLASSPATH?=A0How would I do that?=A0I=92m not much of a java =
user=85
>
> =A0
>
> THANKS!!! LORI=A0-- Please include reply to an...@sb.... =A0
>

XSLT Processor and Java, help GREATLY appreciated

[angel <an...@sb...>]

Hi.  Can someone please help?
 
I've just installed XSLT-processor version 2.1 in emacs and all looks
good so far, the XSLT Menus are there, etc.
 
But when I try to Apply XSLT to an xml file, I get this in my *xslt*
buffer:
 
" Couldn't find or load essential class `java/lang/Object'
java.lang.NoClassDefFoundError java/lang/Object "
 
 
I've never used java through emacs so I think this is where I need help.
Here's the version of java on my machine:  
 
mojave% java -version
Kaffe Virtual Machine
Copyright (c) 1996-2000
Transvirtual Technologies, Inc.  All rights reserved
Engine: Just-in-time v3   Version: 1.0.6   Java Version: 1.1 
 
I have not installed JDEE - is that what I need?  Or do I have to just
set some CLASSPATH?  How would I do that?  I'm not much of a java user.
 
THANKS!!! LORI  -- Please include reply to an...@sb....