Travis P wrote:
> On Apr 5, 2004, at 11:15 AM, C.A.T.Magic wrote:
>> If you follow the thread I tried XML and ended with a new problem,
>> the "#13\r\n" linefeeds inside of the log messages.
>
> Ah, okay, had forgotten that. Those issues look surmountable.
>
> You can see here what is prescribed for white-space and end-of-line
> handling:
> http://www.w3.org/TR/2004/REC-xml-20040204/#sec-white-space
thanks for your help and this link. this cleared up a lot.
i now found out that this was a bug with text/binary (windows)
mode on file open.
> You may find that you have a non-compliant processor. Compliant processors
> are readily available for C/C++/Java (see my comment below), but I don't
> know
> about Ruby/Python, etc.
the xml parser supplied with ruby seems to work and produces the
correct output. i've not yet figured out how i get the right xml parser
callbacks but thats just a matter of time and learing on my part... :)
>> I also think using an XML parser for this task is overkill.
>> I'd get a new deopendency on an XML parser module in my tools,
>> have to find a free or at least LGPL parser that is bugfree and
>> up-to-date etc...
> Well, Subversion uses expat which is included with apr-util. It is
> included in the source tarball and has a BSD-style license. For Java
> and C/C++ apps, I've used Xerces (http://xml.apache.org ; again, a very
> liberal license ). You may find that once you have such a reusable
> software component, it proves its worth in numerous other applications.
> But then again, perhaps not for your tasks.
i have to experiment a bit more with existing xml parsers and then
rewrite some parts of my tools... but I agree that it's not a bad thing
to have an xml parser at hand.
thanks for all the responses on this thread.
c.a.t.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 6 02:14:54 2004