RE: Getting breaks: revisited

[Keiron Liddle]

On Fri, 2002-11-15 at 19:48, Victor Mote wrote:
> Just to be clear, I should point out that there is not a layout that is
> impossible to perform. The standard allows (and would have to)
> implementation-specific handling of what they call "over-constrained"
> requirements. In other words, requirements can be prioritized and allowed to
> slip when they are contradictory or "impossible".
> 
> >From a design standpoint, the best ideas I have seen/heard revolve around
> some scoring system. I think the HZ program, TeX, and Lout all use this
> approach. To do this, you would need for each break manager to return not
> just the best break, but a collection of possible breaks with some ranking
> mechanism. Ideally, somebody at the highest level (page-sequence) decides
> what is best, based on information that percolates up from the lower levels.
> This implies to me that we can see the entire page-sequence sub-tree at one
> time, which may not be true in our SAX event-based model. It seems that the
> page-sequence would attempt to lay itself out using the "best" breaks that
> came up from sub-nodes, then adjust if over-constrained, perhaps with the
> concept of a layout Plan or Proposal.

The idea of the best break is that it is the best break, not just an
allowed break.
So if there is a block with keep together always it could have the best
break inside it simply because the previous best break was also a keep
always and it was further from the optimum distance.

The key is, as you put it, percolate the information up from the lower
levels. We don't want to do it for every single possible break but in
some cases it does need to do that.

I am sure I know how to find the best break in a page, the problem is
how to write code to do that when there are lots of difficult things
like floats, footnotes, page columns etc.

> I know it is easier said than done, and may already be done. Please pardon
> my ignorance of the current design. I would offer it as my $.02 worth, but
> someone would want a nickel change ($.05).



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

DO NOT REPLY [Bug 14576] - [PATCH] fsize in FontFileReader is not set

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14576

[PATCH] fsize in FontFileReader is not set





--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 10:04 ---
Sorry, I forgot to send attchment.
I'm at work now, and I can access the CVS now.
I can send a patch at 7PM CET.
but it so easy that I dive the detail here

in package org.apache.fop.fonts, class FontFileReader, 
you must add the following line 

this.fsize= this.file.length; 

in the private void init(InputStream in) method.

It must be like this:
private void init(InputStream in) throws java.io.IOException {
java.io.ByteArrayOutputStream bout = new java.io.ByteArrayOutputStream
();
try {
copyStream(in, bout);
this.file = bout.toByteArray();
this.fsize= this.file.length;// PATCH to avoid EOFException
} finally {
bout.close();
}
}


many thanks ansd sorry for the attachment,
Bernard

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

DO NOT REPLY [Bug 13295] - different results using xml or fo (from the same xml-file)

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13295

different results using xml or fo (from the same xml-file)





--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 10:32 ---
Provide an example (xml + xsl) illustrating the problem, please.

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

cvs commit: xml-fop/src/org/apache/fop/fonts FontFileReader.java

[jeremias]

jeremias2002/11/18 02:44:42

  Modified:src/org/apache/fop/fonts Tag: fop-0_20_2-maintain
FontFileReader.java
  Log:
  Fixed Bug 14576
  EOFException in TTFReader (fsize in FontFileReader is not set)
  Submitted by: [EMAIL PROTECTED]
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.3.2.2   +4 -2  xml-fop/src/org/apache/fop/fonts/FontFileReader.java
  
  Index: FontFileReader.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/fonts/FontFileReader.java,v
  retrieving revision 1.3.2.1
  retrieving revision 1.3.2.2
  diff -u -r1.3.2.1 -r1.3.2.2
  --- FontFileReader.java   8 Nov 2002 10:25:26 -   1.3.2.1
  +++ FontFileReader.java   18 Nov 2002 10:44:41 -  1.3.2.2
  @@ -1,6 +1,6 @@
   /*
* $Id$
  - * Copyright (C) 2001 The Apache Software Foundation. All rights reserved.
  + * Copyright (C) 2001-2002 The Apache Software Foundation. All rights reserved.
* For details on use and redistribution please refer to the
* LICENSE file included with these sources.
*/
  @@ -30,6 +30,8 @@
   try {
   copyStream(in, bout);
   this.file = bout.toByteArray();
  +this.fsize = this.file.length;
  +this.current = 0;
   } finally {
   bout.close();
   }
  
  
  

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

DO NOT REPLY [Bug 14576] - [PATCH] fsize in FontFileReader is not set

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14576

[PATCH] fsize in FontFileReader is not set

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 10:47 ---
I've just applied your patch to the maint branch. Thanks a lot.

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

Re: patch process

[Oleg Tkachenko]

Ralph LaChance wrote:


I believe it makes sense to add the changes to the maintenance
branch (in the event that there is ever an 0.20.5 release);
in turn, they will be useful to inform the awt and awt/print renderer
in the redesign, so I'll separately submit them to there if necessary.


Make sense, but what's wrong with one bugzilla entry?


It's been a while since I've sent in patches, and wanted to check
whether the preferred course is to submit the full sources (it affects
3 source files), or only diffs. And, if diffs, should they be
against current CVS or against the 0.20.4 release.


diffs are prefered and surely against current cvs (fop-0_20_2-maintain branch).


btw: Seems to me that
http://xml.apache.org/dist/fop/
used to contain daily (twice daily?) snapshots
of the latest source-in-progress. Did that change?


No, that page is about FOP releases, snapshots are available at 
http://cvs.apache.org/snapshots/xml-fop, but afaik these are snapshots of the 
trunk.

--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel


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

Re: patch process

[Christian Geisert]

Ralph LaChance wrote:

Hi all,

I've worked out (and will submit via bugzilla) both
an explanation and a solution to the text measuring & layout
problems that I reported recently in the awt and
awt/print renderers.


Great.


I believe it makes sense to add the changes to the maintenance
branch (in the event that there is ever an 0.20.5 release);


Sure .. RC should be out this week.


in turn, they will be useful to inform the awt and awt/print renderer
in the redesign, so I'll separately submit them to there if necessary.

It's been a while since I've sent in patches, and wanted to check
whether the preferred course is to submit the full sources (it affects
3 source files), or only diffs. And, if diffs, should they be
against current CVS or against the 0.20.4 release.


diff -u against current maintenance branch would be the best.


btw: Seems to me that
http://xml.apache.org/dist/fop/
used to contain daily (twice daily?) snapshots
of the latest source-in-progress. Did that change?


http://cvs.apache.org/snapshots/xml-fop/
We should add this to the documentation...

Christian


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

Re: patch process

[Oleg Tkachenko]

Christian Geisert wrote:


http://cvs.apache.org/snapshots/xml-fop/
We should add this to the documentation...


http://xml.apache.org/fop/download.html mentions it already.

--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel


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

Re: patch process

[Christian Geisert]

Oleg Tkachenko wrote:

Christian Geisert wrote:


http://cvs.apache.org/snapshots/xml-fop/
We should add this to the documentation...


http://xml.apache.org/fop/download.html mentions it already.


Doh .. well .. Ralph should really RTFM ;-)

Christian


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

Re: Frustration With FOP

[Oleg Tkachenko]

W. Eliot Kimber wrote:


I feel a need to say something about my frustration with FOP, because I
think it's a potential issue for the XSL FO world in general and it
concerns me, especially as a person who's working very hard to try to
advance the acceptance and use of FO, both through educating potential
users and working with the various implementations to identify flaws and
suggest improvements.


