From 7a07cdb51e90bcb3a33d0ba6bcd1d00f30e6d83a Mon Sep 17 00:00:00 2001 From: David Lawrence Ramsey Date: Sat, 19 Nov 2005 06:14:31 +0000 Subject: [PATCH] in faq.html, add a new section 5.3 to explain the status of nano's Unicode support git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3202 35c25a1d-7b9e-4130-9fde-d3aeb78583b8 --- ChangeLog | 3 +++ doc/faq.html | 8 ++++++-- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index b0be5144..5445f8d9 100644 --- a/ChangeLog +++ b/ChangeLog @@ -221,6 +221,9 @@ CVS code - - Mention that the minimum required version of texinfo is 4.0, since that's the first version that supports generating HTML. (DLR) +- doc/faq.html: + - Add a new section 5.3 to explain the status of nano's Unicode + support. (Mike Frysinger, minor tweaks by DLR) - doc/nano.texi: - Fix inconsistent wording and punctuation. (DLR) - Add missing configure options. (Mike Frysinger, minor tweaks diff --git a/doc/faq.html b/doc/faq.html index 8f582b57..1a73e64a 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -45,7 +45,8 @@ 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?
6.2. Why should I use Pico instead of nano?
@@ -221,6 +222,8 @@

In any case, translating nano is very easy. Just grab the nano.pot file from the latest and greatest nano distribution (it's in the po/ directory) and translate each line into your native language on the msgstr line. When you're done, you should send it to the TP's central po repository.

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.

6. Advocacy and Licensing

6.1. Why should I use nano instead of Pico?

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

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

8. ChangeLog

-

2005/08/27 - Update email address. (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)
2005/07/04 - Update section 4.10 to mention that pasting from the X clipboard via the middle mouse button also works when the Shift key is used. (DLR)
-- 2.39.5