Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 37646 invoked from network); 25 Oct 2003 17:58:39 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 25 Oct 2003 17:58:39 -0000 Received: (qmail 92393 invoked by uid 500); 25 Oct 2003 17:58:28 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 92355 invoked by uid 500); 25 Oct 2003 17:58:28 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 92342 invoked from network); 25 Oct 2003 17:58:27 -0000 Received: from unknown (HELO junior.lgc.com) (134.132.72.99) by daedalus.apache.org with SMTP; 25 Oct 2003 17:58:27 -0000 Received: from lgchvw01.lgc.com (lgchvw01.lgc.com [134.132.93.107]) by junior.lgc.com (8.11.7/8.11.3) with SMTP id h9PHvLQ01202 for ; Sat, 25 Oct 2003 12:57:22 -0500 (CDT) Received: from 134.132.93.152 by lgchvw01.lgc.com (InterScan E-Mail VirusWall NT); Sat, 25 Oct 2003 11:46:51 -0500 Received: by lgchexchbh.ad.lgc.com with Internet Mail Service (5.5.2657.72) id ; Sat, 25 Oct 2003 11:46:51 -0500 Message-ID: From: Dominique Devienne To: "'Ant Developers List'" Subject: RE: replacement of properties in addText(String) Date: Sat, 25 Oct 2003 11:46:50 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > From: Conor MacNeill [mailto:conor@cortexebusiness.com.au] > > > > Also, can someone explain me why Ant merges all the text segments > > of a node, when this node contains child elements? SAX doesn't... > > It has never really been a goal of Ant to support mixed content. In > general, elements should either support nested content or nested elements. Thanks. I appreciate the details, and I'll look up the thread for more. > This issue could be revisited but would need to be changed in a backward > compatible way. i.e. the Task would need to indicate that it wants to > receive mixed content. Is the usecase strong? No. I merely wanted to know the rational behind the current behavior, which I re-discovered working on an enhanced , which supports pretty-printing nested elements like s, etc... I turn around the issue by detecting mixed content, and failing in this case, and provided a simple nested element to properly interspace textual info with other nested elements. --DD --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org