Re: Problems with URL encoding in FOP docs

[J.Pietschmann]

Peter B. West wrote:
In http://xml.apache.org/fop/design/alt.design/index.html there occurs 
the following link:
http://marc.theaimsgroup.com/%3Fl=fop-dev%26m=103890259919360%26w=2";>

The question mark and ampersand are encoded as expected.  When I hover 
on this link in Mozilla, I get:
http://marc.theaimsgroup.com/?l=fop-dev&m=103890259919360&w=2
as expected.

When I follow the link, I get the _encoded_ values in the location 
window, and 
Well, the server is right: the URL is sent verbatim, with the special
chars encoded, which makes the server look for an object named
 /?l=fop-dev&m=103890259919360&w=2
rather than for the object
 /
with the parameters
 l=fop-dev
 m=103890259919360
 w=2
passed.
 the website tells me that URL with the _unencoded_ values is 
not available.
An artefact of the error message generator, I would think.
When I manually change the URL in the location window to 
contain the _encoded_ values, it works.
Weird, but probably "works as designed."
How do I fix this?
Something is wrong with the XSLT processor's serializer. The usual
drill
- Check JDK version, upgrade if necessary
- Install latest Xalan into lib/endorsed, if necessary
- Submit bug report, if the problem still persists.
It might be prudent to check whether the source doesn't already contain
the wrong URL.
J.Pietschmann

Problems with URL encoding in FOP docs

[Peter B. West]

Fops,
In http://xml.apache.org/fop/design/alt.design/index.html there occurs 
the following link:
http://marc.theaimsgroup.com/%3Fl=fop-dev%26m=103890259919360%26w=2";>

The question mark and ampersand are encoded as expected.  When I hover 
on this link in Mozilla, I get:
http://marc.theaimsgroup.com/?l=fop-dev&m=103890259919360&w=2
as expected.

When I follow the link, I get the _encoded_ values in the location 
window, and the website tells me that URL with the _unencoded_ values is 
not available.  When I manually change the URL in the location window to 
contain the _encoded_ values, it works.

How do I fix this?
Peter
--
Peter B. West 

cvs commit: xml-fop/docs/xml-docs/data document.svg logo.svg title.svg track.svg

[jeremias]

jeremias2004/03/02 12:26:43

  Modified:docs xml2pdf.xsl xslfoRef.xml
   docs/design/alt.design layoutmanagers.xml
   docs/design/fo_impl fo_classes.xml fo_classes.xsl
   docs/xml-docs fop.xml xml2pdf.xsl xml2xml.xsl
   docs/xml-docs/data document.svg logo.svg title.svg track.svg
  Log:
  Applied Apache License Version 2.0 by following the instructions at 
http://www.apache.org/dev/apply-license.html.
  
  Revision  ChangesPath
  1.7   +16 -0 xml-fop/docs/xml2pdf.xsl
  
  Index: xml2pdf.xsl
  ===
  RCS file: /home/cvs/xml-fop/docs/xml2pdf.xsl,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- xml2pdf.xsl   30 Nov 2002 08:54:26 -  1.6
  +++ xml2pdf.xsl   2 Mar 2004 20:26:42 -   1.7
  @@ -1,3 +1,19 @@
  +
  +
   http://www.w3.org/1999/XSL/Transform"; version="1.0"
xmlns:fo="http://www.w3.org/1999/XSL/Format";>
  
  
  
  1.3   +18 -1 xml-fop/docs/xslfoRef.xml
  
  Index: xslfoRef.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/xslfoRef.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- xslfoRef.xml  30 Nov 2002 08:54:26 -  1.2
  +++ xslfoRef.xml  2 Mar 2004 20:26:42 -   1.3
  @@ -1,5 +1,21 @@
   
   
  +
  +
   http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd";>
   
  
  
  
  1.3   +16 -0 xml-fop/docs/design/fo_impl/fo_classes.xml
  
  Index: fo_classes.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/design/fo_impl/fo_classes.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- fo_classes.xml30 Nov 2002 07:24:10 -  1.2
  +++ fo_classes.xml2 Mar 2004 20:26:42 -   1.3
  @@ -1,4 +1,20 @@
   
  +
  +
   
   
  
  
  
  1.3   +16 -0 xml-fop/docs/design/fo_impl/fo_classes.xsl
  
  Index: fo_classes.xsl
  ===
  RCS file: /home/cvs/xml-fop/docs/design/fo_impl/fo_classes.xsl,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- fo_classes.xsl30 Nov 2002 07:24:10 -  1.2
  +++ fo_classes.xsl2 Mar 2004 20:26:42 -   1.3
  @@ -1,4 +1,20 @@
   
  +
  +
   http://www.w3.org/1999/XSL/Transform"; version="1.0"
 xmlns:fo="http://www.w3.org/1999/XSL/Format";>
  
  
  
  1.18  +16 -0 xml-fop/docs/xml-docs/fop.xml
  
  Index: fop.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/fop.xml,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- fop.xml   30 Nov 2002 01:14:51 -  1.17
  +++ fop.xml   2 Mar 2004 20:26:42 -   1.18
  @@ -1,4 +1,20 @@
   
  +
  +
   
 http://xml.apache.org/"; label="Home"/>
 
  
  
  
  1.12  +15 -0 xml-fop/docs/xml-docs/xml2pdf.xsl
  
  Index: xml2pdf.xsl
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/xml2pdf.xsl,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- xml2pdf.xsl   30 Nov 2002 01:14:51 -  1.11
  +++ xml2pdf.xsl   2 Mar 2004 20:26:42 -   1.12
  @@ -1,5 +1,20 @@
   
  +
  +
   
  +
   http://www.w3.org/1999/XSL/Transform"; version="1.0">
   
   
  
  
  
  1.3   +16 -0 xml-fop/docs/xml-docs/data/document.svg
  
  Index: document.svg
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/data/document.svg,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- document.svg  30 Nov 2002 01:14:51 -  1.2
  +++ document.svg  2 Mar 2004 20:26:42 -   1.3
  @@ -1,4 +1,20 @@
   
  +
  +
   http://www.w3.org/TR/2000/CR-SVG-20001102/DTD/svg-20001102.dtd";>
   
  
  
  
  1.4   +16 -0 xml-fop/docs/xml-docs/data/logo.svg
  
  Index: logo.svg
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/data/logo.svg,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- logo.svg  9 Dec 2002 10:52:27 -   1.3
  +++ logo.svg  2 Mar 2004 20:26:43 -   1.4
  @@ -1,4 +1,20 @@
   
  +
  +
   http://www.w3.org/TR/2000/CR-SVG-20001102/DTD/svg-20001102.dtd";>
   
  
  
  
  1.3   +16 -0 xml-fop/docs/xml-docs/data/title.svg
  
  Index: title.svg
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/data/title.svg,v
  retrieving revision 1.2
 

RE: [PATCH] Building docs with Forrest 0.5

[Victor Mote]

Glen Mazza wrote:

> Sometime tomorrow--I just added Andreas' name to our
> teampage (he OK'ed it) so it will take awhile to get
> to the Forrestbot stage area--please republish the
> website.  Thanks.

Sorry to be so slow. We have some cosmetic issues related to the Forrest
upgrade that I would like to resolve before republishing, so that we can
keep the current look as a reference point. I'll republish as quickly after
that as possible.

Thanks for adding Andreas to the page -- it is definitely well-deserved.

Victor Mote

Re: [PATCH] Building docs with Forrest 0.5

[Clay Leeds]

You're right. I'll let them know.

Clay

Victor Mote wrote:

Clay Leeds wrote:


BTW, I just noticed they upgraded their fop back-end from fop-0.20.4 to
fop-0.20.5rc3a. Any chance they can get that updated to fop-0.20.5
before they release? I'm hoping someone on that list can submit the
request correctly, so I don't have to sign up for their mail list just
to make the request...


I don't mind doing it, but, as per my previous message, you probably want to
join that list anyway, and it would be good for Jeff et al to know of your
increased involvement here.
Victor Mote

RE: [PATCH] Building docs with Forrest 0.5

[Victor Mote]

Clay Leeds wrote:

> BTW, I just noticed they upgraded their fop back-end from fop-0.20.4 to
> fop-0.20.5rc3a. Any chance they can get that updated to fop-0.20.5
> before they release? I'm hoping someone on that list can submit the
> request correctly, so I don't have to sign up for their mail list just
> to make the request...

I don't mind doing it, but, as per my previous message, you probably want to
join that list anyway, and it would be good for Jeff et al to know of your
increased involvement here.

Victor Mote

RE: [PATCH] Building docs with Forrest 0.5

[Victor Mote]

Clay Leeds wrote:

> Sounds good to me.
>
> Having never played around with Forrest, I'd like a little help getting
> up to speed. Victor (et al), could you give me any pointers or links to
> things I should pay attention to in building this? In particular, tips
> on how to get started, as well as any links that will help get me on my
> way (such as FOP's site.xml in CVS, and any other such links), as well
> as perhaps showing me (if you know) how to change one of the sections
> and/or links, I'll do what it takes to extrapolate that to the rest of
> the site.

I haven't gone to the trouble of becoming an expert, but kind of follow a
"need to know" approach -- if I need to know, I'll go find out. The basics
are documented at:
http://xml.apache.org/fop/dev/doc.html
which you may want to supplement as you learn more.

Other general things:
1. Forrest uses Apache Cocoon for its processing, so a rudimentary
understanding of Cocoon is very helpful. I purchased Mozcar & Aston's
"Cocoon Developer's Handbook", which was of some help.
2. The big gotcha on the FOP site is compliance.xml, which requires (AFAICT)
a custom processing step as it uses a specialized DTD, its own stylesheet
etc.
3. One of the things we had asked for was a site-wide way of describing the
FOP web site, especially one that was not directory-structure dependent. I
think they have implemented this, and I think that is what Jeff is referring
to in his email. The main benefit to us is that we should be able to
rearrange our web site doc without having to move files around as much.
4. The last time I used it (circa January), the Forrest web site assumed
that I knew more than I did, and it was of limited use to me. This was
partly because things are changing on that project pretty fast. It may be
much better now, I just don't know. The good news is that they give
excellent support & you will probably want to join the mailing list for that
purpose.
5. Our doc is generated by forrestbot, which is essentially a snapshot of
Forrest that is set up to run automatically on the Apache server(s). See the
above link for more details. You will not ordinarily need to work with a
copy of Forrest on your local machine. (Christian probably has to for
creating the release documentation).
6. I probably know more than I am telling here, but that is all I can think
of ATM. Feel free to ask specific questions if you have them.

> I've taken a gander at http://xml.apache.org/forrest/changes.html for
> some ideas, and that's helpful. I'll also spend some time going through
> their docs. BTW, I notice that 0.5 is still unreleased... Anyway, I'd be
> happy to check some of this stuff out...

The key thing here is that forrestbot is using a 0.5 release candidate, and
forrestbot is what drives our concerns.

> Web Maestro Clay
>
> p.s. I'll be going to Kaua'i for my birthday (at the end of next
> week--lucky me!) Hopefully I'll be far along in the process by then... ;-p

AFAIK, there is no rush. Thanks for jumping in to help here.

Victor Mote

Re: [PATCH] Building docs with Forrest 0.5

[Clay Leeds]

BTW, I just noticed they upgraded their fop back-end from fop-0.20.4 to 
fop-0.20.5rc3a. Any chance they can get that updated to fop-0.20.5 
before they release? I'm hoping someone on that list can submit the 
request correctly, so I don't have to sign up for their mail list just 
to make the request...

Web Maestro Clay

;-p

Re: [PATCH] Building docs with Forrest 0.5

[Clay Leeds]

Victor Mote wrote:
Incidentally, I noticed a recent discussion about creating a unified PDF
manual for FOP.  Forrest 0.5 has a 'site.pdf' matcher, which generates a
PDF of the whole site.  It would be quite simple to modify the relevant
sitemap (aggregate.xmap) to only merge the subset of XML docs comprising
the manual.  This would require adopting a unified site.xml menu file,
instead of the per-directory book.xml's that FOP currently uses.
Unless anyone thinks this is urgent, I'm going to defer working on this
until we get, er, the technology that Forrest uses to create PDFs, working a
bit, ahem, better. OTOH, perhaps Clay or someone else would like to jump in
& digest the new features of 0.5.
Victor Mote
Sounds good to me.

Having never played around with Forrest, I'd like a little help getting 
up to speed. Victor (et al), could you give me any pointers or links to 
things I should pay attention to in building this? In particular, tips 
on how to get started, as well as any links that will help get me on my 
way (such as FOP's site.xml in CVS, and any other such links), as well 
as perhaps showing me (if you know) how to change one of the sections 
and/or links, I'll do what it takes to extrapolate that to the rest of 
the site.

I've taken a gander at http://xml.apache.org/forrest/changes.html for 
some ideas, and that's helpful. I'll also spend some time going through 
their docs. BTW, I notice that 0.5 is still unreleased... Anyway, I'd be 
happy to check some of this stuff out...

Web Maestro Clay

p.s. I'll be going to Kaua'i for my birthday (at the end of next 
week--lucky me!) Hopefully I'll be far along in the process by then... ;-p

RE: [PATCH] Building docs with Forrest 0.5

[Glen Mazza]

Victor,

Sometime tomorrow--I just added Andreas' name to our
teampage (he OK'ed it) so it will take awhile to get
to the Forrestbot stage area--please republish the
website.  Thanks.

Thanks,
Glen

--- Victor Mote <[EMAIL PROTECTED]> wrote:
> Jeff Turner wrote:
> 
> > The attached patch will get FOP documentation
> building cleanly with the
> > imminent Forrest 0.5 release.  There are two
> changes:


__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

RE: [PATCH] Building docs with Forrest 0.5

[Victor Mote]

Jeff Turner wrote:

> The attached patch will get FOP documentation building cleanly with the
> imminent Forrest 0.5 release.  There are two changes:
>
>  - It creates a new file, src/documentation/sitemap-0.5.xmap, which is a
>0.5-specific version of FOP's overridden sitemap.  This means the site
>can continue to be built with the old Forrest, and everyone doesn't
>have to upgrade at once.
>
>  - It comments out the DOCTYPE declarations from the SVG image files.
>This is a workaround for what appears to be a Cocoon bug
>(ClassCastExceptions when looking up the DTD).

I have applied this patch. Thanks, Jeff, very much for your efforts in
reducing the impact of the upgrade.

> Incidentally, I noticed a recent discussion about creating a unified PDF
> manual for FOP.  Forrest 0.5 has a 'site.pdf' matcher, which generates a
> PDF of the whole site.  It would be quite simple to modify the relevant
> sitemap (aggregate.xmap) to only merge the subset of XML docs comprising
> the manual.  This would require adopting a unified site.xml menu file,
> instead of the per-directory book.xml's that FOP currently uses.

Unless anyone thinks this is urgent, I'm going to defer working on this
until we get, er, the technology that Forrest uses to create PDFs, working a
bit, ahem, better. OTOH, perhaps Clay or someone else would like to jump in
& digest the new features of 0.5.

Victor Mote

RE: [PATCH] Building docs with Forrest 0.5

[Victor Mote]

Jeff Turner wrote:

> The attached patch will get FOP documentation building cleanly with the
> imminent Forrest 0.5 release.  There are two changes:
> 
>  - It creates a new file, src/documentation/sitemap-0.5.xmap, which is a
>0.5-specific version of FOP's overridden sitemap.  This means the site
>can continue to be built with the old Forrest, and everyone doesn't
>have to upgrade at once.
> 
>  - It comments out the DOCTYPE declarations from the SVG image files.
>This is a workaround for what appears to be a Cocoon bug
>(ClassCastExceptions when looking up the DTD).
> 
> 
> Incidentally, I noticed a recent discussion about creating a unified PDF
> manual for FOP.  Forrest 0.5 has a 'site.pdf' matcher, which generates a
> PDF of the whole site.  It would be quite simple to modify the relevant
> sitemap (aggregate.xmap) to only merge the subset of XML docs comprising
> the manual.  This would require adopting a unified site.xml menu file,
> instead of the per-directory book.xml's that FOP currently uses.

Thanks, Jeff. I should be able to get to this later today or tomorrow.

Victor Mote

[PATCH] Building docs with Forrest 0.5

[Jeff Turner]

Hi,

The attached patch will get FOP documentation building cleanly with the
imminent Forrest 0.5 release.  There are two changes:

 - It creates a new file, src/documentation/sitemap-0.5.xmap, which is a
   0.5-specific version of FOP's overridden sitemap.  This means the site
   can continue to be built with the old Forrest, and everyone doesn't
   have to upgrade at once.

 - It comments out the DOCTYPE declarations from the SVG image files.
   This is a workaround for what appears to be a Cocoon bug
   (ClassCastExceptions when looking up the DTD).


Incidentally, I noticed a recent discussion about creating a unified PDF
manual for FOP.  Forrest 0.5 has a 'site.pdf' matcher, which generates a
PDF of the whole site.  It would be quite simple to modify the relevant
sitemap (aggregate.xmap) to only merge the subset of XML docs comprising
the manual.  This would require adopting a unified site.xml menu file,
instead of the per-directory book.xml's that FOP currently uses.

Cheers,

--Jeff
? .bash_history
? .vim
? .vimrc
? forrest-05.diff
Index: src/documentation/sitemap-0.5.xmap
===
RCS file: src/documentation/sitemap-0.5.xmap
diff -N src/documentation/sitemap-0.5.xmap
--- /dev/null   1 Jan 1970 00:00:00 -
+++ src/documentation/sitemap-0.5.xmap  11 Sep 2003 11:09:42 -
@@ -0,0 +1,441 @@
+
+
+
+
+http://apache.org/cocoon/sitemap/1.0";>
+  
+
+  
+  
+
+
+
+  
+  
+//*[local-name() = 'section']
+title/text()
+  
+
+  
+  
+  
+href src
+site ext
+
+
+  
+
+  
+  /site//
+  /@href
+
+
+  
+
+  
+  /site/external-refs//
+  /@href
+
+  
+
+  
+  
+false
+false
+false
+
org.apache.xalan.processor.TransformerFactoryImpl
+

+

+  
+
+  
+
+
+
+  
+
+
+
+  
+-//W3C//DTD HTML 4.01 Transitional//EN
+http://www.w3.org/TR/html4/loose.dtd
+  
+
+  
+  
+  
+source
+-//APACHE//DTD Documentation V1.2//EN
+document-v12.dtd
+  
+
+  
+
+  
+  
+
+  
+  
+  
+
+  
+ISO-8859-1
+  
+ 
+
+
+
+  
+  
+
+
+
+  
+
+
+
+  
+  
+
+  
+
+  
+
+  
+
+  
+
+
+
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+
+
+
+  
+  
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+  
+
+
+
+  
+
+
+
+  
+
+
+
+  
+
+
+
+  
+
+
+
+  
+
+
+
+
+
+  
+
+  
+  
+
+  
+
+  
+
+  
+
+  
+  
+
+  
+
+  
+
+  
+
+
+
+  
+
+
+
+
+
+
+
+
+
+
+
+
+
+  
+  
+  
+
+  
+
+  
+  
+
+
+
+  
+  
+ 
+  
+
+  
+
+
+
+
+  
+
+  
+
+  
+  
+  
+
+
+
+
+
+  
+  
+  
+
+  
+
+  
+
+
+
+  
+  
+
+  
+
+  
+
+
+
+  
+  
+
+  
+
+  
+
+  
+
+
+
+
+
+
+  
+  
+  
+  
+  
+
+  
+
+  
+
+  
+
+  
+
+  
+
+  
+
+  
+  
+
+
+  
+  
+
+
+  
+
+  
+
+  
+  
+
+  
+  
+
+
+  
+  
+
+  
+  
+
+
+  
+  
+
+
+
+  
+
+  
+
+
+
+
+  
+
+  
+   
+
+
+  
+
+  
+  
+  
+
+
+  
+  
+
+   
+
+  
+
+  
+  
+  
+
+
+  
+  
+
+  
+
+  
+
+  
+
+  
+
+
+
+
+
+  
+  
+
+
+  
+
+  
+
+  
+
+  
+
+  
+  
+
+  
+  
+
+  
+  
+
+  
+ 
+
+  
+
+
+
+
+
+
+
+
+
+  
+
+  
+  
+  
+  
+
+
+
+  
+
Index: src/documentation/

cvs commit: xml-fop/docs readme

[chrisg]

chrisg  2003/02/09 19:35:27

  Modified:.Tag: fop-0_20_2-maintain build.xml
   docs Tag: fop-0_20_2-maintain readme
  Log:
  Updated build for 0.20.5 release
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.44.2.35 +13 -4 xml-fop/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/xml-fop/build.xml,v
  retrieving revision 1.44.2.34
  retrieving revision 1.44.2.35
  diff -u -r1.44.2.34 -r1.44.2.35
  --- build.xml 15 Jan 2003 14:09:56 -  1.44.2.34
  +++ build.xml 10 Feb 2003 03:35:27 -  1.44.2.35
  @@ -111,7 +111,6 @@
 
   
   
  -
   
   
   
  @@ -119,13 +118,21 @@
   
   
   
  +
  +
  +
  +
  +
   
   
  +
   
   
   
   
   
  +
  +
   
   
   
  @@ -151,9 +158,9 @@
   
   
   
  -
   
   
  +
   
   
   
  @@ -164,6 +171,8 @@
   
   
   
  +
  +
 
   
 
  @@ -185,9 +194,9 @@
   
   
   
  -
  +
   
  -
  +
   
   
   
  
  
  
  No   revision
  
  
  No   revision
  
  
  1.2.4.1   +1 -13 xml-fop/docs/readme
  
  Index: readme
  ===
  RCS file: /home/cvs/xml-fop/docs/readme,v
  retrieving revision 1.2
  retrieving revision 1.2.4.1
  diff -u -r1.2 -r1.2.4.1
  --- readme16 Dec 2000 22:49:32 -  1.2
  +++ readme10 Feb 2003 03:35:27 -  1.2.4.1
  @@ -3,17 +3,5 @@
   xslfoRef.xml  a short xsl:fo reference
   xml2pdf.xsl   a stylesheet, to convert xslfoRef.xml to pdf
   
  -html-docs Fop documentation in html files
  -xml-docs  Fop documentation in xml files and a script to create pdf 
documentation
  -
  -designUML diagrams showing the Fop design
  -bugtests  contains a set of xsl:fo files which are used to test 
  -  changes to the Fop code
  -graphics  some graphics used by the examples and test files
  -examples  a lot of xs:fo example files 
  -examples/fo   some simple examples to get you started
  -examples/
  -  pagination  some simple and some not so simple examples how to use the
  -  new page layout tags in xsl:fo
  -examples/svg  quite a lot of examples using svg
  +documentation is in build/site/index.html
   
  
  
  

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

cvs commit: xml-fop/examples/plan/docs - New directory

[jeremias]

jeremias2003/01/29 08:33:42

  xml-fop/examples/plan/docs - New directory

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

cvs commit: xml-fop/examples/mathml/docs - New directory

[jeremias]

jeremias2003/01/29 08:23:31

  xml-fop/examples/mathml/docs - New directory

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

cvs commit: xml-fop/docs/graphics fop.jpg linux.bmp listgeometry.gif page.gif xml_feather.gif xml_feather_transparent.gif

[jeremias]

jeremias2003/01/29 08:21:35

  Removed: docs/graphics fop.jpg linux.bmp listgeometry.gif page.gif
xml_feather.gif xml_feather_transparent.gif
  Log:
  Move over to examples/fo/graphics

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

cvs commit: xml-fop/docs/examples/tables background.fo borders.fo break.fo headfoot.fo keep.fo omit.fo space.fo widowsorphans.fo

[jeremias]

jeremias2003/01/29 08:11:22

  Removed: docs/examples .cvsignore build.xml results.html runtests.bat
runtests.sh
   docs/examples/advanced K3.TTF K3.xml bar.conf.xml barcode.fo
cid-fonts.fo cid-fonts.pdf giro.fo
   docs/examples/fo alignment.fo blockcontainer.fo border.fo
bordershorthand.fo character.fo corresprop.fo
extensive.fo fonts.fo hyphen.fo images.fo
inhprop.fo instream.fo leader.fo link.fo list.fo
newlinktest.fo normal.fo normalex.fo pdfoutline.fo
readme.fo simple.fo table.fo tableunits.fo
textdeko.fo
   docs/examples/footnotes columns.fo simple.fo
   docs/examples/keeps_and_breaks columnlevel1.fo pagelevel1.fo
pagelevel2.fo pagelevel3.fo pagelevel4.fo
   docs/examples/markers glossary.xml glossary.xsl hide.fo
   docs/examples/pagination allregions.fo basic1.fo basic2.fo
franklin_2pageseqs.fo franklin_alt.fo
franklin_rep.fo franklin_rep_max_repeats.fo
franklin_rep_max_repeats_expl.fo
franklin_rep_max_repeats_nl.fo
   docs/examples/region_body simplecol.fo simplecol2.fo
simplecol3.fo simplecol4.fo
   docs/examples/svg boxes.svg embedding.fo external.fo
multi.svg ref.svg view.svg
   docs/examples/tables background.fo borders.fo break.fo
headfoot.fo keep.fo omit.fo space.fo
widowsorphans.fo
  Log:
  Move over to examples/fo

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

cvs commit: xml-fop/docs/foschema fop.xsd schema2completion.xsl schema2dtd.xsl

[jeremias]

jeremias2003/01/29 08:01:44

  Removed: docs/foschema fop.xsd schema2completion.xsl schema2dtd.xsl
  Log:
  Move over to src/foschema

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

Re: docs/xslfoRef.xml

[Jeremias Maerki]

Cool, thanks.

On 13.01.2003 19:57:46 J.Pietschmann wrote:
> Jeremias Maerki wrote:
> > There's a xslfoRef.xml containing a "small reference for XSL-FO". An
> > XSLT exists for converting the reference to FO. It still reflects the
> > Candidate Recommendation, so it is outdated. Can I simply delete it or
> > should I move it somewhere, too?
> 
> Keep it for the moment. I think I'll xdocify and update it
> once I get a bit of time to spare.


Jeremias Maerki


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

Re: docs/xslfoRef.xml

[J.Pietschmann]

Jeremias Maerki wrote:

There's a xslfoRef.xml containing a "small reference for XSL-FO". An
XSLT exists for converting the reference to FO. It still reflects the
Candidate Recommendation, so it is outdated. Can I simply delete it or
should I move it somewhere, too?


Keep it for the moment. I think I'll xdocify and update it
once I get a bit of time to spare.

J.Pietschmann



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

cvs commit: xml-fop/docs/graphics fop.jpg linux.bmp listgeometry.gif page.gif xml_fax.tif xml_feather.gif xml_feather_transparent.gif

[jeremias]

jeremias2003/01/13 10:31:33

  Removed: docs/graphics Tag: fop-0_20_2-maintain fop.jpg linux.bmp
listgeometry.gif page.gif xml_fax.tif
xml_feather.gif xml_feather_transparent.gif
  Log:
  Moved over to examples/fo/graphics

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

cvs commit: xml-fop/docs/examples/tables background.fo borders.fo break.fo headfoot.fo keep.fo omit.fo space.fo widowsorphans.fo

[jeremias]

jeremias2003/01/13 10:29:13

  Removed: docs/examples Tag: fop-0_20_2-maintain .cvsignore build.xml
results.html runtests.bat runtests.sh
   docs/examples/advanced Tag: fop-0_20_2-maintain cid-fonts.fo
cid-fonts.pdf giro.fo test_ja.fo
   docs/examples/fo Tag: fop-0_20_2-maintain bgimage.fo
border.fo bordershorthand.fo character.fo
contlabel.fo corresprop.fo extensive.fo fonts.fo
hyphen.fo images.fo inhprop.fo instream.fo
leader.fo link.fo list.fo newlinktest.fo normal.fo
normalex.fo pdfoutline.fo readme.fo simple.fo
table.fo tableunits.fo textdeko.fo
   docs/examples/footnotes Tag: fop-0_20_2-maintain columns.fo
simple.fo
   docs/examples/keeps_and_breaks Tag: fop-0_20_2-maintain
columnlevel1.fo pagelevel1.fo pagelevel2.fo
pagelevel3.fo pagelevel4.fo
   docs/examples/markers Tag: fop-0_20_2-maintain glossary.xml
glossary.xsl hide.fo
   docs/examples/pagination Tag: fop-0_20_2-maintain
allregions.fo basic1.fo basic2.fo
franklin_2pageseqs.fo franklin_alt.fo
franklin_rep.fo franklin_rep_max_repeats.fo
franklin_rep_max_repeats_expl.fo
franklin_rep_max_repeats_nl.fo
   docs/examples/region_body Tag: fop-0_20_2-maintain
simplecol.fo simplecol2.fo simplecol3.fo
simplecol4.fo
   docs/examples/svg Tag: fop-0_20_2-maintain boxes.svg
embedding.fo external.fo multi.svg ref.svg view.svg
   docs/examples/tables Tag: fop-0_20_2-maintain background.fo
borders.fo break.fo headfoot.fo keep.fo omit.fo
space.fo widowsorphans.fo
  Log:
  Moved over to examples/fo

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

docs/xslfoRef.xml

[Jeremias Maerki]

Hi there

There's a xslfoRef.xml containing a "small reference for XSL-FO". An
XSLT exists for converting the reference to FO. It still reflects the
Candidate Recommendation, so it is outdated. Can I simply delete it or
should I move it somewhere, too?

It's the only thing left in the docs directory when I'm finished moving
docs/examples to examples/fo.


Jeremias Maerki


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

cvs commit: xml-fop/docs/foschema fop.xsd fop4f.xsd schema2completion.xsl schema2dtd.xsl

[jeremias]

jeremias2003/01/13 08:36:40

  Removed: docs/foschema Tag: fop-0_20_2-maintain fop.xsd fop4f.xsd
schema2completion.xsl schema2dtd.xsl
  Log:
  Moved over to src/foschema

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

cvs commit: xml-fop/docs/examples/svg external.fo

[chrisg]

chrisg  2003/01/08 17:10:48

  Modified:docs/examples/fo Tag: fop-0_20_2-maintain images.fo list.fo
   docs/examples/svg Tag: fop-0_20_2-maintain external.fo
  Log:
  corrected relative urls for external-graphic in examples
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.11.2.3  +5 -5  xml-fop/docs/examples/fo/images.fo
  
  Index: images.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/images.fo,v
  retrieving revision 1.11.2.2
  retrieving revision 1.11.2.3
  diff -u -r1.11.2.2 -r1.11.2.3
  --- images.fo 18 Nov 2002 14:37:45 -  1.11.2.2
  +++ images.fo 9 Jan 2003 01:10:47 -   1.11.2.3
  @@ -43,31 +43,31 @@
   
 A GIF image in FOP
 
  -
  +
 
   
   
 A transparent GIF image in 
FOP
 
  -
  +
 
   
   
 A JPEG image in FOP
 
  -
  +
 
   
   
 A BMP image in FOP
 
  -
  +
 
   
   
 A TIFF image in FOP (Only 
works with JAI!)
   
  -  
  +  
   
   
   
  
  
  
  1.6.4.5   +1 -1  xml-fop/docs/examples/fo/list.fo
  
  Index: list.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/list.fo,v
  retrieving revision 1.6.4.4
  retrieving revision 1.6.4.5
  diff -u -r1.6.4.4 -r1.6.4.5
  --- list.fo   30 Nov 2002 00:27:54 -  1.6.4.4
  +++ list.fo   9 Jan 2003 01:10:47 -   1.6.4.5
  @@ -225,7 +225,7 @@
  url: http://www.w3.org/TR/xsl/ -->
 
  -
  +
 
 
   
 
  -
  +
 
   
 
  -This svg document () is also obtained 
from
  +This svg document () is also obtained 
from
   an external file using the fo:external-graphic. It has another svg image inside and 
references
   part of another svg image.
 
  @@ -122,7 +122,7 @@
   
 
   This example is an svg from an external image:
  -
  +
   it has a viewbox that resizes the contents.
 
   
  
  
  

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

cvs commit: xml-fop/docs/examples/advanced giro.fo

[jeremias]

jeremias2003/01/04 07:11:59

  Modified:docs/examples/advanced Tag: fop-0_20_2-maintain giro.fo
  Log:
  Fixed a missing master-reference reported by Darrel Riekhof.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.1.2.2   +1 -1  xml-fop/docs/examples/advanced/giro.fo
  
  Index: giro.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/advanced/giro.fo,v
  retrieving revision 1.1.2.1
  retrieving revision 1.1.2.2
  diff -u -r1.1.2.1 -r1.1.2.2
  --- giro.fo   6 Dec 2001 21:28:18 -   1.1.2.1
  +++ giro.fo   4 Jan 2003 15:11:59 -   1.1.2.2
  @@ -934,7 +934,7 @@
TIFF logo and XSL FO table bar code
 
  
  -   
  +   
 

   
  
  
  

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

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

[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
  ===
  
  http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd";>
  
  
  
  

  Layout managers
  

  


  
Layout managers in FOP

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.


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.  


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.

  

  
  
  
  

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

cvs commit: xml-fop/docs/examples runtests.bat runtests.sh

[olegt]

olegt   2002/12/11 14:13:21

  Modified:.fop.bat
   docs/examples runtests.bat runtests.sh
  Log:
  Removed footprints of bsf.jar.
  
  Revision  ChangesPath
  1.8   +0 -1  xml-fop/fop.bat
  
  Index: fop.bat
  ===
  RCS file: /home/cvs/xml-fop/fop.bat,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- fop.bat   22 Nov 2002 18:07:13 -  1.7
  +++ fop.bat   11 Dec 2002 22:13:20 -  1.8
  @@ -7,7 +7,6 @@
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xalan-2.4.1.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\batik.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\avalon-framework-cvs-20020806.jar
  -set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\bsf.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\jimi-1.0.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\jai_core.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\jai_codec.jar
  
  
  
  1.13  +0 -1  xml-fop/docs/examples/runtests.bat
  
  Index: runtests.bat
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/runtests.bat,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- runtests.bat  22 Nov 2002 18:06:45 -  1.12
  +++ runtests.bat  11 Dec 2002 22:13:21 -  1.13
  @@ -14,7 +14,6 @@
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xalan-2.4.1.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\batik.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\avalon-framework-cvs-20020806.jar
  -set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\bsf.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\jimi-1.0.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\jai_core.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\jai_codec.jar
  
  
  
  1.10  +0 -1  xml-fop/docs/examples/runtests.sh
  
  Index: runtests.sh
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/runtests.sh,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- runtests.sh   22 Nov 2002 18:06:45 -  1.9
  +++ runtests.sh   11 Dec 2002 22:13:21 -  1.10
  @@ -20,7 +20,6 @@
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/xalan-2.4.1.jar
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/batik.jar
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/avalon-framework-cvs-20020806.jar
  -LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/bsf.jar
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/jimi-1.0.jar
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/jai_core.jar
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/jai_codec.jar
  
  
  

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

cvs commit: xml-fop/docs/examples runtests.sh runtests.bat

[olegt]

olegt   2002/12/10 14:28:03

  Modified:.Tag: fop-0_20_2-maintain fop.bat build.xml
   test Tag: fop-0_20_2-maintain createpdf.sh
   docs/examples Tag: fop-0_20_2-maintain runtests.sh
runtests.bat
  Log:
  Removed footprints of bsf.jar.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.4.2.8   +0 -1  xml-fop/fop.bat
  
  Index: fop.bat
  ===
  RCS file: /home/cvs/xml-fop/fop.bat,v
  retrieving revision 1.4.2.7
  retrieving revision 1.4.2.8
  diff -u -r1.4.2.7 -r1.4.2.8
  --- fop.bat   19 Nov 2002 13:42:55 -  1.4.2.7
  +++ fop.bat   10 Dec 2002 22:28:02 -  1.4.2.8
  @@ -7,7 +7,6 @@
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xalan-2.4.1.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\batik.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\avalon-framework-cvs-20020806.jar
  -set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\bsf.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\jimi-1.0.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\jai_core.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\jai_codec.jar
  
  
  
  1.44.2.33 +1 -7  xml-fop/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/xml-fop/build.xml,v
  retrieving revision 1.44.2.32
  retrieving revision 1.44.2.33
  diff -u -r1.44.2.32 -r1.44.2.33
  --- build.xml 10 Dec 2002 15:01:38 -  1.44.2.32
  +++ build.xml 10 Dec 2002 22:28:02 -  1.44.2.33
  @@ -39,13 +39,7 @@
   
   To make things easier for you, the Fop distribution contains a
   precompiled version of Ant and the build scripts take care of all the
  -classpath issues except the following:
  -
  -You need to have xerces.jar, xalan.jar and bsf.jar (comes with xalan) in 
  -your classpath. You can get those from http://xml.apache.org/xerces and 
  -http://xml.apache.org/xalan respectively.
  -
  -Additionaly you have to make sure, that the "JAVA_HOME" environment
  +classpath issues except the following: "JAVA_HOME" environment
   property should be set to match the JVM you want to use. That's it.
   
   
  
  
  
  No   revision
  
  
  No   revision
  
  
  1.4.2.4   +1 -1  xml-fop/test/createpdf.sh
  
  Index: createpdf.sh
  ===
  RCS file: /home/cvs/xml-fop/test/createpdf.sh,v
  retrieving revision 1.4.2.3
  retrieving revision 1.4.2.4
  diff -u -r1.4.2.3 -r1.4.2.4
  --- createpdf.sh  18 Nov 2002 14:37:47 -  1.4.2.3
  +++ createpdf.sh  10 Dec 2002 22:28:02 -  1.4.2.4
  @@ -2,7 +2,7 @@
   
   
   LIBDIR=../lib
  
-LOCALCLASSPATH=$LIBDIR/batik.jar:$LIBDIR/xercesImpl-2.0.1.jar:$LIBDIR/xalan-2.3.1.jar:$LIBDIR/xml-apis.jar:$LIBDIR/bsf.jar
  
+LOCALCLASSPATH=$LIBDIR/batik.jar:$LIBDIR/xercesImpl-2.0.1.jar:$LIBDIR/xalan-2.3.1.jar:$LIBDIR/xml-apis.jar
   
LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/jimi-1.0.jar:$LIBDIR/jai_core.jar:$LIBDIR/jai_codec.jar:$LIBDIR/avalon-framework-cvs-20020806.jar:$LIBDIR/logkit-1.0.jar
   
   $JAVA_HOME/bin/java -cp ../build/fop.jar:$LOCALCLASSPATH 
org.apache.fop.tools.TestConverter -pdf -b ./ basictests.xml
  
  
  
  No   revision
  
  
  No   revision
  
  
  1.8.2.10  +0 -1  xml-fop/docs/examples/runtests.sh
  
  Index: runtests.sh
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/runtests.sh,v
  retrieving revision 1.8.2.9
  retrieving revision 1.8.2.10
  diff -u -r1.8.2.9 -r1.8.2.10
  --- runtests.sh   19 Nov 2002 13:34:08 -  1.8.2.9
  +++ runtests.sh   10 Dec 2002 22:28:02 -  1.8.2.10
  @@ -33,7 +33,6 @@
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/xalan-2.4.1.jar
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/batik.jar
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/avalon-framework-cvs-20020806.jar
  -LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/bsf.jar
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/jimi-1.0.jar
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/jai_core.jar
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/jai_codec.jar
  
  
  
  1.11.2.10 +0 -1  xml-fop/docs/examples/runtests.bat
  
  Index: runtests.bat
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/runtests.bat,v
  retrieving revision 1.11.2.9
  retrieving revision 1.11.2.10
  diff -u -r1.11.2.9 -r1.11.2.10
  --- runtests.bat  19 Nov 2002 13:34:08 -  1.11.2.9
  +++ runtests.bat  10 Dec 2002 22:28:02 -  1.11.2.10
  @@ -14,7 +14,6 @@
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xalan-2.4.1.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\batik.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\avalon-framework-cvs-20020806.jar
  -set LOCALCLASSPATH

cvs commit: xml-fop/docs/design/alt.design AbsolutePosition.dia PropNames.dia PropertyConsts.dia Properties.dia VerticalAlign.dia

[pbwest]

pbwest  2002/12/09 15:41:00

  Removed: docs/design/alt.design AbsolutePosition.dia PropNames.dia
PropertyConsts.dia Properties.dia VerticalAlign.dia
  Log:
  No longer required.

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

cvs commit: xml-fop/docs/xml-docs/data logo.svg track.svg

[keiron]

keiron  2002/12/09 02:52:27

  Modified:docs/xml-docs/data logo.svg track.svg
  Log:
  updated
  
  Revision  ChangesPath
  1.3   +11 -11xml-fop/docs/xml-docs/data/logo.svg
  
  Index: logo.svg
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/data/logo.svg,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- logo.svg  30 Nov 2002 01:14:51 -  1.2
  +++ logo.svg  9 Dec 2002 10:52:27 -   1.3
  @@ -1,7 +1,7 @@
   
   http://www.w3.org/TR/2000/CR-SVG-20001102/DTD/svg-20001102.dtd";>
  -
  +
   
   
   
  @@ -23,11 +23,11 @@
   
   
   
  -
  -
  -
  -
  -
  +
  +
  +
  +
  +
   
   
   
  @@ -59,12 +59,12 @@
   
   
   
  -
  -
  +
  +
   
  -
  -
  -
  +
  +
  +
   
   
   
  
  
  
  1.2   +8 -4  xml-fop/docs/xml-docs/data/track.svg
  
  Index: track.svg
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/data/track.svg,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- track.svg 12 Jun 2002 14:12:19 -  1.1
  +++ track.svg 9 Dec 2002 10:52:27 -   1.2
  @@ -44,11 +44,15 @@
   FOP 0.20.3
   4th March 2002
   
  -
  -FOP 0.20.4
  -12th June 2002
  +
  +FOP 0.20.4
  +12th June 2002
   
  -
  +
  +FOP 0.20.5
  +TBA
  +
  +
   
   
   redesign
  
  
  

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

cvs commit: xml-fop/docs/examples/embedding FopPrintServlet.java FopServlet.java fop.war

[chrisg]

chrisg  2002/12/08 20:04:34

  Removed: docs/examples/embedding Tag: fop-0_20_2-maintain
FopPrintServlet.java FopServlet.java fop.war
  Log:
  Removed old Servlet example (new is in contrib/servlet)

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

cvs commit: xml-fop/docs/foschema fop4.xsd fop4f.xsd

[vmote]

vmote   2002/12/08 15:18:25

  Removed: docs/foschema fop4.xsd fop4f.xsd
  Log:
  Remove docs/foschema/fop4.xsd and fop4f.xsd, which are replaced with
  fop.xsd.

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

cvs commit: xml-fop/docs/foschema fop.xsd

[vmote]

vmote   2002/12/08 15:11:56

  Modified:docs/foschema fop.xsd
  Log:
  This revision corresponds to fop4.xsd, revision 1.2, checked in by pbwest.
  Original log message:
Updated with fop4g.xsd, with s replaced by spaces at tabstops of 2.
  
  Revision  ChangesPath
  1.3   +14 -10xml-fop/docs/foschema/fop.xsd
  
  Index: fop.xsd
  ===
  RCS file: /home/cvs/xml-fop/docs/foschema/fop.xsd,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- fop.xsd   8 Dec 2002 23:03:34 -   1.2
  +++ fop.xsd   8 Dec 2002 23:11:56 -   1.3
  @@ -81,6 +81,10 @@
 This declaration assumes that all  elements must come 
before other stuff, 
 which is not required by spec, but I cannot see any way to express such 
constraints in schema, 
 one could use  instead of , but this way we lose 
control over (color-profile)+ constraint.
  +  
  +  VCP 21-Oct-2002 
  +Updated all (px|pt|mm|cm|in|em) to (px|pt|mm|cm|in|em|%) to allow 
percentage types.
  +Updated the restriction base of those types from NMTOKEN to string
   
   
 
  @@ -785,8 +789,8 @@
   
 
   
  -
  -  
  +
  +  
   
 
 
  @@ -831,7 +835,7 @@
 
   
   
  -  
  +  
   
 
 
  @@ -865,7 +869,7 @@
 
   
   
  -  
  +  
   
 
 
  @@ -1051,7 +1055,7 @@
 length_Type{1,2}
   
 
  -  
  +  
   
 
 
  @@ -1734,13 +1738,13 @@
   
 
 
  -
  -  
  +
  +  
   
 
 
  -
  -  
  +
  +  
   
 
 
  @@ -2917,7 +2921,7 @@
 
   
   
  -  
  +  
   
 
 
  
  
  

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

cvs commit: xml-fop/docs/foschema fop.xsd

[vmote]

vmote   2002/12/07 12:31:30

  Modified:docs/foschema Tag: 1.1.0 fop.xsd
  Log:
  .
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.1.0.1   +0 -0  xml-fop/docs/foschema/fop.xsd
  
  Index: fop.xsd
  ===
  RCS file: /home/cvs/xml-fop/docs/foschema/fop.xsd,v
  retrieving revision 1.1
  retrieving revision 1.1.0.1
  diff -u -r1.1 -r1.1.0.1
  
  
  

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

Re: docs for maintenance release

[Christian Geisert]

Jeremias Maerki wrote:

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


Yes, I'm not sure if automatic merging would work and I don't think 
there will be a lot of changes.

Christian



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

cvs commit: xml-fop/docs/design/understanding area_tree.xml book.xml fo_tree.xml handling_attributes.xml images.xml layout_managers.xml layout_process.xml pdf_library.xml properties.xml renderers.xml status.xml svg.xml understanding.xml xml_parsing.xml

[keiron]

keiron  2002/12/02 04:59:12

  Removed: docs/design float.svg page.svg
   docs/design/alt.design AbsolutePosition.png
AbsolutePosition.png.xml BorderCommonStyle.png
BorderCommonStyle.png.xml PropNames.png
PropNames.png.xml Properties.png Properties.png.xml
PropertyClasses.png PropertyConsts.png
PropertyConsts.png.xml PropertyStaticsOverview.png
SAXParsing.png VerticalAlign.png
VerticalAlign.png.xml XML-event-buffer.png
XMLEventQueue.png alt.properties.xml
block-stacking-constraints.png
block-stacking-keeps.png block-stacking.png
book.xml classes-overview.xml
compound-properties.xml coroutines.png
coroutines.xml footnotes.xml
galley-preprocessing.png galleys.xml
initial-column-values.png intro.xml keeps.xml
line-area-5.png line-area-6.png
parserPersistence.png processPlumbing.png
properties-classes.xml
property-super-classes-full.png
propertyExpressions.xml spaces.xml traits.xml
user-agent-refs.xml xml-parsing.xml
xmlevent-queue.png
   docs/design/understanding area_tree.xml book.xml fo_tree.xml
handling_attributes.xml images.xml
layout_managers.xml layout_process.xml
pdf_library.xml properties.xml renderers.xml
status.xml svg.xml understanding.xml
xml_parsing.xml
  Log:
  no longer needed, moved to src/documentation/content/xdocs/design/

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

cvs commit: xml-fop/docs/examples/tables background.fo borders.fo break.fo headfoot.fo keep.fo omit.fo space.fo widowsorphans.fo

[olegt]

olegt   2002/11/29 16:27:56

  Modified:docs/examples/fo Tag: fop-0_20_2-maintain bordershorthand.fo
character.fo contlabel.fo corresprop.fo fonts.fo
hyphen.fo inhprop.fo link.fo list.fo normal.fo
normalex.fo pdfoutline.fo readme.fo simple.fo
table.fo textdeko.fo
   docs/examples/markers Tag: fop-0_20_2-maintain hide.fo
   docs/examples/pagination Tag: fop-0_20_2-maintain basic1.fo
basic2.fo
   docs/examples/svg Tag: fop-0_20_2-maintain embedding.fo
external.fo
   docs/examples/tables Tag: fop-0_20_2-maintain background.fo
borders.fo break.fo headfoot.fo keep.fo omit.fo
space.fo widowsorphans.fo
  Log:
  Fixed overlaping regions.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.1.2.2   +2 -2  xml-fop/docs/examples/fo/bordershorthand.fo
  
  Index: bordershorthand.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/bordershorthand.fo,v
  retrieving revision 1.1.2.1
  retrieving revision 1.1.2.2
  diff -u -r1.1.2.1 -r1.1.2.2
  --- bordershorthand.fo6 Dec 2001 21:28:18 -   1.1.2.1
  +++ bordershorthand.fo30 Nov 2002 00:27:53 -  1.1.2.2
  @@ -28,7 +28,7 @@
 margin-bottom="2cm" 
 margin-left="2.0cm + 0.5cm" 
 margin-right="(5cm * 1cm) div 2cm">
  -  
  +  
 
 
   
  @@ -41,7 +41,7 @@
 margin-bottom="round(2.4) * 1cm"
 margin-left="2.5 * 1cm" 
 margin-right="5.5cm - 3cm">
  -  
  +  
     
 
   
  
  
  
  1.1.4.2   +1 -1  xml-fop/docs/examples/fo/character.fo
  
  Index: character.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/character.fo,v
  retrieving revision 1.1.4.1
  retrieving revision 1.1.4.2
  diff -u -r1.1.4.1 -r1.1.4.2
  --- character.fo  6 Dec 2001 21:28:18 -   1.1.4.1
  +++ character.fo  30 Nov 2002 00:27:53 -  1.1.4.2
  @@ -25,7 +25,7 @@
 margin-bottom="2cm" 
 margin-left="2.5cm" 
 margin-right="2.5cm">
  -  
  +  
 
 
   
  
  
  
  1.1.2.2   +1 -1  xml-fop/docs/examples/fo/Attic/contlabel.fo
  
  Index: contlabel.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/Attic/contlabel.fo,v
  retrieving revision 1.1.2.1
  retrieving revision 1.1.2.2
  diff -u -r1.1.2.1 -r1.1.2.2
  --- contlabel.fo  24 Nov 2002 22:22:47 -  1.1.2.1
  +++ contlabel.fo  30 Nov 2002 00:27:53 -  1.1.2.2
  @@ -10,8 +10,8 @@
page-width="21cm"
page-height="29.7cm"
master-name="first">
  -  
 
  +  
 
   
 
  
  
  
  1.1.4.2   +2 -2  xml-fop/docs/examples/fo/corresprop.fo
  
  Index: corresprop.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/corresprop.fo,v
  retrieving revision 1.1.4.1
  retrieving revision 1.1.4.2
  diff -u -r1.1.4.1 -r1.1.4.2
  --- corresprop.fo 6 Dec 2001 21:28:18 -   1.1.4.1
  +++ corresprop.fo 30 Nov 2002 00:27:53 -  1.1.4.2
  @@ -28,7 +28,7 @@
 margin-bottom="2cm" 
 margin-left="2.0cm + 0.5cm" 
 margin-right="(5cm * 1cm) div 2cm">
  -  
  +  
 
 
   
  @@ -41,7 +41,7 @@
 margin-bottom="round(2.4) * 1cm"
 margin-left="2.5 * 1cm" 
 margin-right="5.5cm - 3cm">
  -  
  +  
 
     
   
  
  
  
  1.7.4.4   +1 -1  xml-fop/docs/examples/fo/fonts.fo
  
  Index: fonts.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/fonts.fo,v
  retrieving revision 1.7.4.3
  retrieving revision 1.7.4.4
  diff -u -r1.7.4.3 -r1.7.4.4
  --- fonts.fo  26 Jun 2002 20:34:19 -  1.7.4.3
  +++ fonts.fo  30 Nov 2002 00:27:53 -  1.7.4.4
  @@ -11,7 +11,7 @@
  margin-bottom="2cm" 
  margin-left="2.5cm" 
  margin-right="2.5cm">
  -      
  +  
 
 
   
  
  
  
  1.4.2.4   +1 -1  xml-fop/docs/examples/fo/hyphen.fo
  
  Index: hyphen.fo
  =

RE: docs for maintenance release

[Victor Mote]

Peter B. West wrote:

> 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.

Actually, there is no need for this. All we want here is a way to get the
documentation built for the maintenance release. However, even if we wanted
to use this on a regular basis in the maintenance branch, there is no need
to branch these files -- they essentially are shared between the trunk and
the maintenance branch.

Victor Mote


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

Re: docs for maintenance release

[Keiron Liddle]

On Thu, 2002-11-28 at 17:33, Christian Geisert wrote:
> 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?

There is an svg document in docs/xml-docs/data/.
Once the svg2png works then we could use it directly.

> Christian



-
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: 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: 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]

cvs commit: xml-fop/docs/examples/fo border.fo hyphen.fo leader.fo newlinktest.fo pdfoutline.fo readme.fo table.fo tableunits.fo textdeko.fo

[chrisg]

chrisg  2002/11/25 03:56:53

  Modified:.Tag: fop-0_20_2-maintain CHANGES
   docs/examples/fo Tag: fop-0_20_2-maintain border.fo
hyphen.fo leader.fo newlinktest.fo pdfoutline.fo
readme.fo table.fo tableunits.fo textdeko.fo
  Log:
  Updated examples/fo files to remove all errors and warnings during build
  Submitted by: Manuel Mall <[EMAIL PROTECTED]> (see bug #13867)
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.10.2.30 +2 -0  xml-fop/CHANGES
  
  Index: CHANGES
  ===
  RCS file: /home/cvs/xml-fop/CHANGES,v
  retrieving revision 1.10.2.29
  retrieving revision 1.10.2.30
  diff -u -r1.10.2.29 -r1.10.2.30
  --- CHANGES   22 Nov 2002 15:10:44 -  1.10.2.29
  +++ CHANGES   25 Nov 2002 11:56:51 -  1.10.2.30
  @@ -1,6 +1,8 @@
   ==
   Done since 0.20.4 release
   
  +- Updated examples/fo files to remove all errors and warnings during build
  +  Submitted by: Manuel Mall <[EMAIL PROTECTED]> (see bug #13867)
   - Perfomance tuning (reduced object creation etc.) (see bug #14103)
 Submitted by: Henrik Olsson <[EMAIL PROTECTED]> 
   - Update to Xerces 2.2.1 (Jeremias Maerki)
  
  
  
  No   revision
  
  
  No   revision
  
  
  1.8.2.2   +46 -47xml-fop/docs/examples/fo/border.fo
  
  Index: border.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/border.fo,v
  retrieving revision 1.8.2.1
  retrieving revision 1.8.2.2
  diff -u -r1.8.2.1 -r1.8.2.2
  --- border.fo 6 Dec 2001 21:28:18 -   1.8.2.1
  +++ border.fo 25 Nov 2002 11:56:51 -  1.8.2.2
  @@ -1,75 +1,74 @@
   http://www.w3.org/1999/XSL/Format";>
   
   
  +margin-right="0.5cm" margin-left="0.5cm" margin-bottom="0.5cm" 
margin-top="0.75cm"
  +page-width="21cm" page-height="29.7cm" master-name="first">
   
   
   
  +margin-right="2.5cm" margin-left="2.5cm" margin-bottom="2cm" 
margin-top="1cm"
  +page-width="21cm" page-height="29.7cm" master-name="rest">
   
   
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  +
  +
  +
  +
  +
  +
  +
  +
  +
   
   
   
   
   
  - PX7.net
  - 
  +PX7.net
  +
   
  - 44 Liberty St
  - 
  +44 Liberty St
  +
   
  - Newburyport, MA 01950
  - 
  +Newburyport, MA 01950
  +
   
  - 978-462-1152
  - 
  +978-462-1152
  +
   
   
   
  -Sales Receipt
  - 
  +   Sales Receipt
  +
   
   
   
   
  -DATE
  - 
  +   DATE
  +
   
   
   
  - 01/01/2000
  - 
  +01/01/2000
  +
   
   
   
  - SALE #
  - 
  +SALE #
  +
   
   
   
  - 1
  - 
  +1
  +
   
  -
   
   
   
  - SOLD TO
  - 
  +SOLD TO
  +
   
   
   
  @@ -77,8 +76,8 @@
   
   
   
  -   

cvs commit: xml-fop/docs/examples/fo contlabel.fo

[klease]

klease  2002/11/24 14:22:47

  Added:   docs/examples/fo Tag: fop-0_20_2-maintain contlabel.fo
  Log:
  Example of using continued-label extension element
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.1.2.1   +293 -0xml-fop/docs/examples/fo/Attic/contlabel.fo
  
  
  
  

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

cvs commit: xml-fop/docs/examples runtests.sh runtests.bat

[jeremias]

jeremias2002/11/22 10:06:45

  Modified:docs/examples runtests.sh runtests.bat
  Log:
  Adjusted to new JARs
  
  Revision  ChangesPath
  1.9   +13 -1 xml-fop/docs/examples/runtests.sh
  
  Index: runtests.sh
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/runtests.sh,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- runtests.sh   20 Aug 2001 16:16:46 -  1.8
  +++ runtests.sh   22 Nov 2002 18:06:45 -  1.9
  @@ -13,7 +13,19 @@
 exit 1
   fi
   LIBDIR=../../lib
  
-LOCALCLASSPATH=$JAVA_HOME/lib/tools.jar:$JAVA_HOME/lib/classes.zip:$LIBDIR/ant.jar:$LIBDIR/batik.jar:$LIBDIR/buildtools.jar:$LIBDIR/xerces-1.2.3.jar:$LIBDIR/xalan-2.0.0.jar:$LIBDIR/xalanj1compat.jar:$LIBDIR/bsf.jar:$LIBDIR/avalon-framework-4.0.jar:$LIBDIR/logkit-1.0b4.jar:$LIBDIR/jimi-1.0.jar:$LIBDIR/../build/fop.jar
  +LOCALCLASSPATH=$JAVA_HOME/lib/tools.jar:$JAVA_HOME/lib/classes.zip
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/ant.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/xml-apis.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/xercesImpl-2.2.1.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/xalan-2.4.1.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/batik.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/avalon-framework-cvs-20020806.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/bsf.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/jimi-1.0.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/jai_core.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/jai_codec.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/../build/fop.jar
  +
   ANT_HOME=$LIBDIR
   
   echo Building with classpath $CLASSPATH:$LOCALCLASSPATH
  
  
  
  1.12  +13 -2 xml-fop/docs/examples/runtests.bat
  
  Index: runtests.bat
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/runtests.bat,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- runtests.bat  20 Aug 2001 16:16:46 -  1.11
  +++ runtests.bat  22 Nov 2002 18:06:45 -  1.12
  @@ -1,13 +1,24 @@
   @echo off
   
  -echo Fop Test 
  +echo Fop Test
   echo 
   
   if "%JAVA_HOME%" == "" goto error
   
   
   set LIBDIR=..\..\lib
  -set 
LOCALCLASSPATH=%JAVA_HOME%\lib\tools.jar;%JAVA_HOME%\lib\classes.zip;%LIBDIR%\ant.jar;%LIBDIR%\batik.jar;%LIBDIR%\buildtools.jar;%LIBDIR%\xerces-1.2.3.jar;%LIBDIR%\xalan-2.0.0.jar;%LIBDIR%\xalanj1compat.jar;%LIBDIR%\bsf.jar;%LIBDIR%\avalon-framework-4.0.jar;%LIBDIR%\logkit-1.0b4.jar;%LIBDIR%\jimi-1.0.jar;%LIBDIR%\..\build\fop.jar
  +set LOCALCLASSPATH=%JAVA_HOME%\lib\tools.jar;%JAVA_HOME%\lib\classes.zip
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\ant.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xml-apis.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xercesImpl-2.2.1.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xalan-2.4.1.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\batik.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\avalon-framework-cvs-20020806.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\bsf.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\jimi-1.0.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\jai_core.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\jai_codec.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\..\build\fop.jar
   set ANT_HOME=%LIBDIR%
   
   echo Starting Tests ...
  
  
  

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

DO NOT REPLY [Bug 4695] - Fop v0.20.1: docs/examples/embedding/web.xml is invalid

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4695>.
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=4695

Fop v0.20.1: docs/examples/embedding/web.xml is invalid

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2002-11-21 19:45 ---
This web.xml is obsolete. New (and valid) one is now at contrib/servlet/conf.

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

cvs commit: xml-fop/docs/examples runtests.sh runtests.bat

[jeremias]

jeremias2002/11/19 05:34:08

  Modified:docs/examples Tag: fop-0_20_2-maintain runtests.sh
runtests.bat
  Log:
  Adjust classpath
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.8.2.9   +1 -1  xml-fop/docs/examples/runtests.sh
  
  Index: runtests.sh
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/runtests.sh,v
  retrieving revision 1.8.2.8
  retrieving revision 1.8.2.9
  diff -u -r1.8.2.8 -r1.8.2.9
  --- runtests.sh   18 Nov 2002 14:37:45 -  1.8.2.8
  +++ runtests.sh   19 Nov 2002 13:34:08 -  1.8.2.9
  @@ -29,7 +29,7 @@
   LOCALCLASSPATH=$JAVA_HOME/lib/tools.jar:$JAVA_HOME/lib/classes.zip
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/ant-1.5.1.jar
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/xml-apis.jar
  -LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/xercesImpl-2.2.0.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/xercesImpl-2.2.1.jar
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/xalan-2.4.1.jar
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/batik.jar
   LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/avalon-framework-cvs-20020806.jar
  
  
  
  1.11.2.9  +1 -1  xml-fop/docs/examples/runtests.bat
  
  Index: runtests.bat
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/runtests.bat,v
  retrieving revision 1.11.2.8
  retrieving revision 1.11.2.9
  diff -u -r1.11.2.8 -r1.11.2.9
  --- runtests.bat  18 Nov 2002 14:37:45 -  1.11.2.8
  +++ runtests.bat  19 Nov 2002 13:34:08 -  1.11.2.9
  @@ -10,7 +10,7 @@
   set LOCALCLASSPATH=%JAVA_HOME%\lib\tools.jar;%JAVA_HOME%\lib\classes.zip
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\ant-1.5.1.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xml-apis.jar
  -set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xercesImpl-2.2.0.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xercesImpl-2.2.1.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xalan-2.4.1.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\batik.jar
   set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\avalon-framework-cvs-20020806.jar
  
  
  

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

cvs commit: xml-fop/docs/examples runtests.sh runtests.bat

[jeremias]

jeremias2002/11/11 02:19:27

  Modified:docs/examples Tag: fop-0_20_2-maintain runtests.sh
runtests.bat
  Log:
  Updated and improved readability of classpath
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.8.2.7   +11 -1 xml-fop/docs/examples/runtests.sh
  
  Index: runtests.sh
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/runtests.sh,v
  retrieving revision 1.8.2.6
  retrieving revision 1.8.2.7
  diff -u -r1.8.2.6 -r1.8.2.7
  --- runtests.sh   7 Aug 2002 10:29:03 -   1.8.2.6
  +++ runtests.sh   11 Nov 2002 10:19:27 -  1.8.2.7
  @@ -26,7 +26,17 @@
   
   
   LIBDIR=../../lib
  
-LOCALCLASSPATH=$JAVA_HOME/lib/tools.jar:$JAVA_HOME/lib/classes.zip:$LIBDIR/ant-1.4.1.jar:$LIBDIR/batik.jar:$LIBDIR/buildtools.jar:$LIBDIR/xercesImpl-2.0.1.jar:$LIBDIR/xml-apis.jar:$LIBDIR/xalan-2.3.1.jar:$LIBDIR/bsf.jar:$LIBDIR/avalon-framework-cvs-20020806.jar:$LIBDIR/jimi-1.0.jar:$LIBDIR/../build/fop.jar
  +LOCALCLASSPATH=$JAVA_HOME/lib/tools.jar:$JAVA_HOME/lib/classes.zip
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/ant-1.5.1.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/xml-apis.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/xercesImpl-2.2.0.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/xalan-2.4.1.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/batik.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/avalon-framework-cvs-20020806.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/bsf.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/jimi-1.0.jar
  +LOCALCLASSPATH=$LOCALCLASSPATH:$LIBDIR/../build/fop.jar
  +
   ANT_HOME=$LIBDIR
   
   # For Cygwin, switch paths to Windows format before running java
  
  
  
  1.11.2.7  +10 -1 xml-fop/docs/examples/runtests.bat
  
  Index: runtests.bat
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/runtests.bat,v
  retrieving revision 1.11.2.6
  retrieving revision 1.11.2.7
  diff -u -r1.11.2.6 -r1.11.2.7
  --- runtests.bat  7 Aug 2002 10:29:03 -   1.11.2.6
  +++ runtests.bat  11 Nov 2002 10:19:27 -  1.11.2.7
  @@ -7,7 +7,16 @@
   
   
   set LIBDIR=..\..\lib
  -set 
LOCALCLASSPATH=%JAVA_HOME%\lib\tools.jar;%JAVA_HOME%\lib\classes.zip;%LIBDIR%\ant-1.4.1.jar;%LIBDIR%\batik.jar;%LIBDIR%\buildtools.jar;%LIBDIR%\xercesImpl-2.0.1.jar;%LIBDIR%\xml-apis.jar;%LIBDIR%\xalan-2.3.1.jar;%LIBDIR%\bsf.jar;%LIBDIR%\avalon-framework-cvs-20020806.jar;%LIBDIR%\jimi-1.0.jar;%LIBDIR%\..\build\fop.jar
  +set LOCALCLASSPATH=%JAVA_HOME%\lib\tools.jar;%JAVA_HOME%\lib\classes.zip
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\ant-1.5.1.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xml-apis.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xercesImpl-2.2.0.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xalan-2.4.1.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\batik.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\avalon-framework-cvs-20020806.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\bsf.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\jimi-1.0.jar
  +set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\..\build\fop.jar
   set ANT_HOME=%LIBDIR%
   
   echo Starting Tests ...
  
  
  

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

cvs commit: xml-fop/docs/design architecture.xml areas.xml book.xml breakpos.xml embedding.xml extending.xml fotree.xml intro.xml layout.xml optimise.xml properties.xml renderers.xml status.xml useragent.xml

[keiron]

keiron  2002/11/11 01:23:48

  Removed: docs/design architecture.xml areas.xml book.xml breakpos.xml
embedding.xml extending.xml fotree.xml intro.xml
layout.xml optimise.xml properties.xml
renderers.xml status.xml useragent.xml
  Log:
  more to new docs

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

cvs commit: xml-fop/docs/xml-docs/fop bugs.xml compiling.xml configuration.xml document.jpg download.xml embedding.xml examples.xml extensions.xml faq.xml fonts.xml gethelp.xml implemented.xml involved.xml layout.jpg license.xml limitations.xml news.xml output.xml readme.xml relnotes.xml resources.xml running.xml status.xml svg.xml testing.xml title.jpg todo.xml track.png

[keiron]

keiron  2002/11/11 01:22:37

  Removed: docs/xml-docs/fop bugs.xml compiling.xml configuration.xml
document.jpg download.xml embedding.xml
examples.xml extensions.xml faq.xml fonts.xml
gethelp.xml implemented.xml involved.xml layout.jpg
license.xml limitations.xml news.xml output.xml
readme.xml relnotes.xml resources.xml running.xml
status.xml svg.xml testing.xml title.jpg todo.xml
track.png
  Log:
  moved to new docs

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

cvs commit: xml-fop/docs/examples/fo extensive.fo leader.fo

[keiron]

keiron  2002/11/04 08:31:20

  Modified:docs/examples/fo extensive.fo leader.fo
  Log:
  improved examples a bit
  
  Revision  ChangesPath
  1.17  +8 -6  xml-fop/docs/examples/fo/extensive.fo
  
  Index: extensive.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/extensive.fo,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- extensive.fo  11 Dec 2001 12:08:28 -  1.16
  +++ extensive.fo  4 Nov 2002 16:31:20 -   1.17
  @@ -117,18 +117,20 @@
   Thisisdefault!
   Thisis
false!
   Thisistrue!
  - 
  -
  --->
  +]]>
  +
 Embedded SVG
 
   
  
  
  
  1.11  +25 -0 xml-fop/docs/examples/fo/leader.fo
  
  Index: leader.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/leader.fo,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- leader.fo 17 Sep 2002 07:32:10 -  1.10
  +++ leader.fo 4 Nov 2002 16:31:20 -   1.11
  @@ -756,6 +756,31 @@
   
   
 
  +
  +  Mixed:
  +
  +abc
  +
  +http://www.w3.org/2000/svg"; width="10" height="10">
  +
  +
  +
  +
  +
  +  
  +
  +  Mixed:
  +
  +abc
  +
  +http://www.w3.org/2000/svg"; width="10" height="10">
  +
  +
  +
  +
  +def
  +
  +  
   
 
   
  
  
  

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

cvs commit: xml-fop/docs/xml-docs/skins/xml.apache.org/resources script.js

[keiron]

keiron  2002/10/28 01:09:19

  Removed: docs/xml-docs/skins/xml.apache.org/resources script.js
  Log:
  no longer needed

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

RE: location of docs

[Keiron Liddle]

On Fri, 2002-10-25 at 16:49, Victor Mote wrote:
> Joerg is probably the key person to answer this, but I would like to throw
> in 2 cents worth. First, AFAIK, all of our current documentation flows out
> of XML files. If this is not totally true (and it may not be), then it
> probably should be (I think they call it "eating your own dog food"). So,
> docs/xml-docs seems redundant. Perhaps a concept of sources and output would
> be helpful here. Second, one of my goals with the doc is to explicitly
> delineate between user doc and developer doc, so that we can generate
> manuals and web-site areas that are appropriate for each -- specifically to
> keep developer issues out of the user doc. I have been treating the
> documents in docs/xml-docs/design as being developer doc, although there are
> a few documents in the docs/xml-docs/fop directory that are
> developer-oriented as well. I think it would be helpful to have our source
> XML documents organized around that concept as well.

Thanks for the ideas.
I have had a look around and other projects us src/documentation for the
docs, so I will put them in their. Keep it consistent.
I will commit the files and you will be able to see what forrest does so
then you will see how it fits together. Essentially it goes like so:
- docs are in src/documentation (can be somewhere else)
- settings are specified in forrest.properties for location of docs,
sitemap etc.
- you setup an installation of ant+forrest
- run "forrest" from the xml-fop directory
- the docs are converted across to the build/site directory

> My recommended structure for the docs directory is as follows:
> 
> source
> source/dev   See note 1
> source/user
> buildSee note 2
> build/pdf
> build/html
> transient (or temp)  See note 3
> stylesheet
> (the other directories there now are ok -- graphics, examples, etc.)

Forrest specifies many of these things, try it out and see how it works.
You need to get forrest cvs then do build dist. Follow the instructions.

> Note 1 -- for stuff currently in "design" + the documents you are asking
> about and the other developer documents. In my mind "design" is a subset of
> "dev". It might be useful to have "design" as a subdirectory under "dev".

I was thinking of dev as in the user+design documentation of the current
fop development. This is on a tab. Then the design documentation (which
only appplies to the development) is a sub directory thing from the dev
tab menu.

> Note 2 -- perhaps this should be in xml-fop/build/docs instead. It is
> important to have this be in a "build" or "output" directory so that no one
> is tempted to, for example, edit the html files directly

see above

> Note 3 -- for transient transforms when doing builds, including the fo file.
> The build could probably delete the contents, but sometimes it is nice to be
> able to see the intermediate results.

Thats forrest internals...

> All of this, of course, is contingent on Forrest requirements.
> 
> Sorry -- you asked a pretty simple question that was probably directed at
> Joerg. I have been trying to document (and fix where possible) these
> annoyances as they come up, hoping to use my still-mostly-newbie perspective
> to lower the cost of bringing new newbies (??) on board.

I just want to get things in place so that I can get some information
down and let others dive in.



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

RE: location of docs

[Victor Mote]

Keiron Liddle wrote:

> Where will the docs be located.
>
> I am writing/updating some docs for fop development and was wondering
> where I could put the docs.
>
> maybe docs/xml-docs as the base?

Joerg is probably the key person to answer this, but I would like to throw
in 2 cents worth. First, AFAIK, all of our current documentation flows out
of XML files. If this is not totally true (and it may not be), then it
probably should be (I think they call it "eating your own dog food"). So,
docs/xml-docs seems redundant. Perhaps a concept of sources and output would
be helpful here. Second, one of my goals with the doc is to explicitly
delineate between user doc and developer doc, so that we can generate
manuals and web-site areas that are appropriate for each -- specifically to
keep developer issues out of the user doc. I have been treating the
documents in docs/xml-docs/design as being developer doc, although there are
a few documents in the docs/xml-docs/fop directory that are
developer-oriented as well. I think it would be helpful to have our source
XML documents organized around that concept as well.

My recommended structure for the docs directory is as follows:

source
source/dev   See note 1
source/user
buildSee note 2
build/pdf
build/html
transient (or temp)  See note 3
stylesheet
(the other directories there now are ok -- graphics, examples, etc.)

Note 1 -- for stuff currently in "design" + the documents you are asking
about and the other developer documents. In my mind "design" is a subset of
"dev". It might be useful to have "design" as a subdirectory under "dev".

Note 2 -- perhaps this should be in xml-fop/build/docs instead. It is
important to have this be in a "build" or "output" directory so that no one
is tempted to, for example, edit the html files directly

Note 3 -- for transient transforms when doing builds, including the fo file.
The build could probably delete the contents, but sometimes it is nice to be
able to see the intermediate results.

All of this, of course, is contingent on Forrest requirements.

Sorry -- you asked a pretty simple question that was probably directed at
Joerg. I have been trying to document (and fix where possible) these
annoyances as they come up, hoping to use my still-mostly-newbie perspective
to lower the cost of bringing new newbies (??) on board.

It will require someone with commit abilities to do all of this, but, if
approved, I'll be glad to do the fixes and cleanup of the builds to match
the new structure.

Victor Mote


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

location of docs

[Keiron Liddle]

Where will the docs be located.

I am writing/updating some docs for fop development and was wondering
where I could put the docs.

maybe docs/xml-docs as the base?




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

cvs commit: xml-fop/docs/foschema fop4.xsd

[pbwest]

pbwest  2002/10/24 08:23:57

  Modified:docs/foschema fop4.xsd
  Log:
  Updated with fop4g.xsd, with s replaced by spaces at tabstops of 2.
  
  Revision  ChangesPath
  1.2   +14 -10xml-fop/docs/foschema/fop4.xsd
  
  Index: fop4.xsd
  ===
  RCS file: /home/cvs/xml-fop/docs/foschema/fop4.xsd,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- fop4.xsd  24 Oct 2002 15:21:41 -  1.1
  +++ fop4.xsd  24 Oct 2002 15:23:56 -  1.2
  @@ -81,6 +81,10 @@
 This declaration assumes that all  elements must come 
before other stuff, 
 which is not required by spec, but I cannot see any way to express such 
constraints in schema, 
 one could use  instead of , but this way we lose 
control over (color-profile)+ constraint.
  +  
  +  VCP 21-Oct-2002 
  +Updated all (px|pt|mm|cm|in|em) to (px|pt|mm|cm|in|em|%) to allow 
percentage types.
  +Updated the restriction base of those types from NMTOKEN to string
   
   
 
  @@ -785,8 +789,8 @@
   
 
   
  -
  -  
  +
  +  
   
 
 
  @@ -831,7 +835,7 @@
 
   
   
  -  
  +  
   
 
 
  @@ -865,7 +869,7 @@
 
   
   
  -  
  +  
   
 
 
  @@ -1051,7 +1055,7 @@
 length_Type{1,2}
   
 
  -  
  +  
   
 
 
  @@ -1734,13 +1738,13 @@
   
 
 
  -
  -  
  +
  +  
   
 
 
  -
  -  
  +
  +  
   
 
 
  @@ -2917,7 +2921,7 @@
 
   
   
  -  
  +  
   
 
 
  
  
  

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

cvs commit: xml-fop/docs/foschema schema2dtd.xsl schema2completion.xsl

[pbwest]

pbwest  2002/10/24 08:19:35

  Modified:docs/foschema schema2dtd.xsl schema2completion.xsl
  Log:
  Stripped s using tabstops of 2.
  
  Revision  ChangesPath
  1.2   +239 -239  xml-fop/docs/foschema/schema2dtd.xsl
  
  Index: schema2dtd.xsl
  ===
  RCS file: /home/cvs/xml-fop/docs/foschema/schema2dtd.xsl,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- schema2dtd.xsl22 Jul 2002 10:23:26 -  1.1
  +++ schema2dtd.xsl24 Oct 2002 15:19:35 -  1.2
  @@ -1,15 +1,15 @@
   
   
   http://www.w3.org/1999/XSL/Transform";
  - xmlns:saxon="http://icl.com/saxon";
  - xmlns:xs = "http://www.w3.org/2001/XMLSchema";
  - xmlns:fo="http://www.w3.org/1999/XSL/Format";
  - xmlns:date="http://exslt.org/dates-and-times";
  - xmlns:math="http://exslt.org/math";
  - extension-element-prefixes="saxon date math"
  - exclude-result-prefixes="fo">
  +version="1.1"
  +xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
  +xmlns:saxon="http://icl.com/saxon";
  +xmlns:xs = "http://www.w3.org/2001/XMLSchema";
  +xmlns:fo="http://www.w3.org/1999/XSL/Format";
  +xmlns:date="http://exslt.org/dates-and-times";
  +xmlns:math="http://exslt.org/math";
  +extension-element-prefixes="saxon date math"
  +exclude-result-prefixes="fo">
   
   
   
  @@ -45,275 +45,275 @@
Entity definitions for groups of formatting objects
 

*** 

   
  - 
  +  
   

*** 

Attribute Groups   
 

*** 
  - 
  +  
   

*** 

Element Groups 
 

*** 

   
  - 
  +  
   

*** 

Elements   
 

*** 

   
  - 
  +  
   
   
   
  - 
  +  
   <!ENTITY %  " 
  - 
  - 
  - 
  - 
  - 
  -  |
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - %
  - 
  - ;
  - 
  - | 
  - 
  - 
  - %
  - ;
  - 
  - 
  +  
  +
  +  
  +
  +
  +   |
  +
  +  
  +  
  +
  +  
  +
  +  
  +
  +
  +  
  +
  +  
  +
  +
  +  %
  +
  +;
  +
  +  | 
  +
  +
  +  %
  +;
  +  
  +  
   ">
   
   
   
  - 
  +  
   <!ENTITY %  "
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  -  CDATA
  - 
  - 
  - 
  -  (%
  - 
  - ;)
  - 
  - 
  -  CDATA
  - 
  - 
  -  #IMPLIED
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - 
  - %;
  - 
  - 
  - ">
  +  
  +
  +  
  +
  +  
  +
  +
  +  
  +
  +  
  +
  +
  +  
  +
  +
  +  
  + CDATA
  +  
  +  
  +
  + (%
  +
  +;)
  +  
  +  
  + CDATA
  +  
  +
  + #IMPLIED
  +  
  +  
  +
  +  
  +
  +  
  +
  +
  +  %;
  +  
  +  
  +  ">
   
   
   
  - 
  - 
  +  
  +
   <!ENTITY %  "
  - 
  - 
  - 
  - |
  - 

cvs commit: xml-fop/docs/examples/fo alignment.fo

[keiron]

keiron  2002/09/18 23:52:14

  Modified:docs/examples/fo alignment.fo
  Log:
  looks more like the spec example
  
  Revision  ChangesPath
  1.4   +4 -1  xml-fop/docs/examples/fo/alignment.fo
  
  Index: alignment.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/alignment.fo,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- alignment.fo  23 Aug 2002 12:53:45 -  1.3
  +++ alignment.fo  19 Sep 2002 06:52:14 -  1.4
  @@ -1,7 +1,7 @@
   http://www.w3.org/1999/XSL/Format"; 
xmlns:svg="http://www.w3.org/2000/svg";>
   
 
  -
  +
 
   
   
  @@ -199,6 +199,9 @@
   And this is the line of text that follows the line with the aligned objects on it.
   And finally, this line illustrates the normal spacing between lines of text in this 
font.
   
  +
  +
  +
   
 
   
  
  
  

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

cvs commit: xml-fop/docs/examples/fo newlinktest.fo leader.fo

[keiron]

keiron  2002/09/17 00:32:10

  Modified:docs/examples/fo newlinktest.fo leader.fo
  Log:
  improved the examples a bit
  links in static and rotated areas
  better info for use-content on leader
  
  Revision  ChangesPath
  1.3   +36 -2 xml-fop/docs/examples/fo/newlinktest.fo
  
  Index: newlinktest.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/newlinktest.fo,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- newlinktest.fo11 Dec 2001 12:08:28 -  1.2
  +++ newlinktest.fo17 Sep 2002 07:32:10 -  1.3
  @@ -7,7 +7,9 @@
 margin-bottom="1in" 
 margin-left="1in" 
 margin-right="1in">
  -  
  +  
  +  
  +  
   
   
   
  @@ -17,7 +19,18 @@
 
 
   
  -
  +
  +
  +  
  +http://xml.apache.org/fop";
  +   color="rgb(150,150,150)" font-style="italic">
  +   http://xml.apache.org/fop
  +
  +  
  +
   
   
   
  @@ -106,6 +119,27 @@
 
   
   
  +
  +  
  +  Links in different orientations
  +  
  +
  +  
  +This block container has a different reference orientation.
  +
  +  
  +A link applies to the inline parent area that is created
  +by the basic-link. This inline area has a trait specifying
  +the link.
  +  
  +  
  +http://xml.apache.org/fop";
  +   color="blue" text-decoration="underline">
  +   http://xml.apache.org/fop
  +
  +  
  +
  +  
   
   
   
  
  
  
  1.10  +18 -5 xml-fop/docs/examples/fo/leader.fo
  
  Index: leader.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/leader.fo,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- leader.fo 23 Aug 2002 14:36:37 -  1.9
  +++ leader.fo 17 Sep 2002 07:32:10 -  1.10
  @@ -50,7 +50,7 @@
   b) to create entry fields in fill-in-the-blank forms c) to create 
horizontal rules for use as separators. You 
   define the look and use of fo:leader with the property "leader-pattern". It 
can have the following values: a) space. This 
   just creates an space. b) dots. This creates a sequence of "." c) rule. 
