<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<meta name="generator" content="Doxygen 1.8.6"/>
<title>Boost.Locale: Glossary</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="dynsections.js"></script>
<link href="navtree.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="resize.js"></script>
<script type="text/javascript" src="navtree.js"></script>
<script type="text/javascript">
  $(document).ready(initResizable);
  $(window).load(resizeHeight);
</script>
<link href="doxygen.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="top"><!-- do not remove this div, it is closed by doxygen! -->
<div id="titlearea">
<table cellspacing="0" cellpadding="0">
 <tbody>
 <tr style="height: 56px;">
  <td id="projectlogo"><img alt="Logo" src="boost-small.png"/></td>
  <td style="padding-left: 0.5em;">
   <div id="projectname">Boost.Locale
   </div>
  </td>
 </tr>
 </tbody>
</table>
</div>
<!-- end header part -->
<!-- Generated by Doxygen 1.8.6 -->
  <div id="navrow1" class="tabs">
    <ul class="tablist">
      <li><a href="index.html"><span>Main&#160;Page</span></a></li>
      <li class="current"><a href="pages.html"><span>Related&#160;Pages</span></a></li>
      <li><a href="modules.html"><span>Modules</span></a></li>
      <li><a href="namespaces.html"><span>Namespaces</span></a></li>
      <li><a href="annotated.html"><span>Classes</span></a></li>
      <li><a href="files.html"><span>Files</span></a></li>
      <li><a href="examples.html"><span>Examples</span></a></li>
    </ul>
  </div>
</div><!-- top -->
<div id="side-nav" class="ui-resizable side-nav-resizable">
  <div id="nav-tree">
    <div id="nav-tree-contents">
      <div id="nav-sync" class="sync"></div>
    </div>
  </div>
  <div id="splitbar" style="-moz-user-select:none;" 
       class="ui-resizable-handle">
  </div>
</div>
<script type="text/javascript">
$(document).ready(function(){initNavTree('glossary.html','');});
</script>
<div id="doc-content">
<div class="header">
  <div class="headertitle">
<div class="title">Glossary </div>  </div>
</div><!--header-->
<div class="contents">
<div class="textblock"><ul>
<li><a class="anchor" id="term_bmp"></a><b>Basic Multilingual Plane (BMP)</b> &ndash; a part of the <em>Universal Character Set</em> with code points in the range U-0000&ndash;U-FFFF. The most commonly used UCS characters lay in this plane, including all Western, Cyrillic, Hebrew, Thai, Arabic and CJK characters. However there are many characters that lay outside the BMP and they are absolutely required for correct support of East Asian languages.</li>
<li><b>Code</b> <b>Point</b> &ndash; a unique number that represents a "character" in the Universal Character Set. Code points lay in the range of 0-0x10FFFF, and are usually displayed as U+XXXX or U+XXXXXX, where X represents a hexadecimal digit.</li>
<li><a class="anchor" id="term_collation"></a><b>Collation</b> &ndash; a sorting order for text, usually alphabetical. It can differ between languages and countries, even for the same characters.</li>
<li><b>Encoding</b> - a representation of a character set. Some encodings are capable of representing the full UCS range, like UTF-8, and others can only represent a subset of it &ndash; ISO-8859-8 represents only a small subset of about 250 characters of the UCS. <br/>
 Non-Unicode encodings are still very popular, for example the Latin-1 (or ISO-8859-1) encoding covers most of the characters for Western European languages and significantly simplifies the processing of text for applications designed to handle only such languages. <br/>
 For Boost.Locale you should provide an eight-bit (<code>std::string</code>) encoding as part of the locale name, like <code>en_US.UTF-8</code> or <code>he_IL.cp1255</code> . <code>UTF-8</code> is recommended.</li>
<li><b>Facet</b> - or <code>std::locale::facet</code> &ndash; a base class that every object that describes a specific locale is derived from. Facets can be added to a locale to provide additional culture information.</li>
<li><b>Formatting</b> - representation of various values according to locale preferences. For example, a number 1234.5 (C representation) should be displayed as 1,234.5 in the US locale and 1.234,5 in the Russian locale. The date November 1st, 2005 would be represented as 11/01/2005 in the United States, and 01.11.2005 in Russia. This is an important part of localization. <br/>
 For example: does "You have to bring 134,230 kg of rice on 04/01/2010" means "134 tons of rice on the first of April" or "134 kg 230 g
    of rice on January 4th"? That is quite different.</li>
