Nuclex.Fonts 1.2.0

Released on February the 15th, this release incorporates newline support,
drastic performance improvements when text is rendered using the new
TextManager component (even faster than using the BitmapFont directly)
as well as another attempt at finally getting the XBox 360 supported.

List of changes:

• 1.1.0 still had problems with the XBox 360 because the XBox apparently
  is unable to update smaller regions within a texture or vertex buffer.

  Thanks to Peter Pashley, these issues have finally been adressed and
  the remaining XBox 360 issues with Nuclex.Fonts should be solved.

  There are some minor performance issues left on the XBox360 that will
  be adressed at a later time. Namely, the first time a character is used,
  it will eat up some performance. Successive frames won't be affected,
  however, since the character will be in the cache after that.

• The TextManager component now greatly improves rendering speed by
  making better use of vertex batching.

  For the curious: the DrawString() method has to flush the vertices
  to the graphics card after each call to ensure no unwanted surprises
  in the drawing order when you mix text rendering with other drawing
  calls. Thus, it could not make effective use of vertex batching.

• Due to popular demand, newline ('\n') support has been added!

  This is still a work-in-progress feature. It will not yet yield the
  correct results when used for centered or right-aligned text.
  Automatic word-wise line breaking and tab ('\t') spacing haven't
  been completed either and will be provided with a future release.

• The font character bounding box is now expressed in pixels. The importer
  in 1.1.0 had a minor glitch that would save the font's bounding box
  in font units rather than pixels.