From 167a4b7f9c233c9f4e98c0856364b2712f3d020d Mon Sep 17 00:00:00 2001 From: David Lawrence Ramsey Date: Thu, 16 Mar 2006 19:16:28 +0000 Subject: [PATCH] in faq.html, update the Free Translation Project's address git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3305 35c25a1d-7b9e-4130-9fde-d3aeb78583b8 --- ChangeLog | 2 ++ doc/faq.html | 7 ++++--- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index 5642f2d6..76acbddd 100644 --- a/ChangeLog +++ b/ChangeLog @@ -76,6 +76,8 @@ CVS code - space for converted when a line ends in a tab(s) and we're not in UTF-8 mode. (DLR, found by Duncan Geoffry Doyle, Nick Warne, and Mike Frysinger) +- doc/faq.html: + - Update the Free Translation Project's address. (DLR) - doc/nano.1: - Better display the default values for quotestr. (DLR) - doc/nanorc.5: diff --git a/doc/faq.html b/doc/faq.html index 9702e56f..2c35e8e8 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -217,8 +217,8 @@

5. Internationalization

5.1. There's no translation for my language!

-

On June of 2001, GNU nano entered the Free Translation Project and since then, translations should be managed from there.

-

If there isn't a translation for your language, you could ask your language team to translate nano, or better still, join your team and do it yourself. Joining a team is easy. You just need to ask the TP coordinator to add you to your team, and send a translation disclaimer to the FSF (this is necessary as nano is an official GNU package, but it does not mean that you transfer the rights of your work to the FSF, it's just so the FSF can legally manage them).

+

On June of 2001, GNU nano entered the Free Translation Project and since then, translations should be managed from there.

+

If there isn't a translation for your language, you could ask your language team to translate nano, or better still, join your team and do it yourself. Joining a team is easy. You just need to ask the TP coordinator to add you to your team, and send a translation disclaimer to the FSF (this is necessary as nano is an official GNU package, but it does not mean that you transfer the rights of your work to the FSF, it's just so the FSF can legally manage them).

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.

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

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

8. ChangeLog

-

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)
+

2006/03/16 - Update the Free Translation Project's address. (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)
-- 2.39.5