Menu ▾ ▴

#35 No unicode support in new plugload subsystem

0.8
wont-fix
Alex
feature (7) api (8)
2013-07-25
2013-07-10
Alex
No

Filenames in the new plugin system assume ASCII (they use std::string, not wstring).

Implementation

See [[http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx]]

Discussion

  • Alex

    Alex - 2013-07-10
    • labels: --> feature, api
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,4 +1,5 @@
 Filenames in the new plugin system assume ASCII (they use std::string, not wstring).

-Implementation:
-See [http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx]
+Implementation
+--------------
+See [[http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx]]
     

  • Alex

    Alex - 2013-07-25

    As a stopgap measure if this is not implemented by release, we will release v0.7.2 with unicode bugfixes and (maybe) unicode support for *nix.

    However, it would be nice to have this done :)

     

  • Alex

    Alex - 2013-07-25
    • status: accepted --> wont-fix
     

  • Alex

    Alex - 2013-07-25

    Wont-Fix: Why?

    • On Linux, std::string is already UTF-8 aware, so no library support is necessary.
    • On Windows, there are several hacks required to get UTF-8 to work as it is not natively supported.

    See: http://www.utf8everywhere.org/

     

    Last edit: Alex 2013-07-25

Log in to post a comment.

veeam logo