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

2002-06-14 Thread pbwest 

pbwest  2002/06/14 21:20:39

  Modified:src/org/apache/fop/fo Tag: FOP_0-20-0_Alt-Design
PropertySets.java
  Log:
  Completed individual shorthand expansion arrays and added shorthandExpansions array
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.1.2.2   +139 -40   xml-fop/src/org/apache/fop/fo/Attic/PropertySets.java
  
  Index: PropertySets.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/Attic/PropertySets.java,v
  retrieving revision 1.1.2.1
  retrieving revision 1.1.2.2
  diff -u -r1.1.2.1 -r1.1.2.2
  --- PropertySets.java 7 May 2002 05:17:52 -   1.1.2.1
  +++ PropertySets.java 15 Jun 2002 04:20:39 -  1.1.2.2
  @@ -374,37 +374,19 @@
   tableSet = Collections.unmodifiableSet((Set)tableProps);
   }
   
  -/**
  - * Shorthand properties.  Where properties interact, they are listed
  - * in increasing precision.
  - */
  -public static final ROIntArray shorthands =
  -new ROIntArray(new int[] {
  -PropNames.BACKGROUND
  -,PropNames.BACKGROUND_POSITION
  -,PropNames.BORDER
  -,PropNames.BORDER_STYLE
  -,PropNames.BORDER_COLOR
  -,PropNames.BORDER_WIDTH
  -,PropNames.BORDER_TOP
  -,PropNames.BORDER_RIGHT
  -,PropNames.BORDER_BOTTOM
  -,PropNames.BORDER_LEFT
  -,PropNames.BORDER_SPACING
  -,PropNames.CUE
  -,PropNames.FONT
  -,PropNames.MARGIN
  -,PropNames.PADDING
  -,PropNames.PAGE_BREAK_AFTER
  -,PropNames.PAGE_BREAK_BEFORE
  -,PropNames.PAGE_BREAK_INSIDE
  -,PropNames.PAUSE
  -,PropNames.POSITION
  -,PropNames.SIZE
  -,PropNames.VERTICAL_ALIGN
  -,PropNames.WHITE_SPACE
  -,PropNames.XML_LANG
  -});
  +// My preference here for shorthands which expand to compound properties
  +// would be to expand only to the compound, and allow compounds to be
  +// "normally" expanded in a second step.  Unfortunately, the shorthand
  +// border-spacing expands (potentially) into both of the elements of
  +// the border-separation compound.  However, other compound expansions
  +// are defined with only a single value for the compound, so I will
  +// treat border-separation as a special case in the event that two
  +// values are provided.
  +// I''m not sure whether a shorthand specification which sets a compound
  +// property with a single top-level value should be regarded as a
  +// specification for the purposes of inheritance, but I will assume so
  +// until further notice.
  +// pbw
   
   private static final int[] backgroundPosition = {
   PropNames.BACKGROUND_POSITION_HORIZONTAL
  @@ -493,8 +475,7 @@
*/
   public static final ROIntArray borderSpacingExpansion =
   new ROIntArray(new int[] {
  -PropNames.BORDER_SEPARATION_BLOCK_PROGRESSION_DIRECTION
  -,PropNames.BORDER_SEPARATION_INLINE_PROGRESSION_DIRECTION
  +PropNames.BORDER_SEPARATION
   });
   
   public static final ROIntArray cueExpansion =
  @@ -515,11 +496,7 @@
   ,PropNames.FONT_VARIANT
   ,PropNames.FONT_WEIGHT
   ,PropNames.FONT_SIZE
  -,PropNames.LINE_HEIGHT_MINIMUM
  -,PropNames.LINE_HEIGHT_OPTIMUM
  -,PropNames.LINE_HEIGHT_MAXIMUM
  -,PropNames.LINE_HEIGHT_PRECEDENCE
  -,PropNames.LINE_HEIGHT_CONDITIONALITY
  +,PropNames.LINE_HEIGHT
   });
   
   public static final ROIntArray marginExpansion =
  @@ -537,6 +514,128 @@
   ,PropNames.PADDING_BOTTOM
   ,PropNames.PADDING_LEFT
   });
  +
  +public static final ROIntArray pageBreakAfterExpansion =
  +new ROIntArray(new int[] {
  +PropNames.BREAK_AFTER
  +,PropNames.KEEP_WITH_NEXT
  +});
  +
  +public static final ROIntArray pageBreakBeforeExpansion =
  +new ROIntArray(new int[] {
  +PropNames.BREAK_BEFORE
  +,PropNames.KEEP_WITH_PREVIOUS
  +});
  +
  +public static final ROIntArray pageBreakInsideExpansion =
  +new ROIntArray(new int[] {
  +PropNames.KEEP_TOGETHER
  +});
  +
  +public static final ROIntArray pauseExpansion =
  +new ROIntArray(new int[] {
  +PropNames.PAUSE_BEFORE
  +,PropNames.PAUSE_AFTER
  +});
  +
  +public static final ROIntArray positionExpansion =
  +new ROIntArray(new int[] {
  +PropNames.RELATIVE_POSITION
  +,PropNames.ABSOLUTE_POSITION
  +});
  +
  +public static final

JimiException with TIFF

2002-06-14 Thread Padmanabhan, Shobana 

I get an error when I try to include a TIFF in the sample images.fo. If I
replace this with a GIF, it works fine. Any pointers would be appreciated.

Thanks,
Shobana


  A TIF image in
FOP
  

  


ERROR   10240   [fop ] (): Error while creating area : Error creating
FopImage object (Error creating FopImage object
(file:../../graphics/single.tiff) : org.apache.fop.image.JimiImage

If I printStackTrace():

com.sun.jimi.core.JimiException
at
com.sun.jimi.core.JimiReader.getNextJimiImage(JimiReader.java:636)
at
com.sun.jimi.core.JimiReader.getNextImageProducer(JimiReader.java:673)
at
com.sun.jimi.core.JimiReader.getImageProducer(JimiReader.java:451)
at com.sun.jimi.core.Jimi.getImageProducer(Jimi.java:250)
at org.apache.fop.image.JimiImage.loadImage(JimiImage.java:54)
at
org.apache.fop.image.AbstractFopImage.getWidth(AbstractFopImage.java:165)
at
org.apache.fop.fo.flow.ExternalGraphic.layout(ExternalGraphic.java:129)
at org.apache.fop.fo.flow.Block.layout(Block.java:262)
at org.apache.fop.fo.flow.Block.layout(Block.java:262)
at org.apache.fop.fo.flow.Flow.layout(Flow.java:156)
at org.apache.fop.fo.flow.Flow.layout(Flow.java:113)
at
org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:296)
at
org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:200)
at
org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:182)
at
org.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1398)
at
org.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValidator
.java:1019)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XM
LDocumentScanner.java:1256)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
java:381)
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:948)
at org.apache.fop.apps.Driver.render(Driver.java:481)
at org.apache.fop.apps.Driver.run(Driver.java:554)
at FOPConnector.renderFO(TestFOPConnector.java:30)
at TestFOPConnector.main(TestFOPConnector.java:79)
img status -1
new status 1
java.lang.Exception: Image error
at
org.apache.fop.image.FopImageConsumer.isImageReady(FopImageConsumer.java:100
)
at org.apache.fop.image.JimiImage.loadImage(JimiImage.java:60)
at
org.apache.fop.image.AbstractFopImage.getWidth(AbstractFopImage.java:165)
at
org.apache.fop.fo.flow.ExternalGraphic.layout(ExternalGraphic.java:129)
at org.apache.fop.fo.flow.Block.layout(Block.java:262)
at org.apache.fop.fo.flow.Block.layout(Block.java:262)
at org.apache.fop.fo.flow.Flow.layout(Flow.java:156)
at org.apache.fop.fo.flow.Flow.layout(Flow.java:113)
at
org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:296)
at
org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:200)
at
org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:182)
at
org.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1398)
at
org.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValidator
.java:1019)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XM
LDocumentScanner.java:1256)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
java:381)
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:948)
at org.apache.fop.apps.Driver.render(Driver.java:481)
at org.apache.fop.apps.Driver.run(Driver.java:554)
at FOPConnector.renderFO(TestFOPConnector.java:30)
at TestFOPConnector.main(TestFOPConnector.java:79)
org.apache.fop.image.FopImageException: Error while loading image
file:../../graphics/single.tiff : class java.lang.Exception - Image error
at org.apache.fop.image.JimiImage.loadImage(JimiImage.java:132)
at
org.apache.fop.image.AbstractFopImage.getWidth(AbstractFopImage.java:165)
at
org.apache.fop.fo.flow.ExternalGraphic.layout(ExternalGraphic.java:129)
at org.apache.fop.fo.flow.Block.layout(Block.java:262)
at org.apache.fop.fo.flow.Block.layout(Block.java:262)
at org.apache.fop.fo.flow.Flow.layout(Flow.java:156)
at org.apache.fop.fo.flow.Flow.layout(Flow.java:113)
at
org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:296)
at
org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:200)
at
org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:182)
at
org.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1398)
at
org.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValidator
.java:1019)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XM
LDocumentScanner.java:1256)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome

DO NOT REPLY [Bug 9885] New: - link in pdf to another pdf through url doesn't work

2002-06-14 Thread 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=9885

link in pdf to another pdf through url doesn't work

   Summary: link in pdf to another pdf through url doesn't work
   Product: Fop
   Version: 0.20.3
  Platform: Other
OS/Version: Windows XP
Status: NEW
  Severity: Normal
  Priority: Other
 Component: pdf renderer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


When using fo:basic-link to a pdf document through url like http or file, pdf
created by fop is unable to open it. 

http://www.tkachenko.com/simple.pdf";>link

Acrobat gives me "The specified file http://www.tkachenko.com/simple.pdf doesn't
exist". This works in antenna formatter.
I believe link in pdf is created somehow wrong, here is link, created by fop:
/F (http://www.tkachenko.com/simple.pdf)

And here is a link, created by antenna:
/A << /S /URI /URI (http://www.tkachenko.com/simple.pdf) >>

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

DO NOT REPLY [Bug 9880] New: - URL-Authentication in org.apache.fop.image

2002-06-14 Thread 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=9880

URL-Authentication in org.apache.fop.image

   Summary: URL-Authentication in org.apache.fop.image
   Product: Fop
   Version: 0.20.3
  Platform: PC
OS/Version: Windows XP
Status: NEW
  Severity: Enhancement
  Priority: Other
 Component: images
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Dear Eric,

in a project we needed an Apache Webserver authentication via URL. 

The project is a content management system based on the Tamino
XML-Server. Documents can be presented either in HTML or in 
PDF format, this is where FOP comes in the place.

Due to security issues we protected an URL-path with Basic Authentication.
This lead to HTTP 401 errors when trying to get image files into the
FOP process by an HttpRequest.

We added some lines of code to the following classes from the 
package org.apache.fop.image:
BmpImage 
JimiImage 
JAIImage 
JpegImage 
GifImage 
FopImageFactory

We replaced the invocation of the methods URL.getContent() and
URL.openStream() by this code (with slight differences in either
class):



java.net.URLConnection urlCon = this.m_href.openConnection(); 
String userpass = this.m_href.getUserInfo(); 
String auth = "Basic " + new 
 sun.misc.BASE64Encoder().encode(userpass.getBytes()); 
urlCon.setRequestProperty("Authorization", auth); 
ImageProducer ip = (ImageProducer)urlCon.getContent();



We made a straight forward approch with hard encoding of our 
user/password requirements. You should of course better replace
this by invocation of the URL-method getUserInfo() which returns
a colon seperated string "user:password". Maybe you still have
to check whether it is null or not.

Thanks for your good work in the ASF, we hope this info is
helpful for your work!

with best regards

Marko Petersen
Malte Schnack

PS: If you need the amended source files pls contact either
Marko ([EMAIL PROTECTED]) or me ([EMAIL PROTECTED])

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

cvs commit: xml-fop/test/resources/fop/svg link.fo link.svg text.svg

2002-06-14 Thread keiron 

keiron  2002/06/14 07:29:49

  Added:   test/resources/fop/svg link.fo link.svg text.svg
  Log:
  some svg test, links and text
  
  Revision  ChangesPath
  1.1  xml-fop/test/resources/fop/svg/link.fo
  
  Index: link.fo
  ===
  
  
  http://www.w3.org/1999/XSL/Format";>
  

  



  

  

  
  
  

  Embedded/Image SVG

  

  

  
  

  
  
  
  
  
  1.1  xml-fop/test/resources/fop/svg/link.svg
  
  Index: link.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";>
  
  
  
  
  
  GREEN
  
  
  http://xml.apache.org/fop/";>
  
  FOP
  
  
  
  
  Another
  file
  
  
  
  
  RED
  
  
  
  
  
  
  
  
  
  1.1  xml-fop/test/resources/fop/svg/text.svg
  
  Index: text.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";>
  
  
  
  Various Text Elements
  
  Normal Text in 
Helvetica,
  Symbol,
  Unknown,
  Courier,
  Arial
  
  
  Large Text (scaled)
  
  Normal Text (unscaled)
  
  fractional Text
  
  Coloured Text
  Stroked Text
  Stroked/Filled Text
  Overline 
Text
  Underline 
Text
  Strikethrough Text
  
  Text with tspan
  
   
   
   
  
  
  
  
  super and subscripts
  
  
  
   FOP
   FOP
   FOP
   FOP
  
  
  



  
  Filtered Text
  
  
  

   
  
   
  
   
   
  

  
   
  

  
   
  

  
  
  

  
Fop
  
  
  
  
  
  
  
  
  

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

cvs commit: xml-fop/test/resources/fop/svg - New directory

2002-06-14 Thread keiron 

keiron  2002/06/14 07:26:14

  xml-fop/test/resources/fop/svg - New directory

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

cvs commit: xml-fop/test/resources/fop - New directory

2002-06-14 Thread keiron 

keiron  2002/06/14 07:26:01

  xml-fop/test/resources/fop - New directory

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

cvs commit: xml-fop/test/resources - New directory

2002-06-14 Thread keiron 

keiron  2002/06/14 07:23:44

  xml-fop/test/resources - New directory

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

DO NOT REPLY [Bug 9864] New: - fo:list-item-label at the end of line

2002-06-14 Thread 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=9864

fo:list-item-label at the end of line

   Summary: fo:list-item-label at the end of line
   Product: Fop
   Version: 0.20.3
  Platform: All
OS/Version: All
Status: NEW
  Severity: Normal
  Priority: Other
 Component: pdf renderer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Hi!

This bug comes with 0.20.4rc

My list-item-labels will be placed at the end of the line if i set the attribute
text-align="end" at the fo:block element.

The problem comes with the AWTRenderer too.
I had a version, i think 0.20.3 or 0.20.3rc where it works. (only one works)

One example for the bug is one from FOP .../doc/examples/fo/list.fo


example fo:


 
  
   
 -
   
  
  
   
 Item
   
  
 
 
  
   
-
   
  
  
   
Item 2
   
  
 



result:
Item  -
Item  -


thanks

Sascha

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

Re: [ANNOUNCEMENT] FOP 0.20.4 Release Candidate available

2002-06-14 Thread Martin Peřina 

On Čt, 2002-06-13 at 18:10, Christian Geisert wrote:
> Hi all,
> 
> the Release Candidate for 0.20.4 is available at
> http://xml.apache.org/dist/fop for downloading and testing.
> 
> It is planed to make the actual release in about a week (or two?)
> if no serious bugs show up.
> 
> 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 maschine
> - 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
> 
> 
> Feedback/bugreports are welcome especially (but of course not limited)
> for the following issues:
> 
> - compiling FOP with Jdk1.4 under Windows

On Linux with Sun J2SDK 1.4.0_01 it compiles fine.

> - running FOP on a EBCDIC maschine
> - running FOP from Win98/ME command line
> - processing FOP generated PDFs with RIP engines/preflight (?) tools
> - custom font loading with BaseDir property

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:

   
 
   


  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.


> 
> 
> Needs to be done for the release:
> - check documentation (new jar versions, classpath etc.)
> - anything missing in Release Notes/CHANGES ?
>   (apart from fixing my english ;-)

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.


Martin Perina



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

Re: FopServlet

2002-06-14 Thread Nirupama Yalavarti 


--- Holger Prause <[EMAIL PROTECTED]> wrote:
> 
> - Original Message -
> From: "J.Pietschmann" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, June 14, 2002 1:47 AM
> Subject: Re: FopServlet
> 
> 
> > Nirupama Yalavarti wrote:
> > > Thats a great anwere...THE servlet seems to ahve
> run
> > > correctly( In fact it didnt show me any error..)
> > > But where can I find the produced pdf? any idea?
> >
> > In your browser? Look into the browser cache
> first.
> > IEx is a bit fragile when it comes to showing PDF.
> > Configure your webapp so that you can use an URL
> > ending in .pdf for retrieving the PDF:
> >   http://my.host/some/path/to/servlet.pdf
> > or
> >
>
http://my.host/some/path/to/servlet.pdf?xml=foo.xml&xsl=foo.xsl&dummy=.pdf
> >
> 
> 
> Hello,
> 
> maybe you have Avtive X disabled and thats the
> reason why u dont see the
> produced pdf.
> 
> I took my an half an hout to find this out .-)

Thanks a lot, but I could get it by placing the dummy
parameter.
Nirupama


=


__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

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

Re: FopServlet

2002-06-14 Thread Holger Prause 


- Original Message -
From: "J.Pietschmann" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 14, 2002 1:47 AM
Subject: Re: FopServlet


> Nirupama Yalavarti wrote:
> > Thats a great anwere...THE servlet seems to ahve run
> > correctly( In fact it didnt show me any error..)
> > But where can I find the produced pdf? any idea?
>
> In your browser? Look into the browser cache first.
> IEx is a bit fragile when it comes to showing PDF.
> Configure your webapp so that you can use an URL
> ending in .pdf for retrieving the PDF:
>   http://my.host/some/path/to/servlet.pdf
> or
>
http://my.host/some/path/to/servlet.pdf?xml=foo.xml&xsl=foo.xsl&dummy=.pdf
>


Hello,

maybe you have Avtive X disabled and thats the reason why u dont see the
produced pdf.

I took my an half an hout to find this out .-)



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

DO NOT REPLY [Bug 9640] - fop gets font list in font-family property as a string, not a list

2002-06-14 Thread 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=9640

fop gets font list in font-family property as a string, not a list

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2002-06-14 09:27 ---
well, fixed in maintenance branch and going to be in 0.20.4RC.

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

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

2002-06-14 Thread keiron 

keiron  2002/06/14 00:53:34

  Modified:docs/xml-docs/fop status.xml
   docs/design intro.xml status.xml
  Log:
  more status info, design status
  
  Revision  ChangesPath
  1.2   +1 -0  xml-fop/docs/xml-docs/fop/status.xml
  
  Index: status.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/status.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- status.xml12 Jun 2002 14:14:32 -  1.1
  +++ status.xml14 Jun 2002 07:53:34 -  1.2
  @@ -35,6 +35,7 @@
   
   ... and plenty of other areas. See the todo
   list for more details.
  +See ths Status for more information.
   
   
   Development for 1.0DR1 is addressing the design issues for layout and
  
  
  
  1.4   +0 -5  xml-fop/docs/design/intro.xml
  
  Index: intro.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/design/intro.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- intro.xml 17 Dec 2001 10:17:25 -  1.3
  +++ intro.xml 14 Jun 2002 07:53:34 -  1.4
  @@ -14,11 +14,6 @@
   
   
   
  -
  -The information here is still in the early stage, some information
  -may be wrong or misleading. In general there is not a broad enough
  -input and it is lacking in depth of information.
  -
   The information here describes the design and architecture details for FOP.
   Currently this is part of a redesign process for some of the core parts of
   FOP.
  
  
  
  1.2   +46 -1 xml-fop/docs/design/status.xml
  
  Index: status.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/design/status.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- status.xml14 Dec 2001 07:32:28 -  1.1
  +++ status.xml14 Jun 2002 07:53:34 -  1.2
  @@ -1,6 +1,6 @@
   
   
  -
  +
   
   
   
  @@ -19,6 +19,51 @@
   it possible to handle keeps/breaks and spacing better.
 
   
  +A number of issues have been dealt with in the redesigned code.
  +  
  +  
  +
  +
  +
  +avalon integration - logging, configuration, component management, caching, uri 
resolver
  +improved interfaces
  +
  +  no threading/static problems
  +  simpler to use
  +
  +
  +better commandline handling
  +
  +  
  +  
  +
  +
  +Many of these changes will make FOP much better to use and develop.
  +So if you help out with the development you can get to use these
  +things sooner.
  +
  +better layout design - that can handle keeps and
  +spacing better
  +better area tree handling - means it can run in
  +less memory
  +better image handling - redone so it can use a
  +cache and synchronizes properly only on the current image while loading
  +svg now in an xml handler, FOP can be used without batik
  +bookmark extension improved a bit - changed bookmark extension,
  +now requires a wrapping element bookmark
  +new interface for structured documents, rtf and mif
  +better handling of unknown xml and xml from an unknown namespace
  +Changed extensions to allow for external xml
  +Can have a default element mapping for extensions
  +mathml extension
  +another xml -> svg extension
  +svg text normal text if that can be handled otherwise stroked
  +this is done automatically
  +new area tree model
  +new renderer model
  +added handlers for xml in renderer
  +changed area tree xml format to match the area tree hierarchy
  +
   
 
 
  
  
  

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