DO NOT REPLY [Bug 13866] - [PATCH] Support for CCITT encoding of TIFF images in PDF output

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13866

[PATCH] Support for CCITT encoding of TIFF images in PDF output





--- Additional Comments From [EMAIL PROTECTED]  2002-11-29 07:22 ---
Moved the discussion of the image URL resolution issue to a new bug 14948.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: docs for maintenance release

[Peter B. West]

Victor Mote wrote:

Christian Geisert wrote:



for the documentation for the maintenance release I think the
best thing is to copy src/documentation over from trunk and then
add a simple  to build.xml
Comments?



I had a thought left over from our discussion of branching a few weeks ago
that might help here. I convinced myself at the time that, when checking out
the maintenance branch, using the "-f" option on a checkout would get the
trunk version of any files that aren't on the maintenance branch. I am
headed out the door or I would try it right now. I suppose that it is
possible that doing so would also check out some files that would break the
build or override something that we don't want overridden, but I think it
would be worth a try.


It should do.  However, you will still have to 'cvs add' and 'cvs 
commit' them on the maintenance branch.  Another possibility. especially 
for directories are not going to be merged back into the HEAD and whose 
content is largely the same, is to merge them out from HEAD into maint. 
 Not having followed the details of the proposed changes very closely, 
I would have to look at individual cases.

Peter
--
Peter B. West  [EMAIL PROTECTED]  http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: Still on for freeze deadline?

[Peter B. West]

Victor Mote wrote:

Jeremias Maerki wrote:



Let's look at it the other way: Is there a downside to moving all the
files on the client and checking in everything? What do you guys think
would be the best way to accomplish such a thing?



The downside to moving the files on the client & then checking in is that
you have now disconnected the current files from their history.

I don't know how much access we have to the cvs server, but, if we have
enough, I think the preferred way to go is to 1) lock the repository down,
2) burn a copy of the repository onto a CD for backup & a permanent archive,
3) hack away at the repository until everything is as you wish, and 4)
unlock the repository.

However, the truth is that doing it the right "clean" way will be fine as
well. I don't think we have any pressing needs to be greatly attached to the
history. Peter has already documented how to leave an audit trail if you
move in the repository & a similar thing could be done using the other
method.



The '-m"comment"' option on 'cvs add' will set the descriptive text.

