Hey Dave ,
I'm still with IBM , so I have an access to AIXs and Solaris and different
flavours of Linuxes .
If we decide to keep those platforms , I can look after it .
Unfortunatuly I don't have the magic 20% , but I'd love to help .
I can do reviews or other small tasks :)
Dmitry
David
I'm actually surprised that Google returns nothing for such popular build
question .
XalanC build process is starting from building MsgCreator - a small
standalone application for parsing and preparation of the messages.
The linker can't find the Xerces library - please verify that XERCESCROOT
Hi !
Thanks for posting this. Actually , the latest SVN version is implementing
all this steps and you can rebuild XalanC without those tweaks.
Also , in the latest version some significant conformance defects were
fixed , and that's the second reason to use it over the old XalanC1_10_0 .
Spe
Hi !
The trunks are still pretty stable.
Cheers !
Dmitry
"Devanathan, Ramkumar (HP Software BTO)" <[EMAIL PROTECTED]>
23/04/2007 11:37 PM
Please respond to
xalan-c-users@xml.apache.org
To
cc
Subject
RE: Xalan trunk...
Hi all, do we have any updates on this? Do we have a stable relea
advance,
Amish.
Dmitry Hayes wrote:
>
> Hi !
> Solaris/gcc is not a combination we are testing very friequiently .
> From your descriptopn It's difficult to say what kind of error happened.
> Very late , at the linkage stage , the linker can't find xalanMsg. This
so
> is
Hi !
Solaris/gcc is not a combination we are testing very friequiently .
>From your descriptopn It's difficult to say what kind of error happened.
Very late , at the linkage stage , the linker can't find xalanMsg. This so
is built before the main library and contines the error messages for the
]>
14/02/2007 01:57 PM
To
Dmitry Hayes/Toronto/[EMAIL PROTECTED]
cc
Subject
Xalan, 1.10, Solaris
hi Dmitry, i am from hewlett packard's openview r&d center @ Bangalore,
India.
Here we are building and using Xalan 1.10 and Xerces 2.7 (c++ apis) for
one of the products develo
I haven't built XalanC on Win64 recently . We generated makefiles with
Visual Studio and , with small tweaks , managed to build XalanC1.9
Cheers!
Dmitry
Prashanta <[EMAIL PROTECTED]>
29/11/2006 01:25 PM
Please respond to
xalan-c-users@xml.apache.org
To
xalan-c-users@xml.apache.org
cc
S
Hi !
Our makefiles doesn't support the given
configuration, but right now I can't think about any reason why it shouldn't
work.
You may look at the AIX/gcc configuration
in $XALANCROOT/Makefile.incl.in to get the idea how the port should
be done.
Thanks!
Dmitry Hayes
XSLT
lease.
Thanks!
Dmitry Hayes
<[EMAIL PROTECTED]>
28/05/2006 11:45 PM
Please respond to
xalan-c-users@xml.apache.org
To
cc
Subject
RE: Xalan-c release that compiles with
VS2005
Thanks Dmitry.
I could download the latest source
Sorry , instead of "XalanC1.9"
please read the official 1.10 version
Dmitry Hayes
Dmitry Hayes/Toronto/[EMAIL PROTECTED]
26/05/2006 10:40 AM
Please respond to
xalan-c-users@xml.apache.org
To
xalan-c-users@xml.apache.org
cc
Subject
R
, you can get it compiled by mixing the localization
approach of XalanC1.9 with the latest source of XalanC1.10
Dmitry Hayes
<[EMAIL PROTECTED]>
25/05/2006 11:56 PM
Please respond to
xalan-c-users@xml.apache.org
To
cc
Subject
Xalan-c releas
the makefiles should be done , please feed its back to us , we will gladly
commit it to the repository .
Thanks!
Dmitry Hayes
Kelvin <[EMAIL PROTECTED]>
10/27/2005 06:56 AM
Please respond to
xalan-c-users
To
xalan-c-users@xml.apache.org
cc
xalan-dev@xml.apache.org
Subject
If xal
HI !
We reviewed the sample (XPathWrapper)
and decided that the sample is obsolete and should be removed it from the
makefiles (project files).
However we decided to keep the source
for future reference.
You can refer to SimpleXPAthCAPI as
a newer sample.
Thanks!
Dmitry Hayes
XSLT Development
Hello!
We are proud to announce about release of the Xalan-C version 1.10
The new release includes:
- Support for XML 1.1 and Namespaces in XML 1.1.
- Improved and stabilized C pluggable memory management
functionality.
- Various improvements in Xa
Hi John!
Try to use the latest CVS code , the
problem should be fixed there
Thanks!
Dmitry
John Russell <[EMAIL PROTECTED]>
07/14/2005 04:18 AM
Please respond to
xalan-c-users
To
xalan-c-users@xml.apache.org
cc
Subject
Build on SuSE 8 with ICU
problem
Hi
I'm trying to g
Sounds like a defect . Can you pls open
a JIRA issue .
Thanks!
Dmitry Hayes
XSLT Development
IBM Toronto Lab
Phone: 905-413-3820
E-mail: [EMAIL PROTECTED]
"David Hubbard"
<[EMAIL PROTECTED]>
05/13/2005 11:09 AM
Please respond to
xalan-c-users
To
cc
Subj
Hi Bettina!
The 'pkgdata.exe' is a program from
ICU package, that we use in the message library building process.
Usually it's located in the icu/bin
directory.
In your case the program should look
in directory.
My guess would be that your ICUROOT
points to the wrong directory.
and PerfT should work .
Thanks,
Dmitry Hayes
John Jamison <[EMAIL PROTECTED]>
01/04/2005 02:24 PM
Please respond to
xalan-c-users
To
xalan-c-users@xml.apache.org
cc
Subject
Win32 VS 7.1 build problems
Downloaded the 1_9 src tree, configured XERCESROOT and the incl
Hi all!
We are proud to announce about release
of the Xalan-C version 1.9
The new release includes:
-
Plagguble memory management
-
Iterative processing
-
Xalan-C can be tested on the Unix platforms with "Conf"
-
A new flag for XalanTranscoder , providing a
y new features .
The processor right now is in the last
phase of testing - performance testing .
If we don't see any urgent issues ,
we are planning to release the Xalan-C 1.9 before the Christmas holidays.
Thanks and have happy holidays.
Team of Xalan-C committers
- Forwarded by Dmitry
Hayes/T
Nov 9 , Tuesday.
Any comments/suggestions are appreciated
!
Please vote!
Here is my
+1
Thanks!
Dmitry Hayes
Hi Milan!
You can get Xalan-C without any message ( or with one dummy message ) with
modifying our source ( XalanInMemoryMessageLoader.cpp file ) , removing
XalanMessages_1_8D.lib from the link and recompiling.
The XalanMessages_1_8D.dll will be created but not loaded in the run time.
Dmitry
Hi Sami!
XalanDOMString is designed to contain UTF16 string . To be more explicit ,
it contains an array of UCS-2 code points.
You can use CharVectorType when you want to represent UTF-8 strings.
Note that you can't represent every code point of UTF-16 as simply C/C++
"char" .
Dmitry
Hi Bettina !
The project is a "Makefile project" . It's running a makefile , creating
"XalanMsgIndex.hpp" and builds a dll with messages.
The common mistake is incorrect setting of the Xerces includes/libraries in
Tools->Options->Directories.
Please verify that you have followed the build inst
Hi Kelvin !
You can try to download the current CVS version: it comes with the VC7
project files and the source is very close to a version that will be
released as Xalan 1.8 .
Dmitry
[EMAIL PROTECTED]
lan-c-users
Hi Unri !
The tools.ini file used to collect macros setting for VC++ makefiles , and
it can be called from any makefile.
In our implementation only a makefile in the same directory reads it.
But the problem is different: we are building Xalan with dsp/dsw (or
vcproj/sln) and not with exported
, I could manually copy the generated files, and then comment out
the "move" command that fails in Localization.mak, to see if I can
proceed further. But other groups and developers will be using the same
source, and for them to be able to build smoothly I will need to ensure
these problems
s have been generated, but looks like the move fails.
Thanks again for your help!
Urmi
-Original Message-
From: Dmitry Hayes [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 07, 2004 12:32 PM
To: xalan-c-users@xml.apache.org
Subject: RE: Compiling Xalan 1.7 with .NET 2003
Hi !
Hi !
Have you tried to put Xerces in Tools->Options->Projects->VC++ Directories
, in "Executable file","Include files" and "Libarary files" ?
A documentation how to build with .NET will be ready for Xalan1.8 release ,
but the same idea like for VC6 should work .
Thanks,
Dmitry
Hi !
>Maybe I am wrong with my analysis, but if I am right, I think one should
>mention this behaviour within the section "What can I do to speed up
>transformations?" of the Xalan-C-FAQ.
Thanks, we will do it for the upcoming release .
Dmitry.
Hi Milan!
It means that we haven't tested Xalan1.7.0 with Xerces2.5.0 and the Xalan
binaries wouldn't be compatible with the new Xerces release.
However, from my understanding, Xalan 2.5.0 is a bug fixing release after
2.4.0. If you would like to get more details about it,
xerces-c-dev@xml.apac
Hi Don!
>From your point of view nothing is going to be changed in Win32 build of
Xalan: the binary package is still VC6 built package and dsp/dsw files are
still there.
We've just added sln/vcproj files to the project.
Thanks!
Dmitry
Hi all!
It has been more than a month since the Xerces release and now we are
thinking about releasing XalanC 1.8.0, compatible with Xerces 2.5.0
Between the new changes in the release are:
- Compatibility with Xerces 2.5.0 and (optional) ICU 2.6.1
- VC7(2002) support
- HP
Hi Nick!
Now you are in much better situation .
The process looks like that:
With ICU:
MsgCreater.exe (xerces dll is required) takes XalanMsg_en_US.xlf and
creates Debud/nls/icu/en_US.txt file
genrb.exe ( application , provided by ICU , check you ICU root ) is a part
of process , taking Debud/n
Hi Rich !
Our build system takes messages from xliff ( in another words , xml ) file
and convert it to "something" depend on localization method.
In case of Win32 it can be our own dll - "INMEM" method or ICU dll - "ICU"
method . We are independent from Xerces localization method .
I don't know
(67) : fatal error C1083: Cannot open include file:
'LocalMsgIndex.hpp': No such file or directory.
I also downloaded compiled version of xalan 1.7 (for VC6 without ICU) but
LocalMsgIndex.hpp wasn't there either.
Thank you,
Michal
- Original Message -
From: "Dmitry Hayes" <[E
Hi Michael!
Right now we have a problem with Builder , but not with Mac.
The problem is that we don't have an access to the platform to fix the
issue.
As a kind of work around I can suggest you to build the first time with
make/gmake .
Thanks,
Dmitry
Or Dependency Walker (for dlls and exe files ) - Depends.exe
Coming with MS Visual Studio, between Tools
Dmitry
[EMAIL PROTECTED]
t; are XML files from "xml-xalan/c/xdocs" directory .
"The result of compilation of docs" are HTML files from "xml-xalan/c/docs"
directory .
Any opinions, comments and additions are very welcome.
Dmitry Hayes
XSLT Development
Dear Takeaki!
Unfortunately, XalanC has only the VC++ build for Win32.
But if you can create a Borland C++ building environment for XalanC and
submit it to the community, your help will be highly appreciated.
Thanks
Dmitry Hayes
XSLT Development
- Forwarded by Dmitry Hayes/Toronto/IBM
Hi Han!
It seems your question contains the answer too.
If you want to change DOM, use Xerces DOM. If you need to make
transformations, wrap Xerces DOM into Xalan classes( but Xalan inputs are
always immutable).
If you are changing the XalanNode, you are using internal Xalan API, not
intended
Hi all !
I am thinking about design of message localization .
Apparently , Xalan need a similar system, like has Xerces for the last 3
years.
Xerces implements 3 types of local messages : "inMemory", "Resource file
string" for Win32 and with ICU service.
Actually, there exists 4th , "Message Ca
44 matches
Mail list logo