That's handy because that's the algorithm I use when writing the save file back. It's not relevant for the parser though. Providing I can separate all the individual 'tokens' (ie words or strings that belong together), and there only needs to be a space, or a defined character for that (ie a quote, a brace, an equals sign etc).
I have had a bit of connundrum the last day or two. My Parser library when released will be separate from the ckTrim application. This library will be usable by .NET developers to use in their own tools. Other developers will be able to use the library to develop their own bridefinders and family tree makers, and the parser will do the reading, writing and organising of the data into a usable class structure. They just have to use the data in whatever way they want, and then ask the parser to write any changes back.
However, I haven't developed the public interface to this yet, so am reluctant to release it.
But, the decision I made is to put the library code in with the ckTrim application. This means I can release the ckTrim application for those waiting... before finalising my library. The downside is that it will make the .exe a bit bigger - but it'll still be manageable.