You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@xmlgraphics.apache.org by Simon Pepping <sp...@leverkruid.eu> on 2011/03/14 19:15:29 UTC

Re: forrest problem

Hi Pascal,

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.

Simon

On Mon, Mar 14, 2011 at 02:38:07PM +0100, Pascal Sancho wrote:
> Hi Simon,
> 
> On my local system (Win XP + JDK 1.6.0.20 + forrest 0.9-dev):
> 
> invoking ant docs gives me expected result in %FOP%/build/site/
> 
> The only thing I can see is that NBSP is coded as a single byte char
> from ISO-8859-1 table.
> 
> IIRC, when I made some change in doc, I only pushed from there the
> relevant files (dir compare with Forrest-doc WC then commit).
> 
> 
> Le 14/03/2011 13:14, Simon Pepping a écrit :
> > Some xml files created by forrest contain errors. For example,
> > 1.0/graphics.xml: Image�I/O API in the published version with
> > encoding="ISO-8859-1", converted from Image&nbsp;I/O API in the
> > source. I have a utf-8 based Debian GNU/Linux system. Any ideas how to
> > prevent this from happening?
> > 
> > Simon
> > 
> > On Mon, Mar 14, 2011 at 11:50:39AM -0000, spepping@apache.org wrote:
> >> Author: spepping
> >> Date: Mon Mar 14 11:50:31 2011
> >> New Revision: 1081340
> >>
> >> URL: http://svn.apache.org/viewvc?rev=1081340&view=rev
> >> Log:
> >> Publish from forrestbot

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


Re: forrest problem

Posted by Andreas Delmelle <an...@telenet.be>.
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