Return-Path: X-Original-To: apmail-xalan-dev-archive@www.apache.org Delivered-To: apmail-xalan-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A65D210686 for ; Sat, 12 Oct 2013 05:49:08 +0000 (UTC) Received: (qmail 2060 invoked by uid 500); 12 Oct 2013 05:48:30 -0000 Delivered-To: apmail-xalan-dev-archive@xalan.apache.org Received: (qmail 2029 invoked by uid 500); 12 Oct 2013 05:48:05 -0000 Mailing-List: contact dev-help@xalan.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@xalan.apache.org Delivered-To: mailing list dev@xalan.apache.org Received: (qmail 1436 invoked by uid 99); 12 Oct 2013 05:47:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Oct 2013 05:47:56 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [64.255.237.171] (HELO smtp1.pacifier.net) (64.255.237.171) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Oct 2013 05:47:51 +0000 Received: from webmail.iinet.com (web01-proaxis.pacifier.net [64.255.238.1]) by smtp1.pacifier.net (Postfix) with ESMTP id E4BD82CA06; Fri, 11 Oct 2013 22:47:30 -0700 (PDT) Received: from 67.150.174.37 (SquirrelMail authenticated user shathawa@e-z.net) by webmail.iinet.com with HTTP; Fri, 11 Oct 2013 22:47:30 -0700 (PDT) Message-ID: <62364.67.150.174.37.1381556850.squirrel@webmail.iinet.com> In-Reply-To: <45535312-b40a9541d3300222384ba2a6957b772c@pmq4v.m5r2.onet> References: <45535312-b40a9541d3300222384ba2a6957b772c@pmq4v.m5r2.onet> Date: Fri, 11 Oct 2013 22:47:30 -0700 (PDT) Subject: Re: Re: Re: Is xalan still maintained? From: shathawa@e-z.net To: "clare" Cc: shathawa@e-z.net, dev@xalan.apache.org User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Checked: Checked by ClamAV on apache.org Clare, The .ICU builds for the Xalan-C need some more testing and configuration cleanup. The major support for IBM ICU has been moved to the Xerces-C arena. At this time, the ICU integration has been deprecated in Xalan-C due to lack of developer support. I don't know of users that have ICU integrated into Xalan-C. Your assistance in identifying ICU compatibility issues would be appreciated. Sincerely, Steven J. Hathaway > I have Xerces-c 3.1.1. and it appears to be working as MsgCreator is > compiled. (I have Build\Win32\VC9\Release.ICU\MsgCreator.exe) I have run > MsgCreator on src\xalanc\NLS\en_US\XalanMsg_en_US.xlf manually and it > generated LocalMsgData.hpp and LocalMsgIndex.hpp, so it appears there is a > problem with project files for me. > > Clare > > W dniu 2013-10-08 01:47:08 użytkownik napisał: >> The build of LocalMsgData.hpp requires a useable Xerces-C parser >> library. >> An intermediate executable will be created that reads the XLIFE file >> of messages to create the LocalMsgData.dll, and the header file. >> >> You will need at minimum the Xerces-C 3.0, and preferably Xerces-C >> 3.1.1. >> The Xerces-C from the subversion repository should also be usable. >> >> After Xerces-C has been built, you will need to define the XERCESCROOT >> environment variable so that the Xalan-C sources will not fail. >> >> The MsgCreator project is compiled using the Xerces-C parser library. >> The XalanMsgLib project uses the MsgCreator.exe to construct the >> LocalMsgData.dll and LocalMsgData.hpp header files. >> >> Steven J. Hathaway >> >> > Well, if this file would be there, I would probably do not complain. >> This >> > is a head of the output from visual. I don't know. Maybe this XLIFE >> > processing fails, but Visual is too stupid to print the error. But >> then, >> > how to check it? >> > >> > 1>------ Build started: Project: XalanMsgLib, Configuration: Release >> with >> > ICU Win32 ------ >> > 1>Processing XLIFF file >> > 1>Compiling... >> > 1>XalanMsgLib.cpp >> > 1>..\..\..\..\..\src\xalanc\Utils\XalanMsgLib\XalanMsgLib.cpp(25) : >> fatal >> > error C1083: Cannot open include file: 'LocalMsgData.hpp': No such >> file or >> > directory >> > >> > >> > W dniu 2013-10-07 20:50:12 użytkownik >> napisał: >> >> Clare, >> >> >> >> >> >> The file 'LocalMsgData.hpp' is created by the build process. >> >> Depending on your build, the result can be found in >> >> >> >> build/Win32/{VCx}/{Debug|Release}/Nls/Include/ >> >> >> >> build/Win64/{VCx}/{Debug|Release}/Nls/Include/ >> >> >> >> Sincerely, >> >> Steven J. Hathaway >> > >> > >> >> >> > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org For additional commands, e-mail: dev-help@xalan.apache.org