Remove gettext doc excerpt until the license is sorted out.

The Free Software Foundation has distributed the GNU gettext manual
under at least two different licenses (a brief copyleft and GNU FDL),
but neither of those seems compatible with the GPLv2 of ELinks.
(cherry picked from commit 9c1873a517)

po/README

@@ -166,131 +166,8 @@ well, especially Last-Translator and PO-Revision-Date fields.
 --------------------
 
 First set Plural-Forms: header (msgid "" at top of .po file) to some correct
-value, depending on language.
+value, depending on language. See GNU gettext documentation for details, at
-
+http://www.gnu.org/software/gettext
-To help you in this, here is an excerpt from GNU gettext documentation:
-
-Only one form:
-	Some languages only require one single form. There is no distinction
-	between the singular and plural form. An appropriate header entry
-	would look like this:
-
-	Plural-Forms: nplurals=1; plural=0;
-
-	Languages with this property include:
-
-	Finno-Ugric family
-		Hungarian
-	Asian family
-		Japanese, Korean
-	Turkic/Altaic family
-		Turkish
-
-Two forms, singular used for one only:
-	This is the form used in most existing programs since it is what English
-	is using. A header entry would look like this:
-
-	Plural-Forms: nplurals=2; plural=n != 1;
-
-	(Note: this uses the feature of C expressions that boolean expressions
-	 have to value zero or one.)
-
-	Languages with this property include:
-
-	Germanic family
-		Danish, Dutch, English, German, Norwegian, Swedish
-	Finno-Ugric family
-		Estonian, Finnish
-	Latin/Greek family
-		Greek
-	Semitic family
-		Hebrew
-	Romanic family
-		Italian, Portuguese, Spanish
-	Artificial
-		Esperanto
-
-Two forms, singular used for zero and one:
-	Exceptional case in the language family. The header entry would be:
-
-	Plural-Forms: nplurals=2; plural=n>1;
-
-	Languages with this property include:
-
-	Romanic family
-		French, Brazilian Portuguese
-
-Three forms, special case for zero:
-	The header entry would be:
-
-	Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n != 0 ? 1 : 2;
-
-	Languages with this property include:
-
-	Baltic family
-		Latvian
-
-Three forms, special cases for one and two:
-	The header entry would be:
-
-	Plural-Forms: nplurals=3; plural=n==1 ? 0 : n==2 ? 1 : 2;
-
-	Languages with this property include:
-
-	Celtic
-		Gaeilge (Irish)
-
-Three forms, special case for numbers ending in 1[2-9]:
-	The header entry would look like this:
-
-	Plural-Forms: nplurals=3; \
-		plural=n%10==1 && n%100!=11 ? 0 : \
-		n%10>=2 && (n%100<10 || n%100>=20) ? 1 : 2;
-
-	Languages with this property include:
-
-	Baltic family
-		Lithuanian
-
-Three forms, special cases for numbers ending in 1 and 2, 3, 4,
-except those ending in 1[1-4]:
-	The header entry would look like this:
-
-	Plural-Forms: nplurals=3; \
-		plural=n%10==1 && n%100!=11 ? 0 : \
-		n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;
-
-	Languages with this property include:
-
-	Slavic family
-		Croatian, Czech, Russian, Slovak, Ukrainian
-
-Three forms, special case for one and some numbers ending in 2, 3, or 4:
-	The header entry would look like this:
-
-	Plural-Forms: nplurals=3; \
-		plural=n==1 ? 0 : \
-		n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;
-
-	Languages with this property include:
-
-	Slavic family
-		Polish
-
-Four forms, special case for one and all numbers ending in 02, 03, or 04:
-	The header entry would look like this:
-
-	Plural-Forms: nplurals=4; \
-		plural=n%100==1 ? 0 : n%100==2 ? 1 : n%100==3 || n%100==4 ? 2 : 3;
-
-	Languages with this property include:
-
-	Slavic family
-		Slovenian
-
-
-More info at http://www.gnu.org/software/gettext
-
 
 Plural forms will appear like this in .po file: