diff --git a/ChangeLog b/ChangeLog index 5642f2d6355df409cb5897a30b36bd519a8da7ab..76acbddd611b0411e4f1052145baa0e3ed92f482 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 9702e56f697575451fa2b061c6a5f9bdf76fab89..2c35e8e85eaabb24667d84be361925334f1cd493 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -217,8 +217,8 @@ <hr width="100%"> <h1><a name="5"></a>5. Internationalization</h1> <h2><a name="5.1"></a>5.1. There's no translation for my language!</h2> -<blockquote><p>On June of 2001, GNU nano entered the <a href="http://www.iro.umontreal.ca/contrib/po/HTML/">Free Translation Project</a> and since then, translations should be managed from there.</p> - <p>If there isn't a translation for your language, you could ask <a href="http://www.iro.umontreal.ca/contrib/po/HTML/teams.html">your language team</a> to translate nano, or better still, join your team and do it yourself. Joining a team is easy. You just need to ask the <a href="mailto:translation@iro.umontreal.ca">TP coordinator</a> to add you to your team, and send a <a href="http://www.iro.umontreal.ca/contrib/po/HTML/disclaim.html">translation disclaimer to the FSF</a> (this is necessary as nano is an official GNU package, but it does <b>not</b> mean that you transfer the rights of your work to the FSF, it's just so the FSF can legally manage them).</p> +<blockquote><p>On June of 2001, GNU nano entered the <a href="http://www.iro.umontreal.ca/translation/HTML/">Free Translation Project</a> and since then, translations should be managed from there.</p> + <p>If there isn't a translation for your language, you could ask <a href="http://www.iro.umontreal.ca/translation/HTML/teams.html">your language team</a> to translate nano, or better still, join your team and do it yourself. Joining a team is easy. You just need to ask the <a href="mailto:translation@iro.umontreal.ca">TP coordinator</a> to add you to your team, and send a <a href="http://www.iro.umontreal.ca/translation/HTML/disclaim.html">translation disclaimer to the FSF</a> (this is necessary as nano is an official GNU package, but it does <b>not</b> mean that you transfer the rights of your work to the FSF, it's just so the FSF can legally manage them).</p> <p>In any case, translating nano is very easy. Just grab the <b>nano.pot</b> file from the latest and greatest nano distribution (it's in the <b>po/</b> directory) and translate each line into your native language on the <b>msgstr</b> line. When you're done, you should send it to the TP's central po repository.</p></blockquote> <h2><a name="5.2"></a>5.2. I don't like the translation for <x> 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><your_language>.po</b> file with your suggested corrections and they can make the changes reach the nano-devel list.</p></blockquote> @@ -255,7 +255,8 @@ <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>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)<br> +<p>2006/03/16 - Update the Free Translation Project's address. (DLR)<br> +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)<br> 2005/11/19 - Add a new section 5.3 to explain the status of nano's Unicode support. (Mike Frysinger, minor tweaks by DLR)<br> 2005/08/27 - Update email address. (DLR)<br> 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)<br>