forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Armin Waibel (JIRA)" <>
Subject [jira] Commented: (FOR-846) tigris-skin: skinconf.xsl cause poorly readable .pdf-doc 'code' sections
Date Wed, 05 Apr 2006 16:54:44 GMT
    [ ] 

Armin Waibel commented on FOR-846:

We set in our project skinconf.xsl  an extra-css for 'code'
.code {
        border-style: none;
        border-width: 1px;
        font-size : 100%;
        padding: 1em 1.33em 1em 1.33em;
        background : #EEEEEE;
this works perfectly for the generated .html-files (black letter on light-grey background).
But this setting was *ignored* by the .pdf-generator. An example can be found here

So I think now it's some kind of bug - is it splitting hairs? ;-)

You said that tigris-skin is (no longer)/not supported, so it would be great if someone could
change the default color settings of 'code' in tigris skinconf.xsl as workaround (this will
take a few seconds).

> tigris-skin: skinconf.xsl cause poorly readable .pdf-doc 'code' sections
> ------------------------------------------------------------------------
>          Key: FOR-846
>          URL:
>      Project: Forrest
>         Type: Bug

>   Components: Skins (general issues)
>     Versions: 0.7, 0.8-dev
>     Reporter: Armin Waibel
>     Priority: Trivial

> 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)
> ...
> <color name="code" value="#EEEEEE"/>
> ...
> <xsl:if test="not(color[@name='code'])">
>        <color name="code" value="#EEEEEE"/>

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message