DO NOT REPLY [Bug 29099] - images not loading

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29099

images not loading

[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|pdf images does not appear  |images not loading
   |in https|

Re: Building site with forrest

[Clay Leeds]

Correction:
On Jul 28, 2004, at 1:33 PM, Clay Leeds wrote:
2. Files in build/webapps/content are missing. These problems can be
solved
  by copying src/documentation/content into webapps, or by replacing
  in sitemap-0.5.xmap all source references to content/ with
  {project:content}, whatever that may mean.
I don't recall why a sitemap-0.5.xmap was created, but I removed it
completely.
It is still in our CVS repository. And it is the sitemap which forrest
uses in my local build.
True. I didn't remove it from CVS. I removed it from my local copy at 
the request of the forrest-dev folks who were helping me. In fact, I 
eradicated both sitemap*.xmap files from my local directory.
I eradicated them, then grabbed a fresh copy and re-inserted the === 
FOP ADDITIONS === section.

Web Maestro Clay

Re: Building site with forrest

[Clay Leeds]

On Jul 28, 2004, at 11:47 AM, Simon Pepping wrote:
On Sun, Jul 25, 2004 at 12:46:03PM -0700, Clay Leeds wrote:
(More comments inline)
On Jul 25, 2004, at 11:41 AM, Simon Pepping wrote:
I have tried to build the site with forrest, without much success. I
had a few problems:
1. Validation error. I solved this problem by creating an OASIS
catalog.
I solved this by essentially replacing the xml-fop/.../sitemap.xmap
file with a 'clean' version from forrest. I then added the  FOP
ADDITIONS  section.
When online, validation succeeds because the system ids point to the
CVS. Offline, most validation succeeds due to forrest's catalog, which
points to local copies of the DTDs. This does not work for
compliance.xml, which uses its own DTD. There is an SGML Open Catalog
for it, but apparently that is not used. I added an OASIS XML catalog,
and now the local copy of the DTD in my CVS working directory is used.
I'd like to figure out how to do that. I'm using eclipse for much of my 
editing...

2. Files in build/webapps/content are missing. These problems can be
solved
  by copying src/documentation/content into webapps, or by replacing
  in sitemap-0.5.xmap all source references to content/ with
  {project:content}, whatever that may mean.
I don't recall why a sitemap-0.5.xmap was created, but I removed it
completely.
It is still in our CVS repository. And it is the sitemap which forrest
uses in my local build.
True. I didn't remove it from CVS. I removed it from my local copy at 
the request of the forrest-dev folks who were helping me. In fact, I 
eradicated both sitemap*.xmap files from my local directory.

My plan (when I get Forrest building successfully!) is to replace all 
forrest-related files (forrest.properties, site.xml, sitemap.xmap, 
etc.) and eradicate those which are not needed (sitemap-0.5.xmap, as 
well as all of those book.xml files--these are all replaced by 
site.xml--unless there's a compelling reason for them).

Regards, Simon
Thanks for the message. I'm looking forward to getting the forrest 
stuff *&* your documentation files in xml-fop!

Web Maestro Clay

Re: Committing documentation

[Clay Leeds]

On Jul 28, 2004, at 11:51 AM, Simon Pepping wrote:
On Sun, Jul 25, 2004 at 12:51:56PM -0700, Clay Leeds wrote:
As I understand it, you're primarily doing documentation that is more
developer and/or embedded oriented, which is one of the reasons why I
would want to have a new 'Documentation' tab.
Indeed, it is. Does this mandate a specific directory to commit the
files into? Or shall I create a directory in
src/documentation/content/xdocs? Or in src/documentation/content/?
Regards, Simon
Good question. Actually, I was 'putting it out there(tm)' as to whether 
or not other committers thought that was a good idea. Therefore, I'm 
not sure where it should go *yet*.

As for how it goes in, double-check the FAQ docbook section[1] (IIRC 
you did the docs in docbook?). If you need more help, let me know.

Web Maestro Clay
[1]
http://forrest.apache.org/faq.html#docbook

Re: Building site with forrest

[Simon Pepping]

Clay,

Thanks for your reply.

On Sun, Jul 25, 2004 at 12:46:03PM -0700, Clay Leeds wrote:
> Simon,
> 
> I have been working at getting the xml-fop web site working for many 
> months (at first using forrest-0.5.1, and more recently with 
> forrest-0.6 since they're about to release a new version). More 
> recently, I've had some success, but I'm currently working with the 
> forrest-dev list to get them resolved--and we've made progress[1] & 
> [1a].

I appreciate that that is not an easy problem to solve.
 
> (More comments inline)
> 
> On Jul 25, 2004, at 11:41 AM, Simon Pepping wrote:
> >I have tried to build the site with forrest, without much success. I
> >had a few problems:
> >
> >1. Validation error. I solved this problem by creating an OASIS 
> >catalog.
> 
> I solved this by essentially replacing the xml-fop/.../sitemap.xmap 
> file with a 'clean' version from forrest. I then added the  FOP 
> ADDITIONS  section.

When online, validation succeeds because the system ids point to the
CVS. Offline, most validation succeeds due to forrest's catalog, which
points to local copies of the DTDs. This does not work for
compliance.xml, which uses its own DTD. There is an SGML Open Catalog
for it, but apparently that is not used. I added an OASIS XML catalog,
and now the local copy of the DTD in my CVS working directory is used.
 
> >2. Files in build/webapps/content are missing. These problems can be 
> >solved
> >   by copying src/documentation/content into webapps, or by replacing
> >   in sitemap-0.5.xmap all source references to content/ with
> >   {project:content}, whatever that may mean.
> 
> I don't recall why a sitemap-0.5.xmap was created, but I removed it 
> completely.

It is still in our CVS repository. And it is the sitemap which forrest
uses in my local build.

Regards, Simon

-- 
Simon Pepping
home page: http://www.leverkruid.nl

Re: Committing documentation

[Simon Pepping]

On Sun, Jul 25, 2004 at 12:51:56PM -0700, Clay Leeds wrote:

> As I understand it, you're primarily doing documentation that is more 
> developer and/or embedded oriented, which is one of the reasons why I 
> would want to have a new 'Documentation' tab.

Indeed, it is. Does this mandate a specific directory to commit the
files into? Or shall I create a directory in
src/documentation/content/xdocs? Or in src/documentation/content/?

Regards, Simon

-- 
Simon Pepping
home page: http://www.leverkruid.nl

DO NOT REPLY [Bug 30353] - FOP out of memory exception

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30353

FOP out of memory exception

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2004-07-28 08:16 ---
This isnt a bug, you are simply trying to process too much data within the 
given memory constraints. Please ask user related questions on the FOP user 
list, where you will get a speedy response to questions:

http://xml.apache.org/fop/maillist.html#fop-user

There are a few tips on how to resolve memory issues on the web site, see:

http://xml.apache.org/fop/running.html#memory