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 jevgeni...@gmail.com 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
On Wed, Jan 29, 2014 at 4:25 PM, Michael Kay m...@saxonica.com 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
On Tue, Jan 28, 2014 at 4:25 PM, Michael Kay m...@saxonica.com 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
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:
On Wed, Jan 29, 2014 at 11:00 AM, Michael Kay m...@saxonica.com 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
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
On Wed, Jan 29, 2014 at 3:01 PM, Michael Kay m...@saxonica.com 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
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
Hi Michael,
Thanks for your previous replay.
I checked with tcpdump and Wireshark that requests are made to
www.w3.org [0]. Hence the failure without network.
Could you please elaborate how to patch Saxonb 9.1.0.8 to redirect
those requests to a local copy held within Saxon itself?
You can find
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 forward to a later Saxon release that fixes
the problem. The
Dear Mike,
I am trying to solve issue reported against debian: saxonb 9.1.0.8
package. The full report is at:
http://bugs.debian.org/567210
In summary the documentation from:
http://www.saxonica.com/documentation/sourcedocs/xml-catalogs.html
Does not seems to apply when used within
These can be tricky to debug. Are you seeing a trace of URI requests from the
catalog resolver? If not, have you tried using a monitoring tool such as
Wireshark?
The normal cause of problems is that a source file contains a DTD or schema
reference to files hosted on www.w3.org. These requests
Dear submitter,
Could you please confirm that patch proposed at:
http://bugs.debian.org/567210#39
Does solve the issue for you ?
Thanks much
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Tue, Jan 07, 2014 at 02:39:26PM +0100, Mathieu Malaterre wrote:
Dear submitter,
Could you please confirm that patch proposed at:
http://bugs.debian.org/567210#39
Does solve the issue for you ?
It does not appear to solve the problem. It still does not work when
networking is
15 matches
Mail list logo