headers
Victor Mote | 1 Apr 2003 05:40

web site changes

The latest updated web site has a link for compliance.pdf, and has the
"Implemented" & "Limitations" pages removed.

The "compliance" document still has a few problems: 1) the log file
indicates that compliance.html is generating an NPE from Xalan. I will try
to track this down, but haven't found any obvious answers yet -- also, it
doesn't seem to be adversely affecting anything. 2) compliance.pdf is
mangled & unusable, probably because forrestbot uses an old version of FOP.
Even when using a current version, it still doesn't look good, but it is
openable -- probably a combination of FOP limitations & the stylesheet.

I changed the dev/index.html page to explain the 3 lines of development. I
am not sure I explained the Alt Design properly, so Peter, please correct it
if necessary.

More doc changes to come.

Victor Mote (mailto:vic <at> outfitr.com)
2025 Eddington Way
Colorado Springs, Colorado 80916
Voice +1 (719) 622-0650
Fax   +1 (720) 293-0044
Permalink | Reply | 1 comment |
headers
Peter B. West | 1 Apr 2003 07:00
Picon
Picon

Re: web site changes

Victor,

Thanks.  That will do very nicely.

Peter

Victor Mote wrote:
> 
> I changed the dev/index.html page to explain the 3 lines of development. I
> am not sure I explained the Alt Design properly, so Peter, please correct it
> if necessary.

--

-- 
Peter B. West  pbwest <at> powerup.com.au  http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
Permalink | Reply | 0 comments |
headers
bugzilla | 1 Apr 2003 12:22
Picon
Favicon

DO NOT REPLY [Bug 18559] New: - Not enough error messages ("Marformed format string")

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

Not enough error messages ("Marformed format string")

           Summary: Not enough error messages ("Marformed format string")
           Product: Fop
           Version: 0.20.5
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: general
        AssignedTo: fop-dev <at> xml.apache.org
        ReportedBy: mhilpert <at> gmx.de

I have an XML document that i like to transform to PDF as some other documents 
transform correctly, one document does not and FOP just prints this message:

---
[ERROR] ElemTemplateElement error: Malformed format string: 
---

no further text even though there is a colon after "string:"!
(Continue reading)

Permalink | Reply | 0 comments |
headers
bugzilla | 1 Apr 2003 13:10
Picon
Favicon

DO NOT REPLY [Bug 18559] - Not enough error messages ("Marformed format string")

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

Not enough error messages ("Marformed format string")

jeremias <at> apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

------- Additional Comments From jeremias <at> apache.org  2003-04-01 11:10 -------
This is a Xalan problem. Try running the XSL transformation only (without FOP).
Permalink | Reply | 0 comments |
headers
bugzilla | 1 Apr 2003 20:23
Picon
Favicon

DO NOT REPLY [Bug 18576] New: - FOP lops off page numbers in TOC

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

FOP lops off page numbers in TOC

           Summary: FOP lops off page numbers in TOC
           Product: Fop
           Version: 0.20.5
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: Other
         Component: pdf renderer
        AssignedTo: fop-dev <at> xml.apache.org
        ReportedBy: jjramsey <at> pobox.com

I used xsltproc and the DocBook XSL stylesheets, version 1.60.1 to make a .fo
file, and converted the .fo file with FOP. The generated table of contents is
missing the page numbers.
Permalink | Reply | 0 comments |
headers
bugzilla | 1 Apr 2003 20:50
Picon
Favicon

DO NOT REPLY [Bug 18576] - FOP lops off page numbers in TOC

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

FOP lops off page numbers in TOC

------- Additional Comments From jjramsey <at> pobox.com  2003-04-01 18:50 -------
Created an attachment (id=5588)
Tarball with sample XML, FO, and PDF files
Permalink | Reply | 0 comments |
headers
bugzilla | 1 Apr 2003 23:26
Picon
Favicon

DO NOT REPLY [Bug 18576] - FOP lops off page numbers in TOC

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

FOP lops off page numbers in TOC

j3322ptm <at> yahoo.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE

------- Additional Comments From j3322ptm <at> yahoo.de  2003-04-01 21:26 -------

*** This bug has been marked as a duplicate of 635 ***
Permalink | Reply | 0 comments |
headers
bugzilla | 1 Apr 2003 23:26
Picon
Favicon

DO NOT REPLY [Bug 635] - Doesn't support id= attribute in fo:page-sequence

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

Doesn't support id= attribute in fo:page-sequence

j3322ptm <at> yahoo.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jjramsey <at> pobox.com

------- Additional Comments From j3322ptm <at> yahoo.de  2003-04-01 21:26 -------
*** Bug 18576 has been marked as a duplicate of this bug. ***
Permalink | Reply | 0 comments |
headers
Robert Kylberg | 1 Apr 2003 23:40
Picon
Favicon

Is the -c user config option implemented???

I'm reviewing the developer branch code and believe that although 
CommandLineOptions parses the -c option and caches a userConfigFile, 
the config file is not processed. FOP 0.20.5rc2 has an 
org.apache.fop.configuration package for handling the -c option. Hence 
it appears the -c option is not yet implemented on the developer branch.

Could someone please confirm if this is correct and tell me the status 
of re-enabling the -c option on the developer branch?

Thanks,
	Bob
Permalink | Reply | 0 comments |
headers
Mazza, Glen R., ,CPMS | 2 Apr 2003 02:21

Re: web site changes

In compliance.html, it may be nice to have the "W3C XSL-FO 1.0 standard"
phrase in the first sentence hyperlinked to the specification (as is done
already on index.html).  I suspect that link would get very heavy usage if
placed on that page.

Also, the menu on the left can probably be further simplified:  5 sections
instead of 6.  Here's my suggestion:

Project (combines Project & Status)
	Introduction   	(was "Index")
	Latest News 	
	Status
	Changes
	Download FOP
	Release Notes
	Logo Contest!

Using FOP
	Running
	Embedding
	Ant Task
	Output Formats
	Configuration

FOP Extras
	SVG Support 
	FOP Extensions
	Fonts
	PDF Encryption
(Continue reading)

Permalink | Reply | 2 comments |

Gmane