From: David Lawrence Ramsey Date: Mon, 21 Nov 2005 20:08:42 +0000 (+0000) Subject: in faq.html, clarify section 5.3 to better explain how to enable Unicode X-Git-Tag: v1.3.10~40 X-Git-Url: https://git.wh0rd.org/?a=commitdiff_plain;h=d1ab4089659235b396ad897b4e1b1935413f6262;p=nano.git in faq.html, clarify section 5.3 to better explain how to enable Unicode support, and remove the mention of quirks, since they turned out to not be a nano problem git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3206 35c25a1d-7b9e-4130-9fde-d3aeb78583b8 --- diff --git a/ChangeLog b/ChangeLog index 62851137..75b3b195 100644 --- a/ChangeLog +++ b/ChangeLog @@ -224,6 +224,9 @@ CVS code - - doc/faq.html: - Add a new section 5.3 to explain the status of nano's Unicode support. (Mike Frysinger, minor tweaks by DLR) + - Clarify section 5.3 to better explain how to enable Unicode + support, and remove the mention of quirks, since they turned + out to not be a nano problem. (Mike Frysinger and DLR) - doc/nano.1: - Make one non-bold instance of "nano" bold, for consistency. (DLR) diff --git a/doc/faq.html b/doc/faq.html index 1a73e64a..6fd83ea8 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -45,7 +45,7 @@ 4.11. How do I select text for the clipboard in an X terminal when I'm running nano in one and nano's mouse support is turned on?

5. Internationalization

5.1. There's no translation for my language!
- 5.2. I don't like the translation for <x> in my language. How can I fix it? + 5.2. I don't like the translation for <x> in my language. How can I fix it?
5.3. What is the status of Unicode support?

6. Advocacy and Licensing

6.1. Why should I use nano instead of Pico?
@@ -223,7 +223,7 @@

5.2. I don't like the translation for <x> in my language. How can I fix it?

The best way would probably be to e-mail the person listed in the Last-Translator: field in the <your_language>.po file with your suggested corrections and they can make the changes reach the nano-devel list.

5.3. What is the status of Unicode support?

-

With the latest development version (1.3.9+), Unicode should be mostly usable. There are a few quirks with character counting, but with the proper terminal and encoding, you should be able to enter and save Unicode text.

+

With the latest development version (1.3.9+), 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.

6. Advocacy and Licensing

6.1. Why should I use nano instead of Pico?

@@ -255,7 +255,8 @@

Re-read Section 7.4 and you should know the answer.

8. ChangeLog

-

2005/11/19 - Add a new section 5.3 to explain the status of nano's Unicode support. (Mike Frysinger, minor tweaks by DLR)
+

2005/11/21 - Clarify section 5.3 to better explain how to enable Unicode support, and remove the mention of quirks, since they turned out to not be a nano problem. (Mike Frysinger and DLR)
+2005/11/19 - Add a new section 5.3 to explain the status of nano's Unicode support. (Mike Frysinger, minor tweaks by DLR)
2005/08/27 - Update email address. (DLR)
2005/08/10 - Add a new section 4.3, and move all section 4 entries after it down one number, to explain how to deal with numeric keypad problems. (DLR)
2005/08/08 - Update section 3.8 to mention that verbatim input mode now takes a six-digit hexadecimal number. (DLR)