X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 1BC8D3A48C0 for ; Thu, 20 Jan 2005 21:23:22 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 77541-09 for ; Thu, 20 Jan 2005 21:23:16 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 62F7A3A485A for ; Thu, 20 Jan 2005 21:23:18 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j0KLNGKA009278; Thu, 20 Jan 2005 16:23:16 -0500 (EST) To: "Magnus Hagander" Cc: "Mike Blackwell" , pgsql-docs@postgresql.org, pgsql-www@postgresql.org Subject: Re: [DOCS] [BUGS] BUG #1414: DOC - pl/Perl hash tags missing In-reply-to: <6BCB9D8A16AC4241919521715F4D8BCE476696@algol.sollentuna.se> References: <6BCB9D8A16AC4241919521715F4D8BCE476696@algol.sollentuna.se> Comments: In-reply-to "Magnus Hagander" message dated "Thu, 20 Jan 2005 22:11:07 +0100" Date: Thu, 20 Jan 2005 16:23:16 -0500 Message-ID: <9277.1106256196@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.004 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/576 X-Sequence-Number: 7319 "Magnus Hagander" writes: > Going out on a line a bit here - and someone who've worked with teh > system probably knows for sure but... It looks like {} is used as the > template placeholder in the templating system on the website. > It would seem to me that the fix would be as simple as to set > $removeUnknownVariables to false when parsing the docs template, but I'm > far from sure at that. And I have no way to test it. And it might break > something else. End of disclaimers. If the docs template is applying any substitution whatsoever to the documentation HTML files, it's broken. I don't think the above fix is appropriate --- what if the docs contain {foo} where foo does match some variable known to the substituter? regards, tom lane