I am assuming you are using a Win32 platform that is capable of e.g. Unicode
file names.
This is one of the core file-io APIs of HDF5:
hid_t H5Fopen( const char *name, unsigned flags, hid_t fapl_id )
As you can see the file name here is encoded in ASCII characters
with probably some of the extended 8 bit characters still valid.
This means you can _not_ use any Unicode characters in such a case.
A probably simple and thus nice work-around would be:
* for read: determine the file name using Win32 functions and then derive its
8.3 variant from that for using it in the H5Fopen command.
* for write: create the file using a temporary name. close the file using H5F
api and then rename the file to what you want using the win32 api.
Best regards
Alexander Stohr
Algorithm Developer
HDLE - Halla DAS Lab Europe GmbH
Schomburger Strasse 9, 88279 Amtzell, Germany
Tel:+49 7520 2024 800
Mail: [email protected]
Web: www.hdle.com
Managing Directors: Dr. Seok Cheol Kee, Andrea Weuffen, Wolfgang Vieweger
-----Ursprüngliche Nachricht-----
Von: Hdf-forum [mailto:[email protected]] Im Auftrag von
[email protected]
Gesendet: Montag, 4. August 2014 14:34
An: [email protected]
Betreff: [Hdf-forum] Problems when using hdf5 on non English windows
Our app uses internally HDF5 library. Problem occurs when client uses non
english windows - in example japan version.
When he choose to save / load file at path with special characters in filename
like in example some special folder with japanese-like words, whole operation
fails.
Is there any solution for such cases ?
Thanks for any help.
Regards,
Artur
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5
