Mailing-List: contact general-help@xmlgraphics.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@xmlgraphics.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: forrest problem
From: Andreas Delmelle <andreas.delmelle@telenet.be>
In-Reply-To: <20110314181529.GA2362@leverkruid.eu>
Date: Mon, 14 Mar 2011 22:04:03 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E91FA83-1B3C-462E-B1EA-D2E36BC28D4F@telenet.be>
References: <20110314115042.BAC3823889BB@eris.apache.org>
 <20110314121418.GA2376@leverkruid.eu> <4D7E1A3F.2000909@takoma.fr>
 <20110314181529.GA2362@leverkruid.eu>
To: general@xmlgraphics.apache.org

On 14 Mar 2011, at 19:15, Simon Pepping wrote:

Hi Simon

> Thanks for the hint. I see that, indeed, the files in build/site
> (produced by 'ant docs') do not have the problem, while the files in
> build/forrest-docs (produced by 'forrest -f publish.xml build') do
> have it.

I am not entirely sure if it will help, but you could try running =
Forrest with forcing the Java system property "file.encoding", just to =
make sure that any reads or writes from/to streams using the 'default =
platform encoding' are always using UTF-8.


Regards,

Andreas
---


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org