Peter,
I think they don't define it because it is a common well known (to them)
idea that is used across many specs.
Here is a quick definition I found:
http://www.w3.org/TR/2000/PR-UAAG10-2310/#def-user-agent
So if the user agent is FOP (+ how the document is eventually viewed)
then the
keiron 2002/06/06 00:57:02
Modified:src/org/apache/fop/image/analyser Tag: fop-0_20_2-maintain
SVGReader.java
src/org/apache/fop/svg Tag: fop-0_20_2-maintain
SVGElement.java SVGUserAgent.java
Log:
YAAPIC
Revision
Hi Joerg,
I have had a quick look over the document. Looks very good and
comprehensive.
I have attached a diff with some changes, mostly typos.
Should this be checked into the cvs trunk so it can be with the current
docs.
There was no commit email that I could find (not that it always works).
This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2002-06-06/xml-fop.html
Buildfile: build.xml
init-avail:
init-filters-xalan2:
[copy] Copying 1
I think it was about a month ago, a status section
was added to the FOP main page. A good idea.
Four questions :
1) Could it be possible to add a date to this
status : "[last updated xx-March-2002]" ?
2) Could it be possible to move this section higher
? It is difficult to spot.
3) What
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=7200.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I don't know if you've been following the activities on the FOP mailing
list, but they are in the process of doing a core redesign. Based on some
of the comments on the XSmiles features page I posed a few quick question
to the FOP team.
Their response seems to have been fairly positive, so I
At 10:18 AM 6/6/02, you wrote:
In paticular there is a movement afoot to allow a more dynamic rendering
of the FOP content using Swing components, as opposed to the current more
static viewing approach. Support for dynamic changes to the DOM tree (via
scripting) may also be possible.
+1 here
OK, I take back some of what I previously said. I upgraded my xalan to
2.3.1 and that fixed the NPE when transforming the glossary example. I
still consistently get the NPE on my own files from the servlet, but now I
also get it from the command line. Being at a loss, per the xalan 2.3.1
Ok, here is the second stab at it :-)
I'm still crossposting now to other projects that have shown interest.
I have gotten many suggestions privately, so this will contain them +
clarifications, and a concrete example.
This discussion properly resides on the Jakarta Commons mailing list.
To
OK, I thawed the jar files and upgraded to 20.3 (and rolled back my xalan
and xerces changes) and that seems to do the trick. The fo issue was a
bug in an included stylesheet that I fixed.
-Lou
[EMAIL PROTECTED] on 06/06/2002 11:50:26
Please respond to [EMAIL PROTECTED]
To: [EMAIL
I am using FOP to take a single page of XSL:FO content and convert to PDF.
I have embedded FOP in a servlet. When I have one user requesting a page it
takes about 6 or 7 seconds to get the page formatted as PDF. It seems like
each additional simultaneous request pushes the response time by 6 or
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=7200.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
[EMAIL PROTECTED] wrote:
I am now testing using the glossary xml/xsl files in the example directory,
but with the same results. It works fine from the command line, but NPE
whenever I introduce the SAXResult or SAXSource. I'm starting to think it
might be something with me environment.
14 matches
Mail list logo
