Re: Fop and JDK1.2

[Peter B. West]

Christian,

Just did it.

New 
  updated 
  updated 

Peter

Christian Geisert wrote:
> Peter B. West schrieb:
> 
>> plans to use the News page on the web-site to maintain a short history 
>> of releases and release candidates.  The sort of notes that appear in 
> 
> Just do it ;-)
> 
>> the release announcements could be collected there and serve as an 
>> immediate point of reference.


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


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

cvs commit: xml-fop/docs/xml-docs/fop news.xml

[pbwest]

pbwest  2002/06/21 23:12:14

  Modified:docs/xml-docs/fop news.xml
  Log:
  Added rc4 news
  
  Revision  ChangesPath
  1.2   +50 -11xml-fop/docs/xml-docs/fop/news.xml
  
  Index: news.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/news.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- news.xml  24 Apr 2002 23:27:22 -  1.1
  +++ news.xml  22 Jun 2002 06:12:14 -  1.2
  @@ -1,24 +1,63 @@
   
  -
  +
   
   
   
  -
  -News
  -
  -
  -
  -
  -
  -
  +  
  +News
  +
  +
  +
  +  
  +  
  +  
  +
  +  
  + Changes since 0.20.3 include:
  +  
  +  
  + Support for background-image
  + 
  +   FOP should now work with any JAXP1.1 compliant
  +   parser/transformer
  + 
  + 
  +   The following JARs have been updated: Xerces to version
  +   2.0.1, Xalan to version 2.3.1 and Batik to version 1.5beta2.
  + 
  + Fop has been compiled with Jimi support
  + 
  +   Logging has been changed from LogKit to Avalon's Logger
  +   Interface
  + 
  + New hyphenation patterns: turkish, portuguese and czech
  + FOP should now work on a EBCDIC machine
  + 
  +   Support for comma-separated values for the font-family
  +   property
  + 
  + Russian and Czech messages for AWTViewer
  +  
  +  For details see CHANGES file:http://cvs.apache.org/viewcvs.cgi/xml-fop/CHANGES?rev=1.10.2.19";
  +  >http://cvs.apache.org/viewcvs.cgi/xml-fop/CHANGES?rev=1.10.2.19
  +  
  +  
  + See also the full text of the http://marc.theaimsgroup.com/?l=fop-dev&m=102398470424177&w=4";
  + >announcement.
  +  
  +
   
 Welcome Jeremias Maerki, Joerg Pietschmann and Peter B. West!

   
 This is a maintenance release, the first version which supports the XSL-FO
  Recommendation syntax. See the
  -   http://marc.theaimsgroup.com/?l=xml-apache-announce&m=101588818821794";>
  -   announcement for more information.
  +   http://marc.theaimsgroup.com/?l=xml-apache-announce&m=101588818821794";>
  +   announcement for more information.

   
   
  
  
  

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

cvs commit: xml-fop/docs/design/alt.design book.xml

[pbwest]

pbwest  2002/06/21 23:10:16

  Modified:docs/design/alt.design book.xml
  Log:
  Added intro.xml as index
  
  Revision  ChangesPath
  1.5   +2 -1  xml-fop/docs/design/alt.design/book.xml
  
  Index: book.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/design/alt.design/book.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- book.xml  4 Jun 2002 13:39:29 -   1.4
  +++ book.xml  22 Jun 2002 06:10:16 -  1.5
  @@ -5,7 +5,8 @@
 
 
 
  -  
  +  
  +  
 
 
 
  
  
  

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

cvs commit: xml-fop/docs/design/alt.design intro.xml

[pbwest]

pbwest  2002/06/21 23:07:51

  Added:   docs/design/alt.design intro.xml
  Log:
  Intro and index
  
  Revision  ChangesPath
  1.1  xml-fop/docs/design/alt.design/intro.xml
  
  Index: intro.xml
  ===
  
  
  
  
  

  FOP Alternative Design
  Alternative Design Approach to FOP
  $Revision: 1.1 $ $Name:  $
  

  



  

This section of the FOP web site contains notes on approaches
to an alternative design for FOP.  The individual documents
here are fragmentary, being notes of particular issues,
without an overall framework as yet.


The main aims of this redesign effort are:


