Xalan-C Platforms -- Binary Build Summary Report
Xerces-C v3.1.1 (XML Parser Library)
Xalan-C v1.11 (XSLT Tranform Library)
BINARY PLATFORM BUILDS
Microsoft Windows
MS.NET 2003 (VC7.1) x86 [OK]
MS.NET 2005 (VC8) x86_64 [OK]
MS.NET 2008 (VC9) x86_64 [OK]
MS.NET 2010 (VC10
Thanks for the copyright notice (bad symbol)!
Issue is resolved.
Description of what happened:
1. The (svnpubsub) repository has the copyright symbol #xA9; in the
html pages, but the
codepage being used was LATIN-1.
2. When INFRA published the html pages to the website mirrors, the
LATIN-
.1.1 - Debug[OK]
> Xalan-C 1.11 - Release [OK]
> Xalan-C 1.11 - Debug[FAIL]
Xalan-C 1.11 - Debug[OK](( NOW SUCCESSFUL ))
>
> The native c/c++ compilers are GNU.
>
> I needed to declare LD_LIBRARY_PATH in preference to LIBPATH for the build
>
Greetings!
After compiling the GNU make on FreeBSD-9 and renaming the executable to
gmake, I was able to successfully build:
Xerces-C 3.1.1 - Release [OK]
Xerces-C 3.1.1 - Debug[OK]
Xalan-C 1.11 - Release [OK]
Xalan-C 1.11 - Debug[FAIL]
The native c/c++ compilers
imit some excessive traffic
>>> and still
>>> have the needed pages captured by internet webpage indexers.
>>>
>>> #
>>> # Xalan website control: robots.txt
>>> #
>>> # Keep web crawlers out of auto-generated api documentation pages
>
Excellent! Steven, thanks for pulling this all together.
Michael Glavassevich
XML Technologies and WAS Development
IBM Toronto Lab
E-mail: mrgla...@ca.ibm.com
E-mail: mrgla...@apache.org
Steve Hathaway wrote on 12/07/2012 12:34:06 AM:
> Greetings!
>
> The new XALAN website is now published. "h
; still
>> have the needed pages captured by internet webpage indexers.
>>
>> #
>> # Xalan website control: robots.txt
>> #
>> # Keep web crawlers out of auto-generated api documentation pages
>> #
>> User-agent: *
>> Disallow: /xalan-
cessive traffic and
> still
> have the needed pages captured by internet webpage indexers.
>
> #
> # Xalan website control: robots.txt
> #
> # Keep web crawlers out of auto-generated api documentation pages
> #
> User-agent: *
> Disallow: /xalan-c/apiDocs/
> Disallo
Great work Steven!
Gareth
On 12 Jul 2012, at 05:34, Steve Hathaway wrote:
> Greetings!
>
> The new XALAN website is now published. "http://xalan.apache.org";
>
> If you find problems with the new XALAN website pages, please send mail to:
>
> xalan-dev@xml.apache.org
>
> If you have files, f
Greetings!
The new XALAN website is now published. "http://xalan.apache.org";
If you find problems with the new XALAN website pages, please send mail to:
xalan-dev@xml.apache.org
If you have files, fixes, and examples to better the websites of our
projects XALANC and XALANJ, then opening a Ji
ed pages captured by internet webpage indexers.
#
# Xalan website control: robots.txt
#
# Keep web crawlers out of auto-generated api documentation pages
#
User-agent: *
Disallow: /xalan-c/apiDocs/
Disallow: /xalan-j/apidocs/
Disallow: /old/xalan-c/apiDocs/
Disallow: /old/xalan-j/apidocs/
Sincerely,
Ste
Greetings,
I am keeping an eye on this issue!
The new website is net yet available on the mirrors. I will check
in a few hours, and again tomorrow.
Sincerely,
Steven J. Hathaway
Xalan Documentation Project
==
[
https
XALAN-C Binary Library Builds -- Preparation for product release
Xerces-C XML Parser
Platform: FreeBSD-9 [OK]
Platform: PcBSD-9 [UNKNOWN]
Platform: Linux [OK]
Platform: Windows [OK]
Platform: Solaris-11 [UNKNOWN]
Xalan-C XSLT Transformser
Platform: FreeBSD-9
Greetings, -- Xalan-C Build Status Report
I am testing some binary builds of Xalan-C on several platforms.
FreeBSD Version 9 has a problem - distribution has no GNU make.
Windows Visual Studio Platforms
Visual Studio (VC6) obsoleted
Visual Studio .NET 2003 (VC7.1) -- OK
Visual
The Xalan project now has web pages hosted on the subversion server.
The svnsubpub web page publishing path for Xalan TLP is:
http://svn.apache.org/repos/asf/xalan/site/docs/xalan
The Xalan-C project web pages are to be copied to:
http://svn.apache.org/repos/asf/xalan/site/docs/xalan
Greetings,
I have new builds for Microsoft Studio .NET 2003, 2005, 2008, 2010 for
Xalan-C libraries on my developer web site. The compiled binaries for
Xerces-C 3.1.1 are also available.
The Xalan-C build is from the current svn trunk.
The Xerces-C build is from the last stable source
Hi,
The Xalan-C GSoC 2012 project is moving forward. Here is an outline of
what EXSLT functions are implemented and which ones need work.
Samuel will be spending his primary effort toward implementing the
XPath functions in the http://exslt.org/dates-and-times namespace.
Sincerely,
Steven J
Hey Steve,
Afraid not. Suggest you get on to IRC and ask the infra team. They are
very helpful. If you get stuck give us a shout and I will try and help.
Cheers,
Gareth
On 13 May 2012, at 17:14, Steve Hathaway wrote:
> Hi Everyone,
>
> I am studying the buildbot architecture to const
Hi Everyone,
I am studying the buildbot architecture to construct the necessary
master and slaves required to create binary packages for the
upcoming release.
I am reading the buildbot manual.
Do any of you have experience to share regarding the use of
buildbot for Apache? How are the accounts
Samuel,
I have been doing more code review on the internals of XERCES-C
and XALAN-C regarding Numbers and DateTime.
The XPath XObjects should use XalanDOMString to render dateTime types
and the duration types. You can use underlying 64-bit integer
arithmetic on a millisecond time continuum, but
: mrgla...@ca.ibm.com
E-mail: mrgla...@apache.org
Samuel Medeiros wrote on 24/04/2012 05:18:53 PM:
> From: Samuel Medeiros
> To: xalan-dev@xml.apache.org,
> Date: 24/04/2012 05:20 PM
> Subject: Re: Xalan C++ GSoC project?
>
> Michael,
>
> yes, this project was accepted.
>
ing your mentor.
>
> Xalan uses the Apache Subversion Repository for source code control.
>
> I have just made a snapshot of the Xalan-C trunk for tracking
> your work this summer. This branch is intended for your
> experimenting. When your work looks good and passes quality
>
Hi Samuel,
Congratulations! I saw your acceptance from Google.
I am looking forward to being your mentor.
Xalan uses the Apache Subversion Repository for source code control.
I have just made a snapshot of the Xalan-C trunk for tracking
your work this summer. This branch is intended for your
evelopment
> IBM Toronto Lab
> E-mail: mrgla...@ca.ibm.com
> E-mail: mrgla...@apache.org
>
> Samuel Medeiros wrote on 24/04/2012 05:18:53 PM:
>
> > From: Samuel Medeiros
> > To: xalan-dev@xml.apache.org,
> > Date: 24/04/2012 05:20 PM
> > Subject: Re: Xala
he.org,
> Date: 24/04/2012 05:20 PM
> Subject: Re: Xalan C++ GSoC project?
>
> Michael,
>
> yes, this project was accepted.
> I will be pleased to work with the Xalan Dev Team.
>
> Sincerely,
> Samuel Queiroz
>
> Em 24 de abril de 2012 18:01, Michael Glavass
Michael,
yes, this project was accepted.
I will be pleased to work with the Xalan Dev Team.
Sincerely,
Samuel Queiroz
Em 24 de abril de 2012 18:01, Michael Glavassevich
escreveu:
> The GSoC announcement date was yesterday. Haven't seen an acknowledgement
> here yet. Was this project accepted?
>
The GSoC announcement date was yesterday. Haven't seen an acknowledgement
here yet. Was this project accepted?
Thanks.
Michael Glavassevich
XML Technologies and WAS Development
IBM Toronto Lab
E-mail: mrgla...@ca.ibm.com
E-mail: mrgla...@apache.org
[
https://issues.apache.org/jira/browse/XALANC-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven J. Hathaway reassigned XALANC-725:
-
Assignee: (was: Brian Minchau)
> Windows Builds - Xalan-C 1.11 using
Components: XalanC
>Affects Versions: 1.10
>Reporter: Steven J. Hathaway
>Assignee: Steven J. Hathaway
>Priority: Minor
> Fix For: 1.10
>
>
> Should we try to have a bugfix release build of Xalan-C 1.10.1, maintaining
Xalan Documentation Project
>
> Em 5 de abril de 2012 10:40, Samuel Medeiros
> escreveu:
>
>> Steve,
>>
>> I have updated my proposal adding the information that were missing (the
>> schedule and about the intregation with the Xalan C repository).
>>
looks promising. The student
has already created a development environment for XERCES-C and XALAN-C
for coding and debugging activities.
XALANC-724, XALANC-727 -- Automated Build Tools & Automake Upgrade
A prospective student has shown interest and is working
on his project submission.
.
The current implementation is briefly described in the Xalan-C
project documentation under the topic "Extensions Library".
Some of the code on my committer's web site has samples on
how to extend the Function class to create your own extension
functions. The EXSLT functions use t
012 6:49 PM, Samuel Medeiros wrote:
Steve,
I got the sources of Xerces-C and Xalan-C available in
http://xerces.apache.org/xerces-c/download.cgi and
http://svn.apache.org/repos/asf/xalan/c/trunk, respectively. I spent
some hours and I couldn't build them for execute the samples availabl
FYI: Xalan-C Custom XPath Extension Functions
I have updated my committer's web site with source code to implement and
test
some useful XPath extension functions. I also have a XalanCAPI based
application
that installs and tests these functions.
Go to my Committer's Web Pa
See: New binary packages for XALAN-C on my developer's web site
http://www.apache.org/~shathaway
March 26, 2010 -- Built from current SVN snapshot
Platform: Windows // VC71, VC8, VC9, VC10
Now includes a /doc/xalanc directory containing
the LICENSE and NOTICE files for ASF Licens
The sample binary packages on my committer's web page
need the License and NOTICE files added to the top
of the ZIP files. I will make the corrections to the
files and make them available on the web site.
Steven J. Hathaway
Xalan Documentation Project
--
Windows Builds - Xalan-C 1.10.1 bugfixes using SVN Repository
-
Key: XALANC-726
URL: https://issues.apache.org/jira/browse/XALANC-726
Project: XalanC
Issue Type: Task
Windows Builds - Xalan-C 1.11 using IBM-ICU
---
Key: XALANC-725
URL: https://issues.apache.org/jira/browse/XALANC-725
Project: XalanC
Issue Type: Task
Components: XalanC
Affects Versions
Hi Steven,
shath...@e-z.net wrote on 03/05/2012 04:35:56 PM:
> XALAN-C Google Summer of Code - 2012
>
> Here are some areas where the Google Summer of Code (GSOC-2012)
> can have a good impact on preparing for product releases.
>
> GSOC-2012 can help with infrastructure/auto
XALAN-C Google Summer of Code - 2012
Here are some areas where the Google Summer of Code (GSOC-2012)
can have a good impact on preparing for product releases.
GSOC-2012 can help with infrastructure/automation projects by
creating release builds for XALAN-C evaluation and distribution.
I am
The review website http://www.apache.org/~shathaway
has a new install.html page for the XALAN-C
documentation project. There has been lots of
cleanup.
Sincerely,
Steven J. Hathaway
-
To unsubscribe, e-mail: xalan-dev-unsubscr
I have more binary packages for review on my committer web page
in support of planning an XALAN-C/C++ Version 1.11 release strategy.
http://www.apache.org/~shathaway
The Windows binary build packages on the web site include both
a debug build and a release build for the following platforms
MORE XALAN-C DOCUMENTATION FIXES
I fixed more broken links and performed more web page edits
and saved then in the repository. More pages are current
with the trunk Subversion repository.
I have not committed these pages for XALAN-C documentation to
the trunk. They still reside in the
SubProject: XALAN-C
I am getting broken links resolved. New pages for XALAN-C
are available for edit, review, and comment. Check my
committer's web page at: http://www.apache.org/~shathaway
The newest edits will be submitted to the SVN repository on
Monday - 2012-03-05.
The StyleBoo
> Build Xalan-C/C++ API Reference Manal Using Doxygen 1.7 or newer
>
>
> Key: XALANC-713
> URL: https://issues.apache.org/jira/browse/XALANC-713
> Project: XalanC
>
The XALAN-C Subversion Repository has been updated with new material.
Update for creating Xalan-C API documentation has been
submitted to the subversion repository. The DoxyfileXalan
works with the following software products.
doxygenversion 1.7.1
graphviz(dot) version 2.26.3
Preparation of Xalan-C-1.11.0 Windows Binary Release PRE-1
I have successfully built and tested binary builds for Windows
using Xerces-C-3.1.1 and am nearly ready for packaging and
distribution.
Xalan-C-1.11.0-windows-x86-VC71.pre-1.zip
Xalan-C-1.11.0-windows-x86-VC8.pre-1.zip
Xalan-C
Documentation Updates (2/26/2012)
Submitted by: Steven J. Hathaway
Building the new Xalan WebPages from SVN
https://svn.apache.org/repos/asf/xalan/c/branches/XalanDocs
[1] Extract a copy of the branch to a Windows machine.
[2] Copy the Xalan command-line program and necessary libraries into
.
> Xalan-C represents numbers as FLOAT precision instead of DOUBLE
> ---
>
> Key: XALANC-722
> URL: https://issues.apache.org/jira/browse/XALANC-722
> Project: Xalan
E is confirmed correct. 17-18 decimal digits represents
the effective IEEE DOUBLE precision.
It also looks like NAN, and +- Infinity may also be correct.
The issue should be closed.
> Xalan-C represents numbers as FLOAT precision instead of
Xalan-C does indeed have DOUBLE precision resolution.
This table effectively illustrates the number of decimal
digits to binary bit resolution.
3 decimal digits ~= 10 bits
6 decimal digits ~= 20 bits
9 decimal digits ~= 30 bits
12 decimal digits ~= 40 bits
15 decimal digits ~= 50 bits
18 decimal
On 2/20/2012 12:49 PM, David Bertoni wrote:
On 1/16/2012 1:39 PM, shath...@e-z.net wrote:
My current tests with Xalan-C 1.11 seem to indicate that Numbers are
only
useful with the resolution of type FLOAT instead of DOUBLE. The
underlying data storage for numbers appears to be 64-bit DOUBLE
On 1/16/2012 1:39 PM, shath...@e-z.net wrote:
My current tests with Xalan-C 1.11 seem to indicate that Numbers are only
useful with the resolution of type FLOAT instead of DOUBLE. The
underlying data storage for numbers appears to be 64-bit DOUBLE, but the
rendering seems to be restricted to 32
Hi,
Is Xalan-C++ version 1.11 is released? If not how can I get the latest
release
As Xerces-C/C++ Version 3.1.1 is released and can be downloaded from
http://xerces.apache.org/xerces-c/download.cgi. and to work with
xerces3.1.1 I need Xalan 1.11.
Please help.
Thanks
Dinesh
My current tests with Xalan-C 1.11 seem to indicate that Numbers are only
useful with the resolution of type FLOAT instead of DOUBLE. The
underlying data storage for numbers appears to be 64-bit DOUBLE, but the
rendering seems to be restricted to 32-bit FLOAT.
What will be needed to qualify
> On 12/5/2011 5:46 PM, shath...@e-z.net wrote:
>> When building the Xalan-C 1.11 sources in SVN repository for ICU
>> support,
>> should we also link with the Xerces-C 3.1.1 parser library that is
>> compiled with ICU support?
> We should simply remove the old
Martin,
In previous Xalan-C 1.10 with ICU support, there was no ICU integrated
into Xerces-C.
I am wondering if any users have experience compiling and using the current
Xalan-C 1.11 with ICU. I would like their insights for the documentation
project.
Thanks,
Steven J. Hathaway
> Steven as
On 12/5/2011 5:46 PM, shath...@e-z.net wrote:
When building the Xalan-C 1.11 sources in SVN repository for ICU support,
should we also link with the Xerces-C 3.1.1 parser library that is
compiled with ICU support?
We should simply remove the old AllInOneWithICU project files. Here's
how th
Steven asked the following a while back:
>When building the Xalan-C 1.11 sources in SVN repository for ICU support,
>should we also link with the Xerces-C 3.1.1 parser library that is compiled
>with ICU support?
I'm not quite sure what Steven meant to ask. If you're going to
The XalanMessages Library using VS 2003 (VC7.1) is constructed using
makefiles ported from VC6.
The XalanMessages Library construction was redesigned in VS 2005
to use the Xerces-C parser to transform the XalanMsg_en_US.xlf file.
Shall I attempt to back-port the work from VS 2005 into VS 2003 (VC
with content committed to a branch of the xalan/c
repository.
http://svn.apache.org/repos/asf/xalan/c/branches/XalanDocs
> Build Xalan-C/C++ API Reference Manal Using Doxygen 1.7 or newer
>
>
>
[
https://issues.apache.org/jira/browse/XALANC-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven J. Hathaway resolved XALANC-711.
---
Resolution: Fixed
Work continues in http://svn.apache.org/repos/asf/xalan/c/branches
Documentation Project has been committed to SVN repository:
http://svn.apache.org/repos/asf/xalan/c/branches/XalanDocs
Web page content is available for review. Document construction scripts are
available.
The documentation project supports: http://xalan.apache.org
and its sub-project
Are there any committers or users that have attempted the use
and integration of IBM-ICU internationalization of Xalan-C 1.11
with Xerces-C 3.0 or newer?
- Steve
On 12/7/2011 12:20 PM, shath...@e-z.net wrote:
> David,
>
> You have worked in the past with IBM-ICU support with Xalan-C.
&g
/repos/asf/xalan/c/branch/Xalan-Docs
This branch is started by
It contains prototype work for the development of Xalan PMC documentation.
1. Developer-Notes
Contains some useful planning documents, including various style guides,
Version compatibility notes, and other planning documents
[
https://issues.apache.org/jira/browse/XALANC-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven J. Hathaway reassigned XALANC-712:
-
Assignee: Steven J. Hathaway
> Xalan-C++ V1.11 User Guide - Web Pages Rev
[
https://issues.apache.org/jira/browse/XALANC-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven J. Hathaway reassigned XALANC-713:
-
Assignee: Steven J. Hathaway
> Build Xalan-C/C++ API Reference Manal Us
[
https://issues.apache.org/jira/browse/XALANC-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven J. Hathaway reassigned XALANC-711:
-
Assignee: Steven J. Hathaway
> Xalan-C++ API Documentation - Test Bu
[
https://issues.apache.org/jira/browse/XALANC-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven J. Hathaway reassigned XALANC-722:
-
Assignee: (was: Brian Minchau)
> Xalan-C represents numbers as FL
-291
> Xalan-C represents numbers as FLOAT precision instead of DOUBLE
> ---
>
> Key: XALANC-722
> URL: https://issues.apache.org/jira/browse/XALANC-722
> Project: X
Xalan-C represents numbers as FLOAT precision instead of DOUBLE
---
Key: XALANC-722
URL: https://issues.apache.org/jira/browse/XALANC-722
Project: XalanC
Issue Type: Bug
The repository is now fixed with edited .vcproj files for
the Xalan-C Microsoft VS 2005 VC8 builds.
Projects/Win32/VC8/...
Steven J. Hathaway
> Xalan-C Microsoft VS 2005 VC8 has same linker issue now fixed for VC9 and
> VC10. Release builds also want to link with the debug Xalan-C_
Xalan-C Microsoft VS 2005 VC8 has same linker issue now fixed for VC9 and
VC10. Release builds also want to link with the debug Xalan-C_1D.lib
library.
I am preparing a patch to resolve this.
Steven J. Hathaway
-
To
[
https://issues.apache.org/jira/browse/XALANC-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven J. Hathaway resolved XALANC-275.
---
Resolution: Won't Fix
Obsolete Issue
> xalan-c: proposed
More cleanup of Xalan-C v1.11 has been committed
to fix Microsoft Studio build issues (VC9, VC10).
Steven J. Hathaway
-
To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org
For additional commands, e-mail: xalan-dev-h
The Xalan-C 1.11 subversion repository path Projects/Win32/VC9 vcproj
files have been updated to accommodate proper linking of sample files.
The edits I made for VC10 have been ported back to VC9.
I will now look at VC8 to confirm that sample project builds appear
problem free.
I have
When building the Xalan-C 1.11 sources in SVN repository for ICU support,
should we also link with the Xerces-C 3.1.1 parser library that is
compiled with ICU support?
I would appreciate your discussion!
Sincerely,
Steven J. Hathaway
The link issues I fixed with the Microsoft VC10 are also found in the
Project/Win32/VC9 builds. I am preparing updated *.vcproj files to
resolve the issue based on the Project/Win32/VC10 updates.
Description of issue: Release builds of sample programs using
Project/Win32/VC9 also attempt to link
+1 from me as well.
Gareth
On 29 Nov 2011, at 16:55, Michael Glavassevich wrote:
> I assume you're proposing this because those versions are obsolete. If so, +1.
>
> shath...@e-z.net wrote on 11/29/2011 11:41:41 AM:
>
> > XALAN-C I Propose Dropping Some Microsoft Sup
I assume you're proposing this because those versions are obsolete. If so,
+1.
shath...@e-z.net wrote on 11/29/2011 11:41:41 AM:
> XALAN-C I Propose Dropping Some Microsoft Support
>
> I propose dropping support for Microsoft Platforms (VC6 and VC7)
> from the current SVN repos
XALAN-C I Propose Dropping Some Microsoft Support
I propose dropping support for Microsoft Platforms (VC6 and VC7)
from the current SVN repository (ref: XALAN-C 1.11).
The support for Microsoft VC6 and VC7 has been removed from the
XERCES-C (XML Parser) library as of Version 3.0.
The current
I have established a foundation to create automated binary package
releases of XALAN-C for Microsoft Developer Studio, and Microsoft Studio
.NET platforms using compilers (VC6, VC7.1, VC8, VC9, VC10).
See JIRA XALANC-721 for details.
https://issues.apache.org/jira/browse/XALANC-721
I hope
Hi Saurabh,Thanks for your response. I am trying to build(not with native aCC compiler) xalan-c(1.10 version) with gcc and g++ compiler for 32bit HPUX Itanium Architecture machine. For this i have executed runConfigure as follows:$./runConfigure -p hp-11-ia64 -c gcc -x g++Generating makefiles with
Hi All,
I am trying to build Xalan-c(1.10.0 version) on HP-UX system with Itanium
Architecture. I am using gcc(3.4.4 version) as C compiler and g++(3.4.4
version) as C++ compiler, but when i try to build, i am getting following
error:
g++: +DD32: No such file or directory
g++: +Z: No such file
XALAN-C Product Integration Issue -- Microsoft VC6 and VC7 are obsolete.
I am having problems getting Microsoft Development Studio (VC6) to read
the "Xalan.dsw" workgroup file for doing a build based on subversion
repository sources.
I have a new virtual machine with both (VC6)
> Xalan-C does not implement XSLT erratum 23 for xsl:number
> -
>
> Key: XALANC-682
> URL: https://issues.apache.org/jira/browse/XALANC-682
> Project: XalanC
>
Hi,
I need to copy all the child elements from the parent element to output xml
using xalan c++ transform method. However, one of the child element is
prefixed but does not have corresponding namespace.
What should I do in xslt so that all the children elements of parent element
are
tion describing JIRA XALANC-451 enhancement to the
samples and interface definitions. The xalan-c project will accommodate
additional top-level parameter types for XalanTransformer.
> Xalan-C++ V1.11 User Guide - Web Pages
As part of the Apache Project Branding Requirements [1] we need to create
DOAP files for our sub-projects. I've just made some basic ones [2] for
Xalan-J and Xalan-C++.
This will soon show up on projects.apache.org as well as on the main Apache
site periodically (in the featured project se
On 9/6/2011 3:36 AM, Tim Williams wrote:
On Mon, Sep 5, 2011 at 6:00 PM, Steve Hathaway wrote:
I am trying to understand the available infrastructure that can be
used to create some Xalan-C pre-release builds This task is still
early, but I may be able to help coordinate the effort.
What do
On Mon, Sep 5, 2011 at 6:00 PM, Steve Hathaway wrote:
> I am trying to understand the available infrastructure that can be
> used to create some Xalan-C pre-release builds This task is still
> early, but I may be able to help coordinate the effort.
What do you need? The infra team has
I am trying to understand the available infrastructure that can be
used to create some Xalan-C pre-release builds This task is still
early, but I may be able to help coordinate the effort.
I have time to visit Oregon State University and review their
hosting of Apache Infrastructure at their
readme-20110902.txt
build-xalan-docs-20110902.zip = the constructed web pages
build/docs/xalan = http://xalan.apache.org
build/docs/xalan/xalan-c = http://xml.apache.org/xalan-c
build/docs/xalan/xalan-j = http://xml.apache.org/xalan-j
xdocs-xalan-docs-20110902.zip
ings also have a merge of all three web sites
> and scripts that will automate the build of the web sites
> except for some of the API documentation (i.e. doxygen based).
>
> Sincerely,
> Steven J. Hathaway
>
> - - - - - - - - - - - - - - - -
>
> MANIFEST FOR JIRA XALAN
XALANC-712
The XALAN, XALAN-C and XALAN-J web pages can be created relative to
the Windows directory into which you unzip these three files.
bin-win32-20110902.zip
build-xalan-docs-20110902.zip
xdocs-xalan-docs-20110902.zip
These files can be extracted to any directory, but they are
I dont have experience with the international builds for what
has changed from Xerces-C version 2.8 to 3.0 and how their
transcoding modues affect the Xalan-C library. Some brief
discussion on using Xerces-C 3.1.1 for Xalan-C 1.11 international
builds would be appreciated.
I need to have good
The following is my procedure for generating the
Xalan-C/C++ API Reference Web Pages for the
CurrentSVN Version 1.11.
The trademark graphic is one I obtained from the ASF
official trademark logo repository. It is referenced
by the "footer.html" fragment. The "header.html&quo
Here are my notes on building Xalan-C/C++ Web Pages.
The format is similar to the [http://people.apache.org] pages.
The StyleBook XML source pages are still being supported.
The StyleBook Java program is no longer required.
The XHTML output scales very well with modern browsers.
I will soon post
These files are XML based.
In the .NET releases of 2003, 2005, and 2008 -- the *.vcproj files
were elements with configuration content as named attributes.
The change in .NET 2010 is to replace attribute/value content with
element/value content.
David Bertoni has tested Xalan-C with VS 2010, bu
Hey guys,
On 5 Aug 2011, at 17:24, shath...@e-z.net wrote:
> Building Xalan-C/C++ with Microsoft VS 2010 is not integrated into the
> CurrentSVN.
>
> In your SVN snapshot, you will need to copy the
> {SourceDir}/Projects/Win32/VC9 directory to
> {SourceDir}/Projects/Wi
1 - 100 of 2629 matches
Mail list logo
