I want to expand the L10N capabilities I use within Handel; more
specifically its' XSP Taglib interface.
I can easily just add some taglib goo to use my Handel::L10N stuff using
Locale::Maketext.
My second thought was to make it a more generic XSP taglib instead.
Anyone have any interest in su
Dirk,
I'm pretty sure this is fixed in CVS with XSP.pm revision 1.50+
diff -r1.49 -r1.50
1c1
< # $Id: XSP.pm,v 1.49 2003/09/08 07:06:12 matts Exp $
---
> # $Id: XSP.pm,v 1.50 2003/09/17 19:49:52 jwalt Exp $
952a953,956
> if ($attr->{NamespaceURI}) {
> $code .=
'$parent->setAt
Dirk-Willem van Gulik wrote:
We have got some strange behavior while dealing with XSP pages containing
a lot of nested/scoped xml:lang attributes as well as XML-Namaspaces
(which are not used for taglibs but simply to differentiate tags into the
XSLT space).
I think I know what's happening.
foo.xml
Folks,
We have got some strange behavior while dealing with XSP pages containing
a lot of nested/scoped xml:lang attributes as well as XML-Namaspaces
(which are not used for taglibs but simply to differentiate tags into the
XSLT space).
foo.xml:
http://www.w3.org/1999/x
i managed to put up an application with axkit and sawa using the
SAWA::Event::SimpleSub. everythings working perfectly, but i can't
figure out howto process errors.
axkit's
AxErrorStylesheet text/xsl /stylesheets/error.xsl
is no more responsible for catching the internal server errors (500),
an
