You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by sh...@apache.org on 2012/09/28 23:26:07 UTC
svn commit: r1391665 [2/4] - in /xalan/c/branches/GSoC-2012/xdocs: ./
sources/ sources/xalan/ style/dtd/ style/stylesheets/
Added: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/buildlibs.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/buildlibs.xml?rev=1391665&view=auto
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/buildlibs.xml (added)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/buildlibs.xml Fri Sep 28 21:26:05 2012
@@ -0,0 +1,525 @@
+<?xml version="1.0" standalone="no"?>
+<!DOCTYPE s1 SYSTEM "../../style/dtd/document.dtd">
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+
+<s1 title="Building Xalan-C/C++">
+<ul>
+<li><link anchor="winbldenv">Windows Build Environment</link></li>
+<ul>
+<li><link anchor="winbld">Windows Basic Build Instruction</link></li>
+<li><link anchor="winbldcmd">Sample Windows Build Command File</link></li>
+<li><link anchor="winbldinst">Installing the Xalan Library on Windows</link></li>
+</ul>
+<li><link anchor="unixbldenv">UNIX Build Environment</link></li>
+<ul>
+<li><link anchor="unixlibpath">Finding Runtime Libraries</link></li>
+<li><link anchor="unixbldxalan">Building the Xalan-C/C++ XSLT Libraries for UNIX</link></li>
+</ul>
+<li><link anchor="unixcompileref">Reference on Unix Platforms and C++ Compilers</link></li>
+<li><link anchor="xercesmodules">Xerces-C/C++ Transcoders and Plug-in Modules</link></li>
+<!-- <li><link anchor=""></link></li> -->
+</ul>
+
+<br/>
+<p>The Xalan-C/C++ XSLT library is built upon the Xerces-C/C++ XML Parser library. Before compiling the Xalan-C/C++ XSLT library, you must have a usable Xerces-C/C++ library.
+</p>
+<p>You can either install a compatible binary distribution of Xerces-C/C++ or build your own from a source distribution of Xerces-C/C++. You can gain additional capability if you build the Xerces-C/C++ XML Parser library from sources. The Xerces-C/C++ binary distribution is not built for the IBM-ICU libraries. The IBM-ICU libraries provide additional transcoding services.
+</p>
+<p>Building the source code packages ensures that the resulting packages are proper for your system. There are various binary distributions available, but incompatibilities between C++ compilers (even between compiler versions) are known to cause issues with sharing of libraries.
+</p>
+<p>We don't have persons yet committed to build binary distribution releases.
+</p>
+<p>You can get more information on the Xerces-C/C++ distributions at the <jump href="http://xml.apache.org/xerces-c">http://xml.apache.org/xerces-c</jump> web site.
+</p>
+
+<anchor name="winbldenv"/>
+<s2 title="Windows Build Environment">
+
+<p>Build support for Microsoft Visual Studio (VC6) is deprecated.
+</p>
+<p>Building Xalan-C/C++ with Microsoft Visual Studio (VC6) requires the Xerces-C/C++ version 2.8 or older releases. Microsoft VC6 is removed from the Xerces-C/C++ Version 3.x releases.
+</p>
+<p>Building Xalan-C/C++ with Microsoft Visual Studio .NET 2008 (VC9) requires Xerces-C/C++ version 3.1 or newer. Building with Microsoft Visual Studio .NET 2010 (VC10) requires Xerces-C/C++ version 3.1.1 or newer.
+</p>
+<p>Environment variables XERCESCROOT and XALANCROOT are required. Environment ICUROOT is used only if building Xalan-C/C++ with IBM-ICU library support.
+</p>
+<table>
+<tr>
+ <td><en>XERCESCROOT</en></td><td>The Xerces-C/C++ installation directory</td>
+</tr>
+<tr>
+ <td><en>XALANCROOT</en></td><td>The Xalan-C/C++ source directory</td>
+</tr>
+<tr>
+ <td><en>ICUROOT</en></td><td>The IBM-ICU installation directory (only if building with ICU support)</td>
+</tr>
+</table>
+
+<p>I like to create command or batch files to setup the build environment variables and start the Visual Studio .NET development system using the custom build environment. I find this much easier than navigating the graphical interface to add custom build environments. The Microsoft *.vsprops custom property files are not available in the early versions of Visual Studio .NET platforms.
+</p>
+<anchor name="winbld"/>
+<s3 title="Windows Basic Build Instruction">
+<p>If you want to create binary packages from the sources, you may wish to look
+at the <link anchor="winbldcmd">Windows Build Command File</link> in the next section.
+</p>
+<p>A quick experiment in building for Windows is documented in the remainder of this section.
+</p>
+<p>I have Visual Studio 2005, 2008, 2010 on one computer and VC6 and Visual Studio 2003
+installed on another computer.
+</p>
+<p>Microsoft Visual Studio .NET products will usually install
+a Visual Studio Command Prompt icon in the Visual Studio Tools subfolder
+for each version of Visual Studio installed on your computer.
+The Visual Studio Command Prompt automatically sets a basic development environment
+using a "vsvars32.bat" or "vcvarsall.bat" script
+for 32-bit or 64-bit platform builds, and leaves you at the command line for
+customizing your environment.
+</p>
+<p>You then define the XERCESCROOT, XALANCROOT, and ICUROOT environment variables.
+</p>
+<p>If the Xerces-C DLL files are not in directory %XERCESCROOT%\bin, you must add
+a directory to the PATH environment variable so the Xerces-C DLL files can be
+found.
+</p>
+<p>You then launch the Visual Studio .NET by calling <code>devenv</code> with a
+path to the <code>Xalan.sln</code> file as a parameter.
+</p>
+<p>The following section describes how you can build your own scripts to create
+binary packages from Xalan-C compiled sources for the various versions of
+Microsoft Visual Studio products.
+</p>
+</s3>
+<anchor name="winbldcmd"/>
+<s3 title="Sample Windows Build Command File">
+
+<p>I like to use this template for both Xerces-C and Xalan-C builds from sources. The sample shown here is for Xalan-C/C++ because the installation of Xerces-C/C++ should already have been done.
+</p>
+<source>
+SET XERCESCROOT="path to xerces-c installation"
+SET XALANCROOT="sources\xalan\c\"
+</source>
+<p>Set the xalan project path for your version of Microsoft Visual Studio .NET.
+</p>
+<source>
+:: VS 2003 (VC7.1)
+SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC7.1
+
+:: VS 2005 (VC8)
+SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC8
+
+:: VS 2008 (VC9)
+SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC9
+
+:: VS 2010 (VC10)
+SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC10
+</source>
+<p>Set some environment variables so we can easily copy or install the products after they have been built.
+</p>
+<source>
+:: VS 2003 (VC7.1)
+SET XALANCBUILDDIR=%XALANCROOT%\Build\Win32\VC7.1
+
+:: VS 2005 (VC8)
+SET XALANCBUILDDIR=%XALANCROOT%\Build\Win32\VC8
+
+:: VS 2008 (VC9)
+SET XALANCBUILDDIR=%XALANCROOT%\Build\Win32\VC9
+
+:: VS 2010 (VC10)
+SET XALANCBUILDDIR=%XALANCROOT%\Build\Win32\VC10
+</source>
+<p>We use this Visual Studio .NET solution file.
+</p>
+<source>
+SET XALANCBUILDSLN=%XALANCPROJDIR%\xalan.sln
+</source>
+<p>The <code>$(variable)</code> is expanded inside Visual Studio.<br/>
+The <code>%variable%</code> is expanded by the cmd utility before launching the Visual Studio.
+</p>
+<source>
+SET PATH=%WINDIR%\system32;%WINDIR%;%WINDIR%\system32\Wbem
+SET INCLUDE=
+SET LIB=
+SET LIBPATH=
+SET SOURCE=
+</source>
+<p>Set the default environment variables for your version of Microsoft Visual Studio .NET.
+</p>
+<source>
+:: VS 2000 (VC7) - obsolete
+call "%VS70COMNTOOLS%vsvars32.bat"
+
+:: VS 2003 (VC7.1) 32-bit platform
+call "%VS71COMNTOOLS%vsvars32.bat"
+
+:: VS 2005 (VC8) 32-bit platform
+call "%VS80COMNTOOLS%vsvars32.bat"
+
+:: VS 2005 (VC8) 64-bit platform
+call "%VS80COMNTOOLS%\..\..\VC\vcvarsall.bat" x86_amd64
+
+:: VS 2008 (VC9) 32-bit platform
+call "%VS90COMNTOOLS%vsvars32.bat"
+
+:: VS 2008 (VC9) 64-bit platform
+call "%VS90COMNTOOLS%\..\..\VC\vcvarsall.bat" x86_amd64
+
+:: VS 2010 (VC10) 32-bit platform
+call "%VS100COMNTOOLS%vsvars32.bat"
+
+:: VS 2010 (VC10) 64-bit platform
+call "%VS100COMNTOOLS%\..\..\VC\vcvarsall.bat" x86_amd64
+</source>
+<p>The LIBPATH and SOURCE environment variables may not be properly
+set by the vsvars32.bat command file. You may wish to start your
+Visual Studio .NET application without any custom environment
+and examine the Tools -> C/C++ project defaults for the various libraries.
+Then specifically set the paths in the build command file for your project.
+</p>
+<p>The Xalan-C and Xerces-C libraries do not use the Microsoft Framework,
+the "mfc" and the "atl" directives. Microsoft is deprecating their "mfc"
+Microsoft Foundation Classes.
+</p>
+<p>Define the necessary environment variables for building the Xalan-C/C++ libraries and sample programs.
+</p>
+<source>
+SET PATH=%PATH%;%XERCESCROOT%\bin
+
+SET INCLUDE=%INCLUDE%;%XERCESCROOT%\include;%XERCESCROOT%\src
+SET INCLUDE=%INCLUDE%;%XALANCROOT%\src
+
+SET LIB=%LIB%;%XERCESCROOT%\lib
+</source>
+<p>If you are going to build for IBM-ICU support, then add the following environments.
+</p>
+<source>
+SET ICUROOT="path to ibm-icu installation"
+
+SET PATH=%PATH%;%ICUROOT%\bin
+SET INCLUDE=%INCLUDE%;%ICUROOT%\include
+SET LIB=%LIB%;%ICUROOT%\lib;%ICUROOT%\data
+</source>
+<p>Now we should be ready to start the Microsoft Visual Studio .NET using our custom environment using the <code>%XALANCBUILDSLN%</code> solution.
+</p>
+<source>
+devenv.exe "%XALANCBUILDSLN%" /useenv
+</source>
+</s3>
+<anchor name="winbldinst"/>
+<s3 title="Installing the Xalan Library on Windows">
+
+<p>The following command script will install the binary and header files to a target directory that is compatible with the XALANCROOT environment variable for creating applications. Environment variables other than XALANCTARGET are defined in the previous section, the <link anchor="winbldcmd">Visual Studio .NET build example</link>.
+</p>
+<source>
+SET XALANCTARGET="path-to-target-directory"
+
+MKDIR "%XALANCTARGET%\bin"
+MKDIR "%XALANCTARGET%\include"
+MKDIR "%XALANCTARGET%\lib"
+
+CD "%XALANCBUILDDIR%\Release\Nls"
+COPY *.hpp "%XALANCTARGET%"\include
+
+CD "%XALANCBUILDDIR%\Release"
+COPY *.DLL "%XALANCTARGET%\bin"
+COPY *.LIB "%XALANCTARGET%\lib"
+COPY *.EXP "%XALANCTARGET%\lib"
+
+CD "%XALANCBUILDDIR%\Debug"
+COPY *.DLL "%XALANCTARGET%\bin"
+COPY *.PDB "%XALANCTARGET%\bin"
+COPY *.LIB "%XALANCTARGET%\lib"
+COPY *.EXP "%XALANCTARGET%\lib"
+
+CD "%XALANCROOT%\src
+XCOPY xalanc\*.hpp "%XALANCTARGET%\include\xalanc" /E /C /I /R /Y
+XCOPY xalanc\*.h "%XALANCTARGET%\include\xalanc" /E /C /I /R /Y
+</source>
+</s3></s2>
+<anchor name="unixbldenv"/>
+<s2 title="UNIX Build Environment">
+
+<p>I don't like building sources using root or superuser login. I like to do builds in a directory separated from the source tree. A debug build and release build will create shared objects of the same name. I like to target these builds to separate directory trees.
+</p>
+<p>Release builds are targeted at the <code>/usr/local</code> file system.
+</p>
+<p>Debug builds are targeted at the <code>/opt/apache/debug</code> file system.
+</p>
+<p>Source trees are referenced wherever convenient. Using the (<code>--srcdir</code>) configuration parameter allows the source tree to be separate from the build tree. The source tree can even reside on read-only media.
+</p>
+<p>Product builds are done in a build directory path separate from the source tree. This is the working directory from where you perform your builds and installs.
+</p>
+<p><em>Source Trees:</em> (<code>--srcdir</code>) configuration parameter
+</p>
+<p>
+ <code>/opt/xerces/c/<trunk>/</code><the Xerces-C/C++ XML parser library source distribution>
+<br/>
+ <code>/opt/xalan/c/<trunk></code>/<the Xalan-C/C++ XSLT library source distribution>
+</p>
+<p>If the source distribution is well-constructed, the source directory trees can be read-only.
+</p>
+<p><em>Binary Installation Trees:</em> (<code>--prefix</code>) configuration parameter
+</p>
+<p>
+ <code>/usr/local/</code> <the target for the
+release binary installation>
+<br/>
+ <code>./bin</code> The sample programs
+<br/>
+ <code>./lib</code> The shared and static library files
+<br/>
+ <code>./include</code> The library header files
+<br/>
+<br/>
+ <code>/opt/apache/debug/</code> <the target for the
+debug binary installation>
+<br/>
+ <code>./bin</code> The sample programs
+<br/>
+ <code>./lib</code> The shared and static library files
+<br/>
+ <code>./include</code> The library header files
+</p>
+
+<p>The default (<code>--prefix</code>) value is <code>/usr/local</code> which I use for release builds.
+</p>
+<p>I choose (<code>--prefix</code>) value of <code>/opt/apache/debug</code> for debug builds.
+</p>
+
+<p><em>Build Tree:</em> The build working directory tree
+</p>
+<p> <code>/<user-directory>/Build/</code>
+</p>
+
+<p>You can use any empty file system or directory path with write access. Starting with an empty directory is a quick way to do a clean build. Make this empty directory to be your current working directory.
+</p>
+<p>I also like to make some shell scripts so that the build process can be automated. I locate these scripts outside of the Build directory so they don't get lost when I purge directory content.
+</p>
+<p>
+ <code>../build-xerces-lib.sh</code>
+</p>
+<p>
+ <code>../build-xalan-lib.sh</code>
+</p>
+<p>
+ <code>../build-xalan-app.sh</code>
+</p>
+<p>I generate these shell scripts with a text editor and use them to minimize keyboard typing errors.
+</p>
+<anchor name="unixlibpath"/>
+<s3 title="Finding Runtime Libraries">
+
+<p>The various types of UNIX operating systems have differing requirements for finding libraries at runtime.
+</p>
+<table>
+<tr><th>Operating System</th><th>Library Path Environment</th></tr>
+<tr><td>Solaris and Linux</td><td>LD_LIBRARY_PATH</td></tr>
+<tr><td>HP-UX</td><td>SHLIB_PATH</td></tr>
+<tr><td>AIX and BSD</td><td>LIBPATH</td></tr>
+<tr><td>Mac OS X</td><td>DYLD_LIBRARY_PATH</td></tr>
+<tr><td>Cygwin and MinGW</td><td>PATH</td></tr>
+</table>
+
+<p>The Xalan-C/C++ and Xerces-C/C++ shared library objects must be installed in a reachable library path for your platform. The <code>make</code> step creates the libraries in the <code>lib</code> subdirectory of your working directory. The <code>make install</code> step installs these shared objects to the designated <code>{prefix}/lib</code> directory or another directory defined by the <code>--libdir</code> configuration parameter.
+</p>
+<p>In many cases, the <code>/usr/local/lib</code> is already cached in <code>/etc/ld.so.cache</code> or included by <code>/etc/ld.so.conf</code>. The library path environment variable is then used for exceptions. The explicit library path environment variable usually takes precedence over the other methods of finding shared library runtimes. This is useful if you wish to use a debug environment on the same platform that also includes release libraries of the same name.
+</p>
+</s3>
+
+<anchor name="unixbldxalan"/>
+<s3 title="Building the Xalan-C/C++ XSLT Libraries for UNIX">
+
+
+<p>I don't like building sources from a root or superuser login. I also like to do builds in a directory separated from the source tree.
+</p>
+
+<p>If your sources tree is read-only and some required files are not executable, then you need to copy the source to writable media and change the execute attributes of specific files. This command sequence will copy an entire directory tree from <code>{source-dir}</code> to <code>{dest-dir}</code>.
+</p>
+<source>
+ cd {source-dir}
+ find . | cpio -pdmuv {dest-dir}
+</source>
+<p>Connect to the <code>{xalan-src}</code> directory and make specific files executable.
+</p>
+<source>
+ cd {xalan-src}
+ chmod 755 runConfigure configure install-sh
+</source>
+<p>Connect to your empty build directory and construct a script for building the Xalan-C/C++ XSLT products.
+</p>
+
+<p>The Xalan-C/C++ configuration process uses the <code>runConfigure</code> script as a front-end to the automake <code>configure</code> script. Your shell command script should therefore use the <code>runConfigure</code> script.
+</p>
+
+<table>
+<tr><th colspan="2">runConfigure Options</th></tr>
+<tr><th>Option</th><th>Description</th></tr>
+<tr><td>-p</td><td>Build platform: aix, linux, freebsd, netbsd, solaris, hp-10, hp-11, hp11-ia64,
+ irix, tru64, macosx, cygwin</td></tr>
+<tr><td>-c</td><td>C compiler name: gcc, cc, c89, xlc, xlc_r, acc (default = gcc)</td></tr>
+<tr><td>-x</td><td>C++ compiler name: g++, CC, C89, xlC, xlC_r, aCC (default = g++)</td></tr>
+<tr><td>-d</td><td>Indicates a debug build, takes no values, default is No Debug</td></tr>
+<tr><td>-t</td><td>Transcoder to use: 'icu', (Default is null, the Xerces-C/C++ transcoder)</td></tr>
+<tr><td>-m</td><td>Type of localization support: inmem, icu, nls (default is inmem)</td></tr>
+<tr><td>-M</td><td>Locale for message localization: "en_US"</td></tr>
+<tr><td>-r</td><td>Threads option: pthread, dce (default is pthread)</td></tr>
+<tr><td>-b</td><td>Specify 32 or 64 bit build (Default is 32-bit)<br/>
+ On Linux, the 32/64 build is determined by the compiler, kernel, and glibc.</td></tr>
+<tr><td>-P</td><td>Install root directory: value is assigned to the <code>--prefix</code> configure parameter</td></tr>
+<tr><td>-l</td><td>Extra link options (assigned to <code>LDFLAGS</code>)</td></tr>
+<tr><td>-z</td><td>Extra compiler options (assigned to <code>CFLAGS</code> and <code>CXXFLAGS</code>)</td></tr>
+<tr><td>-C</td><td>Extra configuration options (i.e. <code>--srcdir=${SourceDir}</code>)</td></tr>
+<tr><td>-h</td><td>Print the <code>runConfigure</code> help and exit</td></tr>
+</table>
+
+<p>Here are the names of some C/C++ compilers associated with commercial UNIX operating systems used to build Xalan-C/C++ and Xerces-C/C++ packages.
+</p>
+
+<table>
+<tr><th>System</th><th>Platform</th><th>C Compiler</th><th>C++ Compiler</th><th>Comment</th></tr>
+<tr><td>AIX</td><td>aix</td><td>xlc_r</td><td>xlC_r</td><td>thread support</td></tr>
+<tr><td>AIX</td><td>aix</td><td>xlc</td><td>xlC</td><td>no thread support</td></tr>
+<tr><td>Cygwin</td><td>cygwin</td><td>gcc</td><td>g++</td><td></td></tr>
+<tr><td>HP-UX</td><td>hp-11</td><td>cc</td><td>aCC</td><td></td></tr>
+<tr><td>HP-UX</td><td>hp-11-ia64</td><td>cc</td><td>aCC</td><td></td></tr>
+<tr><td>Solaris</td><td>solaris</td><td>cc</td><td>CC</td><td></td></tr>
+</table>
+
+<p>The following example shows you how to construct a usable script with your favorite text editor.
+</p>
+
+<source>
+#!/bin/sh
+# Script to build and install Xalan-C/C++ products from sources
+
+# The Source and Target Directories for Debug Build
+
+# SourceDir="--srcdir=/opt/xalan/c/trunk"
+# DestDir="--prefix=/opt/apache/debug"
+
+# The Source and Target Directories for Release Build
+
+SourceDir="--srcdir=/opt/xalan/c/trunk"
+DestDir="--prefix=/usr/local"
+
+# The Xerces and Xalan package directories
+
+export XALANCROOT=${SourceDir}
+export XERCESCROOT=${DestDir}
+
+# If compiling with IBM-ICU support, the ICUROOT environment variable
+# needs to be defined to specify where the ICU libraries are installed.
+# Specifically, the following directories are accessed:
+# ${ICUROOT}/lib, ${ICUROOT}/include, ${ICUROOT}/data
+# export ICUROOT=/usr/local
+
+export PATH=$PATH:${SourceDir}
+
+# Debug Configure
+
+# runConfigure -p linux -d -c gcc -x g++ -P "${DestDir}" \
+# -C "--srcdir=${SourceDir}"
+
+# Release Configure
+
+runConfigure -p linux -c gcc -x g++ -P "${DestDir}" \
+ -C "--srcdir=${SourceDir}"
+
+# Connect to configured src subdirectory to build the library without
+# sample programs. If you run make from your build directory, then the
+# library and all sample programs will be built.
+
+cd src
+make clean
+make
+
+# As a user with permissions to write to ${DestDir} install the Xalan-C/C++ products
+# ${DestDir}/bin the Xalan command-line utility and sample programs
+# ${DestDir)/lib the Xalan-C/C++ static and dynamic libraries
+# ${DestDir}/include/xalanc/* The header files.
+
+make install
+
+## End of sample build script.
+</source>
+
+</s3>
+</s2>
+<anchor name="unixcompileref"/>
+<s2 title="Reference on Unix Platforms and C++ Compilers">
+
+<p>Some compilers and platforms may need configuration options and variables that differ from the default Linux build. Beware that the runConfigure script for Xalan-C/C++ is a front-end that calls the configure script. The following table is reference information for the build of Xerces-C/C++ version 3.x. The C++ compiler for Xerces should be the same as used for Xalan builds.
+</p>
+
+<table>
+<tr><th colspan="2">Configuration Options For Unix Platforms</th></tr>
+<tr><th>Solaris x86</th><th>Sun CC</th></tr>
+<tr><td colspan="2"><data>./configure CXX=CC CC=cc</data></td></tr>
+
+<tr><th>Solaris x86-64</th><th>Sun CC</th></tr>
+<tr><td colspan="2"><data>./configure CXX=cc CC=cc CFLAGS=-xarch=amd64 CXXFLAGS=-xarch=amd64</data><br/>
+(newer Sun CC versions use -m64 instead of -arch=amd64)</td></tr>
+
+<tr><th>Solaris Sparc</th><th>Sun CC</th></tr>
+<tr><td colspan="2"><data>./configure CXX=CC CC=cc</data></td></tr>
+
+<tr><th>Solaris Sparc v9</th><th>Sun CC</th></tr>
+<tr><td colspan="2"><data>./configure CXX=cc CC=cc CFLAGS=-xarch=v9 CXXFLAGS=-xarch=v9<br/>
+(newer Sun CC versions use -m64 instead of -arch=v9)</data></td></tr>
+
+<tr><th>AIX PowerPC</th><th>IBM XLC++</th></tr>
+<tr><td colspan="2"><data>./configure CXX=xlc_r CC=xlc_r<br/>
+gmake libxerces_c_1a LDFLAGS=-qmkshrobj</data></td></tr>
+
+<tr><th>AIX PowerPC-64</th><th>IBM XLC++</th></tr>
+<tr><td colspan="2"><data>./configure CXX=xlc_r CC=xlc_r CXXFLAGS=-q64 CFLAGS=-q64<br/>
+gmake libxerces_c_1a LDFLAGS=-qmkshrobj</data></td></tr>
+
+<tr><th>HP-UX 1a-64-32</th><th>HP aCC</th></tr>
+<tr><td colspan="2"><data>./configure CXX=aCC CC=aCC CFLAGS=-mt CXXFLAGS=-mt LDFLAGS=-mt</data></td></tr>
+
+<tr><th>HP-UX 1a-64</th><th>HP aCC</th></tr>
+<tr><td colspan="2"><data>./configure CXX=aCC CC=aCC CFLAGS=-mt CXXFLAGS=-"mt +DD64" LDFLAGS="-mt +DD64"</data></td></tr>
+
+<tr><th>Mac OS X x86-64</th><th>GCC</th></tr>
+<tr><td colspan="2"><data>./configure CFLAGS="-arch x86_64" CXXFLAGS="-arch x86_64"</data></td></tr>
+
+<tr><th>Mac OS X PowerPC-64</th><th>GCC</th></tr>
+<tr><td colspan="2"><data>./configure CFLAGS="-arch ppc64" CXXFLAGS="-arch ppc64"</data></td></tr>
+
+<tr><th>Mac OS X x86/PowerPC</th><th>GCC</th></tr>
+<tr><td colspan="2"><data>./configure --disable-dependency-tracking CFLAGS="arch i386 -arch ppc"<br/>
+CXXFLAGS="-arch i386 -arch ppc"</data></td></tr>
+
+<tr><th>MinGW x86</th><th>GCC</th></tr>
+<tr><td colspan="2"><data>./configure LDFLAGS=-no-undefined</data></td></tr>
+
+<tr><th>Cygwin x86</th><th>GCC</th></tr>
+<tr><td colspan="2"><data>./configure LDFLAGS=-no-undefined</data></td></tr>
+</table>
+</s2>
+
+<anchor name="xercesmodules"/>
+<s2 title="Xerces-C/C++ Transcoders and Plug-in Modules">
+<p>Xerces-C/C++ XML Parsers have undergone some additional modularity features. In the version 3 series, the transcoders are now being implemented as runtime modules. Use of the transcoding modules is still experimental for Xalan-C/C++ transformation applications. The basic transcoder capability still exists. Xerces-C/C++ version 2 series had transcoder libraries explicitly built and installed.
+</p>
+<p>A plug-in memory management architecture was introduced in Xerces-C/C++ version 2.7. The plug-in memory management of Xerces-C/C++ is also supported by Xalan-C/C++ applications.
+</p>
+</s2>
+</s1>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/download.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/download.xml?rev=1391665&r1=1391664&r2=1391665&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/download.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/download.xml Fri Sep 28 21:26:05 2012
@@ -19,131 +19,192 @@
<!DOCTYPE s1 SYSTEM "../../style/dtd/document.dtd">
<s1 title="Downloading &xslt4c;">
<anchor name="download"/>
+<p>This section is being rewritten for Xalan-C/C++ Version 1.11. You
+can find the old
+<jump href="../old/xalan-c">Version 1.10</jump> here.
+</p>
+
+<p>We are providing a source package, a documentation package, and
+some compiled binary packages.
+</p>
+
+<p>The binary packages are currently for Windows systems. We can
+use your help <jump href="buildlibs.html">creating binary packages</jump> for
+UNIX and Linux systems.
+</p>
+
+<p><em>THIS IS STILL A PRE-RELEASE PRODUCT</em></p>
+
+<p>A distribution will be mirrored and these pages updated when the packages
+become available to the general public. The current packages for download
+are in a temporary repository for developers.
+</p>
+
+<p>The subversion sources are current for Xalan-C/C++ Version 1.11 and are
+available for download using your favorite subversion <code>svn</code> program.</p>
+
+<p>Apache Xalan-C/C++ Subversion Repository is accessed here.<br/>
+<jump href="http://svn.apache.org/repos/asf/xalan/c/trunk">
+http://svn.apache.org/repos/asf/xalan/c/trunk</jump>
+</p>
+
<s2 title="Downloading what you need">
-<p>For &xslt4c-current;, we are distributing the following:
+
+<p>The Xalan-C/C++ library requires the
+<jump href="http://www.apache.org/dyn/closer.cgi/xerces/c">Xerces-C/C++ XML</jump> Parser 3.0
+or newer, version 3.1.1 is preferred.
+</p>
+
+<p>The source package contains all the scripts needed to build the
+library, sample programs, and documentation for a wide variety
+of Windows and UNIX platforms. The documentation package provides
+usable html documentation for your web browsers.
+</p>
+
+<p>Building the API Reference documents requires a current version of the
+<jump href="http://www.doxygen.org">Doxygen</jump> and
+<jump href="http://www.graphviz.org">GraphViz</jump> programs for UNIX or Linux.
+We have not tried building the API Reference on a Windows platform.
+A usable API Reference is included with the documentation package.
+</p>
+
+<s3 title="Source Packages">
+<p>We are distributing the source package for the Xalan-C/C++
+library, sample programs, and documentation. The source package
+has the StyleBook XML sources for the web pages and a Doxygen
+configuration file to construct the API Reference.
+</p>
+
+<ul>
+ <li>Xalan-C-1.11.source.tar.gz</li>
+ <li>Xalan-C-1.11.source.zip</li>
+</ul>
+</s3>
+
+<s3 title="Documentation Packages">
+<p>We are distributing a package of html web pages for the User
+Guide and interactive API Reference. The documentation package
+describes how to build and use the library for Windows and UNIX
+platforms.
+</p>
+
<ul>
- <li>32-bit and 64-bit AIX 5.1 builds with the xlC_r v6.0 compiler</li>
- <li>32-bit and 64-bit HP-UX 11 builds with the aCC v3.52 compiler</li>
- <li>32-bit Red Hat Linux AS4 build with the gcc 3.4.3 compiler</li>
- <li>32-bit and 64-bit Solaris 2.8 builds with the Forte C++ 6 Update 2 compiler</li>
- <li>64-bit SuSE Linux 8.1 for AMD-64 build with the gcc 3.2.2 compiler</li>
- <li>32-bit Windows build with the Microsoft Visual C++ 6.0 compiler with Service Pack 5</li>
+ <li>Xalan-C-1.11.docs-html.tar.gz</li>
+ <li>Xalan-C-1.11.docs-html.zip</li>
+ <li>Xalan-C-1.11.docs-api.tar.gz</li>
+ <li>Xalan-C-1.11.docs-api.zip</li>
</ul>
+</s3>
+
+<s3 title="Binary Packages">
+<p>We are distributing compiled binary packages for several
+platforms. The Xalan-C/C++ documentation is provided as a
+separate package. We would like to distribute
+binary packages for platforms that have compiled Xerces-C/C++
+distribution support.
</p>
-<!-- Leave this section in for future releases
-<p>New to the &xslt4c-current; binary distribution list, we are also providing the following:
+
+<p>The following binary packages are being prepared for distribution.</p>
+
<ul>
+ <li>Xalan-C-1.11.windows-x86-vc71.zip</li>
+ <li>Xalan-C-1.11.windows-x86-vc8.zip</li>
+ <li>Xalan-C-1.11.windows-x86-vc9.zip</li>
+ <li>Xalan-C-1.11.windows-x86-vc10.zip</li>
+ <li>Xalan-C-1.11.windows-x86_64-vc8.zip</li>
+ <li>Xalan-C-1.11.windows-x86_64-vc9.zip</li>
+ <li>Xalan-C-1.11.windows-x86_64-vc10.zip</li>
</ul>
+
+<p>We currently have no one committed to release UNIX and Linux
+binary packages. If you have scripts to build these packages,
+your help would be appreciated.
+You can contribute by posting your comments to the
+<jump href="mailto:dev@xalan.apache.org">xalan-dev</jump> mailing list.
</p>
+</s3>
+<!-- PLATFORM COMPATIBILITY TABLE GOES HERE
-->
-<p>As with previous releases, the documentation build containing this User's Guide and API documentation will be provided in
- a separate distribution.</p>
-<p>Please contact us at <human-resource-ref idref="xalandev"/> if you would like to help provide builds for other platforms.</p>
-<p>If you do not already have it, you must also download the &xml4c-used; build as indicated below.</p>
-<note>The Xalan distribution files are in <resource-ref idref="xslt4c-distdir"/>. The Xerces distribution files are in
- <resource-ref idref="xml4c-distdir"/>. Xalan documentation is provided in a separate package from the binary distribution
- files. For Windows, documentation is packaged with the file name &xslt4c-docs_dist_zip;. For UNIX, documentation is packaged
- with the file name of &xslt4c-docs_dist_targz;.</note>
-<table>
- <tr>
- <th>Xalan distribution files</th>
- <th>Xerces distribution files</th>
- <th>Platform</th>
- </tr>
- <tr>
- <td>&xslt4c-aix51v6-dist;</td>
- <td>&xml4c-aix51v6-dist;</td>
- <td>AIX 5.1 (32-bit)</td>
- </tr>
- <tr>
- <td>&xslt4c-aix51v6_64-dist;</td>
- <td>&xml4c-aix51v6_64-dist;</td>
- <td>AIX 5.1 (64 bit)</td>
- </tr>
- <tr>
- <td>&xslt4c-hpux11i-dist;</td>
- <td>&xml4c-hpux11i-dist;</td>
- <td>HP-UX 11.i (32 bit)</td>
- </tr>
- <tr>
- <td>&xslt4c-hpux11i_64-dist;</td>
- <td>&xml4c-hpux11i_64-dist;</td>
- <td>HP-UX 11.i (64 bit)</td>
- </tr>
- <tr>
- <td>&xslt4c-redhatAS4-dist;</td>
- <td>&xml4c-redhatAS4-dist;</td>
- <td>RedHat AS4 IA (32-bit)</td>
- </tr>
- <tr>
- <td>&xslt4c-solaris28-dist;</td>
- <td>&xml4c-solaris28-dist;</td>
- <td>Solaris 2.8 (32-bit)</td>
- </tr>
- <tr>
- <td>&xslt4c-solaris28_64-dist; </td>
- <td>&xml4c-solaris28_64-dist;</td>
- <td>Solaris 2.8 (64-bit)</td>
- </tr>
- <tr>
- <td>&xslt4c-suse80_AMD_64-dist; </td>
- <td>&xml4c-suse80_AMD_64-dist; </td>
- <td>SuSE 8.0 on AMD (64-bit)</td>
- </tr>
- <tr>
- <td>&xslt4c-win32-dist;<br/></td>
- <td>&xml4c-winnt-dist;<br/></td>
- <td>Windows 2000 (32-bit)<br/></td>
- </tr>
- <tr>
- <td>&xslt4c-src_dist_zip; <br/>&xslt4c-src_dist_targz;</td>
- <td></td>
- <td>ALL</td>
- </tr>
- <tr>
- <td>&xslt4c-docs_dist_zip; <br/>&xslt4c-docs_dist_targz;</td>
- <td></td>
- <td>ALL</td>
- </tr>
-</table>
+<s3 title="Platform Compatibility">
<p>The compiler version used for each platform is listed in the table below.
+The build platforms shown here have Xerces-C/C++ binary package support.
<table>
<tr>
<th>Platform - Operating System</th>
<th>Compilers</th>
</tr>
<tr>
- <td>AIX 5.1</td>
- <td>IBM C and C++ for AIX 6.00</td>
+ <td>Windows X86</td>
+ <td>VC7.1, VC8, VC9, VC10</td>
+ </tr>
+ <tr>
+ <td>Windows X86_64</td>
+ <td>VC8, VC9, VC10</td>
+ </tr>
+ <tr>
+ <td>HPUX ia64</td>
+ <td>ACC 6</td>
+ </tr>
+ <tr>
+ <td>HPUX ia64_64</td>
+ <td>ACC 6</td>
+ </tr>
+ <tr>
+ <td>AIX powerpc</td>
+ <td>xlc 7.0</td>
</tr>
<tr>
- <td>HP/UX 11.i</td>
- <td>aCC A.03.52</td>
+ <td>AIX powerpc_64</td>
+ <td>xlc 7.0</td>
</tr>
<tr>
- <td>RedHat Linux AS4</td>
- <td>gcc Compiler, version 3.4.3</td>
+ <td>SOLARIS sparc</td>
+ <td>cc 5.10</td>
</tr>
<tr>
- <td>Solaris 2.8</td>
- <td>Sun Workshop 6 update 2</td>
+ <td>SOLARIS sparc_64</td>
+ <td>cc 5.10</td>
</tr>
<tr>
- <td>SuSE 8.0</td>
- <td>gcc Compiler, version 3.2.2</td>
+ <td>SOLARIS X86</td>
+ <td>cc 5.10</td>
</tr>
<tr>
- <td>Windows NT, 2000, and XP</td>
- <td>Microsoft Visual C++ with SP5</td>
+ <td>SOLARIS X86_64</td>
+ <td>cc 5.10</td>
+ </tr>
+ <tr>
+ <td>LINUX X86</td>
+ <td>gcc 3.4</td>
+ </tr>
+ <tr>
+ <td>Linux X86_64</td>
+ <td>gcc 3.4</td>
+ </tr>
+ <tr>
+ <td>MAC OSX X86</td>
+ <td>gcc 4.0</td>
</tr>
</table>
</p>
+<p>Building for platforms other than those listed will require
+a build of the Xerces-C/C++ XML Parser library from the sources.
+Use of Xalan and Xerces libraries compiled with different versions
+of compilers may cause problems</p>
+
<note>Use GNU tar to untar the Solaris distribution file; see <link idref="faq" anchor="faq-11">A tar checksum error on Solaris
- </link>.</note>
+ </link>.
+</note>
+
<p>If you want to take advantage of the support for number formatting, sorting, and encoding the ICU provides, you should also download
and install the <resource-ref idref="icu"/>; see <link idref="usagepatterns" anchor="icu">Using the ICU</link>,</p>
+
+<p>The IBM ICU is supported with Xerces-C version 2.8. Xerces-C version 3 has introduced transcoding support modules, currently being evaluated for Xalan XSLT transcoders.
+</p>
+
<note>To access previous releases of &xslt4c;, visit the <jump href="http://archive.apache.org/dist/xml/xalan-c/">Xalan-C archive
- directory</jump>.</note>
+ directory</jump>.
+</note>
+</s3>
</s2>
-
</s1>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/faq.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/faq.xml?rev=1391665&r1=1391664&r2=1391665&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/faq.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/faq.xml Fri Sep 28 21:26:05 2012
@@ -25,8 +25,6 @@
<q>Where do I go to learn about XSLT?</q>
<a><p>The definitive sources are the W3C XSLT and XPath recommendations: <resource-ref idref="XSLT"/> and
<resource-ref idref="XPath"/>.</p>
- <p>For general questions not specific to &xslt4c;, see Dave Pawson's <resource-ref idref="dpawsonxslfaq"/> and Michael Kay's
- <jump href="http://www.wrox.com/Consumer/Store/Details.asp?ISBN=1861003129">XSLT Programmer's Reference</jump>.</p>
<p>For a brief listing of tutorials, discussion forums, and other materials, see <link idref="overview"
anchor="uptospeed">Getting up to speed with XSLT</link>.</p>
</a>
@@ -34,13 +32,16 @@
<faq title="Asking questions about &xslt4c;">
<q>Where can I ask a question?</q>
-<a><p>For generic questions about XSL stylesheets and transformations, use the <jump href="http://www.mulberrytech.com/xsl/xsl-list/">
- XSL-List -- Open Forum on XSL</jump> hosted by Mulberry Technologies. There is an archive that can be searched as well. Please
- review the archive before posting a new question.</p>
- <p>For specific questions on &xslt4c;, see xalan-c-users@xml.apache.org and xalan-dev@xml.apache.org on
- <jump href="http://archive.covalent.net/">http://archive.covalent.net/</jump>. To subscribe to these mailing lists, see
- <jump href="http://xml.apache.org/mail.html">Mailing Lists</jump>. Again, please review the archives before posting a new
- question.</p>
+<a><p>For specific questions on &xslt4c;, see list archives:
+ <jump href="http://marc.info/?l=xalan-c-users">xalan-c-users</jump>
+ and <jump href="http://marc.info/?l=xalan-dev">xalan-dev</jump>.
+ You must subscribe to these Apache mailing lists before posting your questions.</p>
+<p>The Apache Software Foundation has information on how you can subscribe to
+ the <jump href="http://www.apache.org/foundation/mailinglists.html">mailing lists</jump>.</p>
+<p>You can post messages to the lists by sending mail to:<br/>
+ <jump href="mailto:c-users@xalan.apache.org">Post message to xalan-c-users</jump>. (User's list)<br/>
+ <jump href="mailto:dev@xalan.apache.org">Post message to xalan-dev list</jump>. (Developer's list)</p>
+<p>Again, please review the archives before posting a new question.</p>
</a>
</faq>
@@ -48,7 +49,7 @@
<q>What is &xml4c; and why do I need it?</q>
<a><p>&xml4c; is a validating XML parser written in a portable subset of C++. &xml4c; makes it easy to give your application the ability
to read and write XML data. Like &xslt4c;, &xml4c; is available from the Apache XML site:
- <jump href="http://xml.apache.org/xerces-c/index.html">http://xml.apache.org/xerces-c/index.html</jump></p><!--xml4cNote--></a>
+ <jump href="http://xerces.apache.org/index.html">http://xerces.apache.org</jump></p><!--xml4cNote--></a>
</faq>
<faq title="Which version of Xerces should I be using?">
@@ -93,21 +94,30 @@
<faq title="Building on Windows">
<q>What do I need to rebuild &xslt4c; on Windows?</q>
-<a><p>In order to build &xslt4c; on Windows, you will need the supported version of &xml4c; and MS Visual C++ 6.0 installed with Service
- Pack 5 for Visual C++ and Visual Studio. In previous versions of &xslt4c;, the requirement on MS Visual C++ 6.0 was to have Service
- Pack 3 installed. In this case, you should also apply the bug fixes for the C++ standard library that shipped with Visual C++ 6.0.
- These fixes are available from the Dinkumware site: <jump href="http://www.dinkumware.com/vc_fixes.html">
- http://www.dinkumware.com/vc_fixes.html</jump>.</p>
- <p>If you do not want to apply the Dinkumware patches, or you are using a different Service Pack, you must rebuild all of the Xerces
- and Xalan binaries.</p>
- <p>For more details, see <link idref="build_instruct" anchor="win32">Steps for doing a Windows build</link>.</p>
+<a><p>In order to build Xalan-C++ on Windows, you will need the following:</p>
+<ul>
+<li>The Xalan-C/C++ source distribution package.</li>
+<li>The Xerces-C/C++ source distribution package or a compatible binary distribution package.</li>
+<li>A compatible Microsoft Visual Studio .NET (2003, 2005, 2008, 2010) software development platform.</li>
+</ul>
+<p>The Xalan-C/C++ Version 1.11 (pre-release) is available from the Apache Subversion
+ repository at <em>http://svn.apache.org/repos/asf/xalan/c/trunk/.</em></p>
+<p>After Xalan-C/C++ Version 1.11 is released, it can be downloaded from:
+ <jump href="http://www.apache.org/dyn/closer.cgi/xalan/xalan-c">Xalan Distributions</jump>.</p>
+<p>The Xerces-C/C++ Version 3.1.1 is can be downloaded from:
+ <jump href="http://www.apache.org/dyn/closer.cgi/xerces/c/3">Xerces Distributions</jump>.</p>
+<p>If you are building with the
+ <jump href="http://www.ibm.com/software/globalization/icu/">IBM-ICU</jump>
+ International Components for Unicode library, you will
+ need to rebuild both the Xerces and Xalan libraries.</p>
+<p>For more details, see <link idref="buildlibs" anchor="winbldenv">Steps for doing a Windows build</link>.</p>
</a>
</faq>
<faq title="Building on UNIX">
<q>What do I need to rebuild &xslt4c; on UNIX?</q>
<a><p>To build &xslt4c; on supported UNIX platforms, you need &xml4c;, the GNU make utility, and a supported C++ compiler. For more
- details see: <link idref="build_instruct" anchor="unix">Steps for doing a UNIX build</link>.</p>
+ details see: <link idref="buildlibs" anchor="unixbldenv">Steps for doing a UNIX build</link>.</p>
</a>
</faq>
@@ -118,11 +128,14 @@
<faq title="What is ICU">
<q>What is ICU and why do I need it?</q>
-<a><p>The International Components for Unicode(ICU) is a C and C++ library that provides robust and full-featured Unicode support on
- a wide variety of platforms. &xslt4c; uses the ICU to extend support for encoding, number formatting, and sorting.</p>
+<a><p>The <jump href="http://www.ibm.com/software/globalization/icu/">IBM-ICU</jump>
+ International Components for Unicode(ICU) is a C and C++ library that provides robust and
+ full-featured Unicode support on a wide variety of platforms.
+ &xslt4c; uses the ICU to extend support for encoding, number formatting, and sorting.</p>
<p>The ICU is available for download from <jump href="http://oss.software.ibm.com/icu/index.html">
http://oss.software.ibm.com/icu/index.html</jump>.</p>
- <p>This release of Xalan was tested with &icu-current;.</p>
+ <p>Xalan release 1.10 was tested with &icu-current;. The curent Xalan
+ release 1.11 is not fully tested with IBM-ICU.</p>
<p>For more details see: <link idref="usagepatterns" anchor="icu">Using the International Components for Unicode (ICU)</link>.</p>
<!--icuNote-->
</a>
@@ -209,7 +222,25 @@
<faq title="Submitting Patches">
<q>Who do I submit patches to?</q>
-<a><p>Your contributions are much appreciated! Please e-mail your patches to <human-resource-ref idref="xalandev"/>.</p></a>
+<a><p>Your contributions are much appreciated! You can e-mail your patches to
+ <human-resource-ref idref="xalandev"/> or raise an issue on the
+ <jump href="https://issues.apache.org/jira/browse/XALANC">Jira issue tracking system</jump>.</p>
+ <p>The Xalan projects use Jira as the issue tracking system. Any significant bug or feature request is
+ posted to this system. You must subscribe to the system in order to submit patches and raise
+ issues.</p>
+<ul>
+<li>Subscribe to Jira at:
+ <jump href="https://issues.apache.org/jira">https://issues.apache.org/jira</jump>
+</li>
+<li>Browse the issues at:
+ <jump href="https://issues.apache.org/jira/browse/XALANC">https://issues.apache.org/jira/browse/XALANC</jump>
+</li>
+</ul>
+ <p>Issues posted to the project on Jira at XALANC are automatically posted to the
+ <human-resource-ref idref="xalandev"/></p>
+ <p>Our mailing lists are moderated. You should subscribe to the mailing list in order to
+ post a message, otherwise message delivery requires manual intervention or may be dropped.</p>
+</a>
</faq>
<faq title="Transformation Output Methods">
@@ -303,8 +334,7 @@
<q>Why can't I ouput my results to a file on Windows 95/98?</q>
<a><p>Well, you can, but it doesn't always work. Neither Windows 95 or 98 are supported or tested. There have been reports of
problems on it, especially regarding Unicode support. See
- <jump href="http://marc.theaimsgroup.com/?l=xalan-dev&m=99840914524755&w=2">this post</jump> and
- <jump href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3825">this bug</jump>.</p>
+ <jump href="http://marc.info/?l=xalan-dev&m=99840914524755&w=2">this post</jump>.</p>
</a>
</faq>
@@ -329,8 +359,8 @@
<p>On Windows, the LocalMsgIndex.hpp header is generated by the Localization project. By building any project that has a
dependency on the Localization project, will trigger the Message Localization component to built and the LocalMsgIndex.hpp
to be generated.</p>
- <p>To understand more on how to build with message localization support, see <link idref="build_instruct" anchor="locale">Steps for
- Building with Message Localization Support</link>.</p>
+ <p>On Windows binary distributions, the LocalMsgIndex.hpp file is a member of the "<code>Include</code>" directory.</p>
+ <p>On Unix binary distributions, the LocalMsgIndex.hpp file is a member of the "<code>include/xalanc/PlatformSupport</code>" directory.</p>
</a>
</faq>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/getstarted.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/getstarted.xml?rev=1391665&r1=1391664&r2=1391665&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/getstarted.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/getstarted.xml Fri Sep 28 21:26:05 2012
@@ -27,6 +27,9 @@
<li><link anchor="commandline">Performing your own transformations from the command line</link></li>
<li><link anchor="apps">Setting up your own XSLT applications</link></li>
</ul>
+<p>This section is being rewritten.
+<jump href="index.html#getstarted">See: new getting started</jump>
+</p>
<anchor name="download"/>
<s2 title="Downloading what you need">
<p>For &xslt4c-current;, we are distributing the following:
@@ -53,6 +56,7 @@
<resource-ref idref="xml4c-distdir"/>. Xalan documentation is provided in a separate package from the binary
distribution files. For Windows, documentation is packaged with the file name &xslt4c-docs_dist_zip;. For UNIX,
documentation is packaged with the file name of &xslt4c-docs_dist_targz;.</note>
+<br/>
<table>
<tr>
<th>Xalan distribution files</th>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/history.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/history.xml?rev=1391665&r1=1391664&r2=1391665&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/history.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/history.xml Fri Sep 28 21:26:05 2012
@@ -16,6 +16,32 @@
* limitations under the License.
-->
+<s3 title="Changes for &xslt4c; version 1.11">
+<p>This is a general bug fix release with added stability features.</p>
+<p>Major updates since version 1.10 include:</p>
+<ul>
+ <li>Add support for Xerces-C 3.0 and newer</li>
+ <li>Drop support for Microsoft Studio (VC6)</li>
+ <li>Fix support issues for AIX 5.3</li>
+ <li>Fix support issues for Solaris 2.8</li>
+ <li>Fix support issues for GCC-4.3</li>
+ <li>Add support for Microsoft .NET 2008 (VC9) </li>
+ <li>Add support for Microsoft .NET 2010 (VC10)</li>
+ <li>Add number and nodeset types as top-level stylesheet parameters</li>
+ <li><link anchor="bugfix11">Bugs fixed in this release</link>.</li>
+</ul>
+</s3>
+
+<s3 title="Changes for &xslt4c; version 1.10">
+<p>Major updates since version 1.9 include:</p>
+<ul>
+ <li>Support for XML 1.1 and Namespaces in XML 1.1.</li>
+ <li>Added support for IBM XLC 7.0 compiler on AIX.</li>
+ <li>Improved and stabilized C pluggable memory management functionality.</li>
+ <li>Various improvements in Xalan XML serializers for better performance and stability.</li>
+ <li>Upgrade from Xerces-C 2.6 to Xerces-C 2.7.</li>
+ </ul>
+</s3>
<s3 title="Changes for &xslt4c; version 1.9">
<p>Major updates since version 1.8 include:</p>
@@ -59,9 +85,11 @@
<li>Porting of conf utility to the UNIX platform. The conf utility is a test harness designed to run the conformance tests located under the xml-xalan/test/tests directory. After the tests have been run, a results report is generated in HTML format for easy viewing. For more information on how to use this tool, please see <link idref="commandline" anchor="confexe">"Using the command line utility"</link>.</li>
-->
<li>Implemented optimizations to significantly improve the throughput of the ICU-enabled "format-number" function.</li>
- <li>Changes in the XML Serializer. The serializer will no longer put a newline after the xml header tag unless indent="yes". See bugzilla
+ <li>Changes in the XML Serializer. The serializer will no longer put a newline after the xml header tag unless indent="yes".</li>
+<!-- See bugzilla
<jump href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24304">24304</jump> and
- <jump href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=28386">28386</jump>.</li>
+ <jump href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=28386">28386</jump>.
+-->
</ul>
</s3>
<s3 title="Changes for &xslt4c; version 1.7">
@@ -154,30 +182,30 @@
<p>In addition to adding to the list of platforms on which &xslt4c; builds, our focus for this release has been on bug fixes, performance enhancements,
and providing a simplified C++ and C API for performing standard transformations. Major updates since version 1.0 include:</p>
<ul>
- <li>Added HP-UX 11 build.<br/><br/></li>
- <li>Added Solaris build.<br/><br/></li>
- <li>Greatly improved performance.<br/><br/></li>
- <li>Improved conformance to the XSLT specification.<br/><br/></li>
+ <li>Added HP-UX 11 build.</li>
+ <li>Added Solaris build.</li>
+ <li>Greatly improved performance.</li>
+ <li>Improved conformance to the XSLT specification.</li>
<li>Simplified the C++ API and provided a C API for performing standard transformations with the <link idref="usagepatterns"
- anchor="xalantransformer">XalanTransformer</link> class and associated header files.<br/><br/></li>
+ anchor="xalantransformer">XalanTransformer</link> class and associated header files.</li>
<li>Added sample illustrating use of XalanTransformer and the new C++ API:
- <link idref="samples" anchor="xalantransform">XalanTransform</link>.<br/><br/></li>
+ <link idref="samples" anchor="xalantransform">XalanTransform</link>.</li>
<li>Added sample illustrating use of XalanTransformer, the new C API, and how to run &xslt4c; and perform transformations on an
- Apache Web server: <link idref="samples" anchor="apachemodulexslt">ApacheModuleXSLT</link>.<br/><br/></li>
- <li>Added the <link idref="samples" anchor="streamtransform">StreamTransform</link> sample.<br/><br/></li>
- <li>Eliminated dependencies on non-public Xerces headers; accordingly can now build with the Xerces distribution.<br/><br/></li>
- <li>Fixed namespace mapping and inheritance problems.<br/><br/></li>
- <li>Fixed failure of <copy-of ...> to include CRLFs (if any) in the result.<br/><br/></li>
- <li>Fixed bug sorting in reverse document order based on position. <br/><br/></li>
- <li>Fixed <xsl:number> bug with use of letter-value="traditional" for "classical" Greek numbering.<br/><br/></li>
- <li>Fixed use of <xsl:fallback> within a top-level extension function.<br/><br/></li>
- <li>Fixed HTML output method bug. The <HEAD> element was not including a <META> tag with the encoding.<br/><br/></li>
- <li>Fixed bug using key() in match patterns to find descendants.<br/><br/></li>
- <li>Fixed bug using the id() function in complex match patterns.<br/><br/></li>
- <li>Fixed problem outputting multiple single-character CDATA sections.<br/><br/></li>
- <li>Fixed problem outputting whitespace characters.<br/><br/></li>
- <li>Fixed problem transforming from a stream on UNIX platforms.<br/><br/></li>
- <li>Fixed a bug with the document() function, which was generating a syntax error if called in the following manner: document(<ref>string</ref>,/).<br/><br/></li>
+ Apache Web server: <link idref="samples" anchor="apachemodulexslt">ApacheModuleXSLT</link>.</li>
+ <li>Added the <link idref="samples" anchor="streamtransform">StreamTransform</link> sample.</li>
+ <li>Eliminated dependencies on non-public Xerces headers; accordingly can now build with the Xerces distribution.</li>
+ <li>Fixed namespace mapping and inheritance problems.</li>
+ <li>Fixed failure of <copy-of ...> to include CRLFs (if any) in the result.</li>
+ <li>Fixed bug sorting in reverse document order based on position. </li>
+ <li>Fixed <xsl:number> bug with use of letter-value="traditional" for "classical" Greek numbering.</li>
+ <li>Fixed use of <xsl:fallback> within a top-level extension function.</li>
+ <li>Fixed HTML output method bug. The <HEAD> element was not including a <META> tag with the encoding.</li>
+ <li>Fixed bug using key() in match patterns to find descendants.</li>
+ <li>Fixed bug using the id() function in complex match patterns.</li>
+ <li>Fixed problem outputting multiple single-character CDATA sections.</li>
+ <li>Fixed problem outputting whitespace characters.</li>
+ <li>Fixed problem transforming from a stream on UNIX platforms.</li>
+ <li>Fixed a bug with the document() function, which was generating a syntax error if called in the following manner: document(<ref>string</ref>,/).</li>
<li>Fixed named templates bug accepting global parameter when called with a parameter of the same name that the named template does not
recognize.</li>
</ul>
@@ -185,25 +213,24 @@
<s3 title="Changes for &xslt4c; version 1.0">
<p>Major updates since version 0.40.0 include:</p>
<ul>
- <li>Full support for namespace handling<br/><br/></li>
- <li>Full implementation of the format-number() function and support for the decimal-format element<br/><br/></li>
- <li>Integration with the <resource-ref idref="icu"/> for number formatting, sorting, and output encoding<br/><br/></li>
- <li>Support for the exclude-result-prefixes attribute<br/><br/></li>
+ <li>Full support for namespace handling</li>
+ <li>Full implementation of the format-number() function and support for the decimal-format element</li>
+ <li>Integration with the <resource-ref idref="icu"/> for number formatting, sorting, and output encoding</li>
+ <li>Support for the exclude-result-prefixes attribute</li>
<li>Support for the output encoding attribute</li>
</ul>
</s3>
<s3 title="Changes for &xslt4c; version 0.40.0">
<p>Major updates since version 0.30.0 include:</p>
<ul>
- <li>Permitting OS file names (as well as URLs) as command-line arguments with TestXSLT<br/><br/></li>
- <li>Stricter compliance for HTML and XML output<br/><br/></li>
- <li>Improved handling of relative URI's<br/><br/></li>
- <li>Improved handling of Import and Include<br/><br/></li>
- <li>Better namespace handling (although there are still problems here)<br/><br/></li>
- <li>Support for Document() function<br/><br/></li>
- <li>Support for XPath predicates<br/><br/></li>
- <li>Better handling of parameters to stylesheet and templates<br/><br/></li>
- <li>Full implementation of axes ( with the exception of namespace:: )<br/><br/></li>
+ <li>Permitting OS file names (as well as URLs) as command-line arguments with TestXSLT</li>
+ <li>Stricter compliance for HTML and XML output</li>
+ <li>Improved handling of relative URI's</li>
+ <li>Improved handling of Import and Include</li>
+ <li>Better namespace handling (although there are still problems here)</li>
+ <li>Support for Document() function</li>
+ <li>Support for XPath predicates</li>
+ <li>ProblemListener with a different output stream and call
+ XalanTransformer::setProblemListener() before calling XalanTransformer::transform().</li>
</ul>
</s3>
-
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/index.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/index.xml?rev=1391665&r1=1391664&r2=1391665&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/index.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/index.xml Fri Sep 28 21:26:05 2012
@@ -20,30 +20,281 @@
<!DOCTYPE s1 SYSTEM "../../style/dtd/document.dtd">
<s1 title="&xslt4c-current;">
-<s2 title="What is it?">
-<p>Xalan is an XSLT processor for transforming XML documents into HTML, text, or other XML document types.</p>
-<p>&xslt4c-current; is a robust implementation of the W3C Recommendations for XSL Transformations (XSLT) and the XML Path
- Language (XPath). It works with a compatible release of the &xml4c; XML parser: &xml4c-used;. The focus for this release is on
- bug fixes, pluggable memory management, and enhanced stability improvements in stylesheet execution. For the details, see
- <link idref="whatsnew">What's New In This Release</link>.</p>
-</s2>
-
-
-<s2 title="How do I get it?">
-<p>Download and unzip the &xslt4c; distribution file and the corresponding &xml4c; distributions file for your platform. For the
- details, see <link idref="download">Downloading &xslt4c;</link>. The &xslt4c; distribution includes
- source-only distribution, documentation, sample applications, the complete &xslt4c; source tree.</p>
-<p>Binary distributions are also available for a limited set of platforms.</p>
-</s2>
-
-<s2 title="How about support for internationalization?">
-<p>To extend Unicode support for encoding, number formatting, and sorting, you can download, build, and integrate the
- <resource-ref idref="icu"/> with &xslt4c;. See <link idref="usagepatterns" anchor="icu">Using the ICU</link>.</p>
-</s2>
-
-<s2 title="For more information...">
-<p>For more information, go to the <link idref="overview">&xslt4c; Overview</link> and <link idref="whatsnew">What's New In this
- Release</link>. All of the Xalan documentation on this website is included in the Xalan downloads, as are a number of samples
- to help you start using Xalan to transform XML documents.</p>
-</s2>
+
+<ul>
+<li><link anchor="licenses">Licenses</link></li>
+<li><link anchor="getinvolved">Getting Involved</link></li>
+<li><link anchor="xsltStandards">XSLT Standards Implemented</link></li>
+<li><link anchor="xmlParserLib">XML Parser Library</link></li>
+<li><link anchor="securityIssues">Security Issues</link></li>
+<li><link anchor="getstarted">Getting Started</link></li>
+<li><link anchor="getWhatNeeded">Getting What You Need</link></li>
+</ul>
+<p>The old Xalan-C/C++ 1.10 release can be found at
+<jump href="../old/xalan-c/index.html">xml.apache.org/xalan-c</jump>.</p>
+
+<anchor name="whatisxalan"/>
+<s2 title="What Is Xalan?">
+
+<p>Xalan is an XSLT processor for transforming XML documents
+into HTML, text, or other XML document types.
+It uses for input an XML document and an XSLT stylesheet.
+The engine also supports the entry of top-level stylesheet parameters.
+Documentation exists on how to extend the library with
+your own custom XPath functions.
+</p>
+<p>Xalan-C++ version 1.11 is a robust implementation of the
+W3C Recommendations for
+<jump href="http://www.w3.org/TR/xslt">XSL Transformations (XSLT)</jump>
+and the
+<jump href="http://www.w3.org/TR/xpath">XML Path Language (XPath)</jump>.
+It works with the
+<jump href="http://xerces.apache.org/xerces-c">Xerces-C++ version 3.1.1</jump>
+release of XML parsers.
+The focus for this Xalan release is on bug fixes and
+compatibility with newer development platforms.
+</p>
+<p>The Xalan-C/C++ project creates and distributes a
+standard XSLT library and a simple Xalan command-line
+utility for transforming XML documents.
+</p>
+<p>This project is written in a reduced set of the C++ programming language.
+This makes the library directly usable on numerous platforms.
+A set of 'C' language APIs is also available so that
+XSLT and XPath functionality is easily deployed to 'C' language applications.
+</p>
+<p><jump href="samples.html">Sample programs</jump> are available
+for you to test and experiment with as you learn the Xalan library.
+</p>
+<p>Some of the <jump href="http://www.exslt.org">EXSLT extension functions</jump>
+for XPath are available.
+We need to write and validate more of the EXSLT functions.
+Apache also provides some of their own
+<jump href="extensionslib.html">XPath extensions</jump> for use.
+Documentation and examples are available for you to write
+your own custom <jump href="extensions.html">XPath extensions</jump>.
+</p>
+<p>There is a library of <jump href="extensionslib.html">XPath extensions</jump>
+that are provided by the Apache Xalan community.
+</p>
+</s2>
+
+<anchor name="licenses"/>
+<s2 title="Licenses">
+
+<p>The Xalan-C/C++ software conforms to The Apache Software Foundation
+<jump href="license.html">License, Version 2.0</jump>.
+</p>
+</s2>
+
+<anchor name="getinvolved"/>
+<s2 title="Getting Involved">
+
+<p>You are invited to participate in
+<jump href="http://www.apache.org/foundation/getinvolved.html">The Apache Software Foundation</jump>.
+You will need to subscribe if you wish to receive mail from the lists.
+Some lists require a subscription in order to post messages.
+</p>
+<p>The <jump href="mailto:dev@xalan.apache.org">xalan-dev</jump> mailing list
+is used to communicate product development issues with the software development team.
+The xalan-dev messages are
+<jump href="http://mail-archives.apache.org/mod_mbox/xml-xalan-dev">archived here</jump>
+and on <jump href="http://marc.info/?l=xalan-dev">Marc.info</jump>.
+</p>
+<p>The <jump href="mailto:c-users@xalan.apache.org">xalan-c-users</jump> mailing list
+is used to discuss issues regarding the use of the Xalan-C/C++ software and libraries.
+The xalan-c-users messages are
+<jump href="http://mail-archives.apache.org/mod_mbox/xml-xalan-c-users">archived here</jump>
+and on <jump href="http://marc.info/?l=xalan-c-users">Marc.info</jump>.
+</p>
+<p>The subversion repository changes are logged on the xalan-cvs mailing list and are
+<jump href="http://mail-archives.apache.org/mod_mbox/xml-xalan-cvs">archived here</jump>
+and on <jump href="http://marc.info/?l=xalan-cvs">Marc.info</jump>.
+</p>
+<p>You can review the project sources and change history in the subversion repository at
+<jump href="http://svn.apache.org/viewvc/xalan/c">http://svn.apache.org/viewvc/xalan/c</jump>.
+</p>
+<p>You can get a private copy of the subversion snapshot of the development sources at
+<jump href="http://svn.apache.org/repos/asf/xalan/c/trunk">http://svn.apache.org/repos/asf/xalan/c/trunk</jump>
+using your favorite SVN program.
+</p>
+<p>The JIRA system is used for issue tracking.
+You must create an account before you can post messages and files to the JIRA tracking system.
+You can view the issues at
+<jump href="https://issues.apache.org/jira/browse/XALANC">https://issues.apache.org/jira/browse/XALANC</jump>.
+</p>
+</s2>
+
+<anchor name="xsltStandards"/>
+<s2 title="XSLT Standards Implemented">
+
+<p>Xalan-C/C++ implements the following specifications from the World Wide Web Consortium (W3C).
+</p>
+<ul>
+<li><jump href="http://www.w3.org/TR/xslt">XSL Transformations (XSLT) Version 1.0</jump></li>
+<li><jump href="http://www.w3.org/TR/xpath">XML Path Language (XPath) Version 1.0</jump></li>
+<li><jump href="http://www.w3.org/TR/xml-stylesheet">Associating Style Sheets with XML documents 1.0 (Second Edition)</jump></li>
+</ul>
+
+<p>The next major release of Xalan-C/C++ will hopefully be compatible with following standards. This added support will require a major version change from 1 to 2.
+</p>
+<ul>
+<li><jump href="http://www.w3.org/TR/xslt20">XSL Transformations (XSLT) Version 2.0</jump></li>
+<li><jump href="http://www.w3.org/TR/xslt-xquery-serialization">XSLT 2.0 and XQuery 1.0 Serialization</jump></li>
+<li><jump href="http://www.w3.org/TR/xpath20">XML Path Language (XPath) Version 2.0 (Second Edition)</jump></li>
+<li><jump href="http://www.w3.org/TR/xquery-semantics">XQuery 1.0 and XPath 2.0 Formal Semantics (Second Edition)</jump></li>
+<li><jump href="http://www.w3.org/TR/xpath-datamodel">XQuery 1.0 and XPath 2.0 Data Model (XDM) (Second Edition)</jump></li>
+<li><jump href="http://www.w3.org/TR/xpath-functions">XQuery 1.0 and XPath 2.0 Functions and Operators (Second Edition)</jump></li>
+</ul>
+
+</s2>
+
+<anchor name="xmlParserLib"/>
+<s2 title="XML Parser Library">
+
+<p>Xalan-C/C++ uses the The Apache Software Foundation Xerces-C project that implements parsers for XML 1.0 and XML 1.1.
+The following standards as specified by the
+<jump href="http://www.w3.org/TR">World Wide Web Consortium (W3C)</jump> are implemented by the
+<jump href="http://xerces.apache.org/xerces-c">Xerces-C</jump> XML parser library.
+</p>
+<ul>
+<li><jump href="http://www.w3.org/TR/xml">Extensible Markup Language (XML) 1.0 (Third Edition) - currently (Fifth Edition)</jump></li>
+<li><jump href="http://www.w3.org/TR/xml11">Extensible Markup Language (XML) 1.1 (First Edition) - currently (Second Edition)</jump></li>
+<li><jump href="http://www.w3.org/TR/xml-id">xml:id Version 1.0</jump></li>
+<li><jump href="http://www.w3.org/TR/xmlbase">XML Base (Second Edition)</jump></li>
+<li><jump href="http://www.w3.org/TR/xml-infoset">XML Information Set (Second Edition)</jump></li>
+<li><jump href="http://www.w3.org/TR/xml-names">Namespaces in XML 1.0 (Third Edition)</jump></li>
+<li><jump href="http://www.w3.org/TR/xml-names11">Namespaces in XML 1.1 (Second Edition)</jump></li>
+<li><jump href="http://www.w3.org/TR/xmlschema-1">XML Schema Part 1: Structures Second Edition</jump></li>
+<li><jump href="http://www.w3.org/TR/xmlschema-2">XML Schema Part 2: Datatypes Second Edition</jump></li>
+<li><jump href="http://www.w3.org/TR/REC-DOM-Level-1">Document Object Model (DOM) Level 1</jump></li>
+<li><jump href="http://www.w3.org/TR/ElementTraversal">Element Traversal Specification</jump></li>
+<li><jump href="http://www.w3.org/TR/DOM-Level-2-Core">Document Object Model (DOM) Level 2 Core Specification</jump></li>
+<li><jump href="http://www.w3.org/TR/DOM-Level-2-Traversal-Range">Document Object Model (DOM) Level 2 Traversal and Range Specification</jump></li>
+<li><jump href="http://www.w3.org/TR/DOM-Level-3-Core">Document Object Model (DOM) Level 3 Core Specification</jump></li>
+<li><jump href="http://www.w3.org/TR/DOM-Level-3-Val">Document Object Model (DOM) Level 3 Validation Specification</jump></li>
+<li><jump href="http://www.w3.org/TR/DOM-Level-3-LS">Document Object Model (DOM) Level 3 Load and Save Specification</jump></li>
+<li><jump href="http://www.w3.org/TR/xinclude">XML Inclusions (XInclude) 1.0 (Second Edition)</jump></li>
+</ul>
+<p>The Xerces-C/C++ also supports the <jump href="http://sax.sourceforge.net/">SAX 1.0 and SAX 2.0</jump> projects.
+SAX is primarily Java based. The Xerces-C/C++ project has implemented a SAX C++ API that looks much like the SAX Java API.
+</p>
+<p>Web Services and Web Security recommendations have been developed by the
+<jump href="http://www.w3.org">World Wide Web Consortium (W3C)</jump> and
+<jump href="http://www.oasis-open.org">OASIS-OPEN</jump> Advancing open standards for the information society.
+The Xerces-C/C++ has support for custom entity resolvers which are inherited and
+supported by the Xalan-C/C++ library.
+</p>
+</s2>
+
+<anchor name="securityIssues"/>
+<s2 title="Security Issues">
+
+<p>The Xalan-C/C++ library has hooks so that custom entity resolvers can be deployed.
+The entity resolvers are actually interfaces into the Xerces-C/C++ XML Parser Library.
+Use of trusted entity resolvers greatly increases the security of XML based applications.
+</p>
+<p>The Web Services Architecture uses specifications and recommendations
+that are documented by the following organizations.
+</p>
+<ul>
+<li>World Wide Web Consortium (W3C)<br/>
+ [<jump href="http://www.w3.org">http://www.w3.org]</jump>]</li>
+<li>Advancing open standards for the information society (OASIS-OPEN)<br/>
+ [<jump href="http://www.oasis-open.org">http://www.oasis-open.org</jump>]</li>
+<li>The Sourceforge SAX Project (SAX1, SAX2)<br/>
+ [<jump href="http://sax.sourceforge.net">http://sax.sourceforge.net</jump>]</li>
+<li>Internet Engineering Task Force (IETF)<br/>
+ [<jump href="http://www.ietf.org">http://www.ietf.org</jump>]</li>
+</ul>
+<p>There are some <jump href="secureweb.html">architecture security</jump> issues
+that should be addressed by any XML parser or XSLT transformation application.
+Other than validating and cleaning the content of XML elements,
+the access to untrusted external entities is a big problem for security management.
+</p>
+<p>The "Xalan" comman-line transformation program does not deploy
+an OASIS catalog or perform other security measures.
+URLs are resolved using the system directory of the local machine
+and DNS to resolve host locations.
+The "Xalan" program should be used only with
+trusted XSLT stylesheets and XML documents on a trusted computer.
+</p>
+<p>A future release of the "Xalan" command-line transformation program
+may include support for an OASIS entity resolver catalog.
+</p>
+<p>Information on creating Secure Web Service Applications is useful for review.
+This <jump href="secureweb.html">security overview document</jump> goes beyond the scope of
+XSLT transformations and asks many pertinent security based questions.
+</p>
+</s2>
+
+<anchor name="getstarted"/>
+<s2 title="Getting Started">
+
+<p>The source code and documentation are delivered in separate packages.
+Binary packages comprise the compiled libraries, the Xalan command line utility, and the C/C++ header files.
+The documentation package contains the pre-built documentation.
+The source package contains the sources to build everything.
+</p>
+<p>The current Xalan-C/C++ Version 1.11 is compatible with the stable releases of
+<jump href="http://xerces.apache.org/xerces-c">Xerces-C/C++</jump> Version 3.0 and newer. The current stable release for Xerces-C/C++ is 3.1.1.
+</p>
+<p>The previous Xalan-C/C++ Version 1.10 works with Xerces-C/C++ Versions 2.7.0 and 2.8.0.
+</p>
+<p>If you are having problems using the product,
+send your comments to the <jump href="mailto:c-users@xalan.apache.org">xalan-c-users</jump> mail list.
+</p>
+<p>If you think a change needs to be made or have suggestions for future releases,
+send your comments to the <jump href="mailto:dev@xalan.apache.org">xalan-dev</jump> mail list.
+</p>
+<p>Binary releases are not yet available.
+We would like to distribute Xalan-C/C++ Version 1.11 binary releases
+using the same platforms specified for the compatible Xerces-C binary packages.
+</p>
+</s2>
+
+<anchor name="getWhatNeeded"/>
+<s2 title="Getting What You Need">
+
+<p>What you need depends whether you plan to
+build from the sources or download prebuilt packages.
+</p>
+<p>The development platform used to build the Xalan-C/C++ (XSLT) library
+should be the same as the platform used to build the Xerces-C/C++ (XML) parser library.
+</p>
+<p>Xalan-C/C++ (XSLT) library requires a working Xerces-C/C++ (XML) parser library.
+The supported versions of Xerces-C/C++ version 3.0 or newer. Version 3.1.1
+is recommended.
+</p>
+<p>If you are ambitious and willing to experiment,
+you can download the bleeding edge development from the
+Apache Software Foundation subversion repositories.
+Use your favorite subversion 'svn' utility for download.
+</p>
+<table>
+<tr><td>Xalan-C Repository</td><td>http://svn.apache.org/repos/asf/xalan/c/trunk</td></tr>
+<tr><td>Xerces-C Repository</td><td>http://svn.apache.org/repos/asf/xerces/c/trunk</td></tr>
+</table>
+
+<p>The current stable
+<jump href="http://xerces.apache.org/xerces-c/download.cgi">Xerces-C/C++ (XML) packages</jump>
+are available for download.
+</p>
+<note>The sources from the Xalan-C repository are current for Version 1.11
+until released packages are available.
+You can help us prepare for a Version 1.11 release
+by providing packages for your platforms
+and let us know of your building issues.
+</note><br/>
+
+<p>The previous version packages can still be downloaded until officially replaced.
+</p>
+<table>
+<tr><td>Xalan-C Version 1.10</td><td><jump
+href="http://www.apache.org/dyn/closer.cgi/xml/xalan-c/">Xalan Package Downloads</jump></td></tr>
+<tr><td>Xerces-C Version 2.7</td><td><jump
+href="http://www.apache.org/dyn/closer.cgi/xml/xerces-c/">Xerces Package Downloads</jump></td></tr>
+</table>
+
+</s2>
</s1>
Modified: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/install.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/install.xml?rev=1391665&r1=1391664&r2=1391665&view=diff
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/install.xml (original)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/install.xml Fri Sep 28 21:26:05 2012
@@ -18,56 +18,173 @@
* limitations under the License.
-->
<s1 title="Installing &xslt4c;">
-<s2 title="Setting up the path/library path">
-<ul>
- <li><link anchor="windowspath">For Windows</link></li>
- <li><link anchor="unixpath">For UNIX</link></li>
-</ul>
-<anchor name="windowspath"/>
-<s3 title="For Windows">
-<p>To use the Windows binary distribution, you must place the Xalan executables and the Xalan and Xerces libraries on the path:</p>
-<ul>
- <li>Put &xslt4c-dist;-<my_Windows_distribution>\bin and &xml4c-dist;-<my_Windows_distribution>\bin on the path.</li>
-</ul>
-<p>The Visual C++ Xalan project included with the Windows release knows the relative paths to the Xalan headers and libraries, but it
- does not know where you have unzipped the Xerces distribution. If you plan to use Visual C++ to build Xalan applications or <link
- idref="build_instruct" anchor="rebuild">rebuild Xalan</link>, you must also provide Visual C++ with access to the Xerces headers and libraries.</p>
-<p>Use the Visual C++ Tools menu to open the Options dialog box, go to the Directories tab, and do the following:</p>
<ul>
- <li>Add the path to &xml4c-dist;-<my_Windows_distribution>\include to the list of directories of Include files.</li>
- <li>Add the path to &xml4c-dist;-<my_Windows_distribution>\lib to the list of directories of Library files.</li>
+ <li><link anchor="SourcePkgs">Install Source Packages</link></li>
+ <li><link anchor="BinaryPkgs">Install Binary Packages</link></li>
+ <ul>
+ <li><link anchor="InsWin">Install Windows Packages</link></li>
+ <li><link anchor="InsUnx">InstallUNIX Packages</link></li>
+ <li><link anchor="InsPkgs">Other Packages</link></li>
+ </ul>
+ <li><link anchor="XalanDocPkg">Install Documentation Packages</link></li>
+ <ul>
+ <li><link href="DocWebPkg">Xalan-C User Guide</link></li>
+ <li><link href="DocApiPkg">Xalan-C API Reference</link></li>
+ </ul>
</ul>
+
+<p>A pre-requisite for using the Xalan-C/C++ XSLT library is to
+ have a working Xerces-C/C++ XML Parser library. Xerces-C/C++
+ must be of version 3.0 or newer. Xerces-C/C++ Version 3.1.1 is preferred.
+</p>
+<p>The Xalan-C/C++ project is providing several types of packages.
+</p>
+<p>Source packages contain all of the source code to build the
+ Xalan-C/C++ library, the sample programs, and the documentation.
+ There are UNIX scripts and Windows project files by which the
+ library and sample programs can be built.
+ There are also scripts for building the User Guide web pages and
+ a Doxygen configuration for building the interactive API Reference.
+</p>
+<p>Binary packages contain compiled libraries and the Xalan
+ command line program. The binary packages also contain C/C++
+ header files for basic software development.
+</p>
+<p>Documentation packages contain pre-built directories of web
+ page html files for the Xalan-C/C++ User Guide and the interactive
+ API Reference for programmers.
+</p>
+
+<anchor name="SourcePkgs"/>
+<s2 title="Install Source Packages">
+<p>We have no package managers for source packages. You just extract
+ the contents of the distribution <ref>zip</ref> file or <ref>tar</ref> file
+ into a source directory of your choosing.
+</p>
+<p>You also need to have the necessary C/C++ compiler tools installed
+ and a working copy of the Xerces-C/C++ XML parser library.
+</p>
+<p>Building the
+ <link idref="builddocs" anchor="buildweb">User Guide</link>
+ from sources requires a working Xalan command line program.
+</p>
+<p>Building the interactive
+ <link idref="builddocs" anchor="buildapi">API Reference</link>
+ requires a UNIX or Linux system with a current copy of
+ Doxygen and GraphViz installed.
+</p>
+
+<p>The building of a library from sources results in a directory from which
+ a binary package can be made.
+ <link idref="buildlibs" anchor="unixbldenv">UNIX and Linux builds</link>
+ are automatically targeted to an install destination.
+ <link idref="buildlibs" anchor="winbldinst">Installing a Windows build</link>
+ requires that the specific compiled products be copied to a usable
+ destination directory.
+</p>
+
+</s2>
+<anchor name="BinaryPkgs"/>
+<s2 title="Install Binary Packages">
+<p>The binary packages distributed by <ref>zip</ref> files
+ and <ref>tar</ref> files are usually extracted to the install
+ <code>{target}</code> directory.
+ After extracting the contents, you then need to manually perform
+ some minor system configuration.
+</p>
+<p>Packages that are handled by a package manager are usually
+ installed and configured according to package maintainer.</p>
+
+<anchor name="InsWin"/>
+<s3 title="Install Windows Packages">
+<p>The Xalan-C and Xerces-C packages can be installed to the same
+ <code>{target}</code>
+ directory tree. The debug and release builds have different names
+ for the shared <code>*.DLL</code> files.
+</p>
+<p>Windows operating systems require that the <code>{target}\bin</code>
+ directory be added to the PATH environment. You can make the path
+ a permanent part of the SYSTEM or user login DESKTOP environment.
+ The PATH environment variable should contain an entry
+ where the <code>{target}\bin\*.DLL</code> files are found.
+</p>
+<ol>
+ <li>Right-Click on the computer icon.</li>
+ <li>Select Properties.</li>
+ <li>Select Advanced System Settings.</li>
+ <li>Select Environment Variables.</li>
+ <li>Add the <code>{target}\bin</code> directory to the
+ system PATH environment variable.</li>
+</ol>
+<p>The XP, NT, 2000 and 2003 systems allow environment variables to be
+ set explicitly to individual user accounts.
+ The Vista, Win-7, and 2008 systems have security administration that
+ gets in the way of updating individual user environments.
+</p>
+<p>In a command window or a command environment, you can add the following
+ shell command to set a temporary path to the XALAN <code>{target}\bin</code>
+ directory.
+</p>
+<source>set PATH=%PATH%;{target}\bin</source>
+
+</s3>
+<anchor name="InsUnx"/>
+<s3 title="Install UNIX Packages">
+ <p>The path to the <code>Xalan</code> command line executable program should be added
+ to the PATH environment variable.</p>
+ <p>The path to the shared objects should be added to the system
+ configuration or overridden by specific entry in an environment
+ by which shared objects can be found.</p>
+<p>Here is some more detailed information on
+ <link idref="buildlibs" anchor="unixlibpath">UNIX Runtime</link> configuration.
+</p>
</s3>
+<anchor name="InsPkgs"/>
+<s3 title="Install Other Packages">
+<p>These packages are usually installed and configured by a package manager.
+ You should refer to the documentation provided by the package maintainer.
+</p>
-<anchor name="unixpath"/>
-<s3 title="For UNIX">
-<p>To use one of the UNIX binary distributions, you must place the &xslt4c; executable on the path, and the &xslt4c; and &xml4c;
- libraries on the library path.</p>
-<p>For the &xslt4c; AIX distributions:</p>
-<ul>
- <li>Put &xslt4c-dist;-<my_AIX_distribution>/bin on the path (PATH).</li>
- <li>Put &xslt4c-dist;-<my_AIX_distribution>/lib and &xml4c-dist;-<my_AIX_distribution>/lib on the library path (LIBPATH),
- or copy the shared libraries to /usr/lib.</li>
-</ul>
-<p>For the &xslt4c; HP-UX 11 distributions:</p>
-<ul>
- <li>Put &xslt4c-dist;-<my_HPUX_distribution>/bin on the path (PATH).<br/><br/></li>
- <li>Put &xslt4c-dist;-<my_HPUX_distribution>/lib and &xml4c-dist;-<my_HPUX_distribution>/lib on the library path
- (SHLIB_PATH), or copy the shared libraries to /usr/lib.</li>
-</ul>
-<p>For the &xslt4c; Solaris distributions:</p>
-<ul>
- <li>Put &xslt4c-dist;-<my_Solaris_distribution>/bin on the path (PATH).<br/><br/></li>
- <li>Put &xslt4c-dist;-<my_Solaris_distribution>/lib and &xml4c-dist;-<my_Solaris_distribution>/lib on the library path
- (LD_LIBRARY_PATH), or copy the shared libraries to /usr/lib.</li>
-</ul>
-<p>For the &xslt4c; RedHat and SuSE Linux distributions:</p>
-<ul>
- <li>Put &xslt4c-dist;-<my_Linux_distribution>/bin on the path (PATH).</li>
- <li>Put &xslt4c-dist;-<my_Linux_distribution>/lib and &xml4c-dist;-<my_Linux_distribution>/lib on the library path
- (LD_LIBRARY_PATH), or copy the shared libraries to /usr/lib.</li>
-</ul>
+</s3>
+</s2>
+<anchor name="XalanDocPkg"/>
+<s2 title="Install Documentation Packages">
+<p>The documentation packages are distributed as <ref>tar</ref> files
+ and <ref>zip</ref> files. You just extract the files into a directory
+ that is reachable by your favorite web browser. The head of the
+ documentation tree starts at the <link idref="index">
+ <code>{docs}/xalan-c</code></link> directory.
+</p>
+<p><em>TO DO:</em></p>
+<p>Rework the xalan/c/trunk/xdocs/sources/ scripts so that the
+ source documentation builds are
+ targeted to the xalan/c/trunk/build/docs/xalan-c/ directory path.
+</p>
+<p>Add a documentation script that performs a post-processing
+ operation when building the API Reference from Doxygen to relocate
+ the constructed products to the xalan/c/trunk/build/docs/xalan-c/apiDocs/
+ directory path.
+</p>
+<p>Details are found in our <link idref="builddocs">Build Documents</link> pages.
+</p>
+
+<anchor name="DocWebPkg"/>
+<s3 title="Install Xalan-C User Guide">
+<p>Extract the distributed <ref>tar</ref> file or <ref>zip</ref>
+ file to the <code>{docs}</code> directory. The package populates
+ the <code>{docs}/xalan-c/*</code> directory containing the Xalan-C
+ User Guide web pages.
+</p>
+
+</s3>
+<anchor name="DocApiPkg"/>
+<s3 title="Install Xalan-C API Reference">
+<p>Extract the distributed <ref>tar</ref> file or <ref>zip</ref>
+ file to the <code>{docs}</code> directory. The package populates
+ the <code>{docs}/xalan-c/apiDocs/*</code> directory containing the
+ Xalan-C API Reference for programmers.
+</p>
</s3>
</s2>
</s1>
Added: xalan/c/branches/GSoC-2012/xdocs/sources/xalan/license.xml
URL: http://svn.apache.org/viewvc/xalan/c/branches/GSoC-2012/xdocs/sources/xalan/license.xml?rev=1391665&view=auto
==============================================================================
--- xalan/c/branches/GSoC-2012/xdocs/sources/xalan/license.xml (added)
+++ xalan/c/branches/GSoC-2012/xdocs/sources/xalan/license.xml Fri Sep 28 21:26:05 2012
@@ -0,0 +1,38 @@
+<?xml version="1.0" standalone="no"?>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+<!DOCTYPE s1 SYSTEM "../../style/dtd/document.dtd" [
+<!ENTITY asflicensetext SYSTEM "License" >
+<!ENTITY asfnoticetext SYSTEM "NOTICE" >
+]>
+
+<s1 title="Apache Software License Version 2.0">
+<ul>
+ <li><jump href="http://www.apache.org/licenses/LICENSE-2.0">Apache Software License Version 2.0</jump></li>
+ <li><link anchor="notice">Xalan License Notice</link></li>
+ <li><link anchor="license">Apache Software License Text</link></li>
+</ul>
+<anchor name="notice"/>
+<s2 title="Xalan Software License Notice">
+<source>&asfnoticetext;</source>
+</s2>
+<anchor name="license"/>
+<s2 title="Apache Software License Text">
+<source>&asflicensetext;</source>
+</s2>
+</s1>
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xalan.apache.org
For additional commands, e-mail: commits-help@xalan.apache.org