This creates a line. d) use-content. This creates a 
  -repeating pattern of the content of fo:leader (not supported yet by Fop). 
  +repeating pattern of the content of fo:leader. 
 
   
   
  @@ -718,22 +718,35 @@
 Here is some longer text. Here is some longer text. Here is some longer text. 
 
   
  +  
  +Use-Content
  +  
  +
  +  
  +The following examples show Leader with "use-content".
  +The inline areas from the context of the leader are
  +repeated until the lenght of the leader. The
  +"leader-pattern-width" can be used to set the width
  +of each repeated pattern element. 
  +If this width is less than the inline areas then the width
  +of the inline areas is used.
  +  
   
  -  Characters:
  +  Characters:
   abcd
 
   
  -  Set width:
  +  Set width:
   abcd
 
   
  -  Small Width:
  +  Small Width:
   abcd
 
   
  -  SVG:
  +  SVG:
   
   
   http://www.w3.org/2000/svg"; width="10" height="10">
  
  
  

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

cvs commit: xml-fop/docs/examples/advanced K3.TTF K3.xml bar.conf.xml barcode.fo

[keiron]

keiron  2002/08/19 03:40:57

  Added:   docs/examples/advanced K3.TTF K3.xml bar.conf.xml barcode.fo
  Log:
  added example for embedding fonts
  using free barcode font for embedding
  
  Revision  ChangesPath
  1.1  xml-fop/docs/examples/advanced/K3.TTF
  
