Release 2.3.3

git-svn-id: http://svn.code.sf.net/p/utfcpp/code@137 a809a056-fc17-0410-9590-b4f493f8b08e

doc/ReleaseNotes

@@ -1,11 +1,10 @@
 utf8 cpp library
-Release 2.3.2
+Release 2.3.3
 
-A bug fix release plus minor performance improvements. Thanks to all who reported bugs. 
+A minor bug fix release. Thanks to all who reported bugs. 
 
-Changes from version 2.3.1
+Changes from version 2.3.2
-- Bug fix [3506114]: potential crash in replace_invalid
+- Bug fix [39]: checked.h Line 273 and unchecked.h Line 182 have an extra ';'
-- Bug fix [3426789]: documentation typo
+- Bug fix [36]: replace_invalid() only works with back_inserter
-- Bug fix [3215839]: name clash with std::next
 
 Files included in the release: utf8.h, core.h, checked.h, unchecked.h, utf8cpp.html, ReleaseNotes

doc/utf8cpp.html

@@ -88,9 +88,6 @@
         <li>
           <a href="#points">Points of Interest</a>
         </li>
-        <li>
-          <a href="#conclusion">Conclusion</a>
-        </li>
         <li>
           <a href="#links">Links</a>
         </li>
@@ -101,10 +98,12 @@
     </h2>
     <p>
       Many C++ developers miss an easy and portable way of handling Unicode encoded
-      strings. The original C++ Standard (known as C++98 or C++03) is Unicode agnostic,
+      strings. The original C++ Standard (known as C++98 or C++03) is Unicode agnostic.
-      and while some work is being done to introduce Unicode to the next incarnation
+      C++11 provides some support for Unicode on core language and library level:
-      called C++0x, for the moment nothing of the sort is available. In the meantime,
+      u8, u, and U character and string literals, char16_t and char32_t character types,
-      developers use third party libraries like ICU, OS specific capabilities, or simply
+      u16string and u32string library classes, and codecvt support for conversions 
+      between Unicode encoding forms.
+      In the meantime, developers use third party libraries like ICU, OS specific capabilities, or simply
       roll out their own solutions.
     </p>
     <p>
@@ -1751,6 +1750,10 @@ assert (*un_it == <span class="literal">0x10346</span>);
         non-generic, and doesn't play well with the Standard Library. I definitelly
         recommend looking at ICU even if you don't plan to use it.
       </li>
+      <li>
+        C++11 language and library features. Still far from complete, and not widely
+        supported by compiler vendors. 
+      </li>
       <li>
         <a href=
         "http://www.gtkmm.org/gtkmm2/docs/tutorial/html/ch03s04.html">Glib::ustring</a>.
@@ -1761,18 +1764,9 @@ assert (*un_it == <span class="literal">0x10346</span>);
       <li>
         Platform dependent solutions: Windows and POSIX have functions to convert strings
         from one encoding to another. That is only a subset of what my library offers,
-        but if that is all you need it may be good enough, especially given the fact that
+        but if that is all you need it may be good enough.
-        these functions are mature and tested in production.
       </li>
     </ol>
-    <h2 id="conclusion">
-      Conclusion
-    </h2>
-    <p>
-      Until Unicode becomes officially recognized by the C++ Standard Library, we need to
-      use other means to work with UTF-8 strings. Template functions I describe in this
-      article may be a good step in this direction.
-    </p>
     <h2 id="links">
       Links
     </h2>