Did you know that the Cocoon guys have jimi.jar in their CVS? I wonder
if that's correct and if yes, I think we should do it, too.
From my reading of it, by downloading the jar you automatically agree to the
license. This is quite different to ASL.
It is also non-transferable, I think that
Hi Carsten
I'm currently trying to make XML-Forrest compile again after updating
Cocoon from CVS. The reason was the patch for bug #13247.
You've split up the Parser interface in two, one in the sax subpackage
and one in the dom subpackage. My personal opinion would have been to
rename the
Isn't the jai.jar (which would give fop great functionality!) not
redistributet for the same reason?
Yes.
I think the javax.imageio package is where Jimi and Jai were leading. So once
jdk1.4 can be used...
Best Regards
Markus Schäffler
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=16017.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Victor Mote wrote:
It might be good to have a time window for submissions a separate time
window for voting. If everybody went out and voted today, we would have a
lot of extra votes for the moose that might not be there after the choices
are all visible (just kidding -- I like our logo).
I know I'm getting troublesome, but here's another observation. On our
website we have at least 3 different ways to mention our beloved
Extensible Stylesheet Language Formatting Objects:
- XSL:FO (I'm guilty of using this in the past)
- XSL-FO
- FO
(each in upper- and lowercase)
I believe the
Ah, yes, and it's FOP, not Fop, I believe. :-)
Jeremias Maerki
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Jeremias Maerki wrote:
I know I'm getting troublesome, but here's another observation. On our
website we have at least 3 different ways to mention our beloved
Extensible Stylesheet Language Formatting Objects:
- XSL:FO (I'm guilty of using this in the past)
- XSL-FO
- FO
(each in upper- and
jeremias2003/01/15 05:54:28
Added: src/documentation/resources/images
EmbeddingExampleFO2PDF.png
EmbeddingExampleFO2PDF.svg
EmbeddingExampleObj2PDF.png
EmbeddingExampleObj2PDF.svg
jeremias2003/01/15 05:56:18
Modified:src/documentation/content/xdocs configuration.xml
embedding.xml examples.xml extensions.xml
Log:
Added documentation for the new embedding examples.
Adjusted documentation for new directory structure.
Improved
jeremias2003/01/15 06:00:04
Removed: hyph Tag: fop-0_20_2-maintain cs.xml da.xml de.xml
de_DR.xml el.xml en.xml en_GB.xml en_US.xml es.xml
fi.xml fr.xml hu.xml hyphenation.dtd it.xml nl.xml
no.xml pl.xml pt.xml
jeremias2003/01/15 06:00:12
xml-fop/src/hyph - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
jeremias2003/01/15 06:03:33
Added: src/hyph Tag: fop-0_20_2-maintain README cs.xml da.xml
de.xml de_DR.xml el.xml en.xml en_GB.xml en_US.xml
es.xml fi.xml fr.xml hu.xml hyphenation.dtd it.xml
nl.xml no.xml pl.xml
jeremias2003/01/15 06:09:57
Modified:.Tag: fop-0_20_2-maintain build.xml
Log:
Adjust to new directory for hyphenation
Revision ChangesPath
No revision
No revision
1.44.2.34 +1 -1 xml-fop/build.xml
Hi,
I am using ArborText's EPIC editor Turbo Styler to generate XSL for a
certain XML file.
The final output is for PDF format. Now once the basic styling is done for
the paragraphs, sections etc. how do I set up the page layouts and related
attributes like margin areas, gutter area etc.
Thanks
I've finally finished the documentation for the embedding examples. Most
of the directories have moved to their new locations in the branch. The
last two exceptions are the conf directory and the remains of the docs
directory. The documentation is updated for the new locations but I
haven't yet
If you could give me little more time...
I just checked out the current CVS maintenance branch and planned
to post a diff this evening containing my PS renderer fixes/optimizations
regarding
current position handling...
Do you want to wait?
--
Cappelino Informationstechnologie GmbH
Arnd Beißner
I get the impression that you're in the wrong place. We can't help you
here with the EPIC editor or with Turbo Styler. I've never worked with
ArborText's tools, but don't they allow you already to generate PDFs?
FOP simply accepts XSL-FO as input an can produce various output formats
like PDF,
jeremias2003/01/15 07:01:04
Removed: hyph cs.xml da.xml de.xml de_DR.xml el.xml en.xml
en_GB.xml en_US.xml es.xml fi.xml fr.xml hu.xml
hyphenation.dtd it.xml nl.xml no.xml pl.xml pt.xml
readme ru.xml sk.xml
jeremias2003/01/15 07:02:53
Added: src/hyph README cs.xml da.xml de.xml de_DR.xml el.xml en.xml
en_GB.xml en_US.xml es.xml fi.xml fr.xml hu.xml
hyphenation.dtd it.xml nl.xml no.xml pl.xml pt.xml
ru.xml sk.xml
jeremias2003/01/15 07:07:06
Modified:.build.xml
Log:
Adjust to new directory for hyphenation
Revision ChangesPath
1.72 +1 -3 xml-fop/build.xml
Index: build.xml
===
RCS file:
Hi,
Below is the result of my cross-checking. For each element and
attribute, the first value (yes/no) comes from the schema and the second
one comes from the file compliance.xml. The values tell if the
element/attribute is supported. Then there is my comment.
Notes:
1. Individual compound
Jeremias Maerki wrote:
I'll continue to do the directory moves in the redesign and I'm still
hoping for a volunteer to do the server side move/copy of the src/org
directory to src/java/org.
I'll be glad to help with the server side move/copy. AFAIK, a simple Unix
mv/cp should do the trick on
Victor Mote wrote:
us only about 21 MB of disk space). The real issue is that /everyone's/
sandbox is messed up by this, so it is worthwhile to coordinate this so that
everyone can get changes checked in (or moved aside), blow away their
sandbox, get a clean sandbox after the surgery.
+1
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=16130.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=16130.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi Jeremias,
I just submitted the PS renderer fix/enhancement I recently mentioned
to BugZilla, bug #16130
After removing all of the stuff I also did (but which are not really
shippable yet...), the changes are really quite small.
Basically the change is: the current position is only written to
keiron 2003/01/15 11:30:24
Modified:.build.xml
Log:
include font classes for pdf transcoder
Revision ChangesPath
1.73 +1 -0 xml-fop/build.xml
Index: build.xml
===
RCS file:
Oleg Tkachenko wrote:
It's easy, but we'll loose ability to build old revisions then (didn't we
yet?). If it's not an issue, all we have to do is to move the
directory within
the repository and massage CVSROOT/history, that's it, isn't
it? Well, I'm
going to try on local cvs first with
Oleg Tkachenko wrote:
Also, it would be good to
know that we could get our repository restored if something
went wrong -- do
we know how to do that?
Isn't it just copying xml-fop directory back?
I don't understand. Copying it back from where? Do you mean:
1. We should make our own
Title: Has anybody used the Crystal Reports and how does it compare to the FOP?
Dear FOP developers,
I'm currently facing a difficult decision whether to keep developing reports using FOP or changing over to the Crystal Reports. Having been using FOP for more than 2 years, I have gained
Victor Mote wrote:
Jeremias Maerki wrote:
I'll continue to do the directory moves in the redesign and I'm still
hoping for a volunteer to do the server side move/copy of the src/org
directory to src/java/org.
I'll be glad to help with the server side move/copy. AFAIK, a simple Unix
mv/cp
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=16156.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
33 matches
Mail list logo