<>
  
  
  1.1  xml-fop/docs/examples/advanced/K3.xml
  
  Index: K3.xml
  ===
  
  
  New00392193903300TYPE0CIDFontType20
  
  
  
  1.1  xml-fop/docs/examples/advanced/bar.conf.xml
  
  Index: bar.conf.xml
  ===
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  1.1  xml-fop/docs/examples/advanced/barcode.fo
  
  Index: barcode.fo
  ===
  
  http://www.w3.org/1999/XSL/Format";>
 

   
   


   


   
  
  
  
   

 
 

  
  
  Example embedding Font
  
  
  
  This example shows how to use an embedded font and
  uses a free barcode font as an example. The barcode font is from
  http://www.geocities.com/keith_dimmock/";>http://www.geocities.com/keith_dimmock/
  and is free.
  
  
  
  *ID123456*
  
  
  
  normal text
  
  
  
   *ID123456*   normal text
  
  

 
  
  
  
  

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

cvs commit: xml-fop/docs/design/understanding book.xml layout_managers.xml

[keiron]

keiron  2002/07/31 03:31:55

  Modified:docs/design/understanding book.xml layout_managers.xml
  Log:
  added layout manager info
  Submitted by: Cyril Rognon <[EMAIL PROTECTED]>
  
  Revision  ChangesPath
  1.2   +23 -23xml-fop/docs/design/understanding/book.xml
  
  Index: book.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/design/understanding/book.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- book.xml  17 Mar 2002 17:21:52 -  1.1
  +++ book.xml  31 Jul 2002 10:31:54 -  1.2
  @@ -1,23 +1,23 @@
  -
  -
  -
  -  http://xml.apache.org/fop/";  label="About FOP"/>
  -  
  -  
  -  
  -  
  -  
  -  
  -  
  -  
  -  
  -  
  -  
  -  
  -  
  -  
  -  
  -  
  -  
  -  
  -
  \ No newline at end of file
  +
  +
  +
  +  http://xml.apache.org/fop/";  label="About FOP"/>
  +  
  +  
  +  
  +  
  +  
  +  
  +  
  +  
  +  
  +  
  +  
  +  
  +  
  +  
  +  
  +  
  +  
  +  
  +
  
  
  
  1.2   +66 -12xml-fop/docs/design/understanding/layout_managers.xml
  
  Index: layout_managers.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/design/understanding/layout_managers.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- layout_managers.xml   17 Mar 2002 17:21:52 -  1.1
  +++ layout_managers.xml   31 Jul 2002 10:31:54 -  1.2
  @@ -1,13 +1,67 @@
  -
  -
  - 
  -   
  -  Layout Managers 
  -  All you wanted to know about Layout Managers ! 
  -
  -   
  -   
  -   
  - Yet to come :)) 
  - The series of notes for developers has started but it has not 
