Raw XML

<?oxygen RNGSchema="../resources/schemas/page.rng" type="xml"?>

<?oxygen SCHSchema="../resources/schemas/page.rng"?>

<page:page __file="2db7636c62b07c300d8a0dca15a246cb" __status="-1">......</page:page>

<page:page __file="2db7636c62b07c300d8a0dca15a246cb" __status="-1" xmlns:paloose="http://www.paloose.org/schemas/Paloose/1.0" xmlns:link="http://www.hsfr.org.uk/Schema/Link" xmlns:list="http://www.hsfr.org.uk/Schema/List" xmlns:page="http://www.hsfr.org.uk/Schema/Page" xmlns:t="http://www.hsfr.org.uk/Schema/Text" xmlns:i18n="http://apache.org/cocoon/i18n/2.1" xmlns:xi="http://www.w3.org/2001/XInclude">

<page:meta>......</page:meta>

<page:meta>

<page:title>Paloose — Downloads</page:title>

</page:meta>

<page:content>......</page:content>

<page:content>

<t:heading level="1">Downloads</t:heading>

<t:p>......</t:p>

<t:p>

The latest version can be found

. I will also be sourcing the entire Paloose system on BitBucket in the near future. The SourceForge download will shortly be removed (it is not the latest anyway).

</t:p>

<t:heading level="2">Compact version</t:heading>

<t:p>......</t:p>

<t:p>

See the

for a compact version of Paloose to help with

</t:p>

<t:heading level="2">Simple Site</t:heading>

<t:p>......</t:p>

<t:p>

I have a download of the

</t:p>

<t:heading level="2">Separate log4php</t:heading>

<t:p>......</t:p>

<t:p>

See the

for a discussion of which log4php should be used with the full (uncompacted) version of paloose.

</t:p>

<t:heading level="2">Full code of Paloose site</t:heading>

<t:p>......</t:p>

<t:p>

Someone has suggested that the code of this Paloose site is made available, although I have not included all the build files that I use to construct the whole site. While in general I do not like to display my scruffy programming style to the world (although Paloose itself does that), I have made a

(about 5 Mbytes) — I accept no responsibility for any problems,

<t:foreignWord>caveat emptor</t:foreignWord>

! I cannot guarantee it is the latest version either.

</t:p>

<t:heading level="2">Example Component Template</t:heading>

<t:p>......</t:p>

<t:p>

I have written an example component

that is a "template" for writing generator, transformer and serializer components; also included is an example exceptions class used by the template. Future releases of Paloose will included it in the folder

<t:code type="dir">resources/templates/</t:code>

</t:p>

<t:heading level="2">Sitemap Schema (RELAX-NG/Schematron)</t:heading>

<t:p>......</t:p>

<t:p>

There is an experimental schema for Paloose sitemaps that I use in conjunction with the

. It is distributed in the

<t:code type="dir">paloose/resources/schemas/sitemap_RNG_schemas</t:code>

folder. However I have produced a pretty-printed online version

which is slightly easier to read. If anyone is interested in the transforms and style sheets to produce this version from the XML then please contact me.

</t:p>

<t:heading level="2">Version History</t:heading>

<t:p>......</t:p>

<t:p>

Please see the VERSIONS file that is bundled with the Paloose download for details of older versions (you can also view it

). The compact version is suffixed with "-c" in the version number but otherwise follows the same version scheme.

</t:p>

<t:note type="warning">Versions before 1.12.x and earlier are not compatible with Version 1.13.0 and later. It is relatively easy to update the sitemaps to the latest version, see the documentation on serializers and components.</t:note>

<paloose:versions>......</paloose:versions>

<paloose:versions>

<paloose:version>......</paloose:version>