Hello,
A fresh look/opinion is welcome! Could someone please take a fresh
look at the bug #567210.
After closer look at my last test results (described in my two last
mails to the bug), I tend to think the problem lies in Saxon-{B|HE}.
Any comments are very much appreciated,
Eugene
--
To
On Thu, Jan 30, 2014 at 1:49 PM, Eugene Zhukov wrote:
> It fails immediately without network, but hangs and succeeds with
> network. "Saxon does not have a local copy of PUBLIC -//W3C//DTD
> XHTML+RDFa" is not shown anymore! With tcpdump and wireshark I see a
> request:
> GET /MarkUp/DTD/xhtml-rdf
On Wed, Jan 29, 2014 at 4:25 PM, Michael Kay wrote:
>
>> Warning: SXXP0005: The source document is in namespace
>> http://www.w3.org/2005/Atom, but none of the
>> template rules match elements in this namespace
>
> You can ignore that warning for present purposes.
>> [...]
>> Saxon does not have
> Warning: SXXP0005: The source document is in namespace
> http://www.w3.org/2005/Atom, but none of the
> template rules match elements in this namespace
You can ignore that warning for present purposes.
> [...]
> Saxon does not have a local copy of PUBLIC -//W3C//DTD XHTML+RDFa
> 1.0//EN SYSTEM
On Wed, Jan 29, 2014 at 3:01 PM, Michael Kay wrote:
> OK, so the problem seems to be here:
>
> Cannot read xhtml11/xhtml-inlpres-1.mod file
>
I tried with latest 9.4 and it wasn't the case anymore, but main
problem persisted.
> and the reason would appear to be the absence of the w3c/ prefix on t
OK, so the problem seems to be here:
Cannot read xhtml11/xhtml-inlpres-1.mod file
and the reason would appear to be the absence of the w3c/ prefix on the file
name.
This takes us to here:
https://saxonica.plan.io/boards/3/topics/5625
and that in turn leads me to
https://saxonica.plan.io/issu
On Wed, Jan 29, 2014 at 11:00 AM, Michael Kay wrote:
> If you use the -t option on the command line, then attempts to use local
> copies of W3C DTDs will be traced on System.err. Hopefully this will shed
> more light on why the mechanism isn't working for you.
>
> The EntityResolver that Saxon u
If you use the -t option on the command line, then attempts to use local copies
of W3C DTDs will be traced on System.err. Hopefully this will shed more light
on why the mechanism isn't working for you.
The EntityResolver that Saxon uses in 9.4 can be found here:
https://dev.saxonica.com/repos/a
On Tue, Jan 28, 2014 at 4:25 PM, Michael Kay wrote:
> Saxon-B 9.1 does not include copies of these resources.
>
> You can always write a URIResolver and direct the request to copies held at
> application level, but it can't be done "behind the scenes".
>
> My recommendation would be to move forwa
Control: -1 tag +help
Hello,
The patch/different arguments for invoking saxonb-xslt attached to this
bug report doesn't appear to work with the test case provided by Brian
Carlson and current version of libsaxonb-java in the archive in
jessie/sid. Or at least it's not working for me; it hangs af
tags 567210 patch
severity 567210 grave
thanks
Instead of:
$ cat /usr/bin/saxon-xslt
#!/bin/sh
exec java -classpath /usr/share/java/saxon.jar com.icl.saxon.StyleSheet "$@"
it should read:
#!/bin/sh
java -cp
/etc/xml/resolver:/usr/share/java/xslthl.jar:/usr/share/java/xml-resolver.jar:/usr/sh
tags 567210 important
thanks
Technically this render the package unusable if you do not have
internet connection, right ? Should'nt this be marked a 'grave' then ?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@
On Mon, Aug 29, 2011 at 8:45 PM, brian m. carlson
wrote:
> I'm not using saxonb via ant right now, so the ant task is not critical
> for me anymore. Do you still need someone to fix the underlying bug
> (doc-available returns false for file URIs) or just the ant task? I'll
> try to look into the
On Mon, Aug 29, 2011 at 07:35:50PM +0200, Torsten Werner wrote:
> On Thu, Jan 28, 2010 at 2:15 AM, brian m. carlson
> wrote:
> > I forgot to include the testcase, so it is now attached. Also, since
> > I'm really only using Saxon-B via Ant, if a new feature is added to
> > resolve this problem, I
Hi Brian,
On Thu, Jan 28, 2010 at 2:15 AM, brian m. carlson
wrote:
> I forgot to include the testcase, so it is now attached. Also, since
> I'm really only using Saxon-B via Ant, if a new feature is added to
> resolve this problem, I really need it to be accessible via the Ant
> task.
thanks fo
I forgot to include the testcase, so it is now attached. Also, since
I'm really only using Saxon-B via Ant, if a new feature is added to
resolve this problem, I really need it to be accessible via the Ant
task.
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 713 440 7475 | http:/
Package: libsaxonb-java
Version: 9.0.0.4+svn20080322-3
Severity: normal
In certain cases, the doc-available function wrongly returns false when
the document does, in fact, exist. The attached testcase contains three
files. Running "saxonb-xslt -s:foo.xml -xsl:foo.xsl" produces the
output:
Reque
17 matches
Mail list logo
