On Tuesday, August 05, 2014 11:30:57 AM Nagy-Egri Máté Ferenc wrote: > Hi! > > > > > I have been using CMake for quite some time now, but there are a few things > I don’t understand or I just don’t know how to accomplish. > > 1) Some time ago I posted about Unicode paths inside generated project files > do not work properly. The issue has been fixed. Though this issue is only a > cosmetic one, when I genetate anything with CMake under such a path I see > > -- Build files have been written to: > C:/Users/MßtÚFerenc/OneDrive/Develop/Active/GridRipper/VS2013 > > in the command line, where the actual path should contain “MátéFerenc”. I > don’t know if the displayed string internally is stored this way, or the > encoding gets messed at the very last moment when printed to the console. > Inspecting which is the case might uncover some bugs.
Its messed up when printed to the console. CMake is using the ANSI code page, but your console is using the OEM code page. If you look at the two tables for your ANSI and OEM code pages, you'll see that á on the ANSI code page is the same as ß on the OEM code page. So, when CMake prints the á character, the console displays the ß character. There is a chcp command you can use to change your console code page to your ANSI code page to fix the display. - Clint -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