alt.design  8:04$ cvs add -m"THIS FILE IS BEING ADDED." junk
cvs add: scheduling file `junk' for addition
cvs add: use 'cvs commit' to add this file permanently


The '-m"comment"' option on the subsequent 'cvs commit' will set the log 
text on the first revision of the added file.


alt.design  8:05$ cvs ci -m"It's little me" junk
RCS file: /tmp/pbw/cvstest/alt.design/junk,v
done
Checking in junk;
/tmp/pbw/cvstest/alt.design/junk,v  <--  junk
initial revision: 1.1
done
alt.design  8:06$ cvs log junk

RCS file: /tmp/pbw/cvstest/alt.design/junk,v
Working file: junk
head: 1.1
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
THIS FILE IS BEING ADDED.

revision 1.1
date: 2002/11/28 22:05:55;  author: pbw;  state: Exp;
It's little me
=



Another issue to consider is that if you move the files in the repository,
you need to worry about the dependencies in both branches at the same time.
If you move them in your sandbox & check them in, I am pretty sure that you
will need to either 1) only want them moved in one branch (probably not
desirable), or 2) move them twice, once for each branch. Especially on the
maintenance branch, you will want to be careful to get the new files tagged
with the maintenance branch tag.


I don't think anyone here knows all of the implications of hacking the 
repository.  Safety first.

Peter
--
Peter B. West  [EMAIL PROTECTED]  http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: docs for maintenance release

[Victor Mote]

Christian Geisert wrote:

> for the documentation for the maintenance release I think the
> best thing is to copy src/documentation over from trunk and then
> add a simple  to build.xml
> Comments?

I had a thought left over from our discussion of branching a few weeks ago
that might help here. I convinced myself at the time that, when checking out
the maintenance branch, using the "-f" option on a checkout would get the
trunk version of any files that aren't on the maintenance branch. I am
headed out the door or I would try it right now. I suppose that it is
possible that doing so would also check out some files that would break the
build or override something that we don't want overridden, but I think it
would be worth a try.

Victor Mote


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

RE: Still on for freeze deadline?

[Victor Mote]

Jeremias Maerki wrote:

> Let's look at it the other way: Is there a downside to moving all the
> files on the client and checking in everything? What do you guys think
> would be the best way to accomplish such a thing?

The downside to moving the files on the client & then checking in is that
you have now disconnected the current files from their history.

I don't know how much access we have to the cvs server, but, if we have
enough, I think the preferred way to go is to 1) lock the repository down,
2) burn a copy of the repository onto a CD for backup & a permanent archive,
3) hack away at the repository until everything is as you wish, and 4)
unlock the repository.

However, the truth is that doing it the right "clean" way will be fine as
well. I don't think we have any pressing needs to be greatly attached to the
history. Peter has already documented how to leave an audit trail if you
move in the repository & a similar thing could be done using the other
method.

Another issue to consider is that if you move the files in the repository,
you need to worry about the dependencies in both branches at the same time.
If you move them in your sandbox & check them in, I am pretty sure that you
will need to either 1) only want them moved in one branch (probably not
desirable), or 2) move them twice, once for each branch. Especially on the
maintenance branch, you will want to be careful to get the new files tagged
with the maintenance branch tag.

Victor Mote


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: Still on for freeze deadline?

[Jeremias Maerki]

On 28.11.2002 17:15:46 Christian Geisert wrote:
> Jeremias Maerki wrote:
> > From your original plan we still have to finish the documentation stuff,
> 
> Yes the documentation needs at least to be checked for old versions, 
> errors etc. And it would be nice to document the ant task and new 
> extensions.

I can do some of this as soon as I know where to do it. (See my other
mail)

> > right? Maybe we can also include the reorganized directory layout. But
> 
> I would rather do this after the release.

ok.

> > that will take another week or two, I guess. Especially because I'd like
> > to leave Jörg a chance to voice his opinion. Until then I will be able
> > to include my tutorial.
> 
> IMHO documentation changes (in contrast to code changes) are no problem
> after the release candidate.

You're right.


Jeremias Maerki


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: docs for maintenance release

[Jeremias Maerki]

How will we maintain the website after the copy? Change in trunk then
copy over to maint branch each time something is changed? Or can we
somehow keep both documentation parts separate in their branches and
copy the stuff together when the website needs an update?

On 28.11.2002 17:33:51 Christian Geisert wrote:
> for the documentation for the maintenance release I think the
> best thing is to copy src/documentation over from trunk and then
> add a simple  to build.xml
> Comments?
> 
> The track.png in status.html needs a update. How is it done?


Jeremias Maerki


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

docs for maintenance release

[Christian Geisert]

Hi,

for the documentation for the maintenance release I think the
best thing is to copy src/documentation over from trunk and then
add a simple  to build.xml
Comments?

The track.png in status.html needs a update. How is it done?

Christian



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: FOP Servlet, contrib stuff and tutorial

[Christian Geisert]

Also following other project's conventions. The config files get
included in the jar, so I think they ARE source.


Another issue with the conf dir is that it's also part
of the binary distribution.

Christian


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: Still on for freeze deadline?

[Christian Geisert]

Jeremias Maerki wrote:

From your original plan we still have to finish the documentation stuff,


Yes the documentation needs at least to be checked for old versions, 
errors etc. And it would be nice to document the ant task and new 
extensions.

right? Maybe we can also include the reorganized directory layout. But


I would rather do this after the release.


that will take another week or two, I guess. Especially because I'd like
to leave Jörg a chance to voice his opinion. Until then I will be able
to include my tutorial.


IMHO documentation changes (in contrast to code changes) are no problem
after the release candidate.

Christian


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

DO NOT REPLY [Bug 14768] - NullPointerException in XMLRenderer.isCoarseXML()

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=14768

NullPointerException in XMLRenderer.isCoarseXML()

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2002-11-28 16:08 ---
Patch applied. Thanks.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

cvs commit: xml-fop/src/org/apache/fop/render/xml XMLRenderer.java

[jeremias]

jeremias2002/11/28 08:06:39

  Modified:src/org/apache/fop/render/xml Tag: fop-0_20_2-maintain
XMLRenderer.java
  Log:
  Avoid NPE when options aren't set on the XMLRenderer (Bug 14768)
  Submitted by: Matthias Brunner <[EMAIL PROTECTED]>
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.27.2.8  +10 -2 xml-fop/src/org/apache/fop/render/xml/XMLRenderer.java
  
  Index: XMLRenderer.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/render/xml/XMLRenderer.java,v
  retrieving revision 1.27.2.7
  retrieving revision 1.27.2.8
  diff -u -r1.27.2.7 -r1.27.2.8
  --- XMLRenderer.java  8 Nov 2002 10:25:29 -   1.27.2.7
  +++ XMLRenderer.java  28 Nov 2002 16:06:39 -  1.27.2.8
  @@ -495,7 +495,15 @@
   }
   
   private boolean isCoarseXml() {
  -return ((Boolean)options.get("fineDetail")).booleanValue();
  +if (options == null) {
  +return false;
  +}
  +Boolean b = (Boolean)options.get("fineDetail");
  +if (b != null) {
  +return b.booleanValue();
  +} else {
  +return false;
  +}
   }
   
   /**
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: User Agent

[Jeremias Maerki]

On 28.11.2002 15:48:40 Oleg Tkachenko wrote:
> Jeremias Maerki wrote:
> 
> > I'd vote for an Avalon Configuration object which can be built easily
> > from XML and passed through from Cocoon which is also based on Avalon.
> > Configuration objects are also easily built by hand if necessary.
> Right. Lets stop reinventing the wheel (being diving into avalon).

Cool.

> > The UserAgent should IMO implement the Configurable interface which
> > defines an Avalon standard contract how the object is configured.
> The problem is that user agent properties are just part of FOP configuration 
> properties. May be we should separate FOP config from User Agent config. Well, 
> I need to avalonize my brain first.

That's not a problem. A parent object can easily pass a subtree its own
Configuration to its child. For example, Driver could pass a subtree
(cfg.getChild("useragent")) to a newly instantiated UserAgent
(useragent.configure(cfg.getChild("useragent"))).

Maybe separation of the config makes sense. I'll also look at this more
closely. But I've still got two or three little things in maint I'd like
to finish first.


Jeremias Maerki


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: CVS changes (was Re: Still on for freeze deadline?)

[Oleg Tkachenko]

Christian Geisert wrote:


Won't this break old releases?
For example checking out FOP with tag fop-0_20_3 then build.sh
will probably fail.

I think you right :(

--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: FOP Servlet, contrib stuff and tutorial

[Christian Geisert]

Jeremias Maerki wrote:

On 27.11.2002 17:12:38 Oleg Tkachenko wrote:


Jeremias Maerki wrote:


[..]


The question is actually whether contrib/servlet stuff is included into the 
distribution. If so, I don't see any reason to duplicate java code and war.
Just need to change documentation and probably leave explanatory readme file 
in the examples/embedding directory.
If not, the duplication seems reasonable.
Looking to the archive [1] I see Joerg said "Contrib/servlet is not 
distributed, instead, the Java source and a war file is in 
docs/examples/embedding." I believe we should wait till Joerg is back to 
clarify that.

My intention. I just wanted to get this started.


Sounds like the only problem is that the contrib/servlet stuff
is not in the distribution.
I'll add this and remove the old docs/example/embedding stuff.

Christian




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

CVS changes (was Re: Still on for freeze deadline?)

[Christian Geisert]

Oleg Tkachenko wrote:

Jeremias Maerki wrote:


[..]


Hack of the repository looks feasible, I did it once (one more to do is 
to modify parent CVS/Entry file, which lists all child directories as 
D/foo-dir). Lets try on a non crucial directory first :)

Won't this break old releases?
For example checking out FOP with tag fop-0_20_3 then build.sh
will probably fail.

Christian


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

cvs commit: xml-fop/src/org/apache/fop/fo/pagination ConditionalPageMasterReference.java

[jeremias]

jeremias2002/11/28 07:44:06

  Modified:src/org/apache/fop/fo/pagination Tag: fop-0_20_2-maintain
ConditionalPageMasterReference.java
  Log:
  Make sure that a warning is shown when page-position="last" is used.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.5.2.6   +3 -3  
xml-fop/src/org/apache/fop/fo/pagination/ConditionalPageMasterReference.java
  
  Index: ConditionalPageMasterReference.java
  ===
  RCS file: 
/home/cvs/xml-fop/src/org/apache/fop/fo/pagination/ConditionalPageMasterReference.java,v
  retrieving revision 1.5.2.5
  retrieving revision 1.5.2.6
  diff -u -r1.5.2.5 -r1.5.2.6
  --- ConditionalPageMasterReference.java   19 Nov 2002 01:04:04 -  1.5.2.5
  +++ ConditionalPageMasterReference.java   28 Nov 2002 15:44:06 -  1.5.2.6
  @@ -77,7 +77,7 @@
   return false;
   } else if (pagePosition==PagePosition.LAST) {
   // how the hell do you know at this point?
  -log.debug("LAST PagePosition NYI");
  +log.warn("conditional-page-master-reference: page-position='last' 
is not yet implemented (NYI)");
   return false;
   }
   } else {
  @@ -85,7 +85,7 @@
   return false;
   } else if (pagePosition==PagePosition.LAST) {
   // how the hell do you know at this point?
  -log.debug("LAST PagePosition NYI");
  +log.warn("conditional-page-master-reference: page-position='last' 
is not yet implemented (NYI)");
   // potentially valid, don't return
   }
   }
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: xml-fop/src/org/apache/fop/apps Driver.java

[jeremias]

jeremias2002/11/28 07:43:17

  Modified:src/org/apache/fop/apps Tag: fop-0_20_2-maintain Driver.java
  Log:
  Good error messages when Driver is not initialized properly.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.36.2.8  +9 -7  xml-fop/src/org/apache/fop/apps/Driver.java
  
  Index: Driver.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/apps/Driver.java,v
  retrieving revision 1.36.2.7
  retrieving revision 1.36.2.8
  diff -u -r1.36.2.7 -r1.36.2.8
  --- Driver.java   19 Nov 2002 01:03:57 -  1.36.2.7
  +++ Driver.java   28 Nov 2002 15:43:17 -  1.36.2.8
  @@ -1,6 +1,6 @@
   /*
* $Id$
  - * Copyright (C) 2001 The Apache Software Foundation. All rights reserved.
  + * Copyright (C) 2001-2002 The Apache Software Foundation. All rights reserved.
* For details on use and redistribution please refer to the
* LICENSE file included with these sources.
*/
  @@ -193,9 +193,9 @@
   
   private Logger getLogger() {
   if(log == null) {
  - log = new ConsoleLogger(ConsoleLogger.LEVEL_INFO);
  - log.error("Logger not set");
  - }
  + log = new ConsoleLogger(ConsoleLogger.LEVEL_INFO);
  + log.error("Logger not set");
  + }
   
   return log;
   }
  @@ -433,6 +433,8 @@
* events but isn't a SAX Parser itself.
*/
   public ContentHandler getContentHandler() {
  +if (_stream == null) throw new NullPointerException("OutputStream has not 
been set. Set before getting the ContentHandler");
  +if (_renderer == null) throw new NullPointerException("The renderer has not 
been set. Set before getting the ContentHandler");
   StreamRenderer streamRenderer = new StreamRenderer(_stream, _renderer);
   streamRenderer.setLogger(getLogger());
   _treeBuilder.setLogger(getLogger());
  @@ -446,7 +448,7 @@
* SAX InputSource
*/
   public synchronized void render(XMLReader parser, InputSource source)
  -throws FOPException {
  +throws FOPException {
   parser.setContentHandler(getContentHandler());
   try {
   parser.parse(source);
  @@ -466,7 +468,7 @@
* Build the formatting object tree using the given DOM Document
*/
   public synchronized void render(Document document)
  -throws FOPException {
  +throws FOPException {
DocumentInputSource source = new DocumentInputSource(document);
DocumentReader reader = new DocumentReader();
render(reader, source);
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: xml-fop/src/org/apache/fop/fo/flow Block.java

[chrisg]

chrisg  2002/11/28 07:23:23

  Modified:.Tag: fop-0_20_2-maintain CHANGES
   src/org/apache/fop/fo/flow Tag: fop-0_20_2-maintain
Block.java
  Log:
  Added infinite loop detection (just halts processing, see bug #8878)
  Submitted by: Rhett Aultman ([EMAIL PROTECTED])
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.10.2.33 +2 -1  xml-fop/CHANGES
  
  Index: CHANGES
  ===
  RCS file: /home/cvs/xml-fop/CHANGES,v
  retrieving revision 1.10.2.32
  retrieving revision 1.10.2.33
  diff -u -r1.10.2.32 -r1.10.2.33
  --- CHANGES   26 Nov 2002 18:15:18 -  1.10.2.32
  +++ CHANGES   28 Nov 2002 15:23:22 -  1.10.2.33
  @@ -1,6 +1,7 @@
   ==
   Done since 0.20.4 release
  -
  +- Added infinite loop detection (just halts processing, see bug #8878)
  +  Submitted by: Rhett Aultman ([EMAIL PROTECTED])
   - Added autoselecting  portrait/landscape on PCL Renderer (see bug #6638)
 Submitted by: [EMAIL PROTECTED] (Vicente Salvador)
   - Improved AWT Font-measuring/rendering (see bug #14657)
  
  
  
  No   revision
  
  
  No   revision
  
  
  1.41.2.12 +13 -2 xml-fop/src/org/apache/fop/fo/flow/Block.java
  
  Index: Block.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/flow/Block.java,v
  retrieving revision 1.41.2.11
  retrieving revision 1.41.2.12
  diff -u -r1.41.2.11 -r1.41.2.12
  --- Block.java22 Nov 2002 15:10:46 -  1.41.2.11
  +++ Block.java28 Nov 2002 15:23:23 -  1.41.2.12
  @@ -56,12 +56,15 @@
   
   int areaHeight = 0;
   int contentWidth = 0;
  +int infLoopThreshhold = 50;
   
   String id;
   int span;
   
   // this may be helpful on other FOs too
   boolean anythingLaidOut = false;
  +//Added to see how long it's been since nothing was laid out.
  +int noLayoutCount = 0;
   
   public Block(FObj parent, PropertyList propertyList)
   throws FOPException {
  @@ -77,8 +80,16 @@
   public int layout(Area area) throws FOPException {
   BlockArea blockArea;
   
  -// log.error(" b:LAY[" + marker + "] ");
  +if (!anythingLaidOut) {
  +noLayoutCount++;
  +}
  +if (noLayoutCount > infLoopThreshhold) {
  +throw new FOPException(
  +"No meaningful layout in block after many attempts.  "+
  +"Infinite loop is assumed.  Processing halted.");
  +}
   
  +// log.error(" b:LAY[" + marker + "] ");
   
   if (this.marker == BREAK_AFTER) {
   return Status.OK;
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 14924] - Table disappears when it ends when the page ends

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=14924

Table disappears when it ends when the page ends





--- Additional Comments From [EMAIL PROTECTED]  2002-11-28 15:01 ---
With the files attached I got the correct pdf file (also attached), but If you 
remove from Invoice.xml one or two  tags 
the results disappears.

 

Thank u in advance

CESAR

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

DO NOT REPLY [Bug 14924] - Table disappears when it ends when the page ends

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=14924

Table disappears when it ends when the page ends





--- Additional Comments From [EMAIL PROTECTED]  2002-11-28 14:59 ---
Created an attachment (id=3983)
xsl file

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

DO NOT REPLY [Bug 14924] - Table disappears when it ends when the page ends

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=14924

Table disappears when it ends when the page ends





--- Additional Comments From [EMAIL PROTECTED]  2002-11-28 14:58 ---
Created an attachment (id=3982)
xml file

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

DO NOT REPLY [Bug 14924] - Table disappears when it ends when the page ends

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=14924

Table disappears when it ends when the page ends





--- Additional Comments From [EMAIL PROTECTED]  2002-11-28 14:56 ---
Created an attachment (id=3981)
Java Source

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: User Agent

[Oleg Tkachenko]

Jeremias Maerki wrote:


I'd vote for an Avalon Configuration object which can be built easily
from XML and passed through from Cocoon which is also based on Avalon.
Configuration objects are also easily built by hand if necessary.

Right. Lets stop reinventing the wheel (being diving into avalon).


The UserAgent should IMO implement the Configurable interface which
defines an Avalon standard contract how the object is configured.

The problem is that user agent properties are just part of FOP configuration 
properties. May be we should separate FOP config from User Agent config. Well, 
I need to avalonize my brain first.

--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

DO NOT REPLY [Bug 13586] - fop will not work on linux alpha because jre is broken (workarround included)

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13586

fop will not work on linux alpha because jre is broken (workarround included)





--- Additional Comments From [EMAIL PROTECTED]  2002-11-28 14:43 ---
Oleg, please READ the report again.

I wrote:
--
on axp, I use
float currentLetterSpacing = (float) 9.99;
instead of:
float currentLetterSpacing = Float.NaN;
--

So the comparison is ok if currentLetterSpacing is not initialized with
NaN.

That's the whole fix.
Dont' use
float currentLetterSpacing = Float.NaN
Just use
float currentLetterSpacing = (float) 9.99;

(same source)

This has no side-effects except if somebody uses
leterspacing "9.99" which seems not be a real-world
issue.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

cvs commit: xml-fop/src/org/apache/fop/layoutmgr StaticContentLayoutManager.java

[keiron]

keiron  2002/11/28 06:14:53

  Modified:src/org/apache/fop/layoutmgr StaticContentLayoutManager.java
  Log:
  clear old breaks
  
  Revision  ChangesPath
  1.7   +3 -1  
xml-fop/src/org/apache/fop/layoutmgr/StaticContentLayoutManager.java
  
  Index: StaticContentLayoutManager.java
  ===
  RCS file: 
/home/cvs/xml-fop/src/org/apache/fop/layoutmgr/StaticContentLayoutManager.java,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- StaticContentLayoutManager.java   18 Nov 2002 15:54:15 -  1.6
  +++ StaticContentLayoutManager.java   28 Nov 2002 14:14:53 -  1.7
  @@ -79,7 +79,9 @@
   }
   }
   
  +blockBreaks.clear();
   flush();
  +region = null;
   }
   
   
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 13866] - [PATCH] Support for CCITT encoding of TIFF images in PDF output

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13866

[PATCH] Support for CCITT encoding of TIFF images in PDF output





--- Additional Comments From [EMAIL PROTECTED]  2002-11-28 14:01 
---
I just had a look a the current source with regards to relative URLs.

The relative part is done with a URL.getFile() which returns the path
without "file:" on the Sun JDK. Is this different with the IBM JDK?


I don't think that the Logger problem has to do with the JDK
What kind of error do get?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: Still on for freeze deadline?

[Oleg Tkachenko]

Jeremias Maerki wrote:

Thanks, Victor and Peter. It all sounds a bit scary (I knew that before).
Let's look at it the other way: Is there a downside to moving all the
files on the client and checking in everything?

Lost history?

 What do you guys think

would be the best way to accomplish such a thing?

Hack of the repository looks feasible, I did it once (one more to do is to 
modify parent CVS/Entry file, which lists all child directories as 
D/foo-dir). Lets try on a non crucial directory first :)

--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

cvs commit: xml-fop/src/org/apache/fop/layoutmgr/table Cell.java TableLayoutManager.java

[keiron]

keiron  2002/11/28 05:04:51

  Modified:src/org/apache/fop/layoutmgr/list
ListBlockLayoutManager.java
ListItemLayoutManager.java
   src/org/apache/fop/layoutmgr/table Cell.java
TableLayoutManager.java
  Log:
  added table header and footer
  
  Revision  ChangesPath
  1.5   +2 -1  
xml-fop/src/org/apache/fop/layoutmgr/list/ListBlockLayoutManager.java
  
  Index: ListBlockLayoutManager.java
  ===
  RCS file: 
/home/cvs/xml-fop/src/org/apache/fop/layoutmgr/list/ListBlockLayoutManager.java,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- ListBlockLayoutManager.java   18 Nov 2002 15:54:15 -  1.4
  +++ ListBlockLayoutManager.java   28 Nov 2002 13:04:51 -  1.5
  @@ -104,6 +104,7 @@
   } else {
   curLM.resetPosition(null);
   }
  +over = true;
   break;
   }
   stackSize.add(bp.getStackingSize());
  
  
  
  1.6   +2 -1  
xml-fop/src/org/apache/fop/layoutmgr/list/ListItemLayoutManager.java
  
  Index: ListItemLayoutManager.java
  ===
  RCS file: 
/home/cvs/xml-fop/src/org/apache/fop/layoutmgr/list/ListItemLayoutManager.java,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- ListItemLayoutManager.java19 Nov 2002 07:00:27 -  1.5
  +++ ListItemLayoutManager.java28 Nov 2002 13:04:51 -  1.6
  @@ -135,6 +135,7 @@
   } else {
   curLM.resetPosition(null);
   }
  +over = true;
   break;
   } else {
   lastPos = bp;
  
  
  
  1.8   +2 -1  xml-fop/src/org/apache/fop/layoutmgr/table/Cell.java
  
  Index: Cell.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/layoutmgr/table/Cell.java,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- Cell.java 18 Nov 2002 15:54:16 -  1.7
  +++ Cell.java 28 Nov 2002 13:04:51 -  1.8
  @@ -258,6 +258,7 @@
   public void resetPosition(Position resetPos) {
   if (resetPos == null) {
   reset(null);
  +childBreaks.clear();
   }
   }
   }
  
  
  
  1.6   +39 -6 
xml-fop/src/org/apache/fop/layoutmgr/table/TableLayoutManager.java
  
  Index: TableLayoutManager.java
  ===
  RCS file: 
/home/cvs/xml-fop/src/org/apache/fop/layoutmgr/table/TableLayoutManager.java,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- TableLayoutManager.java   18 Nov 2002 15:54:16 -  1.5
  +++ TableLayoutManager.java   28 Nov 2002 13:04:51 -  1.6
  @@ -86,6 +86,7 @@
*/
   public void setTableHeader(Body th) {
   tableHeader = th;
  +tableHeader.setParentLM(this);
   }
   
   /**
  @@ -95,6 +96,7 @@
*/
   public void setTableFooter(Body tf) {
   tableFooter = tf;
  +tableFooter.setParentLM(this);
   }
   
   /**
  @@ -115,14 +117,26 @@
   
   MinOptMax headerSize = null;
   if (tableHeader != null) {
  +tableHeader.resetPosition(null);
   headerBreak = getHeight(tableHeader, context);
   headerSize = headerBreak.getStackingSize();
  +stackSize.add(headerSize);
   }
   
   MinOptMax footerSize = null;
   if (tableFooter != null) {
  +tableFooter.resetPosition(null);
   footerBreak = getHeight(tableFooter, context);
   footerSize = footerBreak.getStackingSize();
  +stackSize.add(footerSize);
  +}
  +
  +if (stackSize.opt > context.getStackLimit().max) {
  +BreakPoss breakPoss = new BreakPoss(
  +new LeafPosition(this, 0));
  +breakPoss.setFlag(BreakPoss.NEXT_OVERFLOWS, true);
  +breakPoss.setStackingSize(stackSize);
  +return breakPoss;
   }
   
   while ((curLM = (Body)getChildLM()) != null) {
  @@ -213,7 +227,6 @@
  new SectionPosition(this, breaks.size() - 1, 
breaks));
   breakPoss.setStackingSize(stackSize);
   return breakPoss;
  -
   }
   
   /**
  @@ -230,13 +243,22 @@
   
   // add column, body then row areas
   
  -// add table header areas
  -
   int tableHeight = 0;
  -
   Body childLM;
  -int iStartPos = 0;
   LayoutContext

DO NOT REPLY [Bug 14924] - Table disappears when it ends when the page ends

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=14924

Table disappears when it ends when the page ends





--- Additional Comments From [EMAIL PROTECTED]  2002-11-28 11:42 ---
Provide small fo example please (attach it, not copy'n'paste as text).

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

DO NOT REPLY [Bug 1063] - fop does not handle large fo files

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=1063

fop does not handle large fo files

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]



--- Additional Comments From [EMAIL PROTECTED]  2002-11-28 11:40 ---
*** Bug 14928 has been marked as a duplicate of this bug. ***

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

DO NOT REPLY [Bug 14928] - Exception in thread "main" java.lang.OutOfMemoryError

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=14928

Exception in thread "main" java.lang.OutOfMemoryError

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE



--- Additional Comments From [EMAIL PROTECTED]  2002-11-28 11:40 ---
Give java more memory (it's 64Mb by default). You can use -Xms128m -Xmx512m
command line options. And see faq: http://xml.apache.org/fop/faq.html#faq-N1011A.

*** This bug has been marked as a duplicate of 1063 ***

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

DO NOT REPLY [Bug 14928] New: - Exception in thread "main" java.lang.OutOfMemoryError

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=14928

Exception in thread "main" java.lang.OutOfMemoryError

   Summary: Exception in thread "main" java.lang.OutOfMemoryError
   Product: Fop
   Version: 0.20.4
  Platform: Sun
OS/Version: Solaris
Status: NEW
  Severity: Critical
  Priority: Other
 Component: general
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


I don't now what is the problem. fop output is like this :

/usr/local/fop-0.20.4/fop.sh -c /usr/local/fop-0.20.4/conf/userconfig.xml -xml 
pdfOutput504.xml -xsl output.xsl -pdf pdfOutput504.pdf
[INFO] FOP 0.20.4
[INFO] building formatting object tree
[INFO] [1]
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[INFO] [2]
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[INFO] [3]
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[INFO] [4]
[WARNING] table-layout=auto is not supported, using fixed!
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[INFO] [5]
[INFO] [6]
[WARNING] table-layout=auto is not supported, using fixed!
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[INFO] [7]
[INFO] [8]
[INFO] [9]
[INFO] [10]
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[INFO] [1]
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[INFO] [2]
[INFO] [3]
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[INFO] [5]
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD must be specified on 
table.
[WARNING] table-layout=auto is not supported, using fixed!
[ERROR] At least one of minimum, optimum, or maximum IPD m

cvs commit: xml-fop/src/documentation/content/xdocs/design/understanding - New directory

[keiron]

keiron  2002/11/28 02:38:35

  xml-fop/src/documentation/content/xdocs/design/understanding - New directory

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: xml-fop/src/documentation/content/xdocs/design/alt.design - New directory

[keiron]

keiron  2002/11/28 02:38:33

  xml-fop/src/documentation/content/xdocs/design/alt.design - New directory

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 14924] New: - Table disappears when it ends when the page ends

[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://nagoya.apache.org/bugzilla/show_bug.cgi?id=14924

Table disappears when it ends when the page ends

   Summary: Table disappears when it ends when the page ends
   Product: Fop
   Version: 0.20.4
  Platform: All
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: general
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


My table disappears when it ends just at the same time as the page, it is a 
fo:table, not a fo:table-with-caption and it has fo:table-body properly. If the 
lenght of my table is more than the page or less than the page it appears 
correctly.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: User Agent

[Jeremias Maerki]

On 28.11.2002 08:33:31 Keiron Liddle wrote:
> On Wed, 2002-11-27 at 19:19, Oleg Tkachenko wrote:
> > > There could be two ways to set these values. From the command line we
> > > want the config file to set values and when embedding they could extend
> > > the user agent to set the values.
> > And what about the third one - set config file when embedding? That might be 
> > convenient too.
> 
> Config file or config data (eg. in cocoon sitemap, the data is in xml
> under the fop serializer which cocoon converts to config data).
> 
> Yes, the other two make it possible.

I'd vote for an Avalon Configuration object which can be built easily
from XML and passed through from Cocoon which is also based on Avalon.
Configuration objects are also easily built by hand if necessary.

http://jakarta.apache.org/avalon/api/org/apache/avalon/framework/configuration/Configuration.html

The UserAgent should IMO implement the Configurable interface which
defines an Avalon standard contract how the object is configured.

http://jakarta.apache.org/avalon/api/org/apache/avalon/framework/configuration/Configurable.html

Jeremias Maerki


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: FOP Servlet, contrib stuff and tutorial

[Jeremias Maerki]

On 27.11.2002 17:12:38 Oleg Tkachenko wrote:
> Jeremias Maerki wrote:
> 
> > Oleg and I wonder what we should do with the fact that the FOP servlet
> > exists in docs/examples/embedding and contrib/servlet. Joerg seems to
> > have some ideas about this, so I hope he tells us when he's back from
> > holidays. But the other's opinion is also wanted here. IMO the servlet
> > should always be built from the sources now in contrib. The
> > docs/examples/embedding stuff should be deleted. Joerg thinks
> > differently, I think.
> The question is actually whether contrib/servlet stuff is included into the 
> distribution. If so, I don't see any reason to duplicate java code and war.
> Just need to change documentation and probably leave explanatory readme file 
> in the examples/embedding directory.
> If not, the duplication seems reasonable.
> Looking to the archive [1] I see Joerg said "Contrib/servlet is not 
> distributed, instead, the Java source and a war file is in 
> docs/examples/embedding." I believe we should wait till Joerg is back to 
> clarify that.

My intention. I just wanted to get this started.

> > I've started a "How to use FOP in Java/Usage patterns" tutorial
> > yesterday. When finished it will consist of some Java sources, a few XML
> > files (XMLs, FOs, XSLTs) and documentation in XML format.
> That's great.
> 
> > IMO the following things should be done:
> > - move the hyph directory to src/hyph
> +1
> > - move the FO schema to src/foschema
> -1 Is it really source? I believe that's more documentation/test stuff.

IMO that would make it hard to find.

> > - move src/org to src/java/org
> This can confuse people, as it may look like java.org.* packages. Such ones do 
> exist and are reserved to SUN afair.

This has nothing to do with package names. I followed the conventions
used in other Apache projects. The "java" directory is simply there to
separate the other stuff from the Java stuff. Think of the various IDEs
where you have to specify the Java source directories. Not having the
java dir includes all other subdirectories which could be confusing.

> > - move contrib/servlet to examples/servlet
> > - move contrib/plan to examples/plan
> > - move contrib/mathml to examples/mathml
> +1
> 
> > - move conf to src/conf
> -1 it's not a source actually.

Also following other project's conventions. The config files get
included in the jar, so I think they ARE source.

> > - remove docs/examples/embedding
> > - move docs/examples to examples/fo
> +1
> > - place the tutorial in examples/tutorial or tutorial (don't know yet)
> docs/tutorial ?
> 
> [1] http://marc.theaimsgroup.com/?l=fop-dev&m=103196215022751&w=2


Jeremias Maerki


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: Still on for freeze deadline?

[Jeremias Maerki]

Thanks, Victor and Peter. It all sounds a bit scary (I knew that before).
Let's look at it the other way: Is there a downside to moving all the
files on the client and checking in everything? What do you guys think
would be the best way to accomplish such a thing?


Jeremias Maerki


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]