Jeremias Maerki | 1 Apr 12:27 2006
Picon

Re: Including an sRGB color profile?


On 31.03.2006 21:48:43 Max Berger wrote:
> I know I have no vote in this, but I do disagree.

Every opinion is always welcome.

> 1) I still believe that PDF is a print medium and should therefore
> default to CMYK colorspace. If supported correctly by software, the
> colors should show up right on the screen.

One use case of PDF is as a print medium, but it's not the only one. If
we're talking about producing documents for offset printing, then yes, I
agree with you. Fact is that most PDF-producing software packages I know
produce RGB (either uncalibrated DeviceRGB or sRGB). This applies to
OpenOffice, Acrobat Distiller with its default settings, GhostScript.
The list probably goes on.

Supporting CMYK in FOP means some additional work which I don't have
time for (and don't really have a need myself). The client that has
asked me to implement PDF/A-1 is happy with sRGB since it's only about
patent documents. If someone (you?) implements an option to generate a
full CMYK PDF, then I'm all for adding that since it has been requested
a number of times. But doing that per default would be a change in
long-standing standard FOP behaviour which I don't support.

> 2) If you want to embedd the sRGB profile, I would recommend using the
> profiles found at the International Color Consortium:
> http://www.color.org
> 
> especially
(Continue reading)

Sam Ruby | 1 Apr 14:34 2006
Picon

[GUMP <at> vmgump]: Project xml-fop (in module xml-fop) failed

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at general <at> gump.apache.org.

Project xml-fop has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 21 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - xml-fop :  XSL-FO (Formatting Objects) processor

Full details are available at:
    http://vmgump.apache.org/gump/public/xml-fop/xml-fop/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -DEBUG- Sole output [fop.jar] identifier set to project name
 -INFO- Made directory [/usr/local/gump/public/workspace/xml-fop/build/classes]
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository

The following work was performed:
http://vmgump.apache.org/gump/public/xml-fop/xml-fop/gump_work/build_xml-fop_xml-fop.html
Work Name: build_xml-fop_xml-fop (Type: Build)
Work ended in a state of : Failed
Elapsed: 33 secs
Command Line: java -Djava.awt.headless=true
(Continue reading)

bugzilla | 1 Apr 22:56 2006
Picon

DO NOT REPLY [Bug 37813] - span property causes random insertion of page breaks

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37813>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37813

tjunker <at> charter.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |

------- Additional Comments From tjunker <at> charter.net  2006-04-01 21:56 -------
At version .91 Beta
Within a multi column page master 
Within a <fo:block span="all"> a <table> that spans pages reverts to multi 
column on second and subsequent pages.

--

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

thomas.deweese | 2 Apr 14:07 2006
Picon

Re: [GUMP <at> vmgump]: Project xml-fop (in module xml-fop) failed

Hi guys,

    What do you want to do about this?
   Do we need to move these back for you or what?

   You might also consider tracking the svg11 branch in gump rather than 
'trunk'...
This might make more sense in the near term anyway as likely if a release 
of
Batik were to happen in the near term there is a good chance it would be 
the 
svg11 branch (really 'stable' at this point) rather than the trunk/svg12 
branch (new features).

Sam Ruby <rubys <at> us.ibm.com> wrote on 04/01/2006 07:34:31 AM:

> Project xml-fop has an issue affecting its community integration.
> This issue affects 1 projects,
>  and has been outstanding for 21 runs.
> The current state of this project is 'Failed', with reason 'Build 
Failed'.
> For reference only, the following projects are affected by this:

> 
io-01042006.jar:/usr/local/gump/public/workspace/jakarta-servletapi/dist/lib/servlet.jar
> ---------------------------------------------
>     [javac] /x1/gump/public/workspace/xml-
> fop/src/java/org/apache/fop/image/PNGImage.java:57: cannot find symbol
>     [javac] symbol  : class PNGRed
>     [javac] location: class org.apache.fop.image.PNGImage
(Continue reading)

Sam Ruby | 2 Apr 14:37 2006
Picon

[GUMP <at> vmgump]: Project xml-fop (in module xml-fop) failed

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at general <at> gump.apache.org.

Project xml-fop has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 24 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - xml-fop :  XSL-FO (Formatting Objects) processor

Full details are available at:
    http://vmgump.apache.org/gump/public/xml-fop/xml-fop/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -DEBUG- Sole output [fop.jar] identifier set to project name
 -INFO- Made directory [/usr/local/gump/public/workspace/xml-fop/build/classes]
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository

The following work was performed:
http://vmgump.apache.org/gump/public/xml-fop/xml-fop/gump_work/build_xml-fop_xml-fop.html
Work Name: build_xml-fop_xml-fop (Type: Build)
Work ended in a state of : Failed
Elapsed: 32 secs
Command Line: java -Djava.awt.headless=true
(Continue reading)

bugzilla | 2 Apr 17:43 2006
Picon

DO NOT REPLY [Bug 39030] - TTFReader writes file with %20" (percent twenty) in filename

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39030>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39030

------- Additional Comments From laklare <at> ml1.net  2006-04-02 16:43 -------
Thanks.  I may have reported this incorrectly under Xalan-J, but I did put it
out there.  Here's the link: http://issues.apache.org/bugzilla/show_bug.cgi?id=39181

