Re: Happy Holidays

2002-12-21 Thread Bertrand Delacretaz
Happy Holidays team - I've been very quiet lately but this is 
*definitely* a good crowd, I wish I could spend more time here!

-Bertrand


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



Re: bidi in the branch

2002-12-21 Thread Jeremias Maerki
Hi Peter

On 20.12.2002 00:30:13 Peter B. West wrote:
 Jeremias Maerki wrote:
  :-) Ok, you're sentenced to implement the same functionality in the
  trunk. I'm -0 for the inclusion in the branch as it sends the wrong
  message IMO. But I'm looking forward to seeing bidi support in action in
  the trunk.
 
 Jeremias,
 
 I would encourage Oleg to bring this functionality into HEAD.

Didn't I? :-)

 If it 
 already exists in Oleg's working copy of the maint branch (for reasons 
 which have frequently been canvassed here), I think it would be churlish 
 of us to deny access to our faithful band of users.

I would agree was it not for something that is an argument for the
redesign. And read again, please. I wrote -0, not -1. I don't deny
anything to anybody, just expressing an opinion.

 So, fop-0_20_2-maintain +0.
 
 Peter
 
 
  On 19.12.2002 18:11:02 Oleg Tkachenko wrote:
  
 Hello there!
 
 I know, shame on me, shame on me, but I've implemented partial bidi support in 
 the branch. Sorry, it was urgent commercial requirement.
 It seems to be working ok (QA is still verifying it though), but of course 
 it's a patch actually and I don't like it much. My question is: should I 
 commit it to the branch codebase? I'm inclining to implement it in a clean way 
 in the trunk instead of extending/patching the branch.


Jeremias Maerki


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




Re: PDF transforms (was: Re: File prefix again)

2002-12-21 Thread Jeremias Maerki
Hi Keiron

On 20.12.2002 09:41:52 Keiron Liddle wrote:
 On Thu, 2002-12-19 at 21:15, Jeremias Maerki wrote:
  All cool, but how exactly is that better than having a PDF template that
  is stitched behind or in front of the FOP result using iText or PJ?
  Works well. Ok, PDF reading with our own library is a bonus as is better
  XML output for debugging. But I don't see any immediate need for this at
  the moment given our limited resources. Or do I miss anything?
 
 Well I'm not really suggesting is is high priority, just an idea.
 One things is that the XML and the additions can work both in and out of
 Fop.

 At least outputing SAX in the XMLRenderer would probably be an
 improvement.

Ok then. Will you put this on the todo list?

Jeremias Maerki


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




Re: Happy Holidays

2002-12-21 Thread Jeremias Maerki

On 21.12.2002 10:51:50 Bertrand Delacretaz wrote:
 Happy Holidays team - I've been very quiet lately but this is 
 *definitely* a good crowd, I wish I could spend more time here!

Same from me. At least, I'm happy to actually have time to spend here
during the next couple of months, maybe more.

Happy Holidays!

Jeremias Maerki


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




Re: bidi in the branch

2002-12-21 Thread Peter B. West
Jeremias Maerki wrote:

Hi Peter

On 20.12.2002 00:30:13 Peter B. West wrote:


Jeremias Maerki wrote:


:-) Ok, you're sentenced to implement the same functionality in the
trunk. I'm -0 for the inclusion in the branch as it sends the wrong
message IMO. But I'm looking forward to seeing bidi support in action in
the trunk.


Jeremias,

I would encourage Oleg to bring this functionality into HEAD.



Didn't I? :-)



Yes; right above.  Call my comment an extended +0 for the sentence you 
imposed.



If it 
already exists in Oleg's working copy of the maint branch (for reasons 
which have frequently been canvassed here), I think it would be churlish 
of us to deny access to our faithful band of users.


I would agree was it not for something that is an argument for the
redesign. And read again, please. I wrote -0, not -1. I don't deny
anything to anybody, just expressing an opinion.



Same here - just an opinion.  That's why I went for a +0.




So, fop-0_20_2-maintain +0.


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: Happy Holidays

2002-12-21 Thread Victor Mote
Arved Sandstrom wrote:

 I'd like to wish everyone here happy holidays, whatever is appropriate.
 
 This is a good crowd.

Hear, hear! I must agree on both counts.

Victor Mote

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




Re: PDF transforms (was: Re: File prefix again)

2002-12-21 Thread Kevin O'Neill
On Thu, 2002-12-19 at 18:05, Keiron Liddle wrote:
 On Wed, 2002-12-18 at 15:23, Nicola Ken Barozzi wrote:
   I don't get this.  How can PDFs be transformed?
  
  There are Java libraries that read PDFs. What would be really cool is to 
  have a reader or something like it that uses a PDF as a template.
  Using FOP for just filling out forms is overkill, we just need templating.
  
  This is a general use case of PDF transformation, and another that I 
  would really like to see is to generate a non-controlled copy stamp on 
  the PDF for the management of ISO9001 documentation.
  
  Or simply by adding a copyright statement.
 
 Sounds like some good ideas.
 
 It would be possible to do some work with Fop so that it can:
 - convert xsl:fo to paged xml

Is the paged XML a new or existing format?

 - convert paged xml to pdf (or other formats)
 - define templates with the paged xml
 - append paged xml to a current document
 
 So it would be possible to create the paged xml from fo. Then to do a
 transform or directly convert or append the paged xml to pdf.
 Also the extensions and foreign xml can be passed through directly so
 that both formats support the same extensions, such as svg.
 
 So the changes that would need to be made are:
 - improve and update xml renderer so that it can output SAX
 - improve and update AreaTreeBuilder so that it takes SAX input
 - make some additions to the pdf lib so it can load and read pdf
 documents
 
 Then it shouldn't be so hard to add in extensions for pdf forms etc.
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]
-- 
If you don't test then your code is only a collection of bugs which 
apparently behave like a working program. 

Website: http://www.rocketred.com.au/blogs/kevin/


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




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

2002-12-21 Thread pbwest
pbwest  2002/12/21 19:36:11

  Added:   docs/design/alt.design layoutmanagers.xml
  Log:
  Cleaning up.
  
  Revision  ChangesPath
  1.1  xml-fop/docs/design/alt.design/layoutmanagers.xml
  
  Index: layoutmanagers.xml
  ===
  ?xml version=1.0 encoding=UTF-8 standalone=no?
  !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN
  
http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd;
  
  !-- $Id: layoutmanagers.xml,v 1.1 2002/12/22 03:36:11 pbwest Exp $ --
  
  document
header
  titleLayout managers/title
  authors
person name=Peter B. West email=[EMAIL PROTECTED]/
  /authors
/header
body
  section
titleLayout managers in FOP/title
p
What do the layout managers do?  Most layout is is automatic
in the sense of being a straightforward stacking operation.
Sibling inline-areas, including fo:character areas, are
stacked in line-areas in the inline-progression-direction.
Sibling block-areas, including line-areas, are stacked in the
block-progression-direction.
/p
p
In the simple cases in which both the available
block-progression-dimension and the available
inline-progression-dimension are known, this process can be
driven bottom-up.  Available dimensions trickle down from the
top, and the bottom level galleys can determine when their
available areas are full and suspend pending the arrival of
more areas.  Such full notifications bubble back up the tree
of active galleys.  E.g., if an inline galley fills a
line-area of a given inline-p-d and suspends while still
within the available block-p-d, the parent block-area galley
will simply stack the inline-area and notify the inline galley
to continue.  If the inline-galley discovers that the next
line-area that it would generate will not fit in the the
block-p-d, it suspends with a notification to that effect to
its parent.  
/p
p
In more complex cases the dimensions may not be fully
specified, or decisions about layout may depend on later
layout.  In all such cases some layout look-ahead is required
which can report results back to higher layout levels.  The
job for a layout manager in these cirucmstances is to evaluate
the information flowing back and set parameters for the best
fit layout.
/p
  /section
/body
  /document
  
  
  

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




cvs commit: xml-fop/src/documentation/content/xdocs/design/alt.design AbsolutePosition-png.xml BorderCommonStyle-png.xml Properties-png.xml PropertyConsts-png.xml VerticalAlign-png.xml

2002-12-21 Thread pbwest
pbwest  2002/12/21 19:59:35

  Removed: src/documentation/content/xdocs/design/alt.design
AbsolutePosition-png.xml BorderCommonStyle-png.xml
Properties-png.xml PropertyConsts-png.xml
VerticalAlign-png.xml
  Log:
  No longer required.

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




cvs commit: xml-fop/src/documentation/content/xdocs tabs.xml

2002-12-21 Thread pbwest
pbwest  2002/12/21 20:14:40

  Modified:src/documentation/content/xdocs tabs.xml
  Log:
  Fixed headings.
  Replaced Redesign tab with Development, Redesign and alt design.
  
  Revision  ChangesPath
  1.3   +11 -9 xml-fop/src/documentation/content/xdocs/tabs.xml
  
  Index: tabs.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/tabs.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- tabs.xml  19 Nov 2002 07:57:27 -  1.2
  +++ tabs.xml  22 Dec 2002 04:14:40 -  1.3
  @@ -2,12 +2,14 @@
 !DOCTYPE tabs PUBLIC -//APACHE//DTD Cocoon Documentation Tab V1.0//EN
   
http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/tab-cocoon-v10.dtd;
   
  -  tabs software=MyProj
  -title=MyProj
  -copyright=Foo
  -xmlns:xlink=http://www.w3.org/1999/xlink;
  -
  -tab label=Home dir=/
  -tab label=Redesign dir=dev//
  -
  -/tabs
  +tabs software=FOP
  +  title=FOP
  +  copyright=@year@ The Apache Software Foundation
  +  xmlns:xlink=http://www.w3.org/1999/xlink;
  +  
  +  tab label=Home dir=/
  +  tab label=Development dir=dev//
  +  tab label=Redesign dir=design//
  +  tab label=alt design dir=design/alt.design//
  +  
  +/tabs
  
  
  

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




cvs commit: xml-fop/src/documentation/content/design/alt.design PropertyValue.html

2002-12-21 Thread pbwest
pbwest  2002/12/21 20:16:46

  Added:   src/documentation/content/design/alt.design
PropertyValue.html
  Log:
  Htmlized code.
  
  Revision  ChangesPath
  1.1  
xml-fop/src/documentation/content/design/alt.design/PropertyValue.html
  
  Index: PropertyValue.html
  ===
  !DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01//EN
  !-- Created by htmlize-0.67 in css mode. --
  html
head
  titlePropertyValue.java/title
  style type=text/css
  !--
body {
  color: #00;
  background-color: #faf0e6;
} /* default */
.variable-name {
  color: #8b008b;
  background-color: #faf0e6;
} /* font-lock-variable-name-face */
.jde-java-font-lock-package {
  color: #cd;
  background-color: #faf0e6;
} /* jde-java-font-lock-package-face */
.jde-java-font-lock-constant {
  color: #5f9ea0;
  background-color: #faf0e6;
} /* jde-java-font-lock-constant-face */
.keyword {
  color: #8b;
  background-color: #faf0e6;
} /* font-lock-keyword-face */
.jde-java-font-lock-doc-tag {
  color: #008b00;
  background-color: #faf0e6;
} /* jde-java-font-lock-doc-tag-face */
.string {
  color: #008b00;
  background-color: #faf0e6;
} /* font-lock-string-face */
.jde-java-font-lock-number {
  color: #bc8f8f;
  background-color: #faf0e6;
} /* jde-java-font-lock-number-face */
.type {
  color: #4682b4;
  background-color: #faf0e6;
} /* font-lock-type-face */
.jde-java-font-lock-italic {
  background-color: #faf0e6;
  font-style: italic;
} /* jde-java-font-lock-italic-face */
.jde-java-font-lock-modifier {
  color: #da70d6;
  background-color: #faf0e6;
} /* jde-java-font-lock-modifier-face */
.comment {
  color: #8b;
  background-color: #faf0e6;
} /* font-lock-comment-face */
.function-name {
  color: #8b2323;
  background-color: #faf0e6;
} /* font-lock-function-name-face */
a {
  color: inherit;
  background-color: inherit;
  font: inherit;
  text-decoration: inherit;
}
a:hover {
  text-decoration: underline;
}
  --
  /style
/head
body
  pre
  span class=keywordpackage/span span 
class=jde-java-font-lock-packageorg/span.span 
class=jde-java-font-lock-packageapache/span.span 
class=jde-java-font-lock-packagefop/span.span 
class=jde-java-font-lock-packagedatatypes/span;
  
  span class=keywordimport/span span 
class=jde-java-font-lock-packageorg/span.span 
class=jde-java-font-lock-packageapache/span.span 
class=jde-java-font-lock-packagefop/span.span 
class=jde-java-font-lock-packagefo/span.span 
class=jde-java-font-lock-packageexpr/span.span 
class=typePropertyException/span;
  span class=keywordimport/span span 
class=jde-java-font-lock-packageorg/span.span 
class=jde-java-font-lock-packageapache/span.span 
class=jde-java-font-lock-packagefop/span.span 
class=jde-java-font-lock-packagefo/span.span class=typeFONode/span;
  span class=keywordimport/span span 
class=jde-java-font-lock-packageorg/span.span 
class=jde-java-font-lock-packageapache/span.span 
class=jde-java-font-lock-packagefop/span.span 
class=jde-java-font-lock-packagedatastructs/span.span 
class=typeROStringArray/span;
  
  span class=comment/*
   * PropertyValue.java
   * $Id: PropertyValue.html,v 1.1 2002/12/22 04:16:46 pbwest Exp $
   *
   * Created: Tue Nov 20 22:18:11 2001
   * Copyright (C) 2001 The Apache Software Foundation. All rights reserved.
   * For details on use and redistribution please refer to the
   * LICENSE file included with these sources.
   * @author lt;a href=quot;mailto:[EMAIL PROTECTED]quot;gt;Peter B. 
Westlt;/agt;
   * @version $Revision: 1.1 $ $Name:  $
   *//span
  span class=comment/**
   * Base interface for all property value types.
   *//span
  
  span class=jde-java-font-lock-modifierpublic/span span 
class=keywordinterface/span span class=function-name 
id=PropertyValuePropertyValue/span {
  
  span class=jde-java-font-lock-modifierpublic/span span 
class=jde-java-font-lock-modifierstatic/span span 
class=jde-java-font-lock-modifierfinal/span span class=typeint/span
  span class=jde-java-font-lock-constant 
id=NO_TYPENO_TYPE/span = span class=jde-java-font-lock-number0/span
   ,span class=jde-java-font-lock-constant 
id=ANGLEANGLE/span = span class=jde-java-font-lock-number1/span
,span class=jde-java-font-lock-constant 
id=AUTOAUTO/span = span class=jde-java-font-lock-number2/span
,span