Hi Felix, > Before 1.8.8 it was quite easy to extend H5FDwindows.c (windows vfd) to > cope with Unicode by using the wopen/w_char API for IO access on Windows > OS’. > > With 1.8.8. the windows driver was reduced to be a wrapper for the H5FD_SEC2 > driver. > > My question is what is the best way to come back to Unicode Windows support > for file access? H5FDstdio is not recommended for productive use but could > be extended similar to H5FDwindows.c in the early versions. Re-animating the > the full H5FDwindows seems to be against the development of the drivers, > right?
I would say you have two options, assuming you are ok with modifying the HDF5 code and rebuilding the library (as it seems from your email): 1) Just modify the SEC2 driver the way you used to modify the Windows driver. They were basically the same, which was the reason that we tossed the Windows VFD. 2) Copy the SEC2 VFD code, rename it H5FDWindows.c, adjust the internal names to use 'Windows' instead of 'sec2', make your fix, and recompile. A true Windows driver could be written pretty easily, and is at the back of my queue, but is currently unfunded. Also, the stdio code is, in fact, intended to be a demo driver for writing your own VFD (it only uses the public API, not our internal API). It isn't particularly well tested and there are a few open bugs related to external links that have yet to be fixed. Cheers, Dana _______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
