Lower Boost minimum version to 1.48.0 per user request.
Really make it 1.48 instead of 1.49.
Implement GUID using boost's implementation

Since we're maintaining a C api, the implementation is sometimes less than
intuitive from either a C or C++ perspective. I am trying to use as much
boost as possible while making all the guarantees that the C code makes.

One function was declared deprecated because it "wasn't thread safe". This
was straightforward to repair, and is no longer marked deprecated, and there
are now two ways to convert GUID to String: passing your own character
buffer, and having one returned to you that you need to free.
Rename guid_new to guid_replace

`new` implies some allocation. Since guid_new was actually constructing
a guid in place rather than allocating it, it makes much more sense to
call it guid_replace (or guid_construct). We went with guid_replace.
Cleared up GUID construction and allocation

To allocate a GUID, use guid_malloc. To allocate and construct a guid
(which is actually unique), use guid_new (and be sure to free it using
guid_free).
Corrected uses of guid_to_string.

Previously, guid_to_string had been marked deprecated with a note about
it not being thread-safe. It was much worse than "not thread safe", it
was only safe in a particular situation, and its safety was being violated
throughout the code. It was clear that users of guid_to_string did not
understand what it was purporting to do because of its varied uses. Most
uses simply treated it like a Garbage-Collected Java String (use and forget).
I actually found at least one instance where the string was being freed. (!!!)

I made the method have a particular easy-to-understand semantic: it returns
a pointer to a string which must be freed by the caller. I then tried to
track down all uses of this function and correct them. Mostly, I just changed
the usage to guid_to_string_buff with a stack-allocated string to avoid the
the malloc/free cycle.
Remove guid_init and guid_shutdown

They no longer do anything, and it's not probable that they ever will.
Fix a couple of minor issues noticed by Robert Frewell.
Removed the md5 file and updated the build system.

We no longer need md5.h or md5.c because all that work is done in the boost
uuid implementation.
Cleaned up some code and comments.

There should be no impacting changes in this commit.
Simplified some of the GUID code.

This change applies some recommendations from jralls. It better utilizes for loops,
and usage of swap. We also try to make sure the null guid is not freed since it's
reused, and catch a c++ exception to make sure it doens't escape into C code when
parsing a GUID.
Update Swedish translation

Copied from the Translation Project
Revert "The cash flow report should ignore splits in trading accounts."

This reverts commit 15e9bde7c3c190cb5385982343c3c545ab513baf.
See bug 622778 and 722140 for more details.
Revert "Round properly when computing fraction of the transaction's value due to a given split."

This reverts commit d33914139411a49429ec485dbd715a8559010945.
See bug 622778 and bug 722140 for more details.
Revert "Bug #622778 Miscalculation in cashflow reports - Step 03"

This reverts commit 77ff6036551905f15c6819c0b2225f069b5f4257.
See bug 622778 and bug 722140 for more details.
Revert "Bug #622778 Miscalculation in cashflow reports - Step 02"

This reverts commit 8a95c0f0b7ee737a5e00225acd4e639f3ce1d1c2.
See bug 622778 and bug 722140 for more details.
Revert "Bug #622778 Miscalculation in cashflow reports - Step 01"

This reverts commit 77340591a90f1eb16871e25f4c8bebad0092f7f2.
See bug 622778 and bug 722140 for more details.
Added new tests.

Added tests for string_to_guid and guid_replace.
Bug 120199 - Incorrect sort order in "Sort by Statement Date"

	modified:   src/gnome/gtkbuilder/gnc-plugin-page-register.glade
Replace built-in md5 hashing with GChecksum

Prepare for removing it when we replace the GncGUID implementation with Boost.