Changes between Version 5 and Version 6 of rfc23_ogr_unicode

Timestamp:

Apr 25, 2008, 12:43:54 PM (16 years ago)

Author:

warmerdam

Comment:

reworked to use C API instead of CPLString

rfc23_ogr_unicode

@@ -57 +57 @@
 == iconv() ==
 
-It is proposed to implement the CPLString::recode() method using the iconv()
+It is proposed to implement the CPLRecode() method using the iconv()
 and related functions when available.  
 
@@ -66 +66 @@
 to use libiconv in preference to the system iconv() even when it is available.
 
-If iconv() is not available, a stub implementation of the CPLString services
+If iconv() is not available, a stub implementation of the recode services
 will be provided which:
 
@@ -74 +74 @@
  * Implements recoding from "UTF-8" to "ASCII" by turning all non-ASCII multi-byte characters to '?'. 
 
-This hopesfully gives us a weak operational status when built without iconv(), but full operation when it is available.
+This hopefully gives us a weak operational status when built without iconv(), but full operation when it is available.
 
 The --with-iconv=<arg> option will be added to configure.  The argument can be 
@@ -112 +112 @@
 
 Frank Warmerdam will implement the core iconv() capabilities, the 
-CPLString additions and update the ODBC driver.  Other OGR drivers would be
+CPLRecode() additions and update the ODBC driver.  Other OGR drivers would be
 updated as time and demand mandates to conform to the definitions in this RFC by 
 interested developers.