full conformance with the Recommendation
increased performance
reduced memory footprint
no limitation on the size of files


In order to achieve these aims, the primary areas
of design interest are:



  Representing properties, for most purposes, as integers.


  Distributing FOP processing over a number of threads with
  single-point downstream communication and flow control by
  means of traditional producer/consumer queues.  The threads
  so far under consideration are:
  
XML parser
FO tree builder
layout engine
Area tree builder
  


  Representing trees with explicit Tree objects, rather than
  as implicit relationships among other objects.


  Caching integrated into the tree node access methods.




  The ALT DESIGN effort is not taking place on the
  main line of development, represented by the HEAD
  tag on the CVS trunk.  The source is available via the
  FOP_0-20-0_Alt-Design tag.  This code has only a crude,
  non-Ant build environment, and is expected only to
  compile at this stage.  Only the parser stage and the first
  stage of FO tree building is present.  However, the first
  example of producer/consumer binding is working, the Tree
  class with inner Tree.Node and inner
  Tree.Node.iterators classes are available and
  working.  Property handling is quite advanced, and is likely
  to be almost complete some time in July, 2002.


  Only mailto:[EMAIL PROTECTED]";>Peter
  West is working on the ALT DESIGN sub-project.


  
  

  
  
  
  
  

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

Re: FOP in the forrest

[J.Pietschmann]

Christian Geisert wrote:
> Keiron Liddle schrieb:
>> Any questions, comments?

I'm already adapting the docs to the forrest 1.1 DTDs

> There are some issues with the (old) documentation for the maintenance 
> branch which I will bring up in an extra mail.

Are they different from HEAD?

J.Pietschmann


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

DO NOT REPLY [Bug 10100] - Blank lines when render to TEXT

[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=10100

Blank lines when render to TEXT

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2002-06-21 19:35 ---
Most likely this is due to quantization errors. The text renderer used a fixed 
matrix for placing text. It attempts to fit the print positions from FOP layout 
to the fixed matrix. Depending on the offsets, scale difference, etc lines of 
text may skip or overlay.

It may be possible to correct this with judicious choices of margins, font, 
line spacing, etc in the FOs and CPI and LPI settings in the text renderer... 
but this will not be easy.

In most cases the text renderer will not produce output suitable for 
production. However, I have found that it does a better job of producing plain 
text output than some commercial products I have tried, although it does lean 
towards better appearance at expense of preservation of data (i.e. the text may 
look more like the original - but text could be overwritten losing the original 
data).

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

Re: [ANNOUNCEMENT] FOP 0.20.4 Release Candidate available

[Christian Geisert]

Martin Peřina schrieb:

[..]

> It works fine, just two things:
> 
>   1) If baseDir is set for example to "/opt/fop", FOP doesn't
>  add "/" at the end of baseDir as other systems commonly does,
>  so you can start use path for fonts like this:
> 
>  kerning="yes" 
>  embed-file="../fop-fonts/arial-regular.ttf">
>  
>

Good point, I'll add this.

> 
> 
>   2) It would be nice, if baseDir can be set like Java property
>  on the command line, for example:
> 
>java -cp $FOP_CP -DbaseDir=/opt/fop org.apache.fop.apps.Fop a.fo
> 
>  Then there won't be any absolute paths in userconfig.xml.

This should be considered for the configuration handling for the redesign

> I have one more question. Will there be any improvements with
> implementation of last-line-end-indent property in 0.20.4? 
> DocBook stylesheets use it for generating TOC and without this
> property it doesn't look nice.

