Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 40979 invoked from network); 12 Apr 2006 04:15:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Apr 2006 04:15:42 -0000 Received: (qmail 32961 invoked by uid 500); 12 Apr 2006 04:15:42 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 32794 invoked by uid 500); 12 Apr 2006 04:15:41 -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 32783 invoked by uid 99); 12 Apr 2006 04:15:41 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Apr 2006 21:15:41 -0700 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; Tue, 11 Apr 2006 21:15:41 -0700 Received: from ajax (localhost.localdomain [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 2327DD4A02 for ; Wed, 12 Apr 2006 05:15:20 +0100 (BST) Message-ID: <1842699322.1144815320140.JavaMail.jira@ajax> Date: Wed, 12 Apr 2006 05:15:20 +0100 (BST) From: "David Crossley (JIRA)" To: dev@forrest.apache.org Subject: [jira] Closed: (FOR-846) tigris-skin: skinconf.xsl cause poorly readable .pdf-doc 'code' sections In-Reply-To: <911111611.1144243786935.JavaMail.jira@ajax> 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-846?page=all ] David Crossley closed FOR-846: ------------------------------ Fix Version: 0.8-dev Resolution: Fixed I think that you might have missed the importance of what Ross was saying. If you define this colour in your projects' src/documentation/skinconf.xml file then if will over-ride the defaults. There is a potential trap. Look at the comments in skinconf.xml at the section. You need to uncomment one of the color groups. The default group for the "tigris" skin is probably close to the "Collabnet" group of example colours. Anyway, i did apply the change that you suggested to the trunk code. > tigris-skin: skinconf.xsl cause poorly readable .pdf-doc 'code' sections > ------------------------------------------------------------------------ > > Key: FOR-846 > URL: http://issues.apache.org/jira/browse/FOR-846 > Project: Forrest > Type: Bug > Components: Skins (general issues) > Versions: 0.7, 0.8-dev > Reporter: Armin Waibel > Priority: Trivial > Fix For: 0.8-dev > > When using tigirs-skin the generated .pdf-docs 'code' sections are poorly readable, because black letters on dark-blue background is used. > To reproduce: > Seed default project, enable tigris skin in forrest properties and generate the site. Open the generated .pdf-docs and search for "source code"-sections. > Fix: > Change in tigris skinconf.xsl the default and fall back color of 'code' sections from dark blue to another color (e.g. light grey) > ... > > ... > > -- 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