W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > October 2007

XSLT line numbers, <code>, etc.

From: Sean Owen <srowen@google.com>
Date: Sun, 7 Oct 2007 20:13:45 -0400
Message-ID: <e920a71c0710071713u11721cf8ob78af27db9e79a96@mail.gmail.com>
To: public-mobileok-checker <public-mobileok-checker@w3.org>

I don't have any answer for the XSLT line-number issue. The Java
function only works on a Saxon-built DOM. When I try to have the XSLs
use the Saxon-built DOM version of the moki document I get some new,
undecipherable error. So there was not another answer to this? I
thought there may have been some other way to do this in XSL. I think
the XSL-based approach is indeed turning out to be more complex than
imagined, and I don't know if this one is solvable.

Separately, what about the <code> issue? This remains one of the last
major issues in my mind. The XSL function needs to put text into this
node instead of nodes.

I still remain unclear on the status of several of the tests.

I want to put out some alpha release soon once these issues are
minimally resolved. The time I can devote to this is becoming short
and run beyond what I'd expected; I'm not clear about everyone's level
of commitment to the code either. As it is, we are headed to put out a
basic alpha version, and then I'm not sure, which is looking a little
disappointing. I hope we can end up with something more complete, but
it is going to take a little more work.

Received on Monday, 8 October 2007 00:13:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:21:19 UTC