I'm personally very appreciate what are you doing for xsl-fo, Eliot and I 
understand your frustration, but you see, we are rather small team and we do 
our best. Unfortunately FOP doesn't have such a support from software giants 
like, for example, xalan project have so our resources are very limited.

My fear, already borne out by some personal experience, is that FOP will
give people a bad first impression of XSL FO, making them think that FO
is much more limited than it is.  We've already seen a number of posts
to the various FO-related forums where people have confused FOP and
XSL-FO, thinking that a limitation in the current version of FOP is a
limitation in XSL-FO generally.


Well, seems to me your opinion is a good argument for input validation module 
I was talked about recently. We desperately need a module at the input to 
report validation errors, unimplemented warnings etc in a human readable form. 
dtd and schema validation doesn't fit the needs, but schematron schema fits 
perfectly. As afaik xsl-fo schematron schema doesn't exist yet (XEP3 uses 
schematron-like xsl for validation) I'm trying to develop such one. So it's a 
matter of time.
+ documentation, which is updated already.
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel


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

Re: patch process

[Ralph LaChance]

At 07:05 AM 11/18/02, you wrote:

Oleg Tkachenko wrote:

Christian Geisert wrote:


http://cvs.apache.org/snapshots/xml-fop/
We should add this to the documentation...

http://xml.apache.org/fop/download.html mentions it already.


Doh .. well .. Ralph should really RTFM ;-)


I did - about 2 years ago.
"Senior moments" come more often that that these days ;-)
-Ralph



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

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

[keiron]

keiron  2002/11/18 04:47:16

  Modified:src/documentation/content/xdocs bugs.xml
  Log:
  better links to Bugzilla.
  reorganized content into a checklist.
  Submitted by: [EMAIL PROTECTED] (Victor Mote)
  
  Revision  ChangesPath
  1.2   +48 -15xml-fop/src/documentation/content/xdocs/bugs.xml
  
  Index: bugs.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/bugs.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- bugs.xml  4 Nov 2002 16:20:51 -   1.1
  +++ bugs.xml  18 Nov 2002 12:47:16 -  1.2
  @@ -7,20 +7,53 @@
 
 
   
  -  How to report bugs
  -Please report bugs to http://nagoya.apache.org/bugzilla/";>bugzilla, the Apache bug
  -   database. A copy of your bug report is sent automatically to the discussion 
list [EMAIL PROTECTED] 
  -Please make sure, before you report a bug, that it is not mentioned in the 
FAQ or
  -   in the list of open bugs at bugzilla.
  -Please make your description as concise as possible and add an example fo 
  -   file with your report, which just demonstrates the problem. Thanks for your 
help!
  -  
  -  
  -Known bugs
  -A list of known bugs can be found at
  -   http://nagoya.apache.org/bugzilla/";>bugzilla.
  -  
  -
  +  Bugs Already Reported
  +  A list of unresolved reported bugs can be found at
  +http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Fop&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=bugs.component";>FOP
  +Open Bugs (Bugzilla).
  +
  +
  +  Reporting New Bugs
  +  User reports of bugs and requests for enhancements are extremely
  +important parts of FOP development, and we appreciate the time you take to help
  +us track these issues down.
  +To help us ensure that the bug database is as useful as it should be, please
  +use the following checklist if you are considering reporting a new bug:
  +
  +  Is your issue really a request to comply with some aspect of the
  +XSL-FO standard?
  +If so, please do not enter a bug report.
  +The developers already carefully track which standard requirements have been
  +implemented.
  +Other enhancement requests are welcome (although they are not technically
  +"bugs", they are entered and tracked in the same system -- just be sure to mark
  +the issue as an enhancement).
  +  Is your issue addressed by an http://xml.apache.org/fop/faq.html";>FAQ? If so, please do not
  +enter a bug report unless the FAQ did not adequately address your issue.
  +  Has this bug already been reported?
  +See section above for a list of bugs that have already been reported.
  +If the bug has already been reported, please do not open a new bug report.
  +Reporting the same bug twice will only slow the development team down.
  +However, if you have insight that may help developers track an existing problem,
  +please add comments and/or file attachments to the existing bug.
  +  Do you know how to write a good bug report?
  +Please review the
  +http://nagoya.apache.org/bugzilla/bugwritinghelp.html";>Apache Bug
  +Writing Guidelines before submitting your report.
  +  If, and only if, you have passed all of the above steps, please
  +enter a new bug report at
  +http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Fop";>The
  +FOP bug database (Bugzilla).
  +You will be asked to login to an existing Bugzilla account or to create a new
  +one.
  +When entering the bug report, please make your description complete and concise.
  +If appropriate, attach a minimal fo file to your report which demonstrates the
  +problem.
  +  After submission, a copy of your bug report will be automatically
  +sent to the FOP developer discussion list.
  +
  +
  +  
   
  -
   
  
  
  

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

DO NOT REPLY [Bug 14606] - [PATCH] changes to bugs.xml doc

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14606

[PATCH] changes to bugs.xml doc

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 12:51 ---
patch committed.
The changed dtd was not committed, mainly because I had some trouble with the 
patch and didn't put it in.
Should we instead change all dtd declarations for all xml documents to keep it 
consistent.

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

DO NOT REPLY [Bug 14637] New: - fo:retrieve-marker is confused by 2-columns reports

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14637

fo:retrieve-marker is confused by 2-columns reports

   Summary: fo:retrieve-marker is confused by 2-columns reports
   Product: Fop
   Version: 0.20.4
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: page-master/layout
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Overview Description:
  Consider a dictionary-like report with 2 columns and a header mentioning the 
  first and the last entry for one given page.
  To obtain the first item you'd call 
  
  

  while to obtain the last you'd call
  
  

  somewhere in your header.
  The marker "runningHeader" is set as the first block when processing a given 
  dictionary entry.
  
  What happens is that the last entry mentioned in the header of a given
  page is actually the first entry of the following page.
  
  The enclosed test case shows this misbehavior.  
  This bug is always reproducible.

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

Re: Frustration With FOP

[Nikolai Grigoriev]

Oleg,

> As afaik xsl-fo schematron schema doesn't exist yet (XEP3 uses 
> schematron-like xsl for validation) I'm trying to develop such one. 

If you feel that XEP's validation stylesheet may help - at least 
as a source of inspiration to write your Schematron schema -
please feel free to use it. The stylesheet is com/renderx/xep/folint.xsl
inside XEP's Jar file. We plan to make it a public resource, as soon
as we find spare time to present it on our website. 

Regards,

Nikolai Grigoriev
RenderX



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

DO NOT REPLY [Bug 14637] - fo:retrieve-marker is confused by 2-columns reports

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14637

fo:retrieve-marker is confused by 2-columns reports





--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 13:19 ---
Created an attachment (id=3875)
Test case

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

cvs commit: xml-fop/src/documentation forrest.diff

[keiron]

keiron  2002/11/18 06:11:29

  Modified:src/documentation forrest.diff
  Log:
  updated to current forrest
  faq linking to anchors now works
  
  Revision  ChangesPath
  1.2   +21 -13xml-fop/src/documentation/forrest.diff
  
  Index: forrest.diff
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/forrest.diff,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- forrest.diff  12 Nov 2002 09:12:36 -  1.1
  +++ forrest.diff  18 Nov 2002 14:11:29 -  1.2
  @@ -1,10 +1,10 @@
  -Index: src/resources/skins/forrest-site/xslt/fo/document2fo.xsl
  +Index: src/resources/skins/common/xslt/fo/document2fo.xsl
   ===
  -RCS file: 
