Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 14561 invoked from network); 8 Feb 2006 12:19:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Feb 2006 12:19:26 -0000 Received: (qmail 94423 invoked by uid 500); 8 Feb 2006 12:19:25 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 94377 invoked by uid 500); 8 Feb 2006 12:19:24 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 94366 invoked by uid 99); 8 Feb 2006 12:19:24 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Feb 2006 04:19:22 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 88BD1CB for ; Wed, 8 Feb 2006 13:19:01 +0100 (CET) Message-ID: <602597827.1139401141557.JavaMail.jira@ajax.apache.org> Date: Wed, 8 Feb 2006 13:19:01 +0100 (CET) From: "Ross Gardler (JIRA)" To: dev@forrest.apache.org Subject: [jira] Commented: (FOR-559) FAQ+TOC problem: force-toc option In-Reply-To: <1101971747.1119905098691.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/FOR-559?page=comments#action_12365549 ] Ross Gardler commented on FOR-559: ---------------------------------- What do Forrest devs think of this patch, I'm not sure about applying it because it appears to be a workaround not a solution. What it does is add a meta-information value to a documents header:
<xsl:value-of select="@title"/> + true
And then uses this to decide on whether or not to display a TOC: - + I'm +0 on applying this on the grounds that it solves a users problem and that the core problem can be more completely resolved when the dispatcher is utilised. > FAQ+TOC problem: force-toc option > --------------------------------- > > Key: FOR-559 > URL: http://issues.apache.org/jira/browse/FOR-559 > Project: Forrest > Type: New Feature > Components: Skins (general issues) > Versions: 0.6, 0.7, 0.8-dev > Reporter: Jeremias Maerki > Priority: Minor > Attachments: forrest-force-toc.diff > > This is a hybrid patch/RFE/bugfix. Today, I've taken another stab at the problem Clay Leeds reported to you in May: > http://www.mail-archive.com/user@forrest.apache.org/msg00528.html > We have the problem in FOP that the TOC for the FAQ page isn't generated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira