trans-coord-devel
[Top][All Lists]
Advanced

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

trans-coord/gnun/server/gnun ChangeLog GNUmakef...


From: Yavor Doganov
Subject: trans-coord/gnun/server/gnun ChangeLog GNUmakef...
Date: Wed, 08 Feb 2012 20:29:45 +0000

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   12/02/08 20:29:44

Modified files:
        gnun/server/gnun: ChangeLog GNUmakefile gnun.conf mailfail 
                          validate-html-notify.in 
        gnun/server/gnun/doc: gnun.texi web-trans.texi 

Log message:
        Avoid mentioning XHTML.
        * GNUmakefile:
        * gnun.conf:
        * validate-html-notify.in (SUBJ):
        * doc/web-trans.texi (Migrating):
        * doc/gnun.texi (Runtime Variables, triggers, generic.LANG.html)
        (gnun-validate-html): Replace all occurrences of XHTML with the
        more generic HTML.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/ChangeLog?cvsroot=trans-coord&r1=1.245&r2=1.246
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/GNUmakefile?cvsroot=trans-coord&r1=1.111&r2=1.112
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/gnun.conf?cvsroot=trans-coord&r1=1.3&r2=1.4
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/mailfail?cvsroot=trans-coord&r1=1.5&r2=1.6
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/validate-html-notify.in?cvsroot=trans-coord&r1=1.8&r2=1.9
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/gnun.texi?cvsroot=trans-coord&r1=1.44&r2=1.45
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/web-trans.texi?cvsroot=trans-coord&r1=1.27&r2=1.28

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/ChangeLog,v
retrieving revision 1.245
retrieving revision 1.246
diff -u -b -r1.245 -r1.246
--- ChangeLog   30 Jan 2012 14:57:05 -0000      1.245
+++ ChangeLog   8 Feb 2012 20:29:43 -0000       1.246
@@ -1,3 +1,14 @@
+2012-02-08  Yavor Doganov  <address@hidden>
+
+       Avoid mentioning XHTML.
+       * GNUmakefile:
+       * gnun.conf:
+       * validate-html-notify.in (SUBJ):
+       * doc/web-trans.texi (Migrating):
+       * doc/gnun.texi (Runtime Variables, triggers, generic.LANG.html)
+       (gnun-validate-html): Replace all occurrences of `XHTML' with the
+       more generic `HTML'.
+
 2012-01-30  Yavor Doganov  <address@hidden>
 
        * NEWS: Add item about Multiviews.  Release 0.5.

Index: GNUmakefile
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/GNUmakefile,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -b -r1.111 -r1.112
--- GNUmakefile 26 Jan 2012 19:50:24 -0000      1.111
+++ GNUmakefile 8 Feb 2012 20:29:44 -0000       1.112
@@ -474,7 +474,7 @@
 # file exists.  Only applicable for article-rules, if ANNOUNCE=yes.
 # The .hook-ann files are treated differently in the `triggers' rule,
 # because it is a valid (and often occurring in practice) scenario to
-# have a new translation which is invalid (X)HTML.
+# have a new translation which is invalid HTML.
 define announce
 if test -f $$(@F).hook-ann; then \
   echo "echo '<URL:$$(subst $(rootdir),http://www.gnu.org,$$@)>' \
@@ -524,7 +524,7 @@
        [ -f $$@ ] || (cp $$< $$@ ; $(VCSSKIP) $(vcs) add $$@)
 # Since we handle the case when new templates are added by webmasters,
 # it is OK to ignore errors from these, at least until fencepost has
-# an old version of gettext.  The XHTML validation errors should be
+# an old version of gettext.  The HTML validation errors should be
 # clear even if the bug is in the server templates translations.
        -PO=$$@ ; $(check-po)
        $(call update-po,$$@,$$<)

Index: gnun.conf
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/gnun.conf,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- gnun.conf   3 Aug 2010 14:56:08 -0000       1.3
+++ gnun.conf   8 Feb 2012 20:29:44 -0000       1.4
@@ -9,11 +9,11 @@
 # Possible errors that are likely to be fixed by developers only.
 devel-addr  := address@hidden
 
-# Errors from make-prototype and invalid (X)HTML of English articles;
+# Errors from make-prototype and invalid HTML of English articles;
 # webmasters' responsibility.
 web-addr    := address@hidden
 
-# Errors in .po files, or XHTML validation of generated .LANG.html;
+# Errors in .po files, or HTML validation of generated .LANG.html;
 # translators' responsibility.
 transl-addr := address@hidden
 

Index: mailfail
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/mailfail,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- mailfail    30 Jan 2012 08:49:14 -0000      1.5
+++ mailfail    8 Feb 2012 20:29:44 -0000       1.6
@@ -23,7 +23,7 @@
 #
 # Example:
 #
-# ./mailfail address@hidden "Invalid XHTML" ./validate article.html
+# ./mailfail address@hidden "Invalid HTML" ./validate article.html
 
 function usage() {
     echo 1>&2 Usage: ./mailfail [--dry-run] RCPT SUBJECT CMD [ARG ...]

Index: validate-html-notify.in
===================================================================
RCS file: 
/sources/trans-coord/trans-coord/gnun/server/gnun/validate-html-notify.in,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- validate-html-notify.in     30 Jan 2012 08:49:14 -0000      1.8
+++ validate-html-notify.in     8 Feb 2012 20:29:44 -0000       1.9
@@ -47,7 +47,7 @@
     shift 2
 fi
 
-SUBJ="[GNUN Error] ${FILE#../../} is not valid XHTML"
+SUBJ="[GNUN Error] ${FILE#../../} is not valid HTML"
 
 @pkglibexecdir@/mailfail $DRY_RUN "$RCPT" "$SUBJ" \
   @bindir@/gnun-validate-html "$FILE"

Index: doc/gnun.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/gnun.texi,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -b -r1.44 -r1.45
--- doc/gnun.texi       29 Jan 2012 11:28:47 -0000      1.44
+++ doc/gnun.texi       8 Feb 2012 20:29:44 -0000       1.45
@@ -612,7 +612,7 @@
 example:
 
 @example
-Subject: [GNUN Error] gnu/gnu.fa.html is not valid XHTML
+Subject: [GNUN Error] gnu/gnu.fa.html is not valid HTML
 @end example
 
 @node Special Targets
@@ -725,16 +725,16 @@
 
 @c FIXME: Check how Subversion behaves with keywords and update the
 @c paragraph below.
-When a GNUN build completes and some translations fail at the XHTML
-validation stage, the result is checked in the repository, as explained
-earlier (@pxref{Runtime Variables}).  Thus, CVS updates the @w{$}Date$
-RCS keyword (or any other keywords, for that matter) and resets the
-file(s) timestamp.  Next time @command{make} is invoked, the target
-appears newer than the prerequisite so no rebuild is triggered.  The
-purpose of the @code{triggers} target is to ``save'' the information of
-the faulty targets during the main build, and to touch their
-prerequisites in order such invalid articles not to remain online
-unnoticed.
+When a GNUN build completes and some translations fail at the HTML
+validation stage, the result is checked in the repository, as
+explained earlier (@pxref{Runtime Variables}).  Thus, CVS updates the
address@hidden RCS keyword (or any other keywords, for that matter) and
+resets the file(s) timestamp.  Next time @command{make} is invoked,
+the target appears newer than the prerequisite so no rebuild is
+triggered.  The purpose of the @code{triggers} target is to ``save''
+the information of the faulty targets during the main build, and to
+touch their prerequisites in order such invalid articles not to remain
+online unnoticed.
 
 The @code{triggers} target currently executes the files named
 @address@hidden@var{lang}.html.hook} in the @file{server/gnun}
@@ -745,16 +745,16 @@
 
 In addition, this is the rule that takes care of actually sending the
 announcements if @code{ANNOUNCE=yes}.  Since it is a completely valid
-scenario to have a new translation which is initially invalid XHTML, the
-canned command sequence for announcements is recorded in
+scenario to have a new translation which is initially invalid HTML,
+the canned command sequence for announcements is recorded in
 @file{*.hook-ann} files, and they are treated by @code{triggers} in a
-different way.  A newly added @address@hidden file may be invalid,
-in which case GNUN will commit an empty @address@hidden
-file---it is not appropriate to announce it as a new translation as it
-is an empty file completely useless for the general public.  The
address@hidden rule detects this case, and postpones the announcement
-to the next build attempt, when the generated HTML translation is
-supposed to be human-readable.
+different way.  A newly added @address@hidden file may be
+invalid, in which case GNUN will commit an empty
address@hidden@var{lang}.html} file---it is not appropriate to announce it as
+a new translation as it is an empty file completely useless for the
+general public.  The @code{triggers} rule detects this case, and
+postpones the announcement to the next build attempt, when the
+generated HTML translation is supposed to be human-readable.
 
 To summarize, for effective operation GNUN should be invoked
 automatically as @code{make ; cvs|svn|bzr commit -m @dots{} ; make
@@ -1434,7 +1434,7 @@
 
 The contents of @address@hidden is injected right after
 the translators' credits, if any, and before the timestamp.  It should
-be valid XHTML markup.
+be valid HTML markup.
 
 When you modify this file, for example, adding a message to the
 existing empty file or changing a URL, such modification will affect
@@ -1977,14 +1977,14 @@
 
 @node gnun-validate-html
 @subsection The @command{gnun-validate-html} Script
address@hidden validation, XHTML
address@hidden validation, HTML, XHTML
 
-This is a Bash script whose purpose is to ``validate'' both the original
-and translated articles to make sure that they conform to the respective
-W3C standard.  Sometimes webmasters make mistakes, and translators too,
-so this tool is useful to catch errors of that kind.
+This is a Bash script whose purpose is to ``validate'' both the
+original and translated articles to make sure that they conform to the
+respective W3C standard.  Sometimes webmasters make mistakes, and
+translators too, so this tool is useful to catch errors of that kind.
 
-GNUN enforces XHTML validation at build time if invoked with
+GNUN enforces HTML validation at build time if invoked with
 @code{VALIDATE=yes}.
 
 The script expects only one @var{file} as the last argument and will exit

Index: doc/web-trans.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/web-trans.texi,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- doc/web-trans.texi  30 Jan 2012 09:40:13 -0000      1.27
+++ doc/web-trans.texi  8 Feb 2012 20:29:44 -0000       1.28
@@ -5,7 +5,7 @@
 @settitle GNU Web Translators Manual
 @c FIXME: Would be nice to have it in the format `%:b %:d, %:y', but
 @c in English.
address@hidden lastupdate 30.01.2012
address@hidden lastupdate 08.02.2012
 @afourpaper
 @c %**end of header
 
@@ -1194,9 +1194,9 @@
 about the inner markup.  Overall, it is substantially easier than doing
 all of it manually.
 
-Subsequent migrations to newer (X)HTML standards and newer look and feel
-of the website are supposed to happen semi-automatically, although this
-manual will be updated as needed.
+Subsequent migrations to newer HTML standards and newer look and feel
+of the website are supposed to happen semi-automatically, although
+this manual will be updated as needed.
 
 @node SSI
 @section Summary of SSI @code{#include}s



reply via email to

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