libbu++.git - System level, general purpose C++ library.

Age	Commit message (Collapse)	Author
2012-03-25	Code is all reorganized. We're about ready to release. I should write up a	Mike Buland
	little explenation of the arrangement.
2011-10-27	Reorg'd! I merged in the release-fixup branch and fixed all random warnings.	Mike Buland
	I also cleaned up the build script, the symlink generation is faster and looks nicer, there's one think left to fix there, but it's not too bad.
2011-04-07	Pretty sure all utf encoders and decoders are complete and tested.	Mike Buland

2011-04-06	Libbu++ generates it's own system specific config file as well as a fancy	Mike Buland
	version header file all programs can now use to determine which version, api version, and svn revision of libbu++ they're linking against. It doesn't quite work for windows yet, but it will, eventually.
2011-04-04	UtfString is going really well. It can now parse Utf8, Utf16 (le,be), and	Mike Buland
	Utf32 (le,be). The internal storage seems to be working fine, although we do have a problem with random access, but at least we can tell which half of a surrogate pair we're on, so we can always rapidly determine the entire code point from any utf16 index that we're on. The only optomization that I'm not doing yet is reading in entire 16bit or 32bit words at a time and converting them from their byte order to native. There are a few potential issues with that, so we'll see. I added a couple of testing datafiles and a test program, I'll delete them all just as soon as it's verified to write correctly.
2011-04-04	I made some awesome progress on the UtfString system, it stores in native utf16	Mike Buland
	encoding to make things easier (little endian in our case). It can currently read utf8 and utf16be, but not BOM. It will give you full unicode code points instead of the raw utf16 values, which is pretty slick.
2011-03-22	We now have a UTF-8 test parser, I'm going to move it into a functor, I think.	Mike Buland

2011-01-20	Made (very) basic progress towards defining UtfString. It's actually going to	Mike Buland
	use a Bu::String as it's backend storage, so we'll get all the great out of that...
2011-01-20	Wow, got the Stream changes propegated, all tests build with string instead of	Mike Buland
	fstring, and updated the copyright notice to extend to 2011
2011-01-20	Bu::FString is now String, and there's a shell script to fix any other programs	Mike Buland
	that were using fstring, I hope.
2010-11-19	I now think that this may not work out at all. It looks like if we want proper	Mike Buland
	Unicode handling we'll need to implement a series of codecs and converters as well as tables of codepages and lookups. It'll be interesting, I guess, but it makes me care a lot less about proper encoding. Anyway, UtfString uses shorts instead of chars, so it's a step in the right direction, but still not enough to be able to handle proper UTF-16 encoding, maybe UCS-2 encoding, but... ...that's lame. Bu::FBasicString has been generalized a bit with optimizations from libc for char based strings. It also, unfortunately, still uses char-only functions in several places, those all rely on char casting strings at the moment just to get the thing to compile. Basically, it's not a good UTF-16 solution yet, and it may never be and remain compatible with char based strings.