<li><b>Gettext</b> - The GNU localization library used for message formatting. Today it is the de-facto standard localization library in the Open Source world. Boost.Locale message formatting is entirely built on Gettext message catalogs.</li>
<li><b>Locale</b> - a set of parameters that define specific preferences for users in different cultures. It is generally defined by language, country, variants, and encoding, and provides information like: collation order, date-time formatting, message formatting, number formatting and many others. In C++, locale information is represented by the <code>std::locale</code> class.</li>
<li><b>Message</b> <b>Formatting</b> &ndash; the representation of user interface strings in the user's language. The process of translation of UI strings is generally done using some dictionary provided by the program's translator.</li>
<li><b>Message</b> <b>Domain</b> &ndash; in <em>gettext</em> terms, the keyword that represents a message catalog. This is usually an application name. When <em>gettext</em> and Boost.Locale search for a specific message catalog, they search in the specified path for a file named after the domain.</li>
<li><a class="anchor" id="term_normalization"></a> <b>Normalization</b> - Unicode normalization is the process of converting strings to a standard form, suitable for text processing and comparison. For example, character "ü" can be represented by a single code point or a combination of the character "u" and the diaeresis "¨". Normalization is an important part of Unicode text processing. <br/>
 Normalization is not locale-dependent, but because it is an important part of Unicode processing, it is included in the Boost.Locale library.</li>
<li><b>UCS-2</b> - a fixed-width Unicode encoding, capable of representing only code points in the <em>Basic Multilingual Plane (BMP)</em>. It is a legacy encoding and is not recommended for use.</li>
<li><b>Unicode</b> &ndash; the industry standard that defines the representation and manipulation of text suitable for most languages and countries. It should not be confused with the <em>Universal Character Set</em>, it is a much larger standard that also defines algorithms like bidirectional display order, Arabic shaping, etc.</li>
<li><b>Universal Character Set (UCS)</b> - an international standard that defines a set of characters for many scripts and their <em>code</em> <em>points</em>.</li>
<li><b>UTF-8</b> - a variable-width Unicode transformation format. Each UCS code point is represented as a sequence of between 1 and 4 octets that can be easily distinguished. It includes ASCII as a subset. It is the most popular Unicode encoding for web applications, data transfer and storage, and is the de-facto standard encoding for most POSIX operation systems.</li>
<li><b>UTF-16</b> - a variable-width Unicode transformation format. Each UCS code point is represented as a sequence of one or two 16-bit words. It is a very popular encoding for platforms such as the Win32 API, Java, C#, Python, etc. However, it is frequently confused with the <em>UCS-2</em> fixed-width encoding, which can only represent characters in the <em>Basic Multilingual Plane (BMP)</em>. <br/>
 This encoding is used for <code>std::wstring</code> under the Win32 platform, where <code>sizeof(wchar_t)==2</code>.</li>
<li><b>UTF-32/UCS-4</b> - a fixed-width Unicode transformation format, where each code point is represented as a single 32-bit word. It has the advantage of simple code point representation, but is wasteful in terms of memory usage. It is used for <code>std::wstring</code> encoding for most POSIX platforms, where <code>sizeof(wchar_t)==4</code>.</li>
<li><a class="anchor" id="term_case_folding"></a><b>Case Folding</b> - is a process of converting a text to case independent representation. For example case folding for a word "Grüßen" is "grüssen" - where the letter "ß" is represented in case independent way as "ss".</li>
<li><a class="anchor" id="term_title_case"></a><b>Title Case</b> - Is a text conversion where the words are capitalized. For example "hello world" is converted to "Hello World" </li>
</ul>
</div></div><!-- contents -->
</div><!-- doc-content -->

    <li class="footer">
&copy; Copyright 2009-2012 Artyom Beilis,  Distributed under the <a href="http://www.boost.org/LICENSE_1_0.txt">Boost Software License</a>, Version 1.0.
    </li>
   </ul>
 </div>
</body>
</html>