(In reply to comment #1)
> It looks like a bug in Xalan-J. I've changed the code so we open the
> OutputStream to the target file ourselves.
> http://svn.apache.org/viewcvs?rev=387161&view=rev
> 
> Would you mind informing the Xalan-J people about this? Someone else might run
> into this.

--

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Jeremias Maerki | 2 Apr 20:38 2006
Picon

Re: [GUMP <at> vmgump]: Project xml-fop (in module xml-fop) failed


On 02.04.2006 14:07:21 thomas.deweese wrote:
> Hi guys,
> 
>     What do you want to do about this?
>    Do we need to move these back for you or what?

No, it's up to me (sorry for the delay!!!). I wanted to port the codecs
to Commons and start using Commons in FOP. I want to do it in a clean
way and start to make FOP more Classpath-compatible. The ImageWriters
will help a long way here. I've done pretty much everything on the
Commons side and will be ready for the first step on Tuesday (probably).
What you could do in Batik is planning to remove the components I
already migrated to Commons and start using a commons snapshot, too.

>    You might also consider tracking the svg11 branch in gump rather than 
> 'trunk'...
> This might make more sense in the near term anyway as likely if a release 
> of
> Batik were to happen in the near term there is a good chance it would be 
> the 
> svg11 branch (really 'stable' at this point) rather than the trunk/svg12 
> branch (new features).

I didn't think about that. Good hint. I guess it makes sense in this
case to point FOP's Gump descriptor to the branch for the moment. Still,
I'd prefer to use the codecs from Commons now.

> Sam Ruby <rubys <at> us.ibm.com> wrote on 04/01/2006 07:34:31 AM:
> 
(Continue reading)

bugzilla | 3 Apr 00:08 2006
Picon

Bug report for Fop [2006/04/02]

+---------------------------------------------------------------------------+
| Bugzilla Bug ID                                                           |
|     +---------------------------------------------------------------------+
|     | Status: UNC=Unconfirmed NEW=New         ASS=Assigned                |
|     |         OPN=Reopened    VER=Verified    (Skipped Closed/Resolved)   |
|     |   +-----------------------------------------------------------------+
|     |   | Severity: BLK=Blocker     CRI=Critical    MAJ=Major             |
|     |   |           MIN=Minor       NOR=Normal      ENH=Enhancement       |
|     |   |   +-------------------------------------------------------------+
|     |   |   | Date Posted                                                 |
|     |   |   |          +--------------------------------------------------+
|     |   |   |          | Description                                      |
|     |   |   |          |                                                  |
|  953|Opn|Nor|2001-03-12|Incorrect hyperlinks area rendering in justified t|
| 1063|New|Nor|2001-03-21|fop does not handle large fo files                |
| 1180|New|Maj|2001-04-02|Problem with monospaced font                      |
| 1859|Opn|Min|2001-05-22|org.apache.fop.apps.Driver.reset() doesn't fully r|
| 1998|New|Nor|2001-06-05|linefeed-treatment not understood                 |
| 2150|Ass|Maj|2001-06-13|New page with  a table-header but without any tabl|
| 2475|Ass|Nor|2001-07-06|Borders don't appear to work in <fo:table-row>    |
| 2740|New|Maj|2001-07-23|multi-page tables sometimes render badly          |
| 2909|New|Maj|2001-07-30|Gradient render error                             |
| 2964|Ass|Nor|2001-08-02|problems with height of cells in tables           |
| 2988|New|Maj|2001-08-03|0.19: list-item-label does not stick to list-item-|
| 3044|Ass|Maj|2001-08-08|keep-together not functioning                     |
| 3280|New|Nor|2001-08-27|PCL Renderer doesn't work                         |
| 3305|Opn|Nor|2001-08-28|list-block overlapping footnote body              |
| 3497|New|Cri|2001-09-07|id already exists error when using span="all" attr|
| 3824|New|Blk|2001-09-25|MIF option with tables                            |
| 4030|New|Nor|2001-10-08|IOException creating Postscript with graphics on S|
(Continue reading)

bugzilla | 3 Apr 02:09 2006
Picon

DO NOT REPLY [Bug 39184] New: - soft page break on new line

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39184>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39184

           Summary: soft page break on new line
           Product: Fop
           Version: 0.91
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: rtf
        AssignedTo: fop-dev <at> xmlgraphics.apache.org
        ReportedBy: van_le_hoa <at> agd.nsw.gov.au

I am trying to test the conversion FO to RTF using FOP 0.91 beta. I carried 
the test as below:

Create a document in RTF using Ms Word.
Convert RTF document to XSL-FO using RTF2FO using JFO.
Convert XSL-FO document to RTF using FOP 0.91 beta.

  
I have found a bug in the document footer. 

(Continue reading)

bugzilla | 3 Apr 02:12 2006
Picon

DO NOT REPLY [Bug 39184] - soft page break on new line

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39184>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39184

------- Additional Comments From van_le_hoa <at> agd.nsw.gov.au  2006-04-03 01:12 -------
Created an attachment (id=18019)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=18019&action=view)
output rtf

--

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


Gmane