On Fri, Nov 12, 2004 at 10:26:30PM +0100, Peter Svanberg wrote:
> * It is said (on sourceforge) "Operating System: All POSIX
> (Linux/BSD/UNIX-like OSes), Linux" - does this include Solaris 9 (SunOS
> 5.9)? Anyone on the list have experience with installing and using it on
> SunOS?
Personally, I haven't tested it, but it should work as long as
GNU Make and gcc is used. It may also work without gcc, if you
don't enable debugging. If you have troubles, I'd be happy to
provide as much support as I can. I really need to have
feedbacks about modxslt on other architectures. However, if
I were you, I'd wait for the 1.3.8 release of mod-xslt, which
should solve many portability/compilation issues I received
reports for (will be released before monday or monday itself)
> * Besides installation, is it compatible with Dunkels system (2.0.4) on the
> document level?
the PI instruction:
xslt-param has become modxslt-param
xslt-base is no longer used
xslt-stylesheet has become modxslt-stylesheet, with _many_
enhancements, which may break compatibility
you only need to worry about this if your documents
use constructs like <?xslt-param... or <?xslt-stylesheet...
To solve the problem
find . -name '*.xml' |xargs perl -pi -e 's/<\?xslt-/<?modxslt-/g'
should suffice. Backup your documents before doing this and
test them before putting them online!!!
XPath parameters
many more parameters are being passed over to xslt
stylesheets, and the prefix has changed from
xslt- to modxslt- (for example, xslt-version became
modxslt-version),
you should worry about this only if your documents
useconstructs like <xsl:value-of select="$xslt-version" ...
To solve the problem, something like
find . -name '*.xslt' |xargs perl -pi -e 's/\$xslt-/\$modxslt-/g'
should suffice. Again, backup your documents first and test
your stylesheets before putting them back online!!!
Regarding document parsing, xslt usage and so on, it should be
well compatible with Dunkel's work, since it uses the same libraries
to parse documents (libxml2 and libxslt). Some slightly different
behaviors may be observed in url handling (http:// and file://)
and in DTD loading (... standalone="yes" or "no"... in case of
yes, no DTD are ever loaded by mod-xslt). The url handling differences
may cause troubles if you have dinamically generated stylesheets,
like documents that use something like:
<?xslt-stylesheet href="database-xslt.php" ?>
in which case you would probably have to change it in:
<?xslt-stylesheet href="local://database-xslt.php" ?>
or alike. Please refer to the manual to know more about this kind
of urls. Generally speaking, mod-xslt2 should have all mod-xslt
features, plus a few ones. However, the semantic of some of them
has slightly changed, so please read the manual.
Cheers,
Carlo
--
GPG Fingerprint: 2383 7B14 4D08 53A4 2C1A CA29 9E98 5431 1A68 6975
-------------
Term, holidays, term, holidays, till we leave school, and then work, work,
work till we die.
-- C.S. Lewis
