* po/README: Move language fetcing to ...

* linguas.sh: ... here.
	* po/README: Point to linguas.sh.

ChangeLog

@@ -1,3 +1,9 @@
+2012-04-04  Vladimir Serbinenko  <phcoder@gmail.com>
+
+	* po/README: Move language fetcing to ...
+	* linguas.sh: ... here.
+	* po/README: Point to linguas.sh.
+
 2012-04-04  Vladimir Serbinenko  <phcoder@gmail.com>
 
 	* po/README: Exclude ko.po due to disclaimer problems.

linguas.sh

@@ -0,0 +1,17 @@
+#!/bin/sh
+
+rsync -Lrtvz --exclude=ko.po  translationproject.org::tp/latest/grub/ po
+
+(
+    (
+	cd po && ls *.po| cut -d. -f1
+	echo "en@quot"
+	echo "en@hebrew"
+	echo "de@hebrew"
+	echo "en@cyrillic"
+	echo "en@greek"
+	echo "en@arabic"
+	echo "en@piglatin"
+	echo "de_CH"
+    ) | sort | uniq | xargs
+) >po/LINGUAS

po/README

@@ -6,11 +6,7 @@ that will hopefully clarify the situation.
   - If you're a user or a distributor, simply fill the po directory by
     importing translations from the Translation Project:
 
-      rsync -Lrtvz --exclude=ko.po  translationproject.org::tp/latest/grub/ po
+    	 ./linguas.sh
-
-    Then create a po/LINGUAS file listing all the language codes:
-
-      ((cd po && ls *.po| cut -d. -f1; echo "en@quot"; echo "en@hebrew"; echo "de@hebrew"; echo "en@cyrillic"; echo "en@greek"; echo "en@arabic" ;echo "en@piglatin"; echo "de_CH") | sort |uniq |  xargs) >po/LINGUAS
 
     GRUB's build system will automatically detect those and include them
     in your install.