Yes I know the problem but there has been no fix yet
(it's still on my todo list)

> Martin Perina

Thanks for your feedback.

Christian


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

Re: FOP in the forrest

[Christian Geisert]

Keiron Liddle schrieb:
> Hi,
> 
> In order to improve the information, process and updating I suggest we
> start using better document systems.
> Forrest is the first thing that will help us here. With a supplement to
> the sitemap (not sure how to do this) we can also display FOP better. We
> can have a real examples page, show basic examples of XML+XSL to PDF, FO
> to PDF, PS, PCL etc, show SVG to PDF. Also we could display examples of
> functionality and bugs that should be updated with updates to the code.
> 
> Better feedback, faster updates. What more could you ask.

++1

[..]

> Forrest is not live yet so after the release would be a good time to get
> this started.

+1

> Any questions, comments?

I need to have a closer look at Forrest first
(and my Coocon knowlege is .. well .. rather limited at the moment)

There are some issues with the (old) documentation for the maintenance 
branch which I will bring up in an extra mail.

> Regards,
> Keiron.

Christian


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

cvs commit: xml-fop/src/org/apache/fop/datatypes Slash.java

[pbwest]

pbwest  2002/06/21 08:44:03

  Added:   src/org/apache/fop/datatypes Tag: FOP_0-20-0_Alt-Design
Slash.java
  Log:
  Type to accommodate slash in size/height pair of font shorthand.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.1.2.1   +60 -0 xml-fop/src/org/apache/fop/datatypes/Attic/Slash.java
  
  
  
  

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

cvs commit: xml-fop/test/resources/fop/svg images.fo images.svg logo.jpg paints.svg transparency.svg link.svg text.svg

[keiron]

keiron  2002/06/21 08:17:37

  Modified:test/resources/fop/svg link.svg text.svg
  Added:   test/resources/fop/svg images.fo images.svg logo.jpg
paints.svg transparency.svg
  Log:
  more svg tests with transparency, patterns and images
  
  Revision  ChangesPath
  1.2   +1 -1  xml-fop/test/resources/fop/svg/link.svg
  
  Index: link.svg
  ===
  RCS file: /home/cvs/xml-fop/test/resources/fop/svg/link.svg,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- link.svg  14 Jun 2002 14:29:48 -  1.1
  +++ link.svg  21 Jun 2002 15:17:36 -  1.2
  @@ -15,7 +15,7 @@
   FOP
   
   
  -
  +
   
   Another
   file
  
  
  
  1.3   +2 -0  xml-fop/test/resources/fop/svg/text.svg
  
  Index: text.svg
  ===
  RCS file: /home/cvs/xml-fop/test/resources/fop/svg/text.svg,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- text.svg  17 Jun 2002 09:44:05 -  1.2
  +++ text.svg  21 Jun 2002 15:17:36 -  1.3
  @@ -113,6 +113,8 @@
 FOP in FOPfont
   
   
  +  
  +  
   
   
   
  
  
  
  1.1  xml-fop/test/resources/fop/svg/images.fo
  
  Index: images.fo
  ===
  
  
  http://www.w3.org/1999/XSL/Format";>
  

  



  

  

  
  
  

  Embedded/Image SVG

  

  

  

  Image in FO Document.


  

  

  
  
  
  
  
  1.1  xml-fop/test/resources/fop/svg/images.svg
  
  Index: images.svg
  ===
  
  http://www.w3.org/TR/2000/CR-SVG-20001102/DTD/svg-20001102.dtd";>
  http://www.w3.org/2000/svg"; 
xmlns:xlink="http://www.w3.org/1999/xlink";>
  
  
  
  Images in SVG
  
  Jpeg
  
  
  
  Effect or Bitmap
  
  

  


  

  
  
  
  
  Transparency
  
  SEE
  
  
  
  Scaled
  
  
  
  
  
  
  
  
  
  
  
  1.1  xml-fop/test/resources/fop/svg/logo.jpg
  
<>
  
  
  1.1  xml-fop/test/resources/fop/svg/paints.svg
  
  Index: paints.svg
  ===
  
  http://www.w3.org/TR/2000/CR-SVG-20001102/DTD/svg-20001102.dtd";>
  http://www.w3.org/2000/svg"; 
xmlns:xlink="http://www.w3.org/1999/xlink";>
  
  
  
  Paints - Patterns & Gradients
  
  Gradient
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  Pattern
   
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  1.1  xml-fop/test/resources/fop/svg/transparency.svg
  
  Index: transparency.svg
  ===
  
  http://www.w3.org/TR/2000/CR-SVG-20001102/DTD/svg-20001102.dtd";>
  http://www.w3.org/2000/svg"; 
xmlns:xlink="http://www.w3.org/1999/xlink";>
  
  
  
  Transparency in SVG (to PDF)
  
  Shapes
  
  
  
  
  
  
  
  

  

  
  
  Image
  
  SEE
  
  
  
  
  
  Text
  
  SEE
  THROUGH
  
  
  
  
  
  

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

DO NOT REPLY [Bug 4670] - Entity Resolver for Images

[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=4670

Entity Resolver for Images

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]



--- Additional Comments From [EMAIL PROTECTED]  2002-06-21 15:30 ---
*** Bug 6647 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 6647] - external-graphic and configuration "baseDir"

