[Po4a-commits] po4a/t/data-04 text-iso8859.pod-ok,1.2,1.3 utf.pod-ok,1.1,1.2

Denis Barbier po4a-devel@lists.alioth.debian.org
Fri, 27 Aug 2004 18:18:37 +0000


Update of /cvsroot/po4a/po4a/t/data-04
In directory haydn:/tmp/cvs-serv31074/t/data-04

Modified Files:
	text-iso8859.pod-ok utf.pod-ok 
Log Message:
Do not write po4a version number in generated files, this number
has to be fixed everytime in test files.


Index: utf.pod-ok
===================================================================
RCS file: /cvsroot/po4a/po4a/t/data-04/utf.pod-ok,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- utf.pod-ok	9 Aug 2004 15:01:21 -0000	1.1
+++ utf.pod-ok	27 Aug 2004 18:18:34 -0000	1.2
@@ -4,9 +4,8 @@
         * THIS IS NO SOURCE FILE, BUT RESULT OF COMPILATION *
         *****************************************************
 
-This file was generated by po4a(7) version 0.17.2. Do not store
-it (in cvs, for example), but store the po file used as source file by
-pod-translate. 
+This file was generated by po4a(7). Do not store it (in cvs, for example),
+but store the po file used as source file by pod-translate. 
 
 In fact, consider this as a binary, and the po file as a regular .c file:
 If the po get lost, keeping this translation up-to-date will be harder.

Index: text-iso8859.pod-ok
===================================================================
RCS file: /cvsroot/po4a/po4a/t/data-04/text-iso8859.pod-ok,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- text-iso8859.pod-ok	26 Aug 2004 22:54:54 -0000	1.2
+++ text-iso8859.pod-ok	27 Aug 2004 18:18:34 -0000	1.3
@@ -4,9 +4,8 @@
         * THIS IS NO SOURCE FILE, BUT RESULT OF COMPILATION *
         *****************************************************
 
-This file was generated by po4a(7) version 0.18. Do not store
-it (in cvs, for example), but store the po file used as source file by
-pod-translate. 
+This file was generated by po4a(7). Do not store it (in cvs, for example),
+but store the po file used as source file by pod-translate. 
 
 In fact, consider this as a binary, and the po file as a regular .c file:
 If the po get lost, keeping this translation up-to-date will be harder.