Date: Thu, 20 Jan 2005 18:51:16 -0300
From: Alvaro Herrera <alvherre@dcc.uchile.cl>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Magnus Hagander <mha@sollentuna.net>,
	Mike Blackwell <maiku41@anet.com>, pgsql-docs@postgresql.org,
	pgsql-www@postgresql.org
Subject: Re: [DOCS] [BUGS] BUG #1414: DOC - pl/Perl hash tags missing
Message-ID: <20050120215116.GA3135@dcc.uchile.cl>
References: <6BCB9D8A16AC4241919521715F4D8BCE476696@algol.sollentuna.se>
	<9277.1106256196@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <9277.1106256196@sss.pgh.pa.us>
User-Agent: Mutt/1.5.6i

On Thu, Jan 20, 2005 at 04:23:16PM -0500, Tom Lane wrote:
> "Magnus Hagander" <mha@sollentuna.net> 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?

Probably the solution is to use some sort of template escaping, like
{literal} in PHP's smarty.  Not sure what the site is using.

-- 
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
Al principio era UNIX, y UNIX habló y dijo: "Hello world\n".
No dijo "Hello New Jersey\n", ni "Hello USA\n".