Ticket #964: i18n.html.patch

.html

@@ -34 +34 @@
 &nbsp;</li>
   <li><a href="#Preservation">Preservation</a> of existing user code whenever 
   possible.<br>
 &nbsp;</li>
   <li><a href="#More_efficient">More efficient operations</a> when iterating over directories.<br>
 &nbsp;</li>
-  <li>A <a href="convenience.htm#basic_recursive_directory_iterator">recursive 
+  <li>A
+  <a href="tr2_proposal.html#Class-template-basic_recursive_directory_iterator">recursive 
   directory iterator</a> is now provided. </li>
 </ul>
 <p><a href="#Rationale">Rationale</a> for some of the changes is also provided.</p>
 <h2><a name="Internationalization">Internationalization</a></h2>
 <p>Cass templates <i>basic_path</i>, <i>basic_filesystem_error</i>, and <i>
 basic_directory_iterator</i> provide the basic mechanisms for 
@@ -64 +65 @@
 types is performed by path traits classes. The specific conversions for <i>path</i> 
 and <i>wpath</i> is implementation defined, with normative encouragement to use 
 the operating system's preferred file system encoding. For many modern POSIX-based 
 file systems the <i>wpath</i> external encoding is <a href="design.htm#Kuhn">
 UTF-8</a>, while for modern Windows file systems such as NTFS it is
 <a href="http://en.wikipedia.org/wiki/UTF-16">UTF-16</a>.</p>
-<p>The <a href="operations.htm">operational functions</a> in
+<p>The <a href="tr2_proposal.html#Operations-functions">operational functions</a> in
 <a href="../../../boost/filesystem/operations.hpp">operations.hpp</a> are provided with overloads for
 <i>path</i>, <i>wpath</i>, and user-defined <i>basic_path</i>'s. A
-<a href="operations.htm#Do-the-right-thing">&quot;do-the-right-thing&quot; rule</a> 
+<a href="tr2_proposal.html#Requirements-on-implementations">&quot;do-the-right-thing&quot; rule</a> 
 applies to implementations, ensuring that the correct overload will be chosen.</p>
 <h2><a name="Simplification">Simplification</a> of path interface</h2>
 <p>Prior versions of the library required users of class <i>path</i> to identify 
 the format (native or generic) and name error-checking policy, either via a 
 second constructor argument or via a default mechanism. That approach caused 
 complaints, particularly from users not needing the name checking features. The 
@@ -85 +86 @@
   These constructors are only provided to ease the transition of existing code.<br>
 &nbsp;</li>
   <li>Path name checking functionality has been moved out of class path and into 
   separate free-functions. This still provides name checking for those who need 
   it, but with much less impact on those who don't need it.</li>
 </ul>
-<p>Additionally, <a href="exception.htm">basic_filesystem_error</a> has been put 
+<p>Additionally,
+<a href="tr2_proposal.html#Class-template-basic_filesystem_error">basic_filesystem_error</a> has been put 
 on a diet and generally simplified.</p>
 <p>Error codes have been simplified and aligned with [POSIX-01]. A supporting 
 header <a href="../../../boost/filesystem/cerrno.hpp">
 &lt;boost/filesystem/cerrno.hpp&gt;</a> is also provided.</p>
 <p><code>&quot;//:&quot;</code> has been introduced as a path escape prefix to identify 
 native paths. Rationale: simplifies basic_path constructor interfaces, easier 
@@ -107 +109 @@
 what the expectations were for true and false values of the various predicates. 
 See the <a href="#table">table</a> below.</p>
 <h3>status()</h3>
 <p>As part of the predicate discussions, particularly with Rob Stewart, it 
 became obvious that sometimes applications need access to raw status information 
 without any possibility of an exception being thrown. The
-<a href="operations.htm#status">status()</a> function was added to meet this 
+<a href="tr2_proposal.html#Status-functions">status()</a> function was added to meet this 
 need. It also proved clearer to specify the semantics of predicate functions in 
 terms of status().</p>
 <h3><a name="is_file">is_file</a>()</h3>
 <p>About the same time, Jeff Garland suggested that an 
