From 16437239908061f4ef8e560b940c577d2d186183 Mon Sep 17 00:00:00 2001 From: David Lawrence Ramsey Date: Sun, 26 Aug 2007 15:21:05 +0000 Subject: [PATCH] in doc/faq.html, update links to the Free Translation Project git-svn-id: svn://svn.savannah.gnu.org/nano/branches/nano_2_0_branch/nano@4169 35c25a1d-7b9e-4130-9fde-d3aeb78583b8 --- ChangeLog | 1 + doc/faq.html | 7 ++++--- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index 37fc0acc..a49e8250 100644 --- a/ChangeLog +++ b/ChangeLog @@ -84,6 +84,7 @@ CVS code - - Add COPYING.DOC to EXTRA_DIST. (DLR) - doc/faq.html: - Update RPM links for nano 2.0.x. (DLR) + - Update links to the Free Translation Project. (DLR) - doc/man/fr/nano.1, doc/man/fr/nanorc.5, doc/man/fr/rnano.1: - Make all copyright notices consistent. (DLR) - Delete translation of old licensing terms, until it can be diff --git a/doc/faq.html b/doc/faq.html index 467e21ba..cc9cb6f5 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -222,8 +222,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.

@@ -259,7 +259,8 @@

7.5. Can I have CVS write access?

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

8. ChangeLog

-

2007/07/29 - Update RPM links for nano 2.0.x. (DLR)
+

2007/08/26 - Update links to the Free Translation Project. (DLR)
+2007/07/29 - Update RPM links for nano 2.0.x. (DLR)
2007/04/18 - Add a new section 4.14 to explain how autoindent affects pasted text. (John M. Gabriele, minor tweaks by DLR)
2007/04/04 - Update email address. (DLR)
2007/01/01 - Update section 4.1 to describe how to open files with names beginning with '+' at specified columns as well as lines. (DLR)
-- 2.39.5