thanks, that was the solution. Pablo
----- Original Message ----- From: "Tony Dodd" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 11, 2003 1:10 PM Subject: RE: CDATA section > Pablo > > I found just the same. This problem will go away if you set > split-cdata-sections to false, assuming you can safely do that. > > Tony Dodd > > >-----Original Message----- > >From: Pablo Yabo [mailto:[EMAIL PROTECTED] > >Sent: 11 March 2003 13:40 > >To: [EMAIL PROTECTED] > >Subject: Re: CDATA section > > > > > >that was a mistake, but the CData section is created using API > >functions, so it has the opening square bracket. I need to > >send to another library the data inside the CDATA, so I need > >to send <Trigger><None/></Trigger>, no > ><Trigger></></Trigger>. I need to replace &It; with '<'. > > > >Pablo > > > >----- Original Message ----- > >From: "Jesse Pelton" <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Sent: Tuesday, March 11, 2003 10:15 AM > >Subject: RE: CDATA section > > > > > >> I don't know if it would be relevant, but you've omitted the opening > >square > >> bracket in your CDATA section. Does it actually look the way you > >indicated, > >> or does it include the opening square bracket ("<![CDATA[ > >> <Trigger><None/></Trigger> ]]>") as required by the spec? > >> > >> -----Original Message----- > >> From: Pablo Yabo [mailto:[EMAIL PROTECTED] > >> Sent: Tuesday, March 11, 2003 7:49 AM > >> To: [EMAIL PROTECTED] > >> Subject: Re: CDATA section > >> > >> > >> I've got a code fragment: > >> ... > >> m_formTarget = new MemBufFormatTarget; > >> > >> theSerializer->writeNode(m_formTarget, *m_doc); > >> delete theSerializer; > >> > >> return (const char *) m_formTarget->getRawBuffer(); > >> } > >> > >> the document m_doc has CDATA section as this "<![CDATA > >> <Trigger><None/></Trigger> ]]>" > >> > >> and when I get the buffer they are written as: <![CDATA[ > >> <Trigger></></Trigger> > >> ]]> > >> > >> Pablo > >> > >> > >> ----- Original Message ----- > >> From: "Gareth Reakes" <[EMAIL PROTECTED]> > >> To: <[EMAIL PROTECTED]> > >> Sent: Tuesday, March 11, 2003 9:16 AM > >> Subject: Re: CDATA section > >> > >> > >> > Hi, > >> > post the snippet of code where you do this and I will annotate it > >> > explaining what is going on. > >> > > >> > Gareth > >> > > >> > > >> > On Tue, 11 Mar 2003, Pablo Yabo wrote: > >> > > >> > > but, I send the tree to a MemBufFormatTarget and then I get the > >> > > text > >> with > >> > > getRawBuffer. > >> > > How can I get the original document here? > >> > > > >> > > Pablo > >> > > ----- Original Message ----- > >> > > From: "Gareth Reakes" <[EMAIL PROTECTED]> > >> > > To: "xerces" <[EMAIL PROTECTED]> > >> > > Sent: Tuesday, March 11, 2003 5:54 AM > >> > > Subject: Re: CDATA section > >> > > > >> > > > >> > > > Hi, > >> > > > when the content is serialized xerces will escape < characters > >> > > > in CDATA as this would make the document illegal. It > >will remove > >> > > > them > >> again > >> > > > when you parse. > >> > > > > >> > > > Gareth > >> > > > > >> > > > > >> > > > > >> > > > On Mon, 10 Mar 2003, Pablo Yabo wrote: > >> > > > > >> > > > > Hi, > >> > > > > How can I add a string "<trigger>something</trigger>" in the > >> > > > > data > >> > > section. > >> > > > > When I add the content the library changes the > >content as this > >> > > "<Trigger></></Trigger>". > >> > > > > > >> > > > > Pablo > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