/home/cvspublic/xml-forrest/src/resources/skins/forrest-site/xslt/fo/document2fo.xsl,v
  -retrieving revision 1.3
  -diff -u -r1.3 document2fo.xsl
   src/resources/skins/forrest-site/xslt/fo/document2fo.xsl 1 Nov 2002 02:49:58 
-   1.3
  -+++ src/resources/skins/forrest-site/xslt/fo/document2fo.xsl 8 Nov 2002 12:05:50 
-
  +RCS file: 
/home/cvspublic/xml-forrest/src/resources/skins/common/xslt/fo/document2fo.xsl,v
  +retrieving revision 1.2
  +diff -u -r1.2 document2fo.xsl
  +--- src/resources/skins/common/xslt/fo/document2fo.xsl   16 Nov 2002 22:58:50 
-  1.2
   src/resources/skins/common/xslt/fo/document2fo.xsl   18 Nov 2002 14:09:29 
-
   @@ -2,6 +2,7 @@

http://www.w3.org/1999/XSL/Transform";
  @@ -92,17 +92,15 @@



  -@@ -191,7 +233,12 @@
  -   NOTICE: 
  +@@ -192,6 +234,11 @@

  
  --
  -+
  ++
  

0
  @@ -133,13 +131,15 @@
  text-align="start">
  

  -@@ -456,7 +512,14 @@
  +@@ -456,7 +512,16 @@
  

  
   +
   +  
  -+
  ++
  ++  
  ++
   +  
   +  

  @@ -148,3 +148,11 @@
  

  
  +@@ -587,7 +652,6 @@
  +  []
  +
  +  
  +-
  + 
  + 
  + 
  
  
  

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

cvs commit: xml-fop/test createpdf.sh

[chrisg]

chrisg  2002/11/18 06:37:47

  Modified:.Tag: fop-0_20_2-maintain CHANGES build.bat build.sh
build.xml
   docs/examples Tag: fop-0_20_2-maintain runtests.bat
runtests.sh
   docs/examples/fo Tag: fop-0_20_2-maintain images.fo
   src/org/apache/fop/image Tag: fop-0_20_2-maintain
FopImageFactory.java
   src/org/apache/fop/messaging Tag: fop-0_20_2-maintain
MessageHandler.java
   src/org/apache/fop/pdf Tag: fop-0_20_2-maintain
PDFXObject.java
   src/org/apache/fop/tools/anttasks Tag: fop-0_20_2-maintain
Fop.java
   test Tag: fop-0_20_2-maintain createpdf.sh
  Added:   docs/graphics Tag: fop-0_20_2-maintain xml_fax.tif
   src/org/apache/fop/image Tag: fop-0_20_2-maintain
TiffImage.java
   src/org/apache/fop/pdf Tag: fop-0_20_2-maintain
