[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gnustandards ChangeLog maintain.texi

From: Karl Berry
Subject: gnustandards ChangeLog maintain.texi
Date: Fri, 14 Mar 2008 16:05:45 +0000

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       08/03/14 16:05:45

Modified files:
        .              : ChangeLog maintain.texi 

Log message:
        discussion disclaim.translation


Index: ChangeLog
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -b -r1.67 -r1.68
--- ChangeLog   24 Feb 2008 18:23:38 -0000      1.67
+++ ChangeLog   14 Mar 2008 16:05:45 -0000      1.68
@@ -1,3 +1,8 @@
+2008-03-14  Karl Berry  <address@hidden>
+       * maintain.texi (Copyright Papers): discuss disclaim.translation
+       and the Translation Project.
 2008-02-24  Karl Berry  <address@hidden>
        * maintain.texi (Automated Upload Registration): avoid double "also".

Index: maintain.texi
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.156
retrieving revision 1.157
diff -u -b -r1.156 -r1.157
--- maintain.texi       10 Mar 2008 15:15:39 -0000      1.156
+++ maintain.texi       14 Mar 2008 16:05:45 -0000      1.157
@@ -5,7 +5,7 @@
 @c For double-sided printing, uncomment:
 @c @setchapternewpage odd
 @c This date is automagically updated when you save this file:
address@hidden lastupdate March 10, 2008
address@hidden lastupdate March 14, 2008
 @c %**end of header
 @dircategory GNU organization
@@ -300,6 +300,16 @@
 changes to a manual, you can use @file{assign.future.manual}.
 For a translation of a manual, use @file{assign.translation.manual}.
+For translations of program strings (as used by GNU Gettext, for
+example; @pxref{Internationalization,,,standards,GNU Coding
+Standards}), use @file{disclaim.translation}.  If you make use of the
+Translation Project (@url{}) facilities,
+please check with the TP coordinators that they have sent the
+contributor the papers; if they haven't, then you should send the
+papers.  In any case, you should wait for the confirmation from the
+FSF that the signed papers have been received and accepted before
+integrating the new contributor's material, as usual.
 If a contributor is reluctant to sign an assignment for a large change,
 and is willing to sign a disclaimer instead, that is acceptable, so you
 should offer this alternative if it helps you reach agreement.  We

reply via email to

[Prev in Thread] Current Thread [Next in Thread]