]> git.proxmox.com Git - ceph.git/blame - ceph/src/boost/libs/locale/doc/running_examples_under_windows.txt
bump version to 12.2.2-pve1
[ceph.git] / ceph / src / boost / libs / locale / doc / running_examples_under_windows.txt
CommitLineData
7c673cae
FG
1//
2// Copyright (c) 2009-2011 Artyom Beilis (Tonkikh)
3//
4// Distributed under the Boost Software License, Version 1.0. (See
5// accompanying file LICENSE_1_0.txt or copy at
6// http://www.boost.org/LICENSE_1_0.txt)
7//
8
9// vim: tabstop=4 expandtab shiftwidth=4 softtabstop=4 filetype=cpp.doxygen
10/*!
11\page running_examples_under_windows Running Examples under Microsoft Windows
12
13All of the examples that come with Boost.Locale are designed for UTF-8 and it is
14the default encoding used by Boost.Locale.
15
16However, the default narrow encoding under Microsoft Windows is not UTF-8 and
17the output of the applications would not be displayed correctly in the console.
18
19So in order to use UTF-8 encoding under the Windows console and see the output correctly, do the following:
20
21-# Open a \c cmd window
22-# Change the default font to a TrueType font: go to properties-\>font (right click on title-bar-\>properties-\>font) and
23change the font to a TrueType font like Lucida Console
24-# Change the default codepage to 65001 (UTF-8) by running <tt>chcp 65001</tt>
25
26Now all of the examples should display UTF-8 characters correctly (if the font supports them).
27
28<b>Note for Visual Studio users:</b> Microsoft Visual Studio assumes that all source files are encoded using an "ANSI" codepage
29like 1252. However all examples use UTF-8 encoding by default, so wide character examples would
30not work under MSVC as-is. In order to force it to treat source files as UTF-8 you need to
31convert the files to UTF-8 with BOM, which can be done easily by re-saving them from Notepad,
32which adds a BOM to UTF-8 files by default.
33
34
35*/
36