CCFFilter.java
  Log:
  Added support for CCITT Group 4 encoded TIFF files
  Made JAI support dynamic (no recompile needed anymore)
  Submitted by: Manuel Mall <[EMAIL PROTECTED]> (see bug #13866)
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.10.2.27 +3 -0  xml-fop/CHANGES
  
  Index: CHANGES
  ===
  RCS file: /home/cvs/xml-fop/CHANGES,v
  retrieving revision 1.10.2.26
  retrieving revision 1.10.2.27
  diff -u -r1.10.2.26 -r1.10.2.27
  --- CHANGES   11 Nov 2002 18:30:15 -  1.10.2.26
  +++ CHANGES   18 Nov 2002 14:37:44 -  1.10.2.27
  @@ -1,6 +1,9 @@
   ==
   Done since 0.20.4 release
   
  +- Added support for CCITT Group 4 encoded TIFF files
  +  Made JAI support dynamic (no recompile needed anymore)
  +  Submitted by: Manuel Mall <[EMAIL PROTECTED]> (see bug #13866)
   - Fixed problem with jpegs with icc profile and acrobat reader 5 (Bug #11301)
 Submitted by: Stephan Neuhaus <[EMAIL PROTECTED]>
   - Fix bug in LinkSet.mergeLinks() (ArrayOutOfBoundsException when number of 
  
  
  
  1.14.2.9  +2 -0  xml-fop/build.bat
  
  Index: build.bat
  ===
  RCS file: /home/cvs/xml-fop/build.bat,v
  retrieving revision 1.14.2.8
  retrieving revision 1.14.2.9
  diff -u -r1.14.2.8 -r1.14.2.9
  --- build.bat 11 Nov 2002 10:24:39 -  1.14.2.8
  +++ build.bat 18 Nov 2002 14:37:45 -  1.14.2.9
  @@ -15,6 +15,8 @@
   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 ANT_HOME=%LIBDIR%
   
  
  
  
  1.15.2.12 +2 -0  xml-fop/build.sh
  
  Index: build.sh
  ===
  RCS file: /home/cvs/xml-fop/build.sh,v
  retrieving revision 1.15.2.11
  retrieving revision 1.15.2.12
  diff -u -r1.15.2.11 -r1.15.2.12
  --- build.sh  11 Nov 2002 10:24:38 -  1.15.2.11
  +++ build.sh  18 Nov 2002 14:37:45 -  1.15.2.12
  @@ -37,6 +37,8 @@
   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
   
   # antRun must be executable (can't do this in build.xml because Ant uses antRun
   # to do the chmod)
  
  
  
  1.44.2.27 +5 -3  xml-fop/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/xml-fop/build.xml,v
  retrieving revision 1.44.2.26
  retrieving revision 1.44.2.27
  diff -u -r1.44.2.26 -r1.44.2.27
  --- build.xml 11 Nov 2002 10:24:07 -  1.44.2.26
  +++ build.xml 18 Nov 2002 14:37:45 -  1.44.2.27
  @@ -212,7 +212,7 @@
   
   
   
  - 
  +
   
   
   
  @@ -223,7 +223,7 @@
   
   
   
  - 
  +
   
   
   
  @@ -236,6 +236,7 @@
   
   
   
  +
   
   
   
  @@ -356,6 +357,7 @@
   
   
 
  +  
   
 
   
  @@ -374,7 +376,7 @@
   
   
 
  +
excludes="**/${jimi},**/${jai},**/${tiff},**/${xsltransform},**/${trax},**/apps/TraxInputHandler.java"/>
 
   
   
  
  
  
  No   revision
  
  
  No   revision
  
  
  1.11.2.8  +2 -0  xml-fop/docs/examples/runtests.bat
  
  Index: runtests.bat
  

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

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13866

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





--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 15:09 
---
Thanks for your contribution.

I've committed everything except the change concerning relative URIs
(current code works for me under Linux)

Avalon-framework contains ConsoleLogger and examples are working out
of the box for me.

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

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

[keiron]

keiron  2002/11/18 07:54:16

  Modified:src/org/apache/fop/fo FONode.java Title.java
   src/org/apache/fop/fo/flow Block.java Flow.java Leader.java
ListItem.java
   src/org/apache/fop/fo/pagination PageSequence.java
   src/org/apache/fop/layoutmgr AbstractLayoutManager.java
BlockContainerLayoutManager.java
BlockLayoutManager.java BreakPoss.java
ContentLayoutManager.java FlowLayoutManager.java
InlineStackingLayoutManager.java LayoutManager.java
LineLayoutManager.java PageLayoutManager.java
StaticContentLayoutManager.java
   src/org/apache/fop/layoutmgr/list Item.java
ListBlockLayoutManager.java
ListItemLayoutManager.java
   src/org/apache/fop/layoutmgr/table Body.java Caption.java
Cell.java Row.java
TableAndCaptionLayoutManager.java
TableLayoutManager.java
  Log:
  set user agent on layout managers for values and logging
  improved break handling so that it breaks before overflow
  
  Revision  ChangesPath
  1.33  +5 -1  xml-fop/src/org/apache/fop/fo/FONode.java
  
  Index: FONode.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/FONode.java,v
  retrieving revision 1.32
  retrieving revision 1.33
  diff -u -r1.32 -r1.33
  --- FONode.java   15 Nov 2002 11:56:27 -  1.32
  +++ FONode.java   18 Nov 2002 15:54:13 -  1.33
  @@ -45,6 +45,10 @@
   userAgent = ua;
   }
   
  +public FOUserAgent getUserAgent() {
  +return userAgent;
  +}
  +
   public void setStructHandler(StructureHandler st) {
   }
   
  
  
  
  1.12  +3 -1  xml-fop/src/org/apache/fop/fo/Title.java
  
  Index: Title.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/Title.java,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- Title.java3 Sep 2002 11:45:13 -   1.11
  +++ Title.java18 Nov 2002 15:54:14 -  1.12
  @@ -35,11 +35,13 @@
   InlineStackingLayoutManager lm;
   lm = new InlineStackingLayoutManager(this,
new LMiter(children.listIterator()));
  +lm.setUserAgent(getUserAgent());
   lm.init();
   
   // get breaks then add areas to title
   
   ContentLayoutManager clm = new ContentLayoutManager(title);
  +clm.setUserAgent(getUserAgent());
   lm.setParentLM(clm);
   
   clm.fillArea(lm);
  
  
  
  1.65  +2 -1  xml-fop/src/org/apache/fop/fo/flow/Block.java
  
  Index: Block.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/flow/Block.java,v
  retrieving revision 1.64
  retrieving revision 1.65
  diff -u -r1.64 -r1.65
  --- Block.java15 Nov 2002 11:56:28 -  1.64
  +++ Block.java18 Nov 2002 15:54:14 -  1.65
  @@ -176,6 +176,7 @@
   
   public void addLayoutManager(List list) {
   BlockLayoutManager blm = new BlockLayoutManager(this);
  +blm.setUserAgent(getUserAgent());
   TextInfo ti = propMgr.getTextLayoutProps(fontInfo);
   blm.setBlockTextInfo(ti);
   list.add(blm);
  
  
  
  1.35  +4 -2  xml-fop/src/org/apache/fop/fo/flow/Flow.java
  
  Index: Flow.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/flow/Flow.java,v
  retrieving revision 1.34
  retrieving revision 1.35
  diff -u -r1.34 -r1.35
  --- Flow.java 20 Jun 2002 09:14:13 -  1.34
  +++ Flow.java 18 Nov 2002 15:54:14 -  1.35
  @@ -111,7 +111,9 @@
   }
   
   public void addLayoutManager(List list) {
  -list.add(new FlowLayoutManager(this));
  +FlowLayoutManager lm = new FlowLayoutManager(this);
  +lm.setUserAgent(getUserAgent());
  +list.add(lm);
   }
   
   }
  
  
  
  1.30  +3 -1  xml-fop/src/org/apache/fop/fo/flow/Leader.java
  
  Index: Leader.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/flow/Leader.java,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- Leader.java   15 Nov 2002 11:56:28 -  1.29
  +++ Leader.java   18 Nov 2002 15:54:14 -  1.30
  @@ -123,12 +123,14 @@
   InlineStackingLayoutManager lm;
   lm = new InlineStackingLayoutManager(this,
new LMiter(children.listIterator()));
  +lm.setUserAgent(getUserAgent());
   lm.i

Re: Frustration With FOP

[Oleg Tkachenko]

Nikolai Grigoriev wrote:


If you feel that XEP's validation stylesheet may help - at least
as a source of inspiration to write your Schematron schema -
please feel free to use it. The stylesheet is com/renderx/xep/folint.xsl
inside XEP's Jar file. We plan to make it a public resource, as soon
as we find spare time to present it on our website.


Thank you, Nikolai! I'll consider it, why not, at least XEP and FOP will have 
the same validation behaviour. But our nonimplemented stuff requires 
modifications of the xsl.

--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel


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

[PATCH] changes to bugs.xml doc

[Victor Mote]

Keiron Liddle wrote (while committing patch from "Bug" 14606):

> patch committed.
> The changed dtd was not committed, mainly because I had some
> trouble with the
> patch and didn't put it in.
> Should we instead change all dtd declarations for all xml
> documents to keep it
> consistent.

I did not realize until I looked right now that I failed to use the -u
option on my diff. Sorry about that.

Yes, we should change all of the declarations to be consistent. I'll go
ahead & do that en masse instead of piecemeal.

Victor Mote


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

Novice: Seeking to control PDF properties using xsl:FO

[Mike Connor]

Hey there,

 

I’m new to a lot of this stuff but gotta catch up
quick if I would like to continue eating, having a roof over my head etc J.

 

I need to investigate what PDF properties can be controlled
through FO (Example:  Locking during saves, what can be config’d/edited,
can I add custom toolbars to PDF from FO?)  and I barely know where to
start.  

Is it possible to have a PDF in a Web page and have a link
for say printing that would initiate a PDF print rather than a browser printer.

 

Any leads/pointers would be greatly appreciated.

 

Mike 

 

Testing

[Mike Connor]

Received?

 

Mike 

 

Received?

[Mike Connor]

 

 

Mike Connor

 

RE: Novice: Seeking to control PDF properties using xsl:FO

[Rhett Aultman]

It's 
my understanding that none of the things you've mentioned are actually part of 
the FO standard, since FO doesn't deal with the possible rendering formats that 
FO can be translated to.  How could any of the things you mentioned be 
applicable to an AWT rendering or a text rendering?  I haven't seen a part 
of the FO spec that deals with the things you're talking about, although I'm 
only a junior developer around here.
 
I 
think we've talked about special PDF extensions for FOP, too, but that doesn't 
really go anywhere because we have so much else to be doing.

  -Original Message-From: Mike Connor 
  [mailto:[EMAIL PROTECTED]]Sent: Monday, November 18, 2002 
  2:01 PMTo: [EMAIL PROTECTED]Subject: Novice: 
  Seeking to control PDF properties using xsl:FO
  
  Hey there,
   
  I’m new to a lot of this stuff but 
  gotta catch up quick if I would like to continue eating, having a roof over my 
  head etc J.
   
  I need to investigate what PDF 
  properties can be controlled through FO (Example:  Locking during saves, 
  what can be config’d/edited, can I add custom toolbars to PDF from FO?) 
   and I barely know where to start.  
  Is it possible to have a PDF in a 
  Web page and have a link for say printing that would initiate a PDF print 
  rather than a browser printer.
   
  Any leads/pointers would be 
  greatly appreciated.
   
  Mike 
  
   

Re: Novice: Seeking to control PDF properties using xsl:FO

[Oleg Tkachenko]

Mike Connor wrote:


I need to investigate what PDF properties can be controlled through FO 
(Example:  Locking during saves, what can be config’d/edited, can I add 
custom toolbars to PDF from FO?)  and I barely know where to start. 
None of them are defined in xsl-fo, because they are too pdf-specific. 
You can use extensions or postprocess pdf by a pdf-oriented software 
(iText is on the top of the list). And where to start - Dave Pawson's 
"Introduction to xsl-fo" [1] is the best one IMO.

PS. And please, don't post to the list in html format, see mail lists 
guidelines[2] how to turn it off.

[1] http://www.dpawson.co.uk/xsl/sect3/bk/index.html
[2] http://jakarta.apache.org/site/mail.html
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel


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

DO NOT REPLY [Bug 14637] - fo:retrieve-marker is confused by 2-columns reports

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14637

fo:retrieve-marker is confused by 2-columns reports

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 22:30 ---
fo:marker should be the first child of an object you want to mark, so in the
following snippet you are marking dummy inner block, not outer one, which
actually starts new entry.

  

  Entry 37

  

Therefore solution is just to get rid of your dummy block.

  
Entry 37


This works fine for me using fop-0.20.5cvs.

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

Re: Testing

[Martin Stricker]

"Mike Connor" wrote:
>
> Received?

No. ;=D

Best regards,
Martin Stricker
-- 
Homepage: http://www.martin-stricker.de/
Linux Migration Project: http://www.linux-migration.org/
Red Hat Linux 7.3 for low memory: http://www.rule-project.org/
Registered Linux user #210635: http://counter.li.org/

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

DO NOT REPLY [Bug 14656] New: - add valid URIs for all xdoc DTD declarations

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14656

add valid URIs for all xdoc DTD declarations

   Summary: add valid URIs for all xdoc DTD declarations
   Product: Fop
   Version: 1.0dev
  Platform: All
OS/Version: All
Status: NEW
  Severity: Enhancement
  Priority: Other
 Component: documentation
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The attached patch file contains:
1. Valid URIs for all xdoc DTD declarations. There may be better URIs to use, 
but I don't know what they are. These work.
2. Some minor changes for xdoc documents that were discovered to be invalid 
after the DTD declarations were fixed.
3. Changed tabs.xml so that the 2nd tab on our site will now read "Redesign" 
instead of "dev" (this was discussed in a recent thread).

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

DO NOT REPLY [Bug 14656] - add valid URIs for all xdoc DTD declarations

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14656

add valid URIs for all xdoc DTD declarations





--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 22:36 ---
Created an attachment (id=3881)
patch file for DTD declarations for xdoc documents

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

DO NOT REPLY [Bug 14656] - [PATCH] add valid URIs for all xdoc DTD declarations

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14656

[PATCH] add valid URIs for all xdoc DTD declarations

[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|add valid URIs for all xdoc |[PATCH] add valid URIs for
   |DTD declarations|all xdoc DTD declarations



--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 22:39 ---
add keyword [PATCH] to description.

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

DO NOT REPLY [Bug 14657] New: - [PATCH] Awt measuring/rendering problems

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14657

[PATCH] Awt measuring/rendering problems 

   Summary: [PATCH] Awt measuring/rendering problems
   Product: Fop
   Version: 0.20.4
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: awt renderer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The AWT Renderer and its subclass Print renderer (lives in the PrintStarter)
sizes text 
incorrectly at certain zoom scalings.  It is especially with
bold text.  The problem shows up 
differently with jre 1.3.x and 1.4.x

The solution requires two actions:
1) to enable the 
Rendering Hint - FractionalMetrics
2) to use getStringBounds to obtain the size of a 
character
   rather than charWidth.

3 files in package ...fop.render.awt are affected, 
AWTRenderer, 
AWTFontMetrics, and FontSetup.

Diff file follows below

'best
-
Ralph LaChance

Index: xml-
fop/src/org/apache/fop/render/awt/AWTFontMetrics.java
===
RCS 
file: /home/cvspublic/xml-
fop/src/org/apache/fop/render/awt/AWTFontMetrics.java,v
retrieving revision 
1.3.2.3
diff -u -r1.3.2.3 AWTFontMetrics.java
--- xml-
fop/src/org/apache/fop/render/awt/AWTFontMetrics.java   8 Nov 2002 10:25:27 -
1.3.2.3
+++ xml-fop/src/org/apache/fop/render/awt/AWTFontMetrics.java   18 Nov 
2002 22:41:37 -
@@ -177,14 +177,26 @@
 public int width(int i, String family, int style, 
int size) {
 int w;
 setFont(family, style, size);
+
+// Nov 18, 2002,  aml/rlc  
+// 
measure character width using getStringBounds for better results
+
+char [] ac = new char 
[1] ;
+ac [0] = (char) i ;
+
+double dWidth = fmt.getStringBounds (ac, 0, 1, 
graphics).getWidth() * FONT_FACTOR ;
+
+// The following was left in based on this comment 
from the past (may be vestigial)
+
 // the output seems to look a little better if the
 // space 
is rendered larger than given by
 // the FontMetrics object
-if (i <= 32)
-w = (int)(1.4 * 
fmt.charWidth(i) * FONT_FACTOR);
-else
-w = (int)(fmt.charWidth(i) * FONT_FACTOR);
-
return w;
+
+if (i <=32)
+  dWidth = dWidth * 1.4 ;
+
+return (int) dWidth ;
+
 }
 
 
/**
Index: xml-
fop/src/org/apache/fop/render/awt/AWTRenderer.java
===
RCS 
file: /home/cvspublic/xml-
fop/src/org/apache/fop/render/awt/AWTRenderer.java,v
retrieving revision 
1.38.2.9
diff -u -r1.38.2.9 AWTRenderer.java
--- xml-
fop/src/org/apache/fop/render/awt/AWTRenderer.java  8 Nov 2002 10:25:27 -
1.38.2.9
+++ xml-fop/src/org/apache/fop/render/awt/AWTRenderer.java  18 Nov 2002 
22:41:38 -
@@ -15,6 +15,7 @@
 import org.apache.fop.render.AbstractRenderer;
 
import org.apache.fop.render.pdf.*;
 import org.apache.fop.svg.*;
+import 
org.apache.fop.render.pdf.*;
 import org.apache.fop.viewer.*;
 
 import 
org.w3c.dom.svg.*;
@@ -373,6 +374,11 @@
 
 graphics = pageImage.createGraphics();
 
+
// Nov 18, 2002 - [aml/rlc] eliminates layout problems at various scaling
+
+
graphics.setRenderingHint (RenderingHints.KEY_FRACTIONALMETRICS,
+   
RenderingHints.VALUE_FRACTIONALMETRICS_ON);
+
 transform(graphics, scaleFactor, 
0);
 drawFrame();
 
@@ -859,7 +865,13 @@
 int oldPageNumber = pageNumber;
 
 graphics = 
(Graphics2D)g;
-Page aPage = (Page)pageList.get(pageIndex);
+
+// Nov 18, 2002 - 
[aml/rlc] eliminates layout problems at various scaling
+
+graphics.setRenderingHint 
(RenderingHints.KEY_FRACTIONALMETRICS,
+   
RenderingHints.VALUE_FRACTIONALMETRICS_ON);
+
+Page aPage = 
(Page)pageList.elementAt(pageIndex);
 renderPage(aPage);
 graphics = oldGraphics;
 

Index: xml-
fop/src/org/apache/fop/render/awt/FontSetup.java
===
RCS 
file: /home/cvspublic/xml-
fop/src/org/apache/fop/render/awt/FontSetup.java,v
retrieving revision 
1.3.2.4
diff -u -r1.3.2.4 FontSetup.java
--- xml-
fop/src/org/apache/fop/render/awt/FontSetup.java8 Nov 2002 10:25:27 -
1.3.2.4
+++ xml-fop/src/org/apache/fop/render/awt/FontSetup.java18 Nov 2002 
22:41:38 -
@@ -19,8 +19,8 @@
 // Java
 import java.awt.Font;
 import 
java.awt.Graphics2D;
-import java.util.List;

DO NOT REPLY [Bug 14659] New: - spurious (nuisance) errors on print/awt renderers

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14659

spurious (nuisance) errors on print/awt renderers

   Summary: spurious (nuisance) errors on print/awt renderers
   Product: Fop
   Version: 0.20.4
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Minor
  Priority: Other
 Component: awt renderer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Both the awt renderer and the print renderer output some
spurious error messages to the 
logger.

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

DO NOT REPLY [Bug 14659] - spurious (nuisance) errors on print/awt renderers

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14659

spurious (nuisance) errors on print/awt renderers





--- Additional Comments From [EMAIL PROTECTED]  2002-11-18 23:25 
---
I've worked out a corrections for both of these minor annoyances.
I'm not sure these are the 
~right~ solutions, but they work.

btw:  There seems to be a problem (line endings?) 
with
fop.app.PrintStarter.java - If I make a single character change
in the file, diff 
reports that the whole thing changed   ;-(

The actual diff is appended below for AWTStarter, 

a ~description~ of the change to PrintStarter follow below that

Index: xml-
fop/src/org/apache/fop/apps/AWTStarter.java
===
RCS 
file: /home/cvspublic/xml-fop/src/org/apache/fop/apps/AWTStarter.java,v
retrieving 
revision 1.9.2.4
diff -u -r1.9.2.4 AWTStarter.java
--- xml-
fop/src/org/apache/fop/apps/AWTStarter.java 4 Jul 2002 12:00:25 -   1.9.2.4
+++ xml-
fop/src/org/apache/fop/apps/AWTStarter.java 18 Nov 2002 23:13:30 -
@@ -93,7 +93,7 
@@
 renderer.setProgressListener(frame);
 renderer.setComponent(frame);
 driver = 
new Driver();
-driver.setLogger(log);
+driver.setLogger(new 
ConsoleLogger(ConsoleLogger.LEVEL_INFO));
 if (errorDump) {
 
driver.setErrorDump(true);
 }

description of change to PrintStarter.java

The 
run() method should look like this:

public void run() throws FOPException {
Driver 
driver = new Driver();
if (errorDump) {
driver.setErrorDump(true);
}

// String 
version = Version.getVersion();   // removed
// MessageHandler.errorln(version); // 
removed

driver.setLogger (new ConsoleLogger(ConsoleLogger.LEVEL_INFO)) ;

log.info (Version.getVersion()) ;

etc. etc.

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

DO NOT REPLY [Bug 14659] - spurious (nuisance) errors on print/awt renderers

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14659

spurious (nuisance) errors on print/awt renderers





--- Additional Comments From [EMAIL PROTECTED]  2002-11-19 00:22 ---
Ralph,

fop.app.PrintStarter.java is one of the files that Bernard D'Havé noted as
having line ending problems in Bug 14626.  I am about to clean up all of the
*source files* that he mentioned (thanks to perl).

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

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

[pbwest]

pbwest  2002/11/18 16:47:01

  Modified:src/org/apache/fop/apps Tag: fop-0_20_2-maintain
CommandLineOptions.java
  Log:
  Clean up line endings.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.14.2.8  +653 -653  xml-fop/src/org/apache/fop/apps/CommandLineOptions.java
  
  Index: CommandLineOptions.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/apps/CommandLineOptions.java,v
  retrieving revision 1.14.2.7
  retrieving revision 1.14.2.8
  diff -u -r1.14.2.7 -r1.14.2.8
  --- CommandLineOptions.java   17 Sep 2002 22:01:04 -  1.14.2.7
  +++ CommandLineOptions.java   19 Nov 2002 00:47:01 -  1.14.2.8
  @@ -1,653 +1,653 @@
  -/*
  - * $Id$
  - * Copyright (C) 2001 The Apache Software Foundation. All rights reserved.
  - * For details on use and redistribution please refer to the
  - * LICENSE file included with these sources.
  - */
  -
  -package org.apache.fop.apps;
  -
  -// FOP
  -
  -import org.apache.fop.apps.FOPException;
  -import org.apache.fop.configuration.Configuration;
  -import org.apache.fop.messaging.MessageHandler;
  -import org.apache.fop.render.txt.TXTRenderer;
  -// Avalon
  -import org.apache.avalon.framework.logger.ConsoleLogger;
  -import org.apache.avalon.framework.logger.Logger;
  -
  -// java
  -import java.io.File;
  -import java.io.FileNotFoundException;
  -
  -/**
  - * Options parses the commandline arguments
  - */
  -public class CommandLineOptions {
  -
  -/* input / output not set */
  -private static final int NOT_SET = 0;
  -/* input: fo file */
  -private static final int FO_INPUT = 1;
  -/* input: xml+xsl file */
  -private static final int XSLT_INPUT = 2;
  -/* output: pdf file */
  -private static final int PDF_OUTPUT = 1;
  -/* output: screen using swing */
  -private static final int AWT_OUTPUT = 2;
  -/* output: mif file */
  -private static final int MIF_OUTPUT = 3;
  -/* output: sent swing rendered file to printer */
  -private static final int PRINT_OUTPUT = 4;
  -/* output: pcl file */
  -private static final int PCL_OUTPUT = 5;
  -/* output: postscript file */
  -private static final int PS_OUTPUT = 6;
  -/* output: text file */
  -private static final int TXT_OUTPUT = 7;
  -/* output: svg file */
  -private static final int SVG_OUTPUT = 8;
  -/* output: XML area tree */
  -private static final int AREA_OUTPUT = 9;
  -
  -/* use debug mode */
  -Boolean errorDump = Boolean.FALSE;
  -/* show configuration information */
  -Boolean dumpConfiguration = Boolean.FALSE;
  -/* suppress any progress information */
  -Boolean quiet = Boolean.FALSE;
  -/* for area tree XML output, only down to block area level */
  -Boolean suppressLowLevelAreas = Boolean.FALSE;
  -/* user configuration file */
  -File userConfigFile = null;
  -/* input fo file */
  -File fofile = null;
  -/* xsltfile (xslt transformation as input) */
  -File xsltfile = null;
  -/* xml file (xslt transformation as input) */
  -File xmlfile = null;
  -/* output file */
  -File outfile = null;
  -/* input mode */
  -int inputmode = NOT_SET;
  -/* output mode */
  -int outputmode = NOT_SET;
  -/* language for user information */
  -String language = null;
  -
  -private java.util.HashMap rendererOptions;
  -
  -private Logger log;
  -
  -public CommandLineOptions(String[] args)
  -throws FOPException, FileNotFoundException {
  -
  -setLogger(new ConsoleLogger(ConsoleLogger.LEVEL_INFO));
  -
  -boolean optionsParsed = true;
  -rendererOptions = new java.util.HashMap();
  -try {
  -optionsParsed = parseOptions(args);
  -if (optionsParsed) {
  -checkSettings();
  -if (errorDump != null && errorDump.booleanValue()) {
  -debug();
  -}
  -}
  -} catch (FOPException e) {
  -printUsage();
  -throw e;
  -} catch (java.io.FileNotFoundException e) {
  -printUsage();
  -throw e;
  -}
  -
  -}
  -
  -/**
  - * parses the commandline arguments
  - * @return true if parse was successful and procesing can continue, false if 
processing should stop
  - * @exception FOPException if there was an error in the format of the options
  - */
  -private boolean parseOptions(String args[]) throws FOPException {
  -for (int i = 0; i < args.length; i++) {
  -if (args[i].equals("-d") || args[i].equals("--full-error-dump")) {
  -errorDump = Boolean.TRUE;
  -

DO NOT REPLY [Bug 14626] - List of files with bad CR/LF

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14626

List of files with bad CR/LF





--- Additional Comments From [EMAIL PROTECTED]  2002-11-19 01:14 ---
Created an attachment (id=3883)
List of files cleaned up

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

DO NOT REPLY [Bug 14626] - List of files with bad CR/LF

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14626

List of files with bad CR/LF





--- Additional Comments From [EMAIL PROTECTED]  2002-11-19 01:16 ---
Created an attachment (id=3884)
List of files YET TO BE cleaned up

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

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

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13866

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





--- Additional Comments From [EMAIL PROTECTED]  2002-11-19 01:20 ---
Christian,

thanks for accepting and committing my patch. I hope to be able to contribute 
more in the future. 

Regarding the resolving of URIs in FopImageFactory you say it works for you 
under Linux. I can say it doesn't work for me under Linux. Could it be that we 
are using different JDKs (I use IBM 1.3.0) and that the behaviour of the URL 
constructor "new URL(context, spec)" has changed? Any way, what I observe is 
that if basedir is something like "file:/..." and the URL in the external-
graphics tag is also "file:/...", ie. has the protocol included (which it has 
for all the FOP examples), then the constructor mentioned above does not 
resolve any relative paths in "spec" as it contains a protocol component which 
according to the URL RFC means it is an absolute URL.

And could a difference in the jdk also account for your observation that the 
logging works out of the box for you but not for me?

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

DO NOT REPLY [Bug 14626] - List of files with bad CR/LF

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14626

List of files with bad CR/LF





--- Additional Comments From [EMAIL PROTECTED]  2002-11-19 01:21 ---
Cleaned up source and package.html files.
Created two attachments:
3883 - list of files which HAVE BEEN cleaned up
3884 - list of files YET TO BE cleaned up

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

DO NOT REPLY [Bug 14668] New: - [PATCH] resources.xml

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14668

[PATCH] resources.xml

   Summary: [PATCH] resources.xml
   Product: Fop
   Version: 1.0dev
  Platform: All
OS/Version: All
Status: NEW
  Severity: Enhancement
  Priority: Other
 Component: documentation
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The attached patch to xdocs/resources.xml:
1. Adds links to the Eyebrowse mail list archives.
2. Adds help and unsubscribe email addresses for the fop-user & fop-dev lists.
3. Rewrote/rearranged some of the verbiage for better structure.

There are some spurious differences at the end of the patch that are related to 
pretty-print.

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

DO NOT REPLY [Bug 14668] - [PATCH] resources.xml

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14668

[PATCH] resources.xml





--- Additional Comments From [EMAIL PROTECTED]  2002-11-19 04:25 ---
Created an attachment (id=3886)
patch file for resources.xml

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

cvs commit: xml-fop/src/org/apache/fop/layoutmgr/list Item.java ListItemLayoutManager.java

[keiron]

keiron  2002/11/18 23:00:27

  Modified:src/org/apache/fop/layoutmgr/list Item.java
ListItemLayoutManager.java
  Log:
  correctly continue lists over page
  
  Revision  ChangesPath
  1.5   +3 -1  xml-fop/src/org/apache/fop/layoutmgr/list/Item.java
  
  Index: Item.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/layoutmgr/list/Item.java,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- Item.java 18 Nov 2002 15:54:15 -  1.4
  +++ Item.java 19 Nov 2002 07:00:27 -  1.5
  @@ -102,6 +102,7 @@
   } else {
   curLM.resetPosition(null);
   }
  +over = true;
   break;
   }
   stackSize.add(bp.getStackingSize());
  @@ -234,6 +235,7 @@
   if (resetPos == null) {
   reset(null);
   } else {
  +setFinished(false);
   //reset(resetPos);
   }
   }
  
  
  
  1.5   +7 -4  
xml-fop/src/org/apache/fop/layoutmgr/list/ListItemLayoutManager.java
  
  Index: ListItemLayoutManager.java
  ===
  RCS file: 
/home/cvs/xml-fop/src/org/apache/fop/layoutmgr/list/ListItemLayoutManager.java,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- ListItemLayoutManager.java18 Nov 2002 15:54:15 -  1.4
  +++ ListItemLayoutManager.java19 Nov 2002 07:00:27 -  1.5
  @@ -35,10 +35,9 @@
   private Item label;
   private Item body;
   
  -private Block curBlockArea;
  +private Block curBlockArea = null;
   
   private List cellList = null;
  -private List columns = null;
   private int listItemHeight;
   private BorderAndPadding borderProps = null;
   private BackgroundProps backgroundProps;
  @@ -171,7 +170,10 @@
   
   MinOptMax itemSize = new MinOptMax(min, opt, max);
   
  -setFinished(true);
  +if (label.isFinished() && body.isFinished()) {
  +setFinished(true);
  +}
  +
   ItemPosition rp = new ItemPosition(this, breakList.size() - 1, breakList);
   BreakPoss breakPoss = new BreakPoss(rp);
   if (over) { 
  @@ -217,6 +219,7 @@
   
   flush();
   
  +curBlockArea = null;
   }
   
   /**
  
  
  

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

AW: Novice: Seeking to control PDF properties using xsl:FO

["Müller, Markus"]

If you want to use PDF-specific extensions, try with renderX - it supports
some special features like bookmarking, etc.
 
Markus

-Ursprüngliche Nachricht-
Von: Mike Connor [mailto:[EMAIL PROTECTED]]
Gesendet am: Montag, 18. November 2002 20:01
An: [EMAIL PROTECTED]
Betreff: Novice: Seeking to control PDF properties using xsl:FO


Hey there,

 

I'm new to a lot of this stuff but gotta catch up quick if I would like to
continue eating, having a roof over my head etc :-).

 

I need to investigate what PDF properties can be controlled through FO
(Example:  Locking during saves, what can be config'd/edited, can I add
custom toolbars to PDF from FO?)  and I barely know where to start.  

Is it possible to have a PDF in a Web page and have a link for say printing
that would initiate a PDF print rather than a browser printer.

 

Any leads/pointers would be greatly appreciated.

 

Mike 

 

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

RE: Frustration With FOP

[Keiron Liddle]

On Sat, 2002-11-16 at 18:55, Victor Mote wrote:
> Fair enough. I submitted and Keiron committed to the CVS repository this
> past week a document that attempts to do a better job of this. It combines
> the "implemented" and "limitations" pages with a complete list of the
> objects and properties in the standard. It has a place to list comments. I
> am not sure what the cycle is for updating our web site from the CVS docs
> right now, but I think that document will be visible after the next update.
> The truth is that this document will need to be heavily updated to give the
> complete picture, but I think it is a step in the right direction, and gives
> us a place to pull this information together. I encourage you to look for it
> on the FOP web site(entitled "Compliance"), and then help us get it cleaned
> up. If you don't want to download & change the CVS, send your comments to me
> & I'll work on getting them into the doc.
> 
> Some of our most valuable developers have invested quite a bit into getting
> the documentation system more automated (using Apache Forrest). That is
> starting to bear fruit, but the truth is that our doc content has gotten a
> bit backed up while that effort was underway. If you have an interest in
> helping us get the doc up to speed, then you jumped in a good time.

Currently the document updating process is manual (but a lot easier than
before).
Now that current cvs fop can handle the documents a lot better I will do
an update once the content is improved.

So keep the updates coming and other things like fo examples are always
welcome.

Keiron.



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

cvs commit: xml-fop/src/documentation forrest.diff

[keiron]

keiron  2002/11/18 23:32:14

  Modified:src/documentation forrest.diff
  Log:
  suppress text nodes in bookmarks
  added page sequence title
  
  Revision  ChangesPath
  1.3   +14 -17xml-fop/src/documentation/forrest.diff
  
  Index: forrest.diff
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/forrest.diff,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- forrest.diff  18 Nov 2002 14:11:29 -  1.2
  +++ forrest.diff  19 Nov 2002 07:32:14 -  1.3
  @@ -4,7 +4,7 @@
   retrieving revision 1.2
   diff -u -r1.2 document2fo.xsl
   --- src/resources/skins/common/xslt/fo/document2fo.xsl   16 Nov 2002 22:58:50 
-  1.2
  -+++ src/resources/skins/common/xslt/fo/document2fo.xsl   18 Nov 2002 14:09:29 
-
   src/resources/skins/common/xslt/fo/document2fo.xsl   19 Nov 2002 07:30:58 
-
   @@ -2,6 +2,7 @@

http://www.w3.org/1999/XSL/Transform";
  @@ -13,7 +13,7 @@
version="1.0">

  
  -@@ -80,14 +81,52 @@
  +@@ -80,14 +81,57 @@
  

  
  @@ -24,6 +24,7 @@
   +  
   +
  
  ++

  
  
  @@ -46,6 +47,10 @@
   +
   +  
   +
  ++  
  ++
  ++  
  ++
   +  
   +


  -@@ -102,6 +141,7 @@
  +@@ -102,6 +146,7 @@
text-align="start">
Page 
  
  @@ -76,7 +81,7 @@



  -@@ -110,6 +150,7 @@
  +@@ -110,6 +155,7 @@
font-style="italic">

  
  @@ -84,7 +89,7 @@



  -@@ -131,6 +172,7 @@
  +@@ -131,6 +177,7 @@
font-style="italic">

  
  @@ -92,7 +97,7 @@



  -@@ -192,6 +234,11 @@
  +@@ -192,6 +239,11 @@

  

  @@ -104,7 +109,7 @@
  

0
  -@@ -201,9 +248,15 @@
  +@@ -201,9 +253,15 @@
  font-family="serif"
  font-size="{$size}pt"
  font-weight="bold"
  @@ -121,7 +126,7 @@
  


  -@@ -255,6 +308,9 @@
  +@@ -255,6 +313,9 @@
  font-size="10pt"
  background-color="#f0f0f0"
  white-space-collapse="false"
  @@ -131,7 +136,7 @@
  text-align="start">
  

  -@@ -456,7 +512,16 @@
  +@@ -456,7 +517,16 @@
  

  
  @@ -148,11 +153,3 @@
  

  
  -@@ -587,7 +652,6 @@
  -  []
  -
  -  
  --
  - 
  - 
  - 
  
  
  

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

Re: AW: Novice: Seeking to control PDF properties using xsl:FO

[Oleg Tkachenko]

Müller, Markus wrote:

If you want to use PDF-specific extensions, try with renderX - it supports
some special features like bookmarking, etc.

You right, but bookmarking also supported by FOP, see 
http://xml.apache.org/fop/extensions.html

--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel


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

cvs commit: xml-fop/src/documentation/content/xdocs/dev book.xml configuration.xml examples.xml extensions.xml faq.xml index.xml svg.xml

[keiron]

keiron  2002/11/18 23:57:29

  Modified:src/documentation/content/xdocs book.xml bugs.xml
compiling.xml compliance.xml configuration.xml
download.xml embedding.xml examples.xml
extensions.xml faq.xml fonts.xml gethelp.xml
implemented.xml index.xml involved.xml license.xml
limitations.xml news.xml output.xml relnotes.xml
resources.xml running.xml status.xml svg.xml
tabs.xml testing.xml
   src/documentation/content/xdocs/design architecture.xml
areas.xml book.xml breakpos.xml embedding.xml
extending.xml fotree.xml index.xml layout.xml
optimise.xml properties.xml renderers.xml
status.xml useragent.xml
   src/documentation/content/xdocs/dev book.xml
configuration.xml examples.xml extensions.xml
faq.xml index.xml svg.xml
  Log:
  The attached patch file contains:
  1. Valid URIs for all xdoc DTD declarations.
  2. Some minor changes for xdoc documents that were discovered to be invalid
  after the DTD declarations were fixed.
  3. Changed tabs.xml so that the 2nd tab on our site will now read "Redesign"
  instead of "dev" (this was discussed in a recent thread).
  Submitted By: [EMAIL PROTECTED] (Victor Mote)
  
  Revision  ChangesPath
  1.7   +3 -1  xml-fop/src/documentation/content/xdocs/book.xml
  
  Index: book.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/book.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- book.xml  13 Nov 2002 12:21:28 -  1.6
  +++ book.xml  19 Nov 2002 07:57:27 -  1.7
  @@ -1,5 +1,7 @@
   
  -  
  +  http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-cocoon2/src/documentation/xdocs/dtd/book-cocoon-v10.dtd";>
  +
   
 
  -
  +http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd";>
   
   
 
  
  
  
  1.2   +2 -1  xml-fop/src/documentation/content/xdocs/compiling.xml
  
  Index: compiling.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compiling.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- compiling.xml 4 Nov 2002 16:20:51 -   1.1
  +++ compiling.xml 19 Nov 2002 07:57:27 -  1.2
  @@ -1,5 +1,6 @@
   
  -
  +http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd";>
   
   
 
  
  
  
  1.2   +2 -1  xml-fop/src/documentation/content/xdocs/compliance.xml
  
  Index: compliance.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compliance.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- compliance.xml13 Nov 2002 12:21:30 -  1.1
  +++ compliance.xml19 Nov 2002 07:57:27 -  1.2
  @@ -1,5 +1,6 @@
   
  -
  +http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-fop/src/documentation/resources/schema/dtd/compliance-v10.dtd?rev=1.1";>
   
   
 
  
  
  
  1.2   +2 -1  xml-fop/src/documentation/content/xdocs/configuration.xml
  
  Index: configuration.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/configuration.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- configuration.xml 4 Nov 2002 16:20:51 -   1.1
  +++ configuration.xml 19 Nov 2002 07:57:27 -  1.2
  @@ -1,5 +1,6 @@
   
  -
  +http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd";>
   
   
   
  
  
  
  1.3   +2 -1  xml-fop/src/documentation/content/xdocs/download.xml
  
  Index: download.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/download.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- download.xml  5 Nov 2002 11:38:03 -   1.2
  +++ download.xml  19 Nov 2002 07:57:27 -  1.3
  @@ -1,5 +1,6 @@
   
  -
  +http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd";>
   
   
   
  
  
  
  1.2   +2 -1  xml-fop/src/documentation/content/xdocs/embedding.xml
  
  Index: embedding.xml
  ===
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/embedding.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- embedding.xml 4 Nov 20

DO NOT REPLY [Bug 14656] - [PATCH] add valid URIs for all xdoc DTD declarations

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14656

[PATCH] add valid URIs for all xdoc DTD declarations

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2002-11-19 07:59 ---
Thanks, committed to cvs.

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