[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=6647

external-graphic and configuration "baseDir"

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE



--- Additional Comments From [EMAIL PROTECTED]  2002-06-21 15:30 ---
Should use a proper resolver anyway.

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

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

DO NOT REPLY [Bug 4670] - Entity Resolver for Images

[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=4670

Entity Resolver for Images

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE



--- Additional Comments From [EMAIL PROTECTED]  2002-06-21 15:21 ---


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

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

DO NOT REPLY [Bug 4348] - FOP has no mechanism to extend protocols

[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=4348

FOP has no mechanism to extend protocols

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]



--- Additional Comments From [EMAIL PROTECTED]  2002-06-21 15:21 ---
*** Bug 4670 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 2987] - Large graphics put FOP 0.19 into an infinite loop

[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=2987

Large graphics put FOP 0.19 into an infinite loop

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]



--- Additional Comments From [EMAIL PROTECTED]  2002-06-21 15:17 ---
*** Bug 3475 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 3475] - Large images cause PDF generation to run out of memory

[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=3475

Large images cause PDF generation to run out of memory

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||DUPLICATE



--- Additional Comments From [EMAIL PROTECTED]  2002-06-21 15:17 ---
The patch has been applied but there are still problems with large images.

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

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

DO NOT REPLY [Bug 6537] - Table is missing in the generated PDF

[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=6537

Table is missing in the generated PDF

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE



--- Additional Comments From [EMAIL PROTECTED]  2002-06-21 15:00 ---


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

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

DO NOT REPLY [Bug 6305] - Using fo:table-and-caption results in empty 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=6305

Using fo:table-and-caption results in empty output

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]
   ||om



--- Additional Comments From [EMAIL PROTECTED]  2002-06-21 15:00 ---
*** Bug 6537 has been marked as a duplicate of this bug. ***

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

[GUMP] Build Failure - xml-fop

[Sam Ruby]

This email is autogenerated from the output from:



Buildfile: build.xml

init-avail:

init-filters-xalan2:
 [copy] Copying 1 file to /home/rubys/jakarta/xml-fop/build/src/codegen

init:
 [echo] --- Fop 1.0dev [1999-2002] 

prepare:
 [echo] Preparing the build directories
[mkdir] Created dir: 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties
[mkdir] Created dir: 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts
[mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/svg
[mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/conf
[mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/hyph
 [copy] Copying 3 files to /home/rubys/jakarta/xml-fop/build/classes/conf

codegen:
 [echo] Resetting codegen directory
 [copy] Copying 30 files to /home/rubys/jakarta/xml-fop/build/src/codegen
 [echo] Generating the java files from xml resources
[style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/allprops.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/Constants.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/genconst.xsl
[style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml 
to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/fo_ignore_this.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/properties.xsl
[style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml 
to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/FOPropertyMapping.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/propmap.xsl
[style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml 
to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/foenums_ignore_this.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/enumgen.xsl
[style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/charlist.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/CodePointMapping.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/code-point-mapping.xsl
[style] Transforming into 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierBold.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierBold.java
[style] Loading stylesheet 
/home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl
[style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Courier.xml to 
/home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Courier.java
[style] home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl:0:0: Fatal 
Error! java.lang.RuntimeException: Programmer assertion is incorrect! - Namespace 
context can not be null! Cause: java.lang.RuntimeException: Programmer assertion is 
incorrect! - Namespace context can not be null!
[style] Failed to process /home/rubys/jakarta/xml-fop/src/codegen/Courier.xml

BUILD FAILED
/home/rubys/jakarta/xml-fop/build.xml:431: Fatal error during transformation

Total time: 27 seconds

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

cvs commit: xml-fop/src/org/apache/fop/svg SVGElement.java SVGUtilities.java

[keiron]

keiron  2002/06/21 07:03:42

  Modified:src/org/apache/fop/fo UnknownXMLObj.java
   src/org/apache/fop/render/awt AWTRenderer.java
   src/org/apache/fop/render/pcl PCLRenderer.java
   src/org/apache/fop/render/ps PSRenderer.java
   src/org/apache/fop/render/txt TXTRenderer.java
   src/org/apache/fop/svg SVGElement.java SVGUtilities.java
  Log:
  removed old imports
  
  Revision  ChangesPath
  1.6   +1 -2  xml-fop/src/org/apache/fop/fo/UnknownXMLObj.java
  
  Index: UnknownXMLObj.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/UnknownXMLObj.java,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- UnknownXMLObj.java20 Jun 2002 09:14:12 -  1.5
  +++ UnknownXMLObj.java21 Jun 2002 14:03:42 -  1.6
  @@ -9,7 +9,6 @@
   
   import org.apache.fop.fo.*;
   import org.apache.fop.layout.FontState;
  -import org.apache.fop.layout.inline.*;
   import org.apache.fop.apps.FOPException;
   
   import org.w3c.dom.Element;
  
  
  
  1.41  +1 -2  xml-fop/src/org/apache/fop/render/awt/AWTRenderer.java
  
  Index: AWTRenderer.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/render/awt/AWTRenderer.java,v
  retrieving revision 1.40
  retrieving revision 1.41
  diff -u -r1.40 -r1.41
  --- AWTRenderer.java  20 Jun 2002 09:14:16 -  1.40
  +++ AWTRenderer.java  21 Jun 2002 14:03:42 -  1.41
  @@ -15,7 +15,6 @@
*/
   
   import org.apache.fop.layout.*;
  -import org.apache.fop.layout.inline.*;
   import org.apache.fop.datatypes.*;
   import org.apache.fop.image.*;
   import org.apache.fop.svg.*;
  
  
  
  1.16  +1 -2  xml-fop/src/org/apache/fop/render/pcl/PCLRenderer.java
  
  Index: PCLRenderer.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/render/pcl/PCLRenderer.java,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- PCLRenderer.java  26 Feb 2002 12:43:09 -  1.15
  +++ PCLRenderer.java  21 Jun 2002 14:03:42 -  1.16
  @@ -16,7 +16,6 @@
   import org.apache.fop.pdf.PDFPathPaint;
   import org.apache.fop.pdf.PDFColor;
   import org.apache.fop.layout.*;
  -import org.apache.fop.layout.inline.*;
   import org.apache.fop.image.*;
   
   import org.w3c.dom.svg.SVGSVGElement;
  
  
  
  1.22  +1 -2  xml-fop/src/org/apache/fop/render/ps/PSRenderer.java
  
  Index: PSRenderer.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/render/ps/PSRenderer.java,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- PSRenderer.java   11 Apr 2002 09:33:31 -  1.21
  +++ PSRenderer.java   21 Jun 2002 14:03:42 -  1.22
  @@ -12,7 +12,6 @@
   import org.apache.fop.render.Renderer;
   import org.apache.fop.image.FopImage;
   import org.apache.fop.layout.*;
  -import org.apache.fop.layout.inline.*;
   import org.apache.fop.datatypes.*;
   import org.apache.fop.fo.properties.*;
   import org.apache.fop.render.pdf.Font;
  
  
  
  1.16  +1 -2  xml-fop/src/org/apache/fop/render/txt/TXTRenderer.java
  
  Index: TXTRenderer.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/render/txt/TXTRenderer.java,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- TXTRenderer.java  26 Feb 2002 12:43:10 -  1.15
  +++ TXTRenderer.java  21 Jun 2002 14:03:42 -  1.16
  @@ -14,7 +14,6 @@
   import org.apache.fop.apps.FOPException;
   import org.apache.fop.fo.properties.*;
   import org.apache.fop.layout.*;
  -import org.apache.fop.layout.inline.*;
   import org.apache.fop.datatypes.*;
   import org.apache.fop.pdf.PDFPathPaint;
   import org.apache.fop.pdf.PDFColor;
  
  
  
  1.27  +1 -2  xml-fop/src/org/apache/fop/svg/SVGElement.java
  
  Index: SVGElement.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/svg/SVGElement.java,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -u -r1.26 -r1.27
  --- SVGElement.java   20 Jun 2002 09:14:16 -  1.26
  +++ SVGElement.java   21 Jun 2002 14:03:42 -  1.27
  @@ -12,7 +12,6 @@
   import org.apache.fop.fo.properties.*;
   import org.apache.fop.layout.FontState;
   import org.apache.fop.apps.FOPException;
  -import org.apache.fop.layout.inline.*;
   import org.apache.fop.configuration.Configuration;
   
   import org.apache.batik.dom.svg.*;
  
  
  
  1.4   +1 -2  xml-fop/src/org/apache/fop/svg/SVGUtilities.java
  
  Index: SVGUtilities.java
  ===
  RCS file: 

FOP in the forrest

[Keiron Liddle]

Hi,

In order to improve the information, process and updating I suggest we
start using better document systems.
Forrest is the first thing that will help us here. With a supplement to
the sitemap (not sure how to do this) we can also display FOP better. We
can have a real examples page, show basic examples of XML+XSL to PDF, FO
to PDF, PS, PCL etc, show SVG to PDF. Also we could display examples of
functionality and bugs that should be updated with updates to the code.

Better feedback, faster updates. What more could you ask.

Other documents:
- changes.xml in / replacing old CHANGES
- todo.xml in /
(both of these can also be contained in a *.xgump file, I'm not sure how
this works?)
- directory of small instructive samples suitable for the website
- functionality examples
- test examples
- SVG examples
- extension examples

Anyone think of any other things which would make things better?

Forrest is not live yet so after the release would be a good time to get
this started.

For those who don't know about forrest, here is the site:
http://xml.apache.org/forrest

Any questions, comments?

Regards,
Keiron.


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

Re: test cases

[Keiron Liddle]

The testing as described here:
http://xml.apache.org/fop/testing.html

that is capable of running the w3c testsuite (and getting lots of errors
etc.).

This is only really about testing the layout. It sort of works but is
possibly a bit early for these type of tests.

I can see a need for other types of tests that do unit tests on parts of
FOP. We could even supply some code for things like threading
performance testing that people can try.

We should determine a directory structure that can encompass this, such
as other projects have for testing.

I have recently put some svg tests under test/resources/fop/svg and we
could have other resources for images etc.

(the docs/examples/tests directory is the old place)

Regards,
Keiron

On Fri, 2002-06-21 at 08:35, Jeremias Maerki wrote:
> Hi Jörg
> 
> I think there is one: test. Keiron, was that you who created it in the
> first place? I must admit that I've never looked into this directory,
> yet. Does the stuff in there work?
> 
> > I've accumulated quit a few testcases from the bugzilla
> > bug reports.
> > Some are working now, some still produce errors.
> > We don't have an explicit test data directory yet.
> > Should I create one?
> 
> Cheers,
> Jeremias Märki



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

Re: test cases

[Joerg Pietschmann]

Jeremias Maerki wrote:
> I think there is one: test. Keiron, was that you who created it in the
> first place? I must admit that I've never looked into this directory,
> yet. Does the stuff in there work?

Ah, yes.
There is also a docs/examples/tests which is empty and is
used to hold the results produced by runtests.{sh|bat} from
the examples.

The (yet another) attempt at formalizing test descriptions
by testsuite.dtd etc. is neat. I'll think about this a bit.

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

Re: Using bugzilla

[Bertrand Delacretaz]

Hi Peter,

I'm 100% with you, keeping in mind Arved's comments however - the success of 
using bugzilla more will depend on the most active people paving the way.

I'm coming to the same conclusions in my commercial projects: tracking tools 
(we recently selected bugzilla for a major project) combined with CVS and 
mailing lists are very efficient for project management and "micro-planning". 
Open-source projects are leading the way here IMHO, showing examples of loose 
communities that work together very efficiently.

BUT this is assuming people are willing to communicate openly and put 
teamwork high on their list.

Another plus for bugzilla is the file attachments that stay with the 
discussion - can be invaluable for loosely-coupled design discussions. 
Digital shots of handwritten design documents (or super-clean Together 
ControlCenter UML diagrams ;-) would increase the "inter-brain bandwidth" a 
lot IMHO.

-Bertrand

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