On Tue, 2009-07-28 at 18:33 +0100, Beat Forster wrote: > I'd prefer the 2nd way. However let me have a > look first to get an impression about > implications.
I gave it a try. The amount of changes in existing code is fairly small, but it was necessary to introduce two new functions with more fuzzy line end matching. See attached patches. The first one is unrelated to the problem, I only changed it because I was going to touch the code anyway. Please let me know what you think. I tested it with \n VTIMZONE definitions and \r\n, both gave the same result. I'd like to include this fix in SyncEvolution 0.9 together with the EXDATE workaround in the XML config. Ideally I'll commit both to the master branches so that it can get included in the upcoming nightly testing. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.
0001-vtimezone-use-const-string-instead-of-string-copy.patch
Description: application/mbox
0002-timezone-parsing-accept-r-n-and-r-as-line-ends-in.patch
Description: application/mbox
_______________________________________________ os-libsynthesis mailing list [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
