nano

nano with my custom patches
git clone git://bsandro.tech/nano
Log | Files | Refs | README | LICENSE

commit b0226fb86aea5db10ffdcfaa32c3d737632f9075
parent 386cc99385bbf79d8324176637920afdf20777ad
Author: David Lawrence Ramsey <pooka109@gmail.com>
Date:   Mon, 12 Jun 2006 20:26:38 +0000

in faq.html, update section 5.3, due to the display fix for two-column
Unicode characters


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3659 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

Diffstat:
MChangeLog | 2++
Mdoc/faq.html | 4++--
2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/ChangeLog b/ChangeLog @@ -425,6 +425,8 @@ CVS code - and how Unicode input only works when Unicode support is enabled. (DLR) - Add minor punctuation, wording, and typo fixes. (DLR) + - Update section 5.3, due to the display fix for two-column + Unicode characters. (DLR) - doc/nano.1: - Update the copyright years to include 2006. (DLR) - Explicitly mention that all regexes should be extended regular diff --git a/doc/faq.html b/doc/faq.html @@ -224,7 +224,7 @@ <h2><a name="5.2"></a>5.2. I don't like the translation for &lt;x&gt; in my language. How can I fix it?</h2> <blockquote><p>The best way would probably be to e-mail the person listed in the <code>Last-Translator:</code> field in the <b>&lt;your_language&gt;.po</b> file with your suggested corrections and they can make the changes reach the nano-devel list.</p></blockquote> <h2><a name="5.3"></a>5.3. What is the status of Unicode support?</h2> -<blockquote><p>With the latest development version (1.3.10+), Unicode should be mostly usable. With your terminal, locale (LC_ALL and similar environment variables), and encoding configured to properly support UTF-8, you should be able to enter and save Unicode text.</p></blockquote> +<blockquote><p>With the latest development version (1.3.12+), Unicode should be usable. With your terminal, locale (LC_ALL and similar environment variables), and encoding configured to properly support UTF-8, you should be able to enter and save Unicode text.</p></blockquote> <hr width="100%"> <h1><a name="6"></a>6. Advocacy and Licensing</h1> <h2><a name="6.1"></a>6.1. Why should I use nano instead of Pico?</h2> @@ -256,7 +256,7 @@ <blockquote><p>Re-read Section <a href="#7.4">7.4</a> and you should know the answer.</p></blockquote> <h2><a name="8"></a>8. ChangeLog</h2> <blockquote> -<p> +<p>2006/06/12 - Update section 5.3, due to the display fix for two-column Unicode characters. (DLR)<br> 2006/06/05 - Add a new section 4.8, and move all section 4 entries after it down one number, to explain how to deal with glibc 2.2.3's crashes involving extended regular expressions. (DLR)<br> 2006/06/04 - Add minor punctuation, wording, and typo fixes. (DLR)<br> 2006/05/27 - Update section 3.8 to mention the new "Unicode Input" prompt, and how Unicode input only works when Unicode support is enabled. (DLR)<br>