-<a href="operations.htm#is_file">is_file()</a> predicate would 
-compliment  
-<a href="operations.htm#is_directory">is_directory()</a>. In working on the analysis below, it became obvious 
+<a href="tr2_proposal.html#Predicate-functions">is_file()</a> predicate would 
+compliment <a href="tr2_proposal.html#Predicate-functions">is_directory()</a>. In working on the analysis below, it became obvious 
 that the expectations for is_file() were different from the expectations for !is_directory(), 
 so is_file() was added. </p>
 <h3><a name="is_other">is_other</a>()</h3>
 <p>On some operating systems, it is possible to have a directory entry which is 
-not for either a directory or a file. The <a href="operations.htm">is_other()</a> 
+not for either a directory or a file. The
+<a href="tr2_proposal.html#Predicate-functions">is_other()</a> 
 function identifies such cases.</p>
 <h3>Should predicates throw on errors?</h3>
 <p>Some conditions reported by operating systems as errors (see
 <a href="#Footnote">footnote</a>) clearly simply indicate that the predicate is 
 false, rather than indicating serious failure. But other errors represent 
 serious hardware or network problems, or permissions problems.</p>
 <p>Some people, particularly Rob Stewart, argue that in a function like 
-<a href="operations.htm#is_directory">is_directory()</a>, any error should simply cause the function to return false. If 
+<a href="tr2_proposal.html#Predicate-functions">is_directory()</a>, any error should simply cause the function to return false. If 
 there is actually an underlying problem, it will be detected it due course when 
 a directory_iterator or fstream operation is attempted.</p>
 <p>That view is was rejected because of the following considerations:</p>
 <ul>
   <li>As a general principle, the earlier errors can be reported, the better. 
   The rationale being that it is often much cheaper to fix errors sooner rather 
@@ -385 +387 @@
   conversions could cause incorrect results, that conversions best left to the 
   operating system would be performed, and that the technical complexity was too 
   great in relation to perceived benefits. User-defined types would only make 
   the problem worse.<br>
 &nbsp;</li>
 </ul>
-<h3>No versions of <a href="operations.htm#status">status()</a> which throw exceptions on 
+<h3>No versions of <a href="tr2_proposal.html#Status-functions">status()</a> which throw exceptions on 
 errors</h3>
 <p>The rationale for not including versions of status() 
 which throw exceptions on errors is that (1) the primary purpose of this 
 function is to perform queries at a very low-level, where exceptions are usually 
 unwanted, and (2) exceptions on errors are already provided by the predicate 
 functions. There would be little or no efficiency gain from providing a throwing 
 version of status().</p>
-<h3>Symlink identifying version of <a href="operations.htm#status">status()</a> function</h3>
+<h3>Symlink identifying version of <a href="tr2_proposal.html#Status-functions">status()</a> function</h3>
 <p>A symlink identifying version of the status() function is distinguished by a 
 second argument. Often separately named functions are more appropriate than 
 overloading when behavior 
 differs, which is the case here, while overloads are more appropriate when 
 behavior is the same but argument types differ (Iain Hanson). Overloading was 
 chosen in this particular case because a subjective judgment that a single 
@@ -412 +414 @@
 characters, the default conversion should not depend on the operating system 
 alone, but on the std::locale(&quot;&quot;) default. For example, the usual encoding 
 for Russian on Linux (and Russian web sites) is KOI8-R (RFC1489). The ability to safely specify a different locale 
 is also provided, to meet unforeseen needs.</p>
 <hr>
 <p>Revised
-<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->16 December, 2005<!--webbot bot="Timestamp" endspan i-checksum="38518" --></p>
+<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->03 June, 2007<!--webbot bot="Timestamp" endspan i-checksum="19946" --></p>
 <p>© Copyright Beman Dawes, 2005</p>
 <p>Distributed under the Boost Software License, Version 1.0.
 (See accompanying file <a href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
 copy at <a href="http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>)</p>
 
 </body>
 
 </html>