<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
sussman wrote:<br>
<blockquote type="cite"
cite="mid200505250116.j4P1GgfV008046@sanpietro.red-bean.com">
<pre wrap="">Author: sussman
Date: Tue May 24 20:16:41 2005
New Revision: 1330
</pre>
</blockquote>
You're a madman. Here's the review you requested.<br>
<blockquote type="cite"
cite="mid200505250116.j4P1GgfV008046@sanpietro.red-bean.com">
<pre wrap="">+ <para>Most modern operating systems have a notion
+ of <quote>current locale</quote>—that is, the current
+ region or country that the computer is located in. The value
+ of the locale affects the way in which programs present data
+ to the user, as well as the way in which they accept user
+ input.</para>
</pre>
</blockquote>
Here, and throughout this section, you should not refer to "the value
of the locale". You've defined a locale, but it isn't the <i>locale </i>that
affects anything on the computer -- it's the values of configuration
tokens related to certain display characteristics and conventions that
often differ from locale to locale.<br>
<blockquote type="cite"
cite="mid200505250116.j4P1GgfV008046@sanpietro.red-bean.com">
<pre wrap="">+
+ <para>On Unix-like systems, the value of the current locale can
+ be seen by running the <command>locale</command>
+ command:</para>
</pre>
</blockquote>
Again, the "locale" program shows not the value of the locale (is that
something studied by the social sciences? :-) ), but the values of
environment variables which control various display conventions that
are locale-dependent. I know it might sound like I'm splitting hairs,
but we should avoid sounding ignorant (even if we really are).<br>
<blockquote type="cite"
cite="mid200505250116.j4P1GgfV008046@sanpietro.red-bean.com">
<pre wrap="">+
+ <screen>
+$ locale
+LANG=
+LC_COLLATE="C"
+LC_CTYPE="C"
+LC_MESSAGES="C"
+LC_MONETARY="C"
+LC_NUMERIC="C"
+LC_TIME="C"
+LC_ALL="C"
+</screen>
+
+ <para>The output is a list of locale-related environment
+ variables and their current values. In this example, the</pre>
</blockquote>
Ah, Now *that's* the Truth I've been searching for.<br>
<blockquote type="cite"
cite="mid200505250116.j4P1GgfV008046@sanpietro.red-bean.com">
<pre wrap="">+ <para>The Subversion client, <command>svn</command>, makes use
+ of the current locale in two ways. First, it notices the
</pre>
</blockquote>
How about, "...honors the current locale configuration in two ways."<br>
<blockquote type="cite"
cite="mid200505250116.j4P1GgfV008046@sanpietro.red-bean.com">
<pre wrap="">+ using the GNU <command>gettext</command> package, which
</pre>
</blockquote>
Package != command. There's no need to add markup to "gettext" when
used in this way, just as we don't add markup every time we refer to
Subversion.<br>
<blockquote type="cite"
cite="mid200505250116.j4P1GgfV008046@sanpietro.red-bean.com">
<pre wrap="">+ results in translation <quote>modules</quote> that end
</pre>
</blockquote>
Lose the <quote>'s. They are modules.<br>
<blockquote type="cite"
cite="mid200505250116.j4P1GgfV008046@sanpietro.red-bean.com">
<pre wrap="">+ system. On Unix, they typically live
+ in <filename>/usr/local/share/locale/</filename>, while on
</pre>
</blockquote>
If we standardize on /usr/bin as the install path, is this still true?
Or does it become /usr/share/locale/ ?<br>
<blockquote type="cite"
cite="mid200505250116.j4P1GgfV008046@sanpietro.red-bean.com">
<pre wrap="">+ as <filename>/usr/local/share/locale/de/LC_MESSAGES/subversion.mo</filename>.
</pre>
</blockquote>
(Same here.)<br>
<blockquote type="cite"
cite="mid200505250116.j4P1GgfV008046@sanpietro.red-bean.com">
<pre wrap="">+ <para>The second way in which locale is important is that it
+ tells the <command>svn</command> program how to interpret your
+ input. The repository stores all paths, filenames, and log
</pre>
</blockquote>
"The second way in which the locale is honored involves how
<command>svn</command> interprets your input.<br>
<blockquote type="cite"
cite="mid200505250116.j4P1GgfV008046@sanpietro.red-bean.com">
<pre wrap="">+ <para>For example, suppose you create a file
+ named<filename>caffè.txt</filename>, and then when committing
+ the file, you write the log message as <quote>Adesso il caffè
+ è più forte</quote>. Both the filename and log message
</pre>
</blockquote>
. o O ( If there's ever another hardcopy, I hope ORA's input filters
can deal with this stuff... )<br>
<blockquote type="cite"
cite="mid200505250116.j4P1GgfV008046@sanpietro.red-bean.com">
<pre wrap="">+ <sidebar>
+ <title>"Error: can't recode string"</title>
+
+ <para>Are you seeing this error? It means that the Subversion
</pre>
</blockquote>
Objection -- leading the witness! Also, I think it's bad form for the
paragraphs in a section to actually depend on the section title having
been read. I know, that might sound odd, but that's just me. Suggest
giving a more generic title ("String recoding errors", say) and moving
the specifics into the main text.<br>
<br>
</body>
</html>