yet gone so far ! Keep watching 
  +
  +
  + 
  +   
  +  Layout Managers 
  +  All you wanted to know about Layout Managers ! 
  +
  +   
  +   
  +   
  +
  +
  +
  +The role of the layout managers is to build the Area Tree by using the
  +information from the FO Tree. The layout managers decide where information
  +is placed in the area tree.
  +A layout manager is typically associated with an FO Object but not always.
  +
  +
  +The layout managers are in between the FO Tree and the Area Tree. They get
  +information from the FO Tree and create areas and build the pages. They
  +hold the state of the layout process as it builds up the areas and pages.
  +They also manage the handling of breaks and spacing between areas.
  +
  +
  +FO Objects can have two types of properties, ones that relate to the layout and 
ones that relate to the rendering. THe layout related properties area used by the 
layout managers to determine how and where to create the areas. The render related 
properties should be passed through to the renderer in the most efficient way possible.
  +
  +
  +
  +
  +
  +When a block creating element is complete then it is possible to build the
  +block area and add it to the paprent.
  +A block area will contain either more block areas or line areas, which are
  +special block areas. The line areas are created by the LineLayoutManager
  +in which the inline areas flow into.
  +So a block area manager handles the lines or blocks as its children and
  +determines things like spacing and breaks.
  +In the case of tables and lists the blocks are stacked in a specific way
  +that needs to be handled by the layout manager.
  +
  +
  +
  +
  +
  +Side floats alter the length of the inline progression dimension for the
  +current line and following lines for the size of the float.
  +This means that the float needs to be handled by the block layout manager
  +so that it can adjust the available inline progression dimension for the
  +relevant line areas.
  +
  +
  +
  +
  +
  +Footnotes and Before Floats are placed in special areas in the body region
  +of the page. The size of these areas is determined by the content. This in
  +turn effects the available size of the main reference area that contains
  +the flow.
  +A layout manager handles the adding and removing of footnotes/floats, this in 
turn effects the available space in the main reference area.
  +
  +
  +(note: more info to follow)
  +
  +
  + 
 
  
  
  

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

cvs commit: xml-fop/docs/foschema fop4f.xsd schema2completion.xsl schema2dtd.xsl

[keiron]

keiron  2002/07/22 03:28:21

  Added:   docs/foschema Tag: fop-0_20_2-maintain fop4f.xsd
schema2completion.xsl schema2dtd.xsl
  Log:
  FO Schema and dtd for use with FOP and editors
  Submitted by: Chuck Paussa <[EMAIL PROTECTED]>
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.1.2.1   +0 -0  xml-fop/docs/foschema/fop4f.xsd
  
  Index: fop4f.xsd
  ===
  RCS file: /home/cvs/xml-fop/docs/foschema/fop4f.xsd,v
  retrieving revision 1.1
  retrieving revision 1.1.2.1
  diff -u -r1.1 -r1.1.2.1
  
  
  
  1.1.2.1   +0 -0  xml-fop/docs/foschema/schema2completion.xsl
  
  Index: schema2completion.xsl
  ===
  RCS file: /home/cvs/xml-fop/docs/foschema/schema2completion.xsl,v
  retrieving revision 1.1
  retrieving revision 1.1.2.1
  diff -u -r1.1 -r1.1.2.1
  
  
  
  1.1.2.1   +0 -0  xml-fop/docs/foschema/schema2dtd.xsl
  
  Index: schema2dtd.xsl
  ===
  RCS file: /home/cvs/xml-fop/docs/foschema/schema2dtd.xsl,v
  retrieving revision 1.1
  retrieving revision 1.1.2.1
  diff -u -r1.1 -r1.1.2.1
  
  
  

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

cvs commit: xml-fop/docs/foschema - New directory

[keiron]

keiron  2002/07/22 03:18:27

  xml-fop/docs/foschema - New directory

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

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

[pbwest]

pbwest  2002/07/08 09:17:02

  Modified:docs/xml-docs/fop news.xml
  Log:
  Update for 0.20.4 release
  
  Revision  ChangesPath
  1.3   +11 -5 xml-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.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- news.xml  22 Jun 2002 06:12:14 -  1.2
  +++ news.xml  8 Jul 2002 16:17:01 -   1.3
  @@ -11,9 +11,8 @@
   
   
 
  -  
 
  -
  +
 
Changes since 0.20.3 include:
 
  @@ -41,16 +40,23 @@
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
  +  "http://cvs.apache.org/viewcvs.cgi/xml-fop/CHANGES?rev=1.10.2.21";
  +  >http://cvs.apache.org/viewcvs.cgi/xml-fop/CHANGES?rev=1.10.2.21
 
 
See also the full text of the http://marc.theaimsgroup.com/?l=fop-dev&m=102607087326357&w=4";
  + >announcement.
  +  
  +
  +
  +  
  + See 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!

   
  
  
  

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

