Changes between Version 7 and Version 8 of rfc30_utf8_filenames


Ignore:
Timestamp:
Sep 21, 2010, 4:17:16 PM (14 years ago)
Author:
warmerdam
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • rfc30_utf8_filenames

    v7 v8  
    109109== File Formats ==
    110110
    111 The proposed implementation really only addresses file format drivers that use VSIFOpenL() and related functions.  Some drivers dependent on external libraries (ie. netcdf) do not have a way to hook the file IO API and may not support utf-8 filenames.  It might be nice to be able to distinguish these.
     111The proposed implementation really only addresses file format drivers that use VSIFOpenL(), VSIFOpen() and related functions.  Some drivers dependent on external libraries (ie. netcdf) do not have a way to hook the file IO API and may not support utf-8 filenames.  It might be nice to be able to distinguish these.
    112112
    113 At the very least any driver marked with GDAL_DCAP_VIRTUALIO as "YES" will support UTF-8.  Perhaps this opportunity ought to be used to more uniformly apply this driver metadata.
    114 
    115 As part of this effort the following drivers have been marked as supporting virtualio (VSI*L API) after testing, or upgraded to support it: BSB, PDS, ISIS2, ISIS3, DIMAP, AIG, XPM, CEOS, SAR_CEOS, SDTS, FIT, GRIB, EIR, LAN, INGR.
     113At the very least any driver marked with GDAL_DCAP_VIRTUALIO as "YES" will support UTF-8.  Perhaps this opportunity ought to be used to more uniformly apply this driver metadata (done).
    116114
    117115== Test Suite ==
    … …  
    119117We will need to introduce some test suite tests with multibyte utf-8 filenames.  In support of that aspects of the VSI*L API - particularly the rename, mkdir, rmdir, functions and VSIFOpenL itself have been exposed in python.
    120118
     119== Documentation ==
     120
     121Appropriate API entry points will be documented as taking and return UTF-8 strings.