#233 Hunspell doesnot support Unicode dictionary file path

v1.0 (example)
closed-fixed
nobody
None
5
2014-08-22
2013-03-14
mahak garg
No

Hunspell uses fopen to open a dictionary file. fopen uses the OS native encoding to interpret the path. On English OS, if i place the Hunspell dictionaries at a location which contains Japanese/Russian characters in the path name , the dictionary files are not loaded. The code page for the English OS is not able to interpret the Japanese/Russian characters correctly.

Discussion

    • status: open --> closed-fixed
    • Group: --> v1.0 (example)
     
  • Fixed in the CVS (only in library level). Description:

    /* Hunspell(aff, dic) - constructor of Hunspell class
     * input: path of affix file and dictionary file
     *
     * In WIN32 environment, use UTF-8 encoded paths started with the long path
     * prefix \\\\?\\ to handle system-independent character encoding and very
     * long path names (without the long path prefix Hunspell will use fopen()
     * with system-dependent character encoding instead of _wfopen()).
     */
    

    Thanks for your bug report!

     
    Last edit: Németh László 2014-05-28