cvs commit: xml-fop/docs/xml-docs/skins/xml.apache.org/stylesheets book2project.xsl changes2document.xsl context2label.xsl copyover.xsl directory2project.xsl document2html.xsl document2image.xsl document2project.xsl faqs-big2document.xsl faqs2document.xsl scan4resources.xsl spec2html.xsl todo2document.xsl

[chrisg]

chrisg  2002/07/05 09:21:54

  Modified:.Tag: fop-0_20_2-maintain build.xml
  Removed: docs/design Tag: fop-0_20_2-maintain architecture.xml
areas.xml book.xml embedding.xml float.svg
fotree.xml intro.xml layout.xml optimise.xml
page.svg properties.xml renderers.xml status.xml
useragent.xml
   docs/design/fo_impl Tag: fop-0_20_2-maintain fo_classes.xml
fo_classes.xsl
   docs/xml-docs Tag: fop-0_20_2-maintain fop.xml readme
xml2pdf.xsl xml2xml.xsl
   docs/xml-docs/data Tag: fop-0_20_2-maintain document.svg
layout.svgz logo.svg title.svg
   docs/xml-docs/dtd Tag: fop-0_20_2-maintain changes-v10.dtd
characters.ent document-v10.dtd faq-v10.dtd
specification-v10.dtd todo-v10.dtd
   docs/xml-docs/fop Tag: fop-0_20_2-maintain bugs.xml
compiling.xml configuration.xml document.jpg
download.xml embedding.xml examples.xml
extensions.xml faq-big.xml faq.xml fonts.xml
implemented.xml involved.xml layout.jpg license.xml
limitations.xml output.xml readme.xml relnotes.xml
resources.xml running.xml svg.xml testing.xml
title.jpg todo.xml
   docs/xml-docs/skins/xml.apache.org Tag: fop-0_20_2-maintain
loader.xml
   docs/xml-docs/skins/xml.apache.org/graphics Tag:
fop-0_20_2-maintain button-a.gif button-b.gif
   docs/xml-docs/skins/xml.apache.org/resources Tag:
fop-0_20_2-maintain bar-border-bottom.gif
bar-border-left.gif bar-border-right.gif
bar-border-top.gif bar-bottom-left.gif
bar-bottom-right.gif bar-top-left.gif
bar-top-right.gif bottom.gif button-asf-hi.gif
button-asf-lo.gif button-w3c-hi.gif
button-w3c-lo.gif button-xml-hi.gif
button-xml-lo.gif close.gif dot.gif join.gif
line.gif logo.gif note.gif right.gif script.js
separator.gif void.gif
   docs/xml-docs/skins/xml.apache.org/stylesheets Tag:
fop-0_20_2-maintain book2project.xsl
changes2document.xsl context2label.xsl copyover.xsl
directory2project.xsl document2html.xsl
document2image.xsl document2project.xsl
faqs-big2document.xsl faqs2document.xsl
scan4resources.xsl spec2html.xsl todo2document.xsl
  Log:
  removed old docs (docs are maintained in the trunk)
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.44.2.19 +3 -5  xml-fop/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/xml-fop/build.xml,v
  retrieving revision 1.44.2.18
  retrieving revision 1.44.2.19
  diff -u -r1.44.2.18 -r1.44.2.19
  --- build.xml 4 Jul 2002 21:38:38 -   1.44.2.18
  +++ build.xml 5 Jul 2002 16:21:52 -   1.44.2.19
  @@ -149,9 +149,7 @@
   
   
   
  -   
  -   
  -   
  +   
  
  
  
  @@ -673,7 +671,7 @@
 
 
   
  -  
  +  
   
   
   
  @@ -692,7 +690,7 @@
 
   
   
  -  
  +  
   
   
   
  
  
  

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

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

[chrisg]

chrisg  2002/07/05 07:14:21

  Modified:docs/xml-docs/fop relnotes.xml
  Log:
  changes for 0.20.4 release notes
  
  Revision  ChangesPath
  1.5   +5 -3  xml-fop/docs/xml-docs/fop/relnotes.xml
  
  Index: relnotes.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/relnotes.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- relnotes.xml  4 Jul 2002 20:54:11 -   1.4
  +++ relnotes.xml  5 Jul 2002 14:14:21 -   1.5
  @@ -32,18 +32,20 @@
   (see Embedding for details).
 
 Building under JDK 1.4:
  -You need to add a method in
  + You need to add a method in
src/org/apache/fop/svg/PDFGraphics2D.java
(search for jdk1.4 and remove the comments)
  - 
 
 To decrease the size of the distributions, ant, xml-docs, design-docs
   and the hyphenation sources have been removed from the binary distribution.
   Javadocs have been removed from the source distribution (use
   build javadocs to generate them).
 
  +  Documentaion generation is broken in the maintenance branch at the moment
  +   (Stylebook needs xerces1). The docs for this release are generated from the 
trunk. 
  +  
 
  -For a more detailed list of changes, see the CHANGES file in the root of 
the FOP distribution.
  +For a more detailed list of changes, see the CHANGES file in the root of 
the FOP distribution.
 
 
   
  
  
  

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

cvs commit: xml-fop/docs/examples/fo list.fo

[chrisg]

chrisg  2002/07/04 13:20:55

  Modified:docs/examples/fo Tag: fop-0_20_2-maintain list.fo
  Log:
  changed list.fo to prevent a bug
  (text-align="end" in a list-item-label)
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.6.4.3   +29 -29    xml-fop/docs/examples/fo/list.fo
  
  Index: list.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/list.fo,v
  retrieving revision 1.6.4.2
  retrieving revision 1.6.4.3
  diff -u -r1.6.4.2 -r1.6.4.3
  --- list.fo   11 Feb 2002 00:43:43 -  1.6.4.2
  +++ list.fo   4 Jul 2002 20:20:55 -   1.6.4.3
  @@ -225,7 +225,7 @@
  url: http://www.w3.org/TR/xsl/ -->
 
  -
  +
 
 
 
 
  -label 1)
  +label 1)
 
  
 
  @@ -589,7 +589,7 @@
   
 
 
  -lab. 2)
  +lab. 2)
 
  
 
  @@ -603,7 +603,7 @@
   
 
 
  -lab.  3)
  +lab.  3)
 
  
 
  @@ -617,7 +617,7 @@
   
 
 
  -lab. 4)
  +lab. 4)
 
  
 
  @@ -631,7 +631,7 @@
   
 
 
  -lab. 5)
  +lab. 5)
 
  
 
  @@ -2009,7 +2009,7 @@
   
 
 
  -1.)
  +1.)
 
  
 
  @@ -2022,7 +2022,7 @@
   
 
 
  -2.)
  +2.)
 
  
 
  @@ -2038,7 +2038,7 @@
   
 
 
  -3.)
  +3.)
 
  
 
  @@ -2051,7 +2051,7 @@
   
 
 
  -4.)
  +4.)
 
  
 
  @@ -2067,7 +2067,7 @@
   
 
 
  -5.)
  +5.)
 
  
 
  @@ -2194,7 +2194,7 @@
 
   
   
  -  1.)
  +  1.)
   

   
  @@ -2355,7 +2355,7 @@
   
 
 
  -1.)
  +1.)
 
  
 
  @@ -2368,7 +2368,7 @@
   
 
 
  -2.)
  +2.)
 
  
 
  @@ -2384,7 +2384,7 @@
   
 
 
  -3.)
  +3.)
 
  
 
  @@ -2397,7 +2397,7 @@
   
 
 
  -4.)
  +4.)
 
  
 
  @@ -2413,7 +2413,7 @@
   
 
 
  -5.)
  +5.)
 
  
 
  @@ -2426,7 +2426,7 @@
   
 
 
  -6.)
  +6.)
 
  
 
  @@ -2442,7 +2442,7 @@
   
 
 
  -7.)
  +7.)
 
  
 
  @@ -2458,7 +2458,7 @@
   
 
 
  -8.)
  +8.)
 
  
 
  @@ -2474,7 +2474,7 @@
   
 
 
  -9.)
  +9.)
 
  
 
  @@ -2490,7 +2490,7 @@
   
 
 
  -10.)
  +10.)
 
  
 
  @@ -2506,7 +2506,7 @@
   
 
 
  -11.)
  + 

cvs commit: xml-fop/docs/examples/fo fonts.fo

[jeremias]

jeremias2002/06/26 13:34:19

  Modified:docs/examples/fo Tag: fop-0_20_2-maintain fonts.fo
  Log:
  Add code for testing and demonstrating fractional font sizes.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.7.4.3   +29 -0 xml-fop/docs/examples/fo/fonts.fo
  
  Index: fonts.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/fonts.fo,v
  retrieving revision 1.7.4.2
  retrieving revision 1.7.4.3
  diff -u -r1.7.4.2 -r1.7.4.3
  --- fonts.fo  11 Feb 2002 00:43:43 -  1.7.4.2
  +++ fonts.fo  26 Jun 2002 20:34:19 -  1.7.4.3
  @@ -185,7 +185,36 @@
 
 
   
  +  
  + Different font sizes: 
  +  
 
  + A
  + A
  + A
  + A
  + A
  + A
  + A
  + A
  + A
  + A
  + A
  + A
  + A
  + A
  + A
  + A
  + A
  + A
  + A
  + A
  + A
  + ---
  + A
  + A
  + A
  + A
   
 
   
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [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]

cvs commit: xml-fop/docs/examples/svg external.fo multi.svg

[keiron]

keiron  2002/06/18 03:58:21

  Modified:docs/examples/svg Tag: fop-0_20_2-maintain external.fo
multi.svg
  Log:
  added xlink ns
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.3.2.2   +2 -2  xml-fop/docs/examples/svg/external.fo
  
  Index: external.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/svg/external.fo,v
  retrieving revision 1.3.2.1
  retrieving revision 1.3.2.2
  diff -u -r1.3.2.1 -r1.3.2.2
  --- external.fo   6 Dec 2001 21:28:20 -   1.3.2.1
  +++ external.fo   18 Jun 2002 10:58:21 -  1.3.2.2
  @@ -1,5 +1,5 @@
   
  -http://www.w3.org/1999/XSL/Format";>
  +http://www.w3.org/1999/XSL/Format"; 
xmlns:xlink="http://www.w3.org/1999/xlink";>
 
   
 
 
  -
  +
 
   
   
  
  
  
  1.1.2.1   +2 -2  xml-fop/docs/examples/svg/multi.svg
  
  Index: multi.svg
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/svg/multi.svg,v
  retrieving revision 1.1
  retrieving revision 1.1.2.1
  diff -u -r1.1 -r1.1.2.1
  --- multi.svg 8 Jun 2001 08:56:02 -   1.1
  +++ multi.svg 18 Jun 2002 10:58:21 -  1.1.2.1
  @@ -2,13 +2,13 @@
   http://www.w3.org/TR/2000/CR-SVG-2802/DTD/svg-2802.dtd";>
   
  -
  +http://www.w3.org/1999/xlink"; width="60" height="40" 
xml:space="preserve">
 


 
 
  -
  +
 
   
   
  
  
  

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

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

[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]

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

[chrisg]

chrisg  2002/06/12 12:54:05

  Modified:docs/xml-docs/fop relnotes.xml
  Log:
  Added release notes for FOP 0.20.4
  
  Revision  ChangesPath
  1.3   +30 -3 xml-fop/docs/xml-docs/fop/relnotes.xml
  
  Index: relnotes.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/relnotes.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- relnotes.xml  17 Mar 2002 17:43:55 -  1.2
  +++ relnotes.xml  12 Jun 2002 19:54:05 -  1.3
  @@ -5,12 +5,39 @@
   
   
   Release Notes
  -Fop 0.20.3
  -
  -
  +Fop 0.20.4
  +Christian Geisert
   
   
   
  +
  +  Important changes since 0.20.3:
  +
  +   FOP should now work with any JAXP1.1 compliant parser/transformer. 
  + It has been successfully tested with Xerces/Xalan, Saxon and JDK1.4 
  + (which includes Crimson and Xalan).
  +   
  +   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 this time
  +but you still have to download
  +http://java.sun.com/products/jimi/";>Jimi
  +and copy it to lib/ to get PNG support (no need to build FOP yourself 
though).
  +  
  +  Building FOP with JDK1.2 does not work. Running is ok except
  +support for additional truetype fonts in AWT Viewer.
  +  
  +  Logging has been changed from LogKit to Avalon's Logger Interface.
  +(see Embedding for details).
  +  
  +  
  +For a more detailed list of changes, see the CHANGES file in the root of 
the FOP distribution.
  +  
  +  
  +
  + 
  +
   
 Important Information:
   
  
  
  

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

cvs commit: xml-fop/docs/xml-docs/fop status.xml readme.xml

[keiron]

keiron  2002/06/12 07:14:32

  Modified:docs/xml-docs fop.xml
   docs/xml-docs/fop readme.xml
  Added:   docs/xml-docs/fop status.xml
  Log:
  moved status to another page with some more info
  
  Revision  ChangesPath
  1.16  +1 -0  xml-fop/docs/xml-docs/fop.xml
  
  Index: fop.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/fop.xml,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- fop.xml   24 Apr 2002 23:27:22 -  1.15
  +++ fop.xml   12 Jun 2002 14:14:32 -  1.16
  @@ -4,6 +4,7 @@



  + 



  
  
  
  1.21  +0 -25 xml-fop/docs/xml-docs/fop/readme.xml
  
  Index: readme.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/readme.xml,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- readme.xml16 May 2002 08:37:09 -  1.20
  +++ readme.xml12 Jun 2002 14:14:32 -  1.21
  @@ -72,31 +72,6 @@
   along with the xml.
   
 
  -  
  -
  -
  -
  -
  -This is the development status of FOP. A branch has been created for
  -maintenance releases while the development is done to address various
  -performance and design issues.
  -
  -
  -Maintenance releases will be done as necessary. Another maintenance release
  -is planned for the near future to provide some fixes and to provide
  -compatibilty with http://xml.apache.org/batik/";>Batik
  -version 1.5 beta2. Other changes are: new hyphentaion patterns, changed
  -to use Avalon Logger interface and added background image support.
  -
  -
  -Development for 1.0DR1 is addressing the design issues for layout and
  -performance. This is focusing on making it possible to be conformant
  -to the spec and be able to handle large documents. This is roughly
  -30% towards a developers release that should have: similar functionality to
  -previous FOP releases, a rough API and a suitable design for developers
  -to work on more functionality.
  -
  -  
 
   The goals of the Apache XML FOP Project are to deliver an XSL FO->PDF 
formatter that is compliant to at least the Basic
  conformance level described in the W3C Recommendation from 15 October 2001, 
and that complies with the 11 March 1999 Portable Document
  
  
  
  1.1      xml-fop/docs/xml-docs/fop/status.xml
  
  Index: status.xml
  ===
  
  
  
  
  
  
  FOP Status
  Current Status of FOP
  
  
  
  
  

  [last updated 10th June 2002]
  
  
  
  
  This is the development status of FOP. A branch has been created for
  maintenance releases while the development is done to address various
  performance and design issues.
  

  

  
  Volunteers needed for:
  
  configuration implementation
  implement formatting objects and properties
  AWT/Swing viewer design and implementation
  documentation
  MIF output
  
  ... and plenty of other areas. See the todo
  list for more details.
  
  
  Development for 1.0DR1 is addressing the design issues for layout and
  performance. The new design focusing on making it possible to be conformant
  to the spec and be able to handle large documents. The development effort
  is roughly 35% towards a developers release.
  
  
  The developers release should have the following: similar functionality
  to previous FOP releases, a rough API and a suitable design for
  developers to work on more functionality.
  
  
  The timing of these events depends on progress made so it is not possible
  to predict any dates.
  
  Binaries
  
fop.jar1,966 kb
hyphention (in fop.jar)717 kb
batik.jar2,164 kb
bsf.jar106 kb
xalan.jar883 kb
xerces.jar1,809 kb
  
  
  Lines of code using "find . -iname "*.java" | xargs cat | wc 
-l"
  
org.apache.fop.*67076
org.apache.fop.fo.*15257 (23%)
org.apache.fop.layoutmgr.*4537 (7%)
org.apache.fop.area.*2314 (3.5%)
org.apache.fop.render.*6474 (10%)
org.apache.fop.pdf.*8113 (12%)
  
  
  Files using "find . -iname "*.java" | wc -l"
  
org.apache.fop.*462
org.apache.fop.fo.*127 (27%)
org.apache.fop.layoutmgr.*28 (6%)
org.apache.fop.area.*36 (8%)
org.apache.fop.render.*35 (8%)
  
  
  

  

  
  Latest maintenance release was FOP 0.20.3 on 4th March 2002.
  See release notes for more
  details. Releases will be made periodically to address minor bugs
  and compatibility.
  
  
  Binaries
  
fop.jar1,695 kb
hyphention (in fop.jar)746 kb
batik.jar2,164 kb
bsf.jar106 kb
xalan.jar906 kb
  

cvs commit: xml-fop/docs/xml-docs/data track.svg

[keiron]

keiron  2002/06/12 07:12:19

  Added:   docs/xml-docs/data track.svg
  Log:
  svg for creating status branch image
  
  Revision  ChangesPath
  1.1  xml-fop/docs/xml-docs/data/track.svg
  
  Index: track.svg
  ===
  
  http://www.w3.org/TR/2000/CR-SVG-20001102/DTD/svg-20001102.dtd";>
  http://www.w3.org/2000/svg";>
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  FOP 0.20.2
  29th Sept 2001
  
  
  branch
  "fop-0_20_2-maintain"
  22nd Oct 2001
  
  
  FOP 0.20.3
  4th March 2002
  
  
  FOP 0.20.4
  12th June 2002
  
  
  
  
  redesign
  
  
  FOP 1.0DR1
  
  
  
  
  
  
  
  
  
  
  

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

cvs commit: xml-fop/docs/examples/svg multi.svg external.fo

[keiron]

