https://svn.boost.org/trac10/ticket/5992 <p> Without support for wide character string paths, we cannot easily open files with Unicode paths in Windows. This makes interprocess/file_mapping practically unusable for Windows programming. A suggestion might be to abstract out the use of raw strings for paths by using filesystem. </p> <p> Without the fix, we are using Win32 API to open memory-mapped files and forking the code for other platforms. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/5992 Trac 1.4.3 Andrey Semashev Sat, 13 Feb 2016 19:10:22 GMT https://svn.boost.org/trac10/ticket/5992#comment:1 https://svn.boost.org/trac10/ticket/5992#comment:1 <ul> <li><strong>cc</strong> <span class="trac-author">Andrey.Semashev@…</span> added </li> </ul> <p> I second this request, although not in relation to <code>file_mapping</code> but to <code>windows_shared_memory</code>. I have my local code using wide-character Windows API everywhere and <code>windows_shared_memory</code> is the only place where I cannot do that. </p> <p> Another rationale for moving away from the ANSI APIs is that they are not available on all Windows versions. They also use the unspecified ANSI code page to convert multibyte strings to UTF-16 (in my code I use UTF-8 for multibyte strings). </p> Ticket