Re: Automatic website update
Victor Mote wrote: Just to be clear -- is the script updating from /home/cvs/xml-fop or from /home/cvs/xml-site/targets/fop? We have discussions floating around about both of these. /home/cvs/xml-site/targets/fop Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Croatian characters in fop created pdf
On Fri, 2002-12-13 at 08:35, Adis Katkic wrote: Hi, croatian characters are of type ISO-8859-2 (latin 2) The unusual characters are: . Whatever the characters are, all I can see is a . I don't know if I said it before, but Fop doesn't use the fonts from you platform, apart from the default fonts you need to embed the fonts. Thanks Keiron but I'm still stack with my problem. If you look at the docs/examples/fo/fonts.fo it has all the characters for the inbuilt fonts. If the characters you need are not there then you will need another font that has the characters, if they are there you need to use the correct encoding or character reference. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Sun XSL Formatter
Peter did ask... The Sun xmlroff XSL formatter is written in C, and it uses libxml2 and libxslt plus the GLib, GObject, and Pango libraries that underlie GTK+ and GNOME (although it does not require either GTK+ or GNOME). The formatter currently produces PDF output only. xmlroff is a command line program, but the bulk of the XSL formatting is implemented as a libfo library that can be linked to any program that requires XSL formatting capability. It will be available under a BSD license. It is being developed on both Solaris and Linux. The formatter is awaiting final approval before the code can be made public source. An announcement will be made on xsl-list, www-xsl-fo, and XSL-FO@YahooGroups once the code is available. Regards, Tony Graham XML Technology Center Sun Microsystems Ireland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Sun XSL Formatter
Not to sound bitter, but it would have been nice to know about this sooner. This pretty much usurps what I and Eric Bischoff have been doing (when we can); I sort of figure it didn't get written in the last month either. Any reason for the blasted secretiveness? Arved -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: December 13, 2002 12:09 PM To: [EMAIL PROTECTED] Subject: Sun XSL Formatter Peter did ask... The Sun xmlroff XSL formatter is written in C, and it uses libxml2 and libxslt plus the GLib, GObject, and Pango libraries that underlie GTK+ and GNOME (although it does not require either GTK+ or GNOME). The formatter currently produces PDF output only. xmlroff is a command line program, but the bulk of the XSL formatting is implemented as a libfo library that can be linked to any program that requires XSL formatting capability. It will be available under a BSD license. It is being developed on both Solaris and Linux. The formatter is awaiting final approval before the code can be made public source. An announcement will be made on xsl-list, www-xsl-fo, and XSL-FO@YahooGroups once the code is available. Regards, Tony Graham XML Technology Center Sun Microsystems Ireland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Ant-based local doc valiation
On Thu, Dec 12, 2002 at 04:54:03PM +0100, Keiron Liddle wrote:
...
Including the DTDs would IMO be a good idea. They are only 57k. The
question is, what catalog-aware validation tool would you use?
I would suggest upgrading the version of Ant bundled with FOP to 1.6-dev
from CVS. This includes xmlcatalog support for multiple external
catalogs. So after editing xdocs, developers could type 'build
validate', and if everything passes, they can safely commit the xdocs.
Then check on http://forrestbot.cocoondev.org if the changes look okay..
and one day, trigger an xml-site commit from that site too. Tada..
Forrest is no longer required for daily edits :)
That sounds like a good idea once things settle down. Especially for
small patches.
If you decide that an Ant 'validate' target using built-in DTDs is a good
idea, I created a patch to add this to FOP:
http://cvs.apache.org/~jefft/tmp/fop-validate.zip
The patch adds about 900k to xml-fop.
Appended is the patch README.
--Jeff
FOP Validation Patch README
Jeff Turner [EMAIL PROTECTED]
Introduction
This patch provides Ant-based validation of the various XML files used to
generate FOP's documentation.
The following files are validated:
src/documentation/content/xdocs/**/*.xml
src/documentation/sitemap.xmap
src/documentation/skinconf.xml
src/documentation/resources/stylesheets/**/*.xsl
The motivation is to prevent casual doc editors from having to download Forrest
to update content. The whole point of XML documentation is to separate content
from presentation. As long as the docs validate, it should be safe to check
them in, and then view the rendered website online at:
http://forrestbot.cocoondev.org/sites/xml-fop/
(updated every hour, or an update can be triggered)
Installation
1) Copy everything in this directory (except this README) to the xml-fop/
directory.
2) In xml-fop, run 'patch -p0 build.xml.diff', which adds a 'validate' target
to build.xml.
3) Delete lib/ant.jar, as it is no longer necessary.
Usage
-
To validate XML files, run './build.sh validate' (Unix) or 'build validate'
(DOS). For better feedback, add a '-v' option. This should be done after an
XML edit, before checking into CVS.
If your editor supports catalogs, then it will be possible to validate docs as
you edit them. Point your editor to the catalog files (either OASIS or XML
format) in tools/schema/
How it works
- The current (2002-12-14) Forrest DTDs are installed in tools/schema/.
- A stripped-down Ant 1.6-dev is installed in tools/ant.
- The new build.{sh,bat} files (and unfortunately, appendcp.bat) will use the
built-in Ant, which has external catalog support.
- The 'validate' target in build.xml will call tools/validate.xml, which
contains xmlvalidate and jing validation tasks. validate.xml is a
stripped-down version of Forrest's forrest.build.xml, and so supports
Forrest's fine-grained validation control properties specified in
forrest.properties (see http://xml.apache.org/forrest/validation.html).
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 15366] New: - 'initial-page-number' generates blank page
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=15366. 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=15366 'initial-page-number' generates blank page Summary: 'initial-page-number' generates blank page Product: Fop Version: 0.20.5 Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have a document of two (or more) pages. What I'm trying to do, is to start page numbering from the second page (i.e. the second page in document is designated as '1'). To achieve this, I explicitly set 'initial-page-number' to 1 for the second 'page-sequence'. When run, PDF renderer inserts one unexpected blank page between the very first page of the document and the second one. If I remove 'initial-page-number' property from the second page, document is rendered properly (ie. without any blank page), however page number of the second page is 2 - which is not what I need. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Setting baseDir in a servlet environment.
I'm building a class to output a dynamic PDF on a web site. Using Websphere. According to the FAQ I can call: org.apache.fop.configuration.Configuration.put(baseDir,c:\my\base\dir). or since I'm using a servlet I should call: org.apache.fop.apps.Options options = new Options( new FIle(userconfig.xml) ); How is this going to be thread safe? Especially if I have more than one conversion running at a time that needs different baseDirs? The faq does not show how the driver loads or obtains this config once I load it. In userconfig.xml how would I say baseDir=c:\mybasedir? I also noticed that org.apache.fop.render.pdf.PDFRenderer has a set options method. Can I create one of these, set options and the pass it to driver.setRenderer(Renderer renderer) instead of setRenderer(Driver.RENDER_PDF). Does calling setOptions override or add to settings that are set in userConfig and config I don't think I have the option of putting my code in a synchronized block because I don't want to cause a deadlock. Any help would be appreciated. Thanks, Robert Wynkoop - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Sun XSL Formatter
Arved Sandstrom wrote: Not to sound bitter, but it would have been nice to know about this sooner. This pretty much usurps what I and Eric Bischoff have been doing (when we can); I sort of figure it didn't get written in the last month either. Any reason for the blasted secretiveness? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Subject: Sun XSL Formatter Peter did ask... Tony, Thanks for the response. I must say, though, that had the product been written in Java, I would have been asking the same question as Arved. 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: Sun XSL Formatter
Well, Java or C or C++ or Haskell, it would have been nice to have a clue. We have an ASF tradition of developing communities...this kind of stuff that Sun and IBM does is getting old. Don't open-source it; sell it. I will argue against its adoption into Apache. Arved -Original Message- From: Peter B. West [mailto:[EMAIL PROTECTED]] Sent: December 13, 2002 8:43 PM To: [EMAIL PROTECTED] Subject: Re: Sun XSL Formatter Arved Sandstrom wrote: Not to sound bitter, but it would have been nice to know about this sooner. This pretty much usurps what I and Eric Bischoff have been doing (when we can); I sort of figure it didn't get written in the last month either. Any reason for the blasted secretiveness? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Subject: Sun XSL Formatter Peter did ask... Tony, Thanks for the response. I must say, though, that had the product been written in Java, I would have been asking the same question as Arved. 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