keiron  2002/06/11 08:32:12

  Modified:docs/examples/svg multi.svg external.fo
  Log:
  fixed xlink namespace and put text in a more suitable position
  
  Revision  ChangesPath
  1.2   +2 -2  xml-fop/docs/examples/svg/multi.svg
  
  Index: multi.svg
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/svg/multi.svg,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- multi.svg 8 Jun 2001 08:56:02 -   1.1
  +++ multi.svg 11 Jun 2002 15:32:12 -  1.2
  @@ -2,13 +2,13 @@
   http://www.w3.org/TR/2000/CR-SVG-2802/DTD/svg-2802.dtd";>
   
  -
  +http://www.w3.org/1999/xlink"; width="60" height="40" 
xml:space="preserve">
 


 
 
  -
  +
 
   
   
  
  
  
  1.5   +2 -2  xml-fop/docs/examples/svg/external.fo
  
  Index: external.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/svg/external.fo,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- external.fo   11 Dec 2001 12:08:30 -  1.4
  +++ external.fo   11 Jun 2002 15:32:12 -  1.5
  @@ -1,5 +1,5 @@
   
  -http://www.w3.org/1999/XSL/Format";>
  +http://www.w3.org/1999/XSL/Format"; 
xmlns:xlink="http://www.w3.org/1999/xlink";>
 
   
 
 
  -
  +
 
   
   
  
  
  

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

cvs commit: xml-fop/docs/examples/fo pdfoutline.fo

[keiron]

keiron  2002/06/10 01:58:51

  Modified:docs/examples/fo pdfoutline.fo
  Log:
  changed to use single xml element to contain all bookmarks
  
  Revision  ChangesPath
  1.4   +2 -0  xml-fop/docs/examples/fo/pdfoutline.fo
  
  Index: pdfoutline.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/pdfoutline.fo,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- pdfoutline.fo 11 Dec 2001 12:08:28 -  1.3
  +++ pdfoutline.fo 10 Jun 2002 08:58:50 -  1.4
  @@ -59,6 +59,7 @@
   
   

  +  
   
 
   What is FOP?
  @@ -119,6 +120,7 @@
 
   License
 
  +  
   
   
   
  
  
  

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

cvs commit: xml-fop/docs/examples runtests.bat

[jeremias]

jeremias2002/06/07 13:14:30

  Modified:docs/examples Tag: fop-0_20_2-maintain runtests.bat
  Log:
  Fixed classpath. Xerces was wrong.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.11.2.5  +1 -1  xml-fop/docs/examples/runtests.bat
  
  Index: runtests.bat
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/runtests.bat,v
  retrieving revision 1.11.2.4
  retrieving revision 1.11.2.5
  diff -u -r1.11.2.4 -r1.11.2.5
  --- runtests.bat  2 Jun 2002 00:13:25 -   1.11.2.4
  +++ runtests.bat  7 Jun 2002 20:14:30 -   1.11.2.5
  @@ -7,7 +7,7 @@
   
   
   set LIBDIR=..\..\lib
  -set 
LOCALCLASSPATH=%JAVA_HOME%\lib\tools.jar;%JAVA_HOME%\lib\classes.zip;%LIBDIR%\ant-1.4.1.jar;%LIBDIR%\batik.jar;%LIBDIR%\buildtools.jar;%LIBDIR%\xercesImpl.jar;%LIBDIR%\xml-apis.jar;%LIBDIR%\xalan-2.3.1.jar;%LIBDIR%\bsf.jar;%LIBDIR%\avalon-framework-cvs-20020315.jar;%LIBDIR%\jimi-1.0.jar;%LIBDIR%\..\build\fop.jar
  +set 
LOCALCLASSPATH=%JAVA_HOME%\lib\tools.jar;%JAVA_HOME%\lib\classes.zip;%LIBDIR%\ant-1.4.1.jar;%LIBDIR%\batik.jar;%LIBDIR%\buildtools.jar;%LIBDIR%\xercesImpl-2.0.1.jar;%LIBDIR%\xml-apis.jar;%LIBDIR%\xalan-2.3.1.jar;%LIBDIR%\bsf.jar;%LIBDIR%\avalon-framework-cvs-20020315.jar;%LIBDIR%\jimi-1.0.jar;%LIBDIR%\..\build\fop.jar
   set ANT_HOME=%LIBDIR%
   
   echo Starting Tests ...
  
  
  

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

cvs commit: xml-fop/docs/examples/fo textdeko.fo

[jeremias]

jeremias2002/06/07 13:13:25

  Modified:docs/examples/fo Tag: fop-0_20_2-maintain textdeko.fo
  Log:
  Added a few samples of letter-spacing attribute.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.3.4.4   +5 -0  xml-fop/docs/examples/fo/textdeko.fo
  
  Index: textdeko.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/textdeko.fo,v
  retrieving revision 1.3.4.3
  retrieving revision 1.3.4.4
  diff -u -r1.3.4.3 -r1.3.4.4
  --- textdeko.fo   9 Jan 2002 11:32:57 -   1.3.4.3
  +++ textdeko.fo   7 Jun 2002 20:13:23 -   1.3.4.4
  @@ -278,6 +278,11 @@
  
 
 
 
  +  
  +  The following blocks demonstrate the letter-spacing 
attribute:
  +  This block does not use any letter-spacing.
  +  This block uses a letter-spacing of 
1mm.
  +  This block uses an fo:inline element to demonstrate letter-spacing.
   
   
 
  
  
  

-
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/04 06:39:29

  Modified:docs/design/alt.design book.xml
  Log:
  Added user-agent-refs
  
  Revision  ChangesPath
  1.4   +1 -0  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.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- book.xml  28 Apr 2002 13:54:40 -  1.3
  +++ book.xml  4 Jun 2002 13:39:29 -   1.4
  @@ -27,4 +27,5 @@
 
 
 
  +  
   
  
  
  

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

cvs commit: xml-fop/docs/design/alt.design user-agent-refs.xml

[pbwest]

pbwest  2002/06/04 06:30:23

  Added:   docs/design/alt.design user-agent-refs.xml
  Log:
  User agent references in XSL
  
  Revision  ChangesPath
  1.1  xml-fop/docs/design/alt.design/user-agent-refs.xml
  
  Index: user-agent-refs.xml
  ===
  
  
  
  
  

  User agent refs
  

  


  


  If the block-progression-dimension of the reference-area is
  larger than that of the viewport-area and the overflow trait
  for the reference-area is scroll, then the
  inline-scroll-amount and block-scroll-amount are determined
  by a scrolling mechanism, if any, provided by the
  user agent. Otherwise, both are zero.




  A computed value is in principle ready to be used, but a
  user agent may not be able to make use of the value in a
  given environment. For example, a user
  agent may only be able to render borders with
  integer pixel widths and may, therefore, have to adjust the
  computed width to an integral number of media pixels.




  There is no XSL mechanism to specify a particular font;
  instead, a selected font is chosen from the fonts available
  to the User Agent based on a set of
  selection criteria. The selection criteria are the following
  font properties: "font-family", "font-style",
  "font-variant", "font-weight", "font-stretch", and
  "font-size", plus, for some formatting objects, one or more
  characters.




  If the User Agent chooses a measurement for
  a 'px' that does not match an integer number of device dots
  in each axis it may produce undesirable effects...




  
The merge-property-values function returns a value of the
property whose name matches the argument, or if omitted
for the property for which the expression is being
evaluated. The value returned is the specified value on
the last fo:multi-property-set, of the parent
fo:multi-properties, that applies to the User
Agent state. If there is no such value, the
computed value of the parent fo:multi-properties is
returned...
  
  
The test for applicability of a User
Agent state is specified using the "active-state"
property.
  




  
The fo:multi-property-set is used to specify an
alternative set of formatting properties that, dependent
on a User Agent state, are applied to the
content.
  


  
The fo:title formatting object is used to associate a
title with a given page-sequence. This title may be used
by an interactive User Agent to identify
the pages. For example, the content of the fo:title can be
formatted and displayed in a "title" window or in a "tool
tip".
  




  ... When pages are used with a User Agent
  such as a Web browser, it is common that the each document
  has only one page. The viewport used to view the page
  determines the size of the page. When pages are placed on
  non-interactive media, such as sheets of paper, pages
  correspond to one or more of the surfaces of the paper.




  
... This title may be used by an interactive User
Agent to identify the pages.
  




  
The dimensions of the areas are determined by the font
metrics for the glyph.
  
  
When formatting an fo:character with a
"treat-as-word-space" value of "true", the User
Agent may use a different method for determining
the inline-progression-dimension of the area.
  




  
Dynamic effects, whereby user actions (including
User Agent state) can influence the
behavior and/or representation of portions of a document,
can be achieved through the use of the formatting objects
included in this section:
  
  
One-directional single-target links.

  The ability to switch between the display of two or more
  formatting object subtrees. This can be used for, e

cvs commit: xml-fop/docs/examples/fo hyphen.fo

[chrisg]

chrisg  02/05/25 05:20:06

  Modified:docs/examples/fo Tag: fop-0_20_2-maintain hyphen.fo
  Log:
  Added czech hyphenation example
  Submitted by: Michal Buchtik <[EMAIL PROTECTED]>
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.4.2.2   +40 -0 xml-fop/docs/examples/fo/hyphen.fo
  
  Index: hyphen.fo
  ===
  RCS file: /home/cvs/xml-fop/docs/examples/fo/hyphen.fo,v
  retrieving revision 1.4.2.1
  retrieving revision 1.4.2.2
  diff -u -r1.4.2.1 -r1.4.2.2
  --- hyphen.fo 6 Dec 2001 21:28:18 -   1.4.2.1
  +++ hyphen.fo 25 May 2002 12:20:06 -  1.4.2.2
  @@ -423,6 +423,46 @@
   forhistorie og tilblivelse.
  
 
  +  
  +  
  +Czech
  +  
  +
  +  
  +  
  +   
  +   Úryvek z knihy Alenka v říši 
divů
  +   
  +Alenka si ani trochu neublížila a v mžiku byla na nohou: pohlédla nad sebe a 
kolem sebe,
  +nad ní bylo temno a před ní nová dlouhá chodba, v níž ještě zahlédla 
pospíchajícího Bílého Králíka.
  +Nesměla ztratit ani vteřinu: jako vítr se pustila za ním a doběhla k němu 
dosti blízko, aby slyšela,
  +jak si povídá, zahýbaje kolem rohu: "U mých uší a vousů, jak je pozdě!" 
Byla těsně za ním, když zahnula
  +kolem rohu. Králík se jí však náhle ztratil z očí. Byla v dlouhé nízké 
síni, osvětlené řadou lamp,
  +visících ze stropu. Po obou stranách síně byly řady dveří, všechny však 
byly zamčeny, a když je Alenka
  +všechny po jedné i po druhé straně vyzkoušela, ubírala se smutně 
prostředkem síně přemýšlejíc, jak se kdy
  +opět dostane domů.
  +   
  +   
  +Pojednou jí stál v cestě malý třínohý stolek, celý z hladkého 
průhledného skla; na něm nebylo nic než malinký
  +zlatý klíček, a Alenku hned napadlo, že by to mohl být klíček od některých 
těch dveří: ale běda! bud' byly zámky
  +příliš velké, nebo klíč příliš malý, ať už tak nebo onak, nehodily se k 
sobě. Když však tak po druhé obcházela,
  +uviděla před sebou nízkou záclonku, které dříve nezpozorovala, a za ní byly 
malé dveře, tak asi patnáct palců
  +vysoké: zkusila zlatý klíček v jejich zámku a k veliké její radosti zapadl. 
Alenka otevřela dveře a shledala,
  +že vedou do malé chodbičky, ne prostornější než myší díra. Poklekla a 
hleděla chodbičkou do nejrozkošnější zahrady,
  +jakou si jen můžete představit. Ó, jak toužila dostat se z malé síně a 
procházeti se mezi záhony zářivých
  +květin a chladnými vodotrysky! Ale dveřmi jí neprošla ani hlava.
  +   
  +   

  
   
  
  
  

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

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

[keiron]

keiron  02/05/21 05:09:04

  Modified:docs/xml-docs/fop embedding.xml
  Log:
  added a bit of info about using xalan
  
  Revision  ChangesPath
  1.19  +15 -0 xml-fop/docs/xml-docs/fop/embedding.xml
  
  Index: embedding.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/embedding.xml,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- embedding.xml 19 May 2002 16:34:07 -  1.18
  +++ embedding.xml 21 May 2002 12:09:04 -  1.19
  @@ -130,6 +130,21 @@
   
 
 
  +
  + 
  +You may want to supply you input to FOP from different data sources.
  +For example you may have a DOM and XSL stylesheet or you may want to
  +set variables in the stylesheet. The page here:
  +http://xml.apache.org/xalan-j/usagepatterns.html";>
  +http://xml.apache.org/xalan-j/usagepatterns.html describes
  +how you can do these things.
  + 
  + 
  +You can use the content handler from the driver to create a SAXResult.
  +The transformer then can fire SAX events on the content handler which
  +will in turn create the rendered output.
  + 
  +


   If FOP is going to be used multiple times within your application
  
  
  

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

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

[jeremias]

jeremias02/05/19 09:34:40

  Modified:docs/xml-docs/fop Tag: fop-0_20_2-maintain embedding.xml
  Log:
  Corrected little omission.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.11.2.3  +1 -1  xml-fop/docs/xml-docs/fop/embedding.xml
  
  Index: embedding.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/embedding.xml,v
  retrieving revision 1.11.2.2
  retrieving revision 1.11.2.3
  diff -u -r1.11.2.2 -r1.11.2.3
  --- embedding.xml 2 Mar 2002 17:40:26 -   1.11.2.2
  +++ embedding.xml 19 May 2002 16:34:40 -  1.11.2.3
  @@ -34,7 +34,7 @@
   
   
 You also need to set the Logger for logging messages, see
  
  
  

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

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

[jeremias]

jeremias02/05/19 09:34:07

  Modified:docs/xml-docs/fop embedding.xml
  Log:
  Corrected little omission.
  
  Revision  ChangesPath
  1.18  +1 -1  xml-fop/docs/xml-docs/fop/embedding.xml
  
  Index: embedding.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/embedding.xml,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- embedding.xml 11 Apr 2002 09:33:24 -  1.17
  +++ embedding.xml 19 May 2002 16:34:07 -  1.18
  @@ -34,7 +34,7 @@
   
   
 You also need to set up logging. Global logging for all FOP
  
  
  

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

cvs commit: xml-fop/docs/xml-docs/fop track.png readme.xml

[keiron]

keiron  02/05/16 01:37:09

  Modified:docs/xml-docs/fop readme.xml
  Added:   docs/xml-docs/fop track.png
  Log:
  added status info to main page
  
  Revision  ChangesPath
  1.20  +25 -0 xml-fop/docs/xml-docs/fop/readme.xml
  
  Index: readme.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/readme.xml,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- readme.xml17 Mar 2002 17:43:55 -  1.19
  +++ readme.xml16 May 2002 08:37:09 -  1.20
  @@ -72,6 +72,31 @@
   along with the xml.
   
 
  +  
  +
  +
  +
  +
  +This is the development status of FOP. A branch has been created for
  +maintenance releases while the development is done to address various
  +performance and design issues.
  +
  +
  +Maintenance releases will be done as necessary. Another maintenance release
  +is planned for the near future to provide some fixes and to provide
  +compatibilty with http://xml.apache.org/batik/";>Batik
  +version 1.5 beta2. Other changes are: new hyphentaion patterns, changed
  +to use Avalon Logger interface and added background image support.
  +
  +
  +Development for 1.0DR1 is addressing the design issues for layout and
  +performance. This is focusing on making it possible to be conformant
  +to the spec and be able to handle large documents. This is roughly
  +30% towards a developers release that should have: similar functionality to
  +previous FOP releases, a rough API and a suitable design for developers
  +to work on more functionality.
  +
  +  
 
   The goals of the Apache XML FOP Project are to deliver an XSL FO->PDF 
formatter that is compliant to at least the Basic
  conformance level described in the W3C Recommendation from 15 October 2001, 
and that complies with the 11 March 1999 Portable Document
  
  
  
  1.1      xml-fop/docs/xml-docs/fop/track.png
  
<>
  
  

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

Re: cvs commit: xml-fop/docs/xml-docs xml2pdf.xsl

[dirkx]

Sorry for the delay - this got stuck in a moderator queue - and I missed
it as it had the same size, down to the last byte, as a spam message I got
on -all- asf accounts.

Dw

-- 
Dirk-Willem van Gulik

On 5 May 2002 [EMAIL PROTECTED] wrote:

> jeremias02/05/05 05:17:42
>
>   Modified:docs Tag: fop-0_20_2-maintain xml2pdf.xsl
>    docs/xml-docs Tag: fop-0_20_2-maintain xml2pdf.xsl
>   Log:
>   Changed master-name to master-reference.
>
>   Revision  ChangesPath
>   No   revision
>
>
>   No   revision
>
>
>   1.4.4.1   +1 -1  xml-fop/docs/xml2pdf.xsl
>
>   Index: xml2pdf.xsl
>   ===
>   RCS file: /home/cvs/xml-fop/docs/xml2pdf.xsl,v
>   retrieving revision 1.4
>   retrieving revision 1.4.4.1
>   diff -u -r1.4 -r1.4.4.1
>   --- xml2pdf.xsl 16 Dec 2000 22:48:48 -  1.4
>   +++ xml2pdf.xsl 5 May 2002 12:17:41 -   1.4.4.1
>   @@ -21,7 +21,7 @@
>   
>   
>
>   -   
>   +   
>   
>  font-size="10pt"
>
>
>
>   No   revision
>
>
>   No   revision
>
>
>   1.9.2.1   +1 -1  xml-fop/docs/xml-docs/xml2pdf.xsl
>
>   Index: xml2pdf.xsl
>   ===
>   RCS file: /home/cvs/xml-fop/docs/xml-docs/xml2pdf.xsl,v
>   retrieving revision 1.9
>   retrieving revision 1.9.2.1
>   diff -u -r1.9 -r1.9.2.1
>   --- xml2pdf.xsl 20 Aug 2001 16:19:58 -  1.9
>   +++ xml2pdf.xsl 5 May 2002 12:17:41 -   1.9.2.1
>   @@ -37,7 +37,7 @@
>   
>   
>
>   -   
>   +   
>   
>  font-size="10pt"
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


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

cvs commit: xml-fop/docs/xml-docs xml2pdf.xsl

[jeremias]

