From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: [gnu.org #181558] format error in html mono web page Date: Sun, 04 Apr 2004 08:02:12 +0300 Organization: JURTA Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <87k70w2v57.fsf@mail.jurta.org> References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1081055563 30485 80.91.224.253 (4 Apr 2004 05:12:43 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 4 Apr 2004 05:12:43 +0000 (UTC) Cc: sinuhe@gnu.org, emacs-devel@gnu.org, webmasters-comment@gnu.org, karl@freefriends.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sun Apr 04 07:12:34 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1B9zvu-0000sg-00 for ; Sun, 04 Apr 2004 07:12:34 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1B9zvt-0008H1-00 for ; Sun, 04 Apr 2004 07:12:34 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1B9ztX-0006P7-Sm for emacs-devel@quimby.gnus.org; Sun, 04 Apr 2004 00:10:07 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1B9zsB-00051H-1x for emacs-devel@gnu.org; Sun, 04 Apr 2004 00:08:43 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1B9zqm-00038K-3c for emacs-devel@gnu.org; Sun, 04 Apr 2004 00:07:48 -0500 Original-Received: from [66.33.219.19] (helo=spoon.dreamhost.com) by monty-python.gnu.org with esmtp (Exim 4.30) id 1B9zpz-0001hs-1z; Sun, 04 Apr 2004 00:06:27 -0500 Original-Received: from mail.jurta.org (80-235-32-177-dsl.mus.estpak.ee [80.235.32.177]) by spoon.dreamhost.com (Postfix) with ESMTP id 863E813D829; Sat, 3 Apr 2004 21:06:24 -0800 (PST) Original-To: rms@gnu.org In-Reply-To: (Richard Stallman's message of "Sat, 03 Apr 2004 18:40:09 -0500") User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3.50 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:21238 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:21238 Richard Stallman writes: > I looked at this, and I think that the problem occurred when Dave > checked the formatter HTML file into CVS. That is because the file > contains something that looks like an RCS keyword. It should contain > $Log$. This is an interesting problem when the output of a file with description of some feature is processed according to its own description on literal strings it contains. The aforementioned HTML file contains also other expanded RCS keywords: the node "(emacs)Version Headers" has $Id$ expanded in several places. For example, in the following paragraph: It is often necessary to use "superfluous" backslashes when writing the strings that you put in this variable. For instance, you might write "$Id\$" rather than "$Id: emacs.html,v 1.1 2003/10/30 01:27:33 sinuhe Exp $". The extra backslash prevents the string constant from being interpreted as a header, if the Emacs Lisp file containing it is maintained with version control. the $Id$ keyword is expanded while $Id\$ is not. One possibility is to take the advice from this paragraph and to quote all RCS keywords in the Emacs manual, with explanations for the reader of the manual how s?he could get the right value from a quoted string. > The long-term fix, perhaps, is to change makeinfo to output some > HTML no-op there which will prevent CVS from recognizing the "keyword". Changing makeinfo to add some HTML no-op, or e.g. to replace a dollar sign by the HTML numerical character reference in RCS keywords will definitely work for HTML output. But one can imagine a situation with the need to put other Texinfo output file types under version control where it will not work. For example, I don't see how RCS keywords could be prevented from expansion in Info output files. > Or could you turn off RCS keyword substitution for the HTML files > of the Emacs manual, and regenerate these and check them in? This problem exists not only in the HTML files like http://www.gnu.org/software/emacs/manual/html_node/emacs_141.html http://www.gnu.org/software/emacs/manual/html_node/emacs_158.html http://www.gnu.org/software/emacs/manual/html_chapter/emacs_16.html but also in other files, e.g. http://www.gnu.org/software/emacs/manual/text/emacs.txt and some Emacs Lisp files under webcvs/emacs. I don't know exactly about workflow for putting files on the GNU Web server, but generally I'd rather suggest not to put generated files under version control. -- Juri Linkov http://www.jurta.org/emacs/