jeremias02/05/05 05:17:42

  Modified:docs Tag: fop-0_20_2-maintain xml2pdf.xsl
   docs/xml-docs Tag: fop-0_20_2-maintain xml2pdf.xsl
  Log:
  Changed master-name to master-reference.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.4.4.1   +1 -1  xml-fop/docs/xml2pdf.xsl
  
  Index: xml2pdf.xsl
  ===
  RCS file: /home/cvs/xml-fop/docs/xml2pdf.xsl,v
  retrieving revision 1.4
  retrieving revision 1.4.4.1
  diff -u -r1.4 -r1.4.4.1
  --- xml2pdf.xsl   16 Dec 2000 22:48:48 -  1.4
  +++ xml2pdf.xsl   5 May 2002 12:17:41 -   1.4.4.1
  @@ -21,7 +21,7 @@


   
  - 
  + 



   
  - 
  + 

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

[pbwest]

pbwest  02/04/28 06:54:40

  Modified:docs/design/alt.design book.xml
  Log:
  Added keeps and spaces
  
  Revision  ChangesPath
  1.3   +2 -0  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.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- book.xml  27 Mar 2002 07:59:56 -  1.2
  +++ book.xml  28 Apr 2002 13:54:40 -  1.3
  @@ -8,6 +8,8 @@
 
 
 
  +  
  +  
 
 
 
  
  
  

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

cvs commit: xml-fop/docs/design/alt.design keeps.xml spaces.xml

[pbwest]

pbwest  02/04/28 06:27:44

  Added:   docs/design/alt.design keeps.xml spaces.xml
  Log:
  Adding documents to ALT DESIGN
  
  Revision  ChangesPath
  1.1  xml-fop/docs/design/alt.design/keeps.xml
  
  Index: keeps.xml
  ===
  
  
  
  
  

  Keeps and breaks
  

  


  
  

The layout galleys and the
layout tree
which is their context have been discussed elsewhere.  Here we
discuss a possible method of implementing keeps and breaks
within the context of layout galleys and the layout tree.



  Breaks may be handled by inserting a column- or page-break
  pseudo-object into the galley stream.  For break-before, the
  object would be inserted before the area in which the flow
  object, to which the property is attached, is leading.  If
  the flow object is leading in no ancestor context, the
  pseudo-object is inserted before the object itself.
  Corresponding considerations apply for break-after.
  Selection of the position for these objects will be further
  examined in the discussion on keeps. 




  Conceptually, all keeps can be represented by a
  keep-together pseudo-area.  The keep-together property
  itself is expressed during layout by wrapping all of the
  generated areas in a keep-together area.  Keep-with-previous
  on formatting object A becomes a keep-together area spanning
  the first non-blank normal area leaf node, L, generated by A
  or its offspring, and the last non-blank normal area leaf
  node preceding L in the area tree.  Likewise, keep-with-next
  on formatting object A becomes a keep-together area spanning
  the last non-blank normal area leaf node, L, generated by A
  or its offspring, and the first non-blank normal area leaf
  node following L in the area tree.
  TODO REWORK THIS for block vs inline


  The obvious problem with this arrangement is that the
  keep-together area violate the hierarachical arrangement of
  the layout tree.  They form a concurrent structure focussed
  on the leaf nodes.  This seems to be the essential problem
  of handling keep-with-(previous/next); that it cuts across
  the otherwise tree-structured flow of processing.  Such
  problems are endemic in page layout.


  In any case, it seems that the relationships between areas
  that are of interest in keep processing need some form of
  direct expression, parallel to the layout tree itself.
  Restricting ourselves too block-level elements, and looking
  only at the simple block stacking cases, we get a diagram
  like the attached PNG.  In order to track the relationships
  through the tree, we need four sets of links.


  Figure 1




  The three basic links are:


  
  Leading edge to leading edge of first normal child.
  Trailing edge to leading edge of next normal
sibling.
  Trailing edge to trailing edge of parent.


  Superimposed on the basic links are bridging links which
  span adjacent sets of links.  These spanning links are the
  tree violators, and give direct access to the areas which
  are of interest in keep processing. They could be
  implemented as double-linked lists, either within the layout
  tree nodes or as separate structures.  Gaps in the spanning
  links are joined by simply reproducing the single links, as
  in the diagram. The whole layout tree for a page is
  effectively threaded in order of interest, as far as keeps
  are concerned.


  The bonus of this structure is that it looks like a superset
  of the stacking constraints.  It gives direct access to all
  sets of adjacent edges and sets of edges whose space
  specifiers need to be resolved. Fences can be easily enough
  detected during the process of space resolution.


  

  
  
  
  
  1.1  xml-fop/docs/design/alt.design/spaces.xml
  
  Index: spaces.xml
  ===
  
  
  
  
  

  Keeps and space-specifiers
  

  


  
  

The layout galleys and the
layout tree
which is the context of this discussion have been discussed
elsewhere.  A previous document
discussed data structures which might facilitate the lining of

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

[pbwest]

pbwest  02/04/28 06:14:45

  Modified:docs/design/alt.design traits.xml
  Log:
  Format of multiple entries tidied up.
  
  Revision  ChangesPath
  1.3   +43 -118   xml-fop/docs/design/alt.design/traits.xml
  
  Index: traits.xml
  ===
  RCS file: /home/cvs/xml-fop/docs/design/alt.design/traits.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- traits.xml28 Mar 2002 06:58:13 -  1.2
  +++ traits.xml28 Apr 2002 13:14:45 -  1.3
  @@ -1,5 +1,5 @@
   
  -
  +
   
  @@ -29,7 +29,10 @@
 
   http://www.w3.org/TR/xsl/slice4.html#area-common";
  ->4.2.2 Common Traits
  +   >4.2.2 Common Traits
  +http://www.w3.org/TR/xsl/slice7.html#writing-mode";
  +>7.27.7 writing-mode
 
 
   
   
   
  -  
  -  
  -http://www.w3.org/TR/xsl/slice7.html#writing-mode";
  ->7.27.7 writing-mode
  -  
  -
  -
 inline-progression-direction
 All areas
 
   http://www.w3.org/TR/xsl/slice4.html#area-common";
  ->4.2.2 Common Traits
  +>4.2.2 Common Traits
  +http://www.w3.org/TR/xsl/slice7.html#writing-mode";
  +>7.27.7 writing-mode
 
 
   
   
   
  -  
  -  
  -http://www.w3.org/TR/xsl/slice7.html#writing-mode";
  ->7.27.7 writing-mode
  -  
  -
  -
 shift-direction
 Inline areas
   
  @@ -77,69 +67,38 @@
 
   http://www.w3.org/TR/xsl/slice4.html#area-common";
  ->4.2.2 Common Traits
  -  
  -  
  -http://www.w3.org/TR/xsl/slice7.html#glyph-orientation-horizontal";
  ->7.27.2 glyph-orientation-horizontal
  -  
  -
  - 
  -  
  -  
  +>4.2.2 Common Traits
   http://www.w3.org/TR/xsl/slice4.html#area-glyph";
  ->4.6.2 Glyph-areas
  -  
  -  
  -http://www.w3.org/TR/xsl/slice7.html#glyph-orientation-vertical";
  ->7.27.3 glyph-orientation-vertical
  -  
  - 
  - 
  -  
  -  
  +>4.6.2 Glyph-areas
   http://www.w3.org/TR/xsl/slice4.html#area-linebuild";
  ->4.7.2 Line-building
  -  
  -  
  -http://www.w3.org/TR/xsl/slice7.html#direction";
  ->7.27.1 direction
  -  
  - 
  - 
  -  
  -  
  +>4.7.2 Line-building
   http://www.w3.org/TR/xsl/slice4.html#rend-intrinsic";
  ->4.9.5 Intrinsic Marks
  -  
  -  
  -http://www.w3.org/TR/xsl/slice7.html#writing-mode";
  ->7.27.7 writing-mode
  -  
  - 
  - 
  -  
  -  
  +>4.9.5 Intrinsic Marks
   http://www.w3.org/TR/xsl/slice7.html#font-model";
  ->7.8.1 Fonts and Font Data
  -  
  - 
  - 
  -  
  -  
  +>7.8.1 Fonts and Font Data
   http://www.w3.org/TR/xsl/slice7.html#writing-mode-related";
   >7.27 Writing-mode-related Properties
 
  - 
  +  
  +http://www.w3.org/TR/xsl/slice7.html#glyph-orientation-horizontal";
  +>7.27.2 glyph-orientation-horizontal
  +http://www.w3.org/TR/xsl/slice7.html#glyph-orientation-vertical";
  +>7.27.3 glyph-orientation-vertical
  + http://www.w3.org/TR/xsl/slice7.html#direction";
  +>7.27.1 direction
  +http://www.w3.org/TR/xsl/slice7.html#writing-mode";
  +>7.27.7 writing-mode
  +  
  +
   
 is-reference-area
 All areas
  @@ -148,55 +107,21 @@
   
"http://www.w3.org/TR/xsl/slice5.html#section-N6691-Non-property-Based-Trait-Generation";
   >5.6 Non-property Based Trait Generation
 
  -  Set "true" on:
  -
  -
  -  
  -  simple-page-master
  -
  -
  -  
  -  title
  -
  -
  -  
  -  region-body
  -
  -
  -  
  -  region-before
  -
  -
  -  
  -  region-after
  -
  -
  -  
  -  region-start
  -
  -
  -  
  -

cvs commit: xml-fop/docs/design/alt.design dirlist.html

[pbwest]

pbwest  02/04/28 05:54:07

  Removed: docs/design/alt.design dirlist.html
  Log:
  Unnecessary file

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

cvs commit: xml-fop/docs/design/alt.design line-area-5.dia line-area-6.dia

[pbwest]

pbwest  02/04/28 01:17:40

  Added:   docs/design/alt.design line-area-5.dia line-area-6.dia
  Log:
  Dia editable version of png
  
  Revision  ChangesPath
  1.1  xml-fop/docs/design/alt.design/line-area-5.dia
  
<>
  
  
  1.1  xml-fop/docs/design/alt.design/line-area-6.dia
  
<>
  
  

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

cvs commit: xml-fop/docs/design/alt.design coroutines.dia

[pbwest]

pbwest  02/04/28 01:15:10

  Added:   docs/design/alt.design coroutines.dia
  Log:
  Dia editable version of png
  
  Revision  ChangesPath
  1.1  xml-fop/docs/design/alt.design/coroutines.dia
  
<>
  
  

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

cvs commit: xml-fop/docs/design/alt.design initial-column-values.dia

[pbwest]

pbwest  02/04/28 01:12:09

  Added:   docs/design/alt.design initial-column-values.dia
  Log:
  Editable version of corresponding png
  
  Revision  ChangesPath
  1.1  xml-fop/docs/design/alt.design/initial-column-values.dia
  
<>
  
  

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

cvs commit: xml-fop/docs/design/alt.design block-stacking-constraints.fig block-stacking-constraints.png block-stacking-keeps.fig block-stacking-keeps.png block-stacking.fig block-stacking.png

[pbwest]

pbwest  02/04/28 01:07:18

  Added:   docs/design/alt.design block-stacking-constraints.fig
block-stacking-constraints.png
block-stacking-keeps.fig block-stacking-keeps.png
block-stacking.fig block-stacking.png
  Log:
  Image files for ALT DESIGN spaces and keeps documents
  
  Revision  ChangesPath
  1.1  xml-fop/docs/design/alt.design/block-stacking-constraints.fig
  
  Index: block-stacking-constraints.fig
  ===
  #FIG 3.2
  Landscape
  Center
  Inches
  Letter  
  100.00
  Single
  -2
  1200 2
  6 300 4575 1350 6300
  2 2 0 2 0 7 70 0 20 0.000 0 0 -1 0 0 5
 375 4650 1275 4650 1275 4875 375 4875 375 4650
  2 2 0 2 0 27 80 0 20 0.000 0 0 -1 0 0 5
 375 5100 1275 5100 1275 5325 375 5325 375 5100
  2 2 0 2 0 11 90 0 20 0.000 0 0 -1 0 0 5
 375 5550 1275 5550 1275 5775 375 5775 375 5550
  2 2 0 2 0 14 100 0 20 0.000 0 0 -1 0 0 5
 375 6000 1275 6000 1275 6225 375 6225 375 6000
  -6
  6 7575 2325 10425 5100
  2 2 0 2 0 14 100 0 20 0.000 0 0 -1 0 0 5
 7650 2400 10350 2400 10350 5025 7650 5025 7650 2400
  2 2 0 2 0 7 60 0 20 0.000 0 0 -1 0 0 5
 8175 2925 9825 2925 9825 3600 8175 3600 8175 2925
  2 2 0 2 0 14 70 0 20 0.000 0 0 -1 0 0 5
 8025 2775 9975 2775 9975 3750 8025 3750 8025 2775
  2 2 0 2 0 7 80 0 20 0.000 0 0 -1 0 0 5
 7950 2700 10050 2700 10050 4725 7950 4725 7950 2700
  4 0 0 50 0 2 18 0. 4 195 165 8850 4350 P\001
  4 0 0 50 0 2 18 0. 4 195 180 8850 3300 B\001
  -6
  6 6975 5400 10725 6225
  2 1 0 4 0 7 50 0 -1 0.000 0 0 -1 0 0 2
 7050 6150 8175 6150
  2 2 0 6 19 7 55 0 -1 0.000 0 0 -1 0 0 5
 7125 5475 8175 5475 8175 5700 7125 5700 7125 5475
  4 0 0 50 0 0 16 0. 4 165 1470 8400 6225 Fence before P\001
  4 0 0 50 0 0 16 0. 4 225 2265 8400 5700 Stacking constraint A,B\001
  -6
  6 2850 5400 6450 6300
  2 2 0 4 4 7 50 0 -1 0.000 0 0 -1 0 0 5
 2925 5475 3975 5475 3975 5700 2925 5700 2925 5475
  2 2 0 4 5 7 50 0 -1 0.000 0 0 -1 0 0 5
 2925 6000 3975 6000 3975 6225 2925 6225 2925 6000
  4 0 0 50 0 0 16 0. 4 225 2220 4200 6225 Stacking constraint P,B\001
  4 0 0 50 0 0 16 0. 4 225 2250 4200 5700 Stacking constraint A,P\001
  -6
  2 2 0 2 0 7 70 0 20 0.000 0 0 -1 0 0 5
 1125 1275 2625 1275 2625 1950 1125 1950 1125 1275
  2 2 0 2 0 27 80 0 20 0.000 0 0 -1 0 0 5
 900 1050 2850 1050 2850 2175 900 2175 900 1050
  2 2 0 2 0 11 90 0 20 0.000 0 0 -1 0 0 5
 750 900 3000 900 3000 2325 750 2325 750 900
  2 2 0 2 0 14 100 0 20 0.000 0 0 -1 0 0 5
 525 675 3225 675 3225 2550 525 2550 525 675
  2 2 0 2 0 7 70 0 20 0.000 0 0 -1 0 0 5
 4200 825 6600 825 6600 2175 4200 2175 4200 825
  2 2 0 2 0 14 100 0 20 0.000 0 0 -1 0 0 5
 4050 675 6750 675 6750 2325 4050 2325 4050 675
  2 2 0 2 0 7 70 0 20 0.000 0 0 -1 0 0 5
 7800 825 10200 825 10200 2175 7800 2175 7800 825
  2 2 0 2 0 14 100 0 20 0.000 0 0 -1 0 0 5
 7650 675 10350 675 10350 2325 7650 2325 7650 675
  2 2 0 4 4 7 50 0 -1 0.000 0 0 -1 0 0 5
 375 2325 3375 2325 3375 2775 375 2775 375 2325
  2 2 0 2 0 7 70 0 20 0.000 0 0 -1 0 0 5
 675 2775 3075 2775 3075 4125 675 4125 675 2775
  2 2 0 2 0 14 100 0 20 0.000 0 0 -1 0 0 5
 525 2625 3225 2625 3225 4275 525 4275 525 2625
  2 2 0 4 5 7 50 0 -1 0.000 0 0 -1 0 0 5
 3900 2775 6900 2775 6900 2925 3900 2925 3900 2775
  2 1 0 4 0 7 50 0 -1 0.000 0 0 -1 0 0 2
 3825 2700 6975 2700
  2 2 0 4 4 7 50 0 -1 0.000 0 0 -1 0 0 5
 3900 2175 6900 2175 6900 2550 3900 2550 3900 2175
  2 2 0 2 0 14 100 0 20 0.000 0 0 -1 0 0 5
 4050 2400 6750 2400 6750 5025 4050 5025 4050 2400
  2 2 0 2 0 7 60 0 20 0.000 0 0 -1 0 0 5
 4575 2925 6225 2925 6225 3600 4575 3600 4575 2925
  2 2 0 2 0 14 70 0 20 0.000 0 0 -1 0 0 5
 4425 2775 6375 2775 6375 3750 4425 3750 4425 2775
  2 2 0 2 0 7 80 0 20 0.000 0 0 -1 0 0 5
 4350 2700 6450 2700 6450 4725 4350 4725 4350 2700
  2 2 0 2 0 27 90 0 20 0.000 0 0 -1 0 0 5
 4200 2550 6600 2550 6600 4875 4200 4875 4200 2550
  2 2 0 6 19 7 55 0 -1 0.000 0 0 -1 0 0 5
 7350 2175 10650 2175 10650 2925 7350 2925 7350 2175
  2 2 0 4 5 7 50 0 -1 0.000 0 0 -1 0 0 5
 7500 2775 10500 2775 10500 2925 7500 2925 7500 2775
  2 2 0 4 4 7 50 0 -1 0.000 0 0 -1 0 0 5
 7500 2175 10500 2175 10500 2700 7500 2700 7500 2175
  4 0 0 50 0 0 18 0. 4 255 225 525 375 a)\001
  4 0 0 50 0 0 18 0. 4 255 240 4050 375 b)\001
  4 0 0 50 0 0 18 0. 4 255 225 7650 375 c)\001
  4 0 0 50 0 0 16 0. 4 225 1725 1425 4875 Content rectangle\001
  4 0 0 50 0 0 16 0. 4 165 690 1425 5325 Border\001
  4 0 0 50 0 0 16 0. 4 225 720 1425 6225 Spaces\001
  4 0 0 50 0 0 16 0. 4 225 780 1425 5775 Padding\001
  4 0 0 50 0 2 18 0. 4 195 195 1725 1725 A\001
  4 0 0 50 0 2 18 0. 4 195 195 5250 1575 A\001
  4