Re: Help for bug 2545

[Luca Mambretti]

 I've gotten a little further on this, now I'm able to obtain correct print and 
AWT output if I modify the method:


public boolean updateClip(Shape cl)

of the class:

org.apache.fop.render.java2d.Java2DGraphicsState


to never intersect new clips with older ones, this is most probably the wrong 
solution, since there might be cases when the intersect is really necessary, 
but at least for my use case it might be enough, i do not need any fancy 
rounding to the edges of the document, and AWT most probably do not support 
them anyway.


I'm not sure if it will be useful to add a patch with this modification to the 
bug, assuming I do not find any failing test cases, I still need to setup the 
junit bits for those.

Thank you again,
Luca.

-Luca Mambretti  wrote: -
To: fop-dev@xmlgraphics.apache.org
From: Luca Mambretti 
Date: 14/12/2015 11:13
Subject: Help for bug 2545

 Hi everyone,

a couple of weeks ago i created this bug:

https://issues.apache.org/jira/browse/FOP-2545#

The problem in short is that when I directly print a document, header and 
footer sections are truncated, the PDF output is fine.


Since it's now becoming quite critical for me I would love to try my luck at 
solving it myself.

I've already started by downloading the sources for 2.0 and setting up a debug 
environment, I do suspect the java2D renderer is to blame, but since I'm not 
that familiar with the sources I would like to ask if anyone that is, could 
point me in the correct direction.

Thany you in advance for your help,
Luca.

RE: Help needed for RTF

[Robert Meyer]

Hi Markus,

I had a quick look at this yesterday but didn't get very far with it past 
confirming what you said earlier. The structure being written has the two list 
items containing only the textrun as children with the table being listed 
separately below. I am not sure yet whether it would simply be a case of fixing 
this by adding the table rtf element as a child of the listitem or whether 
there is more to it. 

I did notice that the table has a case to determine if the is table nested 
within a table cell and to perform a special case where it writes the pard 
keyword. According to the RTF specification, pard is used to reset the text 
formatting so that may need to be done as well for nested tables in lists. I am 
afraid I am not that familiar with RTF to know whether anything else needs to 
be done in this case, but it might just be worth trying it first and see what 
the result is.

If I get a bit of spare time i'll take another look and see if I can get it to 
correctly add the table as a child item and see what happens. In any case i'll 
let you know what I find.

Regards,

Robert Meyer

Subject: Help needed for RTF
Date: Thu, 21 Feb 2013 14:19:09 +0100
From: markus.sticker.e...@zf.com
To: fop-dev@xmlgraphics.apache.org

Hello, I’m looking for Tables nested in Lists.I need some information about the 
process that lead to
lists without  nested tables. Mit freundlichen Grüßen/Kind regardsMarkus Sticker
Technik ZF-Konzern/Operations and Technology ZF Group
Infrastruktur/Infrastructure (OTEP4)ZF Friedrichshafen AG
88038 Friedrichshafen, Deutschland/Germany
Telefon/Phone  +49 7541 77-7644, Telefax/Fax  +49 7541 77-907644
markus.sticker.e...@zf.com
Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Prof. Dr. 
Giorgio Behr 
Vorstand/Board of Management: Dr. Stefan Sommer (Vorsitzender/CEO), Dr. 
Konstantin Sauer, Dr. Peter Ottenbruch, Jürgen Holeksa, Dr. Gerhard Wagner, 
Reinhard Buhl, Rolf Lutz, Wilhelm RehmSitz/Headquarters: Friedrichshafen 
Handelsregistereintrag Amtsgericht Ulm HRB 630206/Trade register of the 
municipal court of Ulm HRB 630206 

Re: Help for svg on IBM AIX

[Max Berger]

Dear Bibhu Das,

you have addressed the wrong mailing list. This list is about
development of fop. For usage problems, please send an email to fop-user.

Bibhu_Das schrieb:
 I have installed the X11 libraries for displaying bar graphs which is
 done by svg fo:instream-foreign-object.
 Can I know the name of specific libraries for displaying svg bar graphs.

For SVG you need the batik libraries, which are part of the fop standard
distribution. So the problem here seems to be something else. Please add:
- a minimal .fo file which shows your problem
- the exact output when you run fop

 Thanks and Regards
 Bibhu Das

Max

-- 
http://max.berger.name/
OpenPGP ID: C93C5700 Fpr: AB6638CE472A499B3959 ADA2F989A2E5C93C5700



signature.asc
Description: OpenPGP digital signature

Re: Help for svg on IBM AIX

[Jeremias Maerki]

Please send questions about FOP to the fop-us...@xmlgraphics.apache.org
list in the future. Thanks.

If you just want to display SVG images, that requires Apache Batik in
the classpath. Batik is bundled with FOP.

I currently know of no FOP extensions that would allow to add bar graphs
(you mean charts, right?) in a special XML dialect as part of an
fo:instream-foreign-object. So that means you have to generate SVG
graphics from bar graphics using a third-party tool. You can find a
number of those under:
http://java-source.net/open-source/charting-and-reporting
Or you use Google's Chart API, for example:
http://code.google.com/apis/chart/ (but that doesn't support SVG)


On 20.02.2009 07:34:01 Bibhu_Das wrote:
 Dear All,
 I have installed the X11 libraries for displaying bar graphs which is done by 
 svg fo:instream-foreign-object.
 Can I know the name of specific libraries for displaying svg bar graphs.
 
 Thanks and Regards
 
 Bibhu Das


Jeremias Maerki

Re: help starting a swt-renderer

[Jeremias Maerki]

Sebastian,

sounds interesting. I'd like to motivate you not to implement a renderer
but implement a IFDocumentHandler/IFPainter pair. This is part of the
new intermediate format I'm currently developing in a branch [1].
Renderers are quite complicated to implement. The new design OTOH allows
you to concentrate on the minimum necessary without the need to know too
many details of the area tree. I'm planning to propose a merge of this
branch into trunk before the end of the year. So I don't think there's
any risk for you to work off this branch for now. After all, I'm doing
the same by re-implementing all previous output formats (except maybe
AFP which Adrian Cumiskey is likely to handle). And it looks like
implementing an IFDocumentHandler takes less than half the development
time of a Renderer.

Like the renderers the IFDocumentHandler implementations are essentially
plug-ins to FOP, so you can easily implement this in a separate project
and if there's enough interest, we can talk about a donation to the FOP
project later.

Information about the design of the new intermediate format and the
resulting interfaces and other infrastructure can be found at [2].
You've also already got a number of examples: PDF, PCL, Java2D/TIFF are
already practically finished. PostScript is on the way and I've started
an SVG implementation in the sandbox. The best example for you is
probably the Java2D/TIFF implementation since it's closest to SWT. That
one also doesn't have to deal with all the file generating classes since
it's just working against a well-known Java API.

To start your SWT implementation, create a new Java project, decide on a
package name and prepare two classes implementing IFDocumentHandler
(document-level) and IFPainter (page-level). These interfaces are found
in the package org.apache.fop.render.intermediate. To register the new
implementation, you need to define a MIME type (see also
MimeConstants.java) and create a class extending AbstractIFDocumentHandlerMaker
which serves as a factory class. Then create a text file called
META-INF/services/org.apache.fop.render.intermediate.IFDocumentHandler
in which you write the fully qualified class name of that maker class.
One thing I may have to add (that is currently missing) is a
setIFDocumentHandlerOverride() method in FOUserAgent, so you can set up
the output in an SWT window. The normal API is optimized for generating
files. I don't want to write too much, yet. This is already the most
important part. I'm happy to guide you further and to help you with any
questions you might have. This should already get you started.

Please consider subscribing to the fop-dev mailing list. That way I
don't have to moderate your posts each time and CC you. ;-)

[1] 
https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/Temp_AreaTreeNewDesign
[2] http://wiki.apache.org/xmlgraphics-fop/AreaTreeIntermediateXml/NewDesign

On 13.11.2008 18:54:35 Sebastian Fuchs wrote:
 Hello,
 
 we successfully use FOP in our eclipse rcp application to export and 
 print documents.
 To provide a print preview and to be able to use all native printer 
 driver capabilities,
 we are willing to write our own SWT renderer basing on the AreaTree.
 
 Where can we find detailed basic information about the structure of 
 AreaTree and the approach of a render implementation ?
 
 If there is general interest, we would contribute our work to the FOP 
 project.
 
 Thanks,
 Sebastian

HTH
Jeremias Maerki

Re: Help Refactoring the Website

[The Web Maestro]

BTW, I added a table column for 0.94 to the Compliance page. I did
*not* remove the 0.20.5 or 0.93 columns. Those can be removed fairly
easily, if decided, but I figured we might want to keep those (but add
a note that fop-0.20.5 is unsupported).

Web Maestro Clay

-- 
Regards,

The Web Maestro
-- 
[EMAIL PROTECTED] - http://homepage.mac.com/webmaestro/
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet

Re: Help Refactoring the Website

[The Web Maestro]

On 7/31/07, Vincent Hennebert [EMAIL PROTECTED] wrote:
 Hi Clay,

 Thanks for chiming in!

I've committed my changes, so the site should be re-factored. There is
likely a bunch of content in the '0.94' realm that needs updating so
it's more relevant to the current release. In addition, there may be
some pages, which will need some attention (like
'branches/fop-0_94/build/site/0.94/releaseNotes_0.94.html',
'branches/fop-0_94/build/site/0.94/changes_0.94.html' and
'branches/fop-0_94/build/site/0.94/knownissues_overview.html').

  It didn't take too much to re-factor the site... Just had to adjust
  the tabs.xml and site.xml documents (and remove the 0.20.5 documents).
  I'll need to do a `svn delete` for the 0.20.5/ and 0.93/ directories,
  so let me know if I should do that NOW, or we need to wait until we're
  more ready for the release.

 As I said I already did it, but if you wanna double-check all the
 better. Also, one thing that would be great if you could have a look at,
 is improving the stylesheet a bit. For example the main content is set
 to be displayed at 80% of its size. That should really not be the case
 as the setting for the main text's size should be left to the user's
 choice (I'm ok with reducing the size of e.g. the menu, however). I'm
 not really sure where to change that as the CSS stylesheets seem to
 directly come from the Forrest distribution.

I haven't had a chance to work on the font-size yet, but here're a
couple of links to get started on it if I can't get to it in time:

http://forrest.apache.org/docs_0_70/your-project.html#skins

http://forrest.apache.org/docs_0_70/skin-package.html

FWIW, I tried modifying the
'branches/fop-0_94/src/documentation/skinconf.xml' file, but it didn't
work. I added the 'p, td, li' declaration to adjust it and make it
larger. I didn't commit my change.

Here are a few locations for the Forrest skin files if you want to
modify them (although the CSS change may be overwritten if someone
else changes it (hence it'd be better to find a 'skinconf.xml'
solution):

apache-forrest-0.7/main/webapp/skins/pelt/css/profile.css.xslt
fop/trunk/build/site/skin/profile.css
fop/trunk/build/site/skin/profile.css.xslt

However, I think it's somewhat of a 'moot' point, as in the upper
right of the page, there are increase and decrease font-size widget
buttons, and the settings appear to follow you from page to page...

Here's the snippet,

  !--
extra-css - here you can define custom css-elements that are
a. overriding the fallback elements or
b. adding the css definition from new elements that you may have
   used in your documentation.
--
  extra-css
!--Example of b.
To define the css definition of a new element that you may have used
in the class attribute of a p node.
e.g. p class=quote/
--
p, td, li {
  font-size: 94%;
}
p.quote {
  margin-left: 2em;
  padding: .5em;
  background-color: #f0f0f0;
  font-family: monospace;
}
.yes { background-color: #99FF99; }
.no  { background-color: #FF; }
.partial { background-color: #CC; }
.ForrestTable td.basic  { text-align: center; }
.ForrestTable td.extended   { text-align: center; }
.ForrestTable td.complete   { text-align: center; }
.ForrestTable td.na { text-align: center; }
.ForrestTable td.yes{ background-color: #99FF99;
text-align: center; }
.ForrestTable td.no { background-color: #FF;
text-align: center; }
.ForrestTable td.partial{ background-color: #CC;
text-align: center; }
.ForrestTable td.category   { /*background-color: #CFDCED;*/
   font-size: 1.2em }

  /extra-css

Web Maestro Clay

-- 
Regards,

The Web Maestro
-- 
[EMAIL PROTECTED] - http://homepage.mac.com/webmaestro/
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet

Re: Help Refactoring the Website

[Vincent Hennebert]

Hi Clay,

The Web Maestro a écrit :
 On 7/31/07, Vincent Hennebert wrote:

 I've committed my changes, so the site should be re-factored. There is
 likely a bunch of content in the '0.94' realm that needs updating so
 it's more relevant to the current release. In addition, there may be
 some pages, which will need some attention (like
 'branches/fop-0_94/build/site/0.94/releaseNotes_0.94.html',
 'branches/fop-0_94/build/site/0.94/changes_0.94.html' and
 'branches/fop-0_94/build/site/0.94/knownissues_overview.html').

That sounds great, thanks! I’ll have a closer look on the WE and
complete if necessary.

 As I said I already did it, but if you wanna double-check all the
 better. Also, one thing that would be great if you could have a look at,
 is improving the stylesheet a bit. For example the main content is set
 to be displayed at 80% of its size. That should really not be the case
 as the setting for the main text's size should be left to the user's
 choice (I'm ok with reducing the size of e.g. the menu, however). I'm
 not really sure where to change that as the CSS stylesheets seem to
 directly come from the Forrest distribution.

 I haven't had a chance to work on the font-size yet, but here're a
 couple of links to get started on it if I can't get to it in time:

 http://forrest.apache.org/docs_0_70/your-project.html#skins

 http://forrest.apache.org/docs_0_70/skin-package.html

 FWIW, I tried modifying the
 'branches/fop-0_94/src/documentation/skinconf.xml' file, but it didn't
 work. I added the 'p, td, li' declaration to adjust it and make it
 larger. I didn't commit my change.

Thanks for the pointers. By adding the following in skinconf.xml:
#content { font-size: 100% }
I managed to get normal size for the main text. I didn’t commit the
change because I wasn’t sure this was the right place to do that.

Strangely enough when I run Forrest on my local copy I get different
(smaller) font sizes than on the website for all the other elements but
the main text (without the above change). The screen.css style sheets
are exactly the same though. I wonder what might be happening?


 Here are a few locations for the Forrest skin files if you want to
 modify them (although the CSS change may be overwritten if someone
 else changes it (hence it'd be better to find a 'skinconf.xml'
 solution):

 apache-forrest-0.7/main/webapp/skins/pelt/css/profile.css.xslt
 fop/trunk/build/site/skin/profile.css
 fop/trunk/build/site/skin/profile.css.xslt

 However, I think it's somewhat of a 'moot' point, as in the upper
 right of the page, there are increase and decrease font-size widget
 buttons, and the settings appear to follow you from page to page...

Still, the user shouldn’t have to do anything to retrieve their favorite
text size. That’s a basic accessibility rule IMHO.
Moreover, I don’t get any font-size widget button, again both on my
local copy and the website!? FWIW I’m using the Trunk of the 0.7 branch.

snip/

Vincent

Re: Help Refactoring the Website

[The Web Maestro]

Hi Vincent,

On 8/2/07, Vincent Hennebert [EMAIL PROTECTED] wrote:
 The Web Maestro a écrit :
  On 7/31/07, Vincent Hennebert wrote:
  As I said I already did it, but if you wanna double-check all the
  better. Also, one thing that would be great if you could have a look at,
  is improving the stylesheet a bit. For example the main content is set
  to be displayed at 80% of its size. That should really not be the case
  as the setting for the main text's size should be left to the user's
  choice (I'm ok with reducing the size of e.g. the menu, however). I'm
  not really sure where to change that as the CSS stylesheets seem to
  directly come from the Forrest distribution.
 
  I haven't had a chance to work on the font-size yet, but here're a
  couple of links to get started on it if I can't get to it in time:
 
  http://forrest.apache.org/docs_0_70/your-project.html#skins
 
  http://forrest.apache.org/docs_0_70/skin-package.html
 
  FWIW, I tried modifying the
  'branches/fop-0_94/src/documentation/skinconf.xml' file, but it didn't
  work. I added the 'p, td, li' declaration to adjust it and make it
  larger. I didn't commit my change.

 Thanks for the pointers. By adding the following in skinconf.xml:
 #content { font-size: 100% }
 I managed to get normal size for the main text. I didn't commit the
 change because I wasn't sure this was the right place to do that.

That's perfect. Go ahead and commit...

 Strangely enough when I run Forrest on my local copy I get different
 (smaller) font sizes than on the website for all the other elements but
 the main text (without the above change). The screen.css style sheets
 are exactly the same though. I wonder what might be happening?

Can you upload the `forrest` output to your web space, so we can take
a look? Here's the result of mine from last night (without the
#content changes):

http://people.apache.org/~clay/fop-0.94/

  Here are a few locations for the Forrest skin files if you want to
  modify them (although the CSS change may be overwritten if someone
  else changes it (hence it'd be better to find a 'skinconf.xml'
  solution):
 
  apache-forrest-0.7/main/webapp/skins/pelt/css/profile.css.xslt
  fop/trunk/build/site/skin/profile.css
  fop/trunk/build/site/skin/profile.css.xslt
 
  However, I think it's somewhat of a 'moot' point, as in the upper
  right of the page, there are increase and decrease font-size widget
  buttons, and the settings appear to follow you from page to page...

 Still, the user shouldn't have to do anything to retrieve their favorite
 text size. That's a basic accessibility rule IMHO.
 Moreover, I don't get any font-size widget button, again both on my
 local copy and the website!? FWIW I'm using the Trunk of the 0.7 branch.

I wonder if it has to do with your browser setup (what are you
using--browser/version, OS/version w service packs, build etc.)? Have
you tried on another machine? Maybe Forrest needs to have a support
ticket put in about the font resize buttons (and if you prefer the
font-size as well).

 snip/

 Vincent

-- 
Regards,

The Web Maestro
-- 
[EMAIL PROTECTED] - http://homepage.mac.com/webmaestro/
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet

Re: Help Refactoring the Website

[Vincent Hennebert]

Hi Clay,

The Web Maestro a écrit :
 Hi Vincent,
 
 On 8/2/07, Vincent Hennebert wrote:
snip/
 Thanks for the pointers. By adding the following in skinconf.xml:
 #content { font-size: 100% }
 I managed to get normal size for the main text. I didn't commit the
 change because I wasn't sure this was the right place to do that.
 
 That's perfect. Go ahead and commit...

Ok, I’ll do.


 Strangely enough when I run Forrest on my local copy I get different
 (smaller) font sizes than on the website for all the other elements but
 the main text (without the above change). The screen.css style sheets
 are exactly the same though. I wonder what might be happening?
 
 Can you upload the `forrest` output to your web space, so we can take
 a look? Here's the result of mine from last night (without the
 #content changes):
 
 http://people.apache.org/~clay/fop-0.94/

Here it is:
http://people.apache.org/~vhennebert/fop-0.94/

snip/
 I wonder if it has to do with your browser setup (what are you
 using--browser/version, OS/version w service packs, build etc.)? Have
 you tried on another machine? Maybe Forrest needs to have a support
 ticket put in about the font resize buttons (and if you prefer the
 font-size as well).

Firefox 2.0.0.5
Ubuntu Feisty
Revision 556027 of Forrest 0.7 but no CSS file got modified when 
I updated my copy (only Java code).

I think I’m becoming crazy. On your version the main text is smaller 
than on mine (without applying the CSS change), which now has normal 
size. For all other text objects (menu, etc.), sizes are the same.

Trying with Konqueror the main text is larger on my version, but also 
the tab titles (Home, Version 0.93, etc.).

I have no font-size button on any version, with any browser. Note that 
I have them on the XML Graphics site.

!?!??
Thanks for looking into this,
Vincent

Re: Help Refactoring the Website

[The Web Maestro]

On 8/2/07, Vincent Hennebert [EMAIL PROTECTED] wrote:
  Strangely enough when I run Forrest on my local copy I get different
  (smaller) font sizes than on the website for all the other elements but
  the main text (without the above change). The screen.css style sheets
  are exactly the same though. I wonder what might be happening?
 
  Can you upload the `forrest` output to your web space, so we can take
  a look? Here's the result of mine from last night (without the
  #content changes):
 
  http://people.apache.org/~clay/fop-0.94/

 Here it is:
 http://people.apache.org/~vhennebert/fop-0.94/

The content appears to be *exactly* the same size, but the font-size
for the tabs appears to be smaller in our versions.

 snip/
  I wonder if it has to do with your browser setup (what are you
  using--browser/version, OS/version w service packs, build etc.)? Have
  you tried on another machine? Maybe Forrest needs to have a support
  ticket put in about the font resize buttons (and if you prefer the
  font-size as well).

 Firefox 2.0.0.5
 Ubuntu Feisty
 Revision 556027 of Forrest 0.7 but no CSS file got modified when
 I updated my copy (only Java code).

 I think I'm becoming crazy. On your version the main text is smaller
 than on mine (without applying the CSS change), which now has normal
 size. For all other text objects (menu, etc.), sizes are the same.

If I were feeling 'feisty' I might say something pithy, like 'You
probably are going crazy...' but I'm not so I'll tell you that the
reason our sites didn't have the font-size adjust buttons was because
they weren't enabled in 'src/documentation/skinconf.xml'. I just
enabled it, as well as:
- compliance links (shows HTML  CSS compliance badges)
- external-link-image (indicates off-site links with mini-image icon)
- and XML file availability (enables re-purposing of content via XML)

 Trying with Konqueror the main text is larger on my version, but also
 the tab titles (Home, Version 0.93, etc.).

 I have no font-size button on any version, with any browser. Note that
 I have them on the XML Graphics site.

Mentioning that it was on the XML Graphics site gave me the clue it
was a preference setting.

 !?!??
 Thanks for looking into this,
 Vincent

Glad I could help... It's been a while since I've delved into Forrest.
In fact, they just released Forrest 0.8, so someone may want to look
into identifying if there's a compelling reason to 'upgrade'. ;-)

-- 
Regards,

The Web Maestro
-- 
[EMAIL PROTECTED] - http://homepage.mac.com/webmaestro/
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet

Re: Help Refactoring the Website

[The Web Maestro]

On 7/30/07, The Web Maestro [EMAIL PROTECTED] wrote:
 Thanks Chris! I'll look into what I can to help re-factor the site to
 remove the 0.20.5 references. I agree, that with 0.93  0.94, the 0.20
 branch information is no longer necessary.

I was able to factor out the 0.20.5 stuff but there are a couple of
relatively minor issues:

1. I am planning to remove 0.93, but want to confirm this should be
removed so we have only 0.94 and trunk ( as well as Trunk, etc.)
2. To create the '0.94' section, I copied the 'Trunk' area, but there
are numerous areas in the documentation which are likely outdated.
Should I commit my changes and let others adjust the documentation to
reflect the recent changes to the code?
3. There are a few places where a 'date' will be required to identify
when 0.94 is released, but I'm not sure what that date is yet.

It didn't take too much to re-factor the site... Just had to adjust
the tabs.xml and site.xml documents (and remove the 0.20.5 documents).
I'll need to do a `svn delete` for the 0.20.5/ and 0.93/ directories,
so let me know if I should do that NOW, or we need to wait until we're
more ready for the release.

Web Maestro Clay

-- 
Regards,

The Web Maestro
-- 
[EMAIL PROTECTED] - http://homepage.mac.com/webmaestro/
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet

Re: Help Refactoring the Website

[Vincent Hennebert]

Hi Clay,

Thanks for chiming in!

It seems we are somewhat duplicating our efforts here. I already removed
the 0.20.5 tab and added a new one for 0.94. Look at the 0.94 branch of
the svn repository. I prefer to work in the branch so that the trunk
stil reflects the current site, and we can re-generate it if ever
needed.
(More below.)

The Web Maestro a écrit :
 On 7/30/07, The Web Maestro [EMAIL PROTECTED] wrote:
 Thanks Chris! I'll look into what I can to help re-factor the site to
 remove the 0.20.5 references. I agree, that with 0.93  0.94, the 0.20
 branch information is no longer necessary.

 I was able to factor out the 0.20.5 stuff but there are a couple of
 relatively minor issues:

 1. I am planning to remove 0.93, but want to confirm this should be
 removed so we have only 0.94 and trunk ( as well as Trunk, etc.)

No, I think the 0.93 section should remain, for those who don’t want to
immediately upgrade. There will be slight config changes between the two
versions so it’s best that each one have its dedicated tab.


 2. To create the '0.94' section, I copied the 'Trunk' area, but there

So did I, which is an indication to me that that was the way to do ;-)

 are numerous areas in the documentation which are likely outdated.
 Should I commit my changes and let others adjust the documentation to
 reflect the recent changes to the code?

Yes, I thought of that afterwards. It may make sense to update the
content /before/ creating the 0.94 tab, in order to avoid duplicating
changes or managing svn merges. I’ve already updated most of the Home
tab and I’ll try to work on the Trunk one ASAP.


 3. There are a few places where a 'date' will be required to identify
 when 0.94 is released, but I'm not sure what that date is yet.

The best IMO is to put an “XX August 20007” everywhere and replace the
“XX” with the actual date once it is known. That is, once the vote is
done, when I upload the artifacts, I’ll do the change and update the
website in the same time.


 It didn't take too much to re-factor the site... Just had to adjust
 the tabs.xml and site.xml documents (and remove the 0.20.5 documents).
 I'll need to do a `svn delete` for the 0.20.5/ and 0.93/ directories,
 so let me know if I should do that NOW, or we need to wait until we're
 more ready for the release.

As I said I already did it, but if you wanna double-check all the
better. Also, one thing that would be great if you could have a look at,
is improving the stylesheet a bit. For example the main content is set
to be displayed at 80% of its size. That should really not be the case
as the setting for the main text’s size should be left to the user’s
choice (I’m ok with reducing the size of e.g. the menu, however). I’m
not really sure where to change that as the CSS stylesheets seem to
directly come from the Forrest distribution.

Thanks,
Vincent

Re: Help Refactoring the Website

[Chris Bowditch]

The Web Maestro wrote:


On 7/29/07, Andreas L Delmelle [EMAIL PROTECTED] wrote:


On Jul 27, 2007, at 18:36, Andreas L Delmelle wrote:


it would be good to refactor
the website before the release and, in particular, remove the 0.20.5
tab.


This could maybe still be done before the release, but I started
wondering...



I'd like to call for help on this, as this is not a small task.
I'll try to do as much as possible on the WE, but that would be
great if
we could share the work. Any volunteers?
Some tasks I can think of right now:
- update the introduction page (latest stable release, version of the
 recommendation implemented...)
- add a small news section on the home page? this would make the site
 look more live. It could simply list the latest versions released.
- correct/update/simplify other pages


Wouldn't it be better, FTM, to focus on making the site 0.94-ready,
and do any serious restyling afterwards? It's just that a release by
itself already takes some work and preparation... Just a thought.



I'll spend some time looking into what it'll take to refactor,
although I agree with Andreas that it would be better to focus on
getting 0.94 ready and do any necessary 'purging' of fop-0.20.5 after
that, if that's what's deemed best.

I'm not actually convinced eradicating it from the FOP site is the
best route, as there will be some who can't upgrade (namely users of
AIX 4.1 and/or others who can't upgrade to a Java Run-time Environment
newer than 1.3)... I would think the fop-0.20.5 information should
remain accessible somewhere other than on http://archive.org/. The
good part is, that the content will likely never change and would
exist on a separate TAB, out of the way. That's not to say I'm firmly
in the trench of keeping the content, but I don't see how it'd hurt to
retain it.



Hi Clay,

0.93 and 0.94 are still compatible with Java 1.3 so AIX 4.1 users will 
still be able to use it. We have clients running AIX who use Java 1.4, 
so I didn't realise AIX couldn't run 1.4. Maybe its down to exact o/s 
version. In either case, we decided to drop support for 1.3 after 0.94. 
So if 1.3 is still needed in the future users can download 0.94. And I 
think the website should reflect this.


The reason why 0.20.5 should be removed from the website is that 
fop-users is still receiving several posts per week relating to it. 
There is now very little knowledge of it within our development team, so 
supporting it is not something we would like to continue. Therefore, 
users should be actively discouraged from downloading it. Looking at the 
website today, I get the impression that 0.20.5 and 0.94 are two 
separate development streams which both receive active maintenance. 
However, we all know that is not the case. 0.9x is a direct replacement 
for the 0.20.x series.


It made sense to keep 0.20.5 on the website for a couple of years after 
the initial 0.9x release to give folk a chance to upgrade. But 0.9x has 
been around for a couple of years and now I believe it is time to start 
encouraging users to switch over.


Chris

Re: Help Refactoring the Website

[The Web Maestro]

On 7/30/07, Chris Bowditch [EMAIL PROTECTED] wrote:
 Hi Clay,

 0.93 and 0.94 are still compatible with Java 1.3 so AIX 4.1 users will
 still be able to use it. We have clients running AIX who use Java 1.4,
 so I didn't realise AIX couldn't run 1.4. Maybe its down to exact o/s
 version. In either case, we decided to drop support for 1.3 after 0.94.
 So if 1.3 is still needed in the future users can download 0.94. And I
 think the website should reflect this.

 The reason why 0.20.5 should be removed from the website is that
 fop-users is still receiving several posts per week relating to it.
 There is now very little knowledge of it within our development team, so
 supporting it is not something we would like to continue. Therefore,
 users should be actively discouraged from downloading it. Looking at the
 website today, I get the impression that 0.20.5 and 0.94 are two
 separate development streams which both receive active maintenance.
 However, we all know that is not the case. 0.9x is a direct replacement
 for the 0.20.x series.

 It made sense to keep 0.20.5 on the website for a couple of years after
 the initial 0.9x release to give folk a chance to upgrade. But 0.9x has
 been around for a couple of years and now I believe it is time to start
 encouraging users to switch over.

 Chris

Thanks Chris! I'll look into what I can to help re-factor the site to
remove the 0.20.5 references. I agree, that with 0.93  0.94, the 0.20
branch information is no longer necessary.

Web Maestro Clay
-- 
Regards,

The Web Maestro
-- 
[EMAIL PROTECTED] - http://homepage.mac.com/webmaestro/
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet

Re: Help Refactoring the Website

[Andreas L Delmelle]

On Jul 27, 2007, at 18:36, Andreas L Delmelle wrote:


On Jul 27, 2007, at 09:57, Vincent Hennebert wrote:

The 0.94 version of FOP is basically ready to be released. The  
poll on
fop-user gave interesting results, although not applicable to the  
next
release. What about creating a wiki page summarizing those user  
wishes?

Users could then maintain it by themselves. Andreas, would you be
willing to take care of this?


Sure.


Just did this. Probably due to the holidays, I presume, but there  
were ultimately only very few explicit requests.


BTW:


As Chris pointed out a few days ago [1],



I'd hereby also like to apologize to Chris for not responding. Not  
really my fault though, just re-checked my mails, and the referenced  
post seems not to have made it into my mailbox... and I'm not in the  
habit of checking for posts on the archives (until they're old history)


Anyway, the idea definitely looks OK to me. I'm all for.


it would be good to refactor
the website before the release and, in particular, remove the 0.20.5
tab.


This could maybe still be done before the release, but I started  
wondering...



I'd like to call for help on this, as this is not a small task.
I'll try to do as much as possible on the WE, but that would be  
great if

we could share the work. Any volunteers?
Some tasks I can think of right now:
- update the introduction page (latest stable release, version of the
  recommendation implemented...)
- add a small news section on the home page? this would make the site
  look more live. It could simply list the latest versions released.
- correct/update/simplify other pages


Wouldn't it be better, FTM, to focus on making the site 0.94-ready,  
and do any serious restyling afterwards? It's just that a release by  
itself already takes some work and preparation... Just a thought.



Cheers

Andreas

Re: Help Refactoring the Website

[Andreas L Delmelle]

On Jul 27, 2007, at 09:57, Vincent Hennebert wrote:


The 0.94 version of FOP is basically ready to be released. The poll on
fop-user gave interesting results, although not applicable to the next
release. What about creating a wiki page summarizing those user  
wishes?

Users could then maintain it by themselves. Andreas, would you be
willing to take care of this?


Sure. I have one more important change I'd like to see in the  
release, and which is just about finished. (concerns the  
PropertyCache, more about that in a separate post later this evening)



As Chris pointed out a few days ago [1], it would be good to refactor
the website before the release and, in particular, remove the 0.20.5
tab. I'd like to call for help on this, as this is not a small task.
I'll try to do as much as possible on the WE, but that would be  
great if

we could share the work. Any volunteers?
Some tasks I can think of right now:
- update the introduction page (latest stable release, version of the
  recommendation implemented...)
- add a small news section on the home page? this would make the site
  look more live. It could simply list the latest versions released.
- correct/update/simplify other pages

So, in short: HEEELP! ;-)


Concerning the documentation, I'm actually limited in my  
possibilities. I know just about enough to update the compliance page  
every once in a while, but thorough restructuring is not something  
I'd immediately take on. I'm afraid I'm of no immediate use there.

Sure hope our Web Maestro Clay chimes in to offer you useful hands.


Cheers

Andreas

Re: Help

[Eddie Mc Greal]

Hi Imran,

I had a similar problem and it turned out to be spaces in the path name
where the war file was deployed.
That may be the issue ­ in any case you can rename your jar file to zip ­
and then browse it to make sure the file is included.

Eddie




On 05/12/2006 10:19, Imran Khan [EMAIL PROTECTED] wrote:

 
 
 -- Forwarded message --
 From: Imran Khan [EMAIL PROTECTED]
 Date: Dec 5, 2006 2:15 PM
 Subject: Help
 To: [EMAIL PROTECTED]
 
 Hi,
 
 I am using FOP jar for transforming a XML file to a PDF file. In the
 Application i am using an XSL file for the transformation purpose.
 The xsl file is used as a resouce within the application.
 The application is bulit and run sucessfully.  Note: XSL file is under the
 same package as class which converts xml to pdf and the class is using the xsl
 file internally using getClass.getResource(XSLT_FILE_NAME).getPath().
 
 
 
 Now i make the jar of the above application and import the jar to a new
 application and call the class for transforming a xml at a given location to
 the pdf . But this time it could not find the xsl file within the jar.
 What could be the possible solution to the above problem. It throws
 FileNotFoundException  for xslt.
 
 Thanks 
 Imran Khan
 
 


Best regards
Eddie Mc Greal
Imilia ­ Interactive Mobile Applications GmbH.
Garystrasse 94,
14195 Berlin
Germany

Phone: int+ 49 (0)30 84591573
Mobile: int + 49 (0) 170 5547619
[EMAIL PROTECTED]

Re: Help

[Imran Khan]

Hi Eddie,

Thanks for your reply. But it did not work
I am getting the following exception:
org.apache.fop.apps.FOPException:
javax.xml.transform.TransformerConfigurationException:
javax.xml.transform.TransformerException: java.io.FileNotFoundException:
E:\JodhpurVidushi\RulesDict\testxml\file:\E:\JodhpurVidushi\RulesDict\xml_pdf_covertor\bin\convertor.jar!\com\xmltopdf\convertor\honeywell.xsl
(The filename, directory name, or volume label syntax is incorrect)

the jar file is at
\E:\JodhpurVidushi\RulesDict\xml_pdf_covertor\bin\convertor.jar
the application in which i imported jar fle is
E:\JodhpurVidushi\RulesDict\testxml\

the xsl file is under \com\xmltopdf\convertor\honeywell.xsl in jar.




On 12/5/06, Eddie Mc Greal [EMAIL PROTECTED] wrote:


 Hi Imran,

I had a similar problem and it turned out to be spaces in the path name
where the war file was deployed.
That may be the issue – in any case you can rename your jar file to zip –
and then browse it to make sure the file is included.

Eddie




On 05/12/2006 10:19, Imran Khan [EMAIL PROTECTED] wrote:



-- Forwarded message --
From: *Imran Khan* [EMAIL PROTECTED]
Date: Dec 5, 2006 2:15 PM
Subject: Help
To: [EMAIL PROTECTED]

Hi,

I am using FOP jar for transforming a XML file to a PDF file. In the
Application i am using an XSL file for the transformation purpose.
The xsl file is used as a resouce within the application.
The application is bulit and run sucessfully.  Note: XSL file is under the
same package as class which converts xml to pdf and the class is using the
xsl file internally using getClass.getResource(XSLT_FILE_NAME).getPath().



Now i make the jar of the above application and import the jar to a new
application and call the class for transforming a xml at a given location to
the pdf . But this time it could not find the xsl file within the jar.
What could be the possible solution to the above problem. It throws
FileNotFoundException  for xslt.

Thanks
Imran Khan




Best regards
Eddie Mc Greal
Imilia – Interactive Mobile Applications GmbH.
Garystrasse 94,
14195 Berlin
Germany

Phone: int+ 49 (0)30 84591573
Mobile: int + 49 (0) 170 5547619
[EMAIL PROTECTED]

Re: Help for ressources to generate Rtf with Fop

[Christian Mayemba]

BONNICHON Franck a écrit :


Hello,
We are using an Fop 0.20.5.
How can we do to generate Rtf instead of Pdf ?
If it is possible, where could we find the good fop.jar to do that ?
Thanks by advance
Best regards
   F. BONNICHON (France)


Bonjour. Je me permet de vous répondre en Français car j'ai vu que vous 
êtes de France :-). Je suis analyste programmeur en Java JSP pour une 
petite SSII
à Dole (en France, à côté de Dijon). Nous éditons un progiciel de 
gestion intégré qui permet la gestion complète de l'activité d'une 
société de service (enregistrement, consultation et modification des 
clients, achats, stocks, commandes fournisseurs, affaires,  exécution 
chantier, fournisseur, gestion des collaborateurs...). Dans le cadre de 
l'utilisation de nôtre logiciel, il a été nécessaire de créer des 
fonctions d'édition de devis, factures, commandes, fiche 
d'intervention... C'est dans ce but que j'ai  mis en place la 
possibilité d'éditer ces diffarents documents au format PDF grâce à FOP 
(actuellement en version 0.20.3, je ne suis pas passé en version 0.20.5 
car elle n'apportait rien de significatif par rapport à l'ancienne). 
Bref, tout ça pour vous dire qu'en matière de RTF (car j'ai été 
confronté comme vous à ce souci, je me suis penché et trouvé la solution 
sur : http://www.codeconsult.ch/jfor/. Vous utiliser FOP, donc vous 
savez que pour l'obtenir, il se base sur deux fichiers de type XML et 
XSL pour en générer un nouveau de type FO. Il récupère ce dernier pour 
finalement aboutir à du PDF. Et bien JFOR permet  d'obtenir du RTF en se 
basant sur un fichier de type FO (également). Faites un tour sur le 
site, vous verrez, tout y est expliqué.

Bon courage!  ;-)

--
-
Christian MAYEMBA 
Société SFWan 
Tél. 03 84 70 95 71

[EMAIL PROTECTED]
-

Re: Help for ressources to generate Rtf with Fop

[Jeremias Maerki]

On 29.03.2006 18:43:21 Christian Mayemba wrote:
 BONNICHON Franck a écrit :
 
  Hello,
  We are using an Fop 0.20.5.
  How can we do to generate Rtf instead of Pdf ?
  If it is possible, where could we find the good fop.jar to do that ?
  Thanks by advance
  Best regards
 F. BONNICHON (France)
 
 Bonjour. Je me permet de vous répondre en Français car j'ai vu que vous 
 êtes de France :-). Je suis analyste programmeur en Java JSP pour une 
 petite SSII
 à Dole (en France, à côté de Dijon). Nous éditons un progiciel de 
 gestion intégré qui permet la gestion complète de l'activité d'une 
 société de service (enregistrement, consultation et modification des 
 clients, achats, stocks, commandes fournisseurs, affaires,  exécution 
 chantier, fournisseur, gestion des collaborateurs...). Dans le cadre de 
 l'utilisation de nôtre logiciel, il a été nécessaire de créer des 
 fonctions d'édition de devis, factures, commandes, fiche 
 d'intervention... C'est dans ce but que j'ai  mis en place la 
 possibilité d'éditer ces diffarents documents au format PDF grâce à FOP 
 (actuellement en version 0.20.3, je ne suis pas passé en version 0.20.5 
 car elle n'apportait rien de significatif par rapport à l'ancienne). 

You may want to look into the latest FOP release 0.91beta then. A lot of
new functionality. :-)

 Bref, tout ça pour vous dire qu'en matière de RTF (car j'ai été 
 confronté comme vous à ce souci, je me suis penché et trouvé la solution 
 sur : http://www.codeconsult.ch/jfor/. Vous utiliser FOP, donc vous 
 savez que pour l'obtenir, il se base sur deux fichiers de type XML et 
 XSL pour en générer un nouveau de type FO. Il récupère ce dernier pour 
 finalement aboutir à du PDF. Et bien JFOR permet  d'obtenir du RTF en se 
 basant sur un fichier de type FO (également). Faites un tour sur le 
 site, vous verrez, tout y est expliqué.
 Bon courage!  ;-)

The alternative is really to upgrade to the latest FOP release (0.91beta)
because JFOR has been integrated into Apache FOP. JFOR development has
stopped. You can now use FOP to create both PDF and RTF. 
http://xmlgraphics.apache.org/fop/download.html


Jeremias Maerki

RE: Help to convert an XML document to another format

[Jimmy Pierre]

Hi All,

Thanks to all who invested time to help me out. What I have done is a
cocktail. Using an XSL stylesheet and xslt2.exe, I have now a well formed
HTML file.

Next thing, I am now installing Ununtu 5.10 in order to try FO.

Best wishes and keep up the good jib,
Jimmy

-Original Message-
From: Carlos M. S. Bento Nogueira [mailto:[EMAIL PROTECTED] 
Sent: Sunday, July 31, 2005 11:37 PM
To: fop-users@xmlgraphics.apache.org; [EMAIL PROTECTED]
Cc: fop-dev@xmlgraphics.apache.org
Subject: Re: Help to convert an XML document to another format

Hi!
I'm using apache cocoon to pass xml documents from xml to html and from xml
to pdf.
Check cocoon features on
http://cocoon.apache.org/2.1/features.html
and see if it fits your problem. It is not an easy framework for
non-programmers though.

CarlosN.




On Sun, 31 Jul 2005, Jimmy Pierre wrote:

 Greetings,



 I am not a programmer, so when I encounter the type of problem that I 
 will expose, I am ever so grateful :-)



 I have a report per machine and the report can only be saved in XML.



 I would like to now convert the report in whatever, HTML, DOC, PDF, 
 spreadsheet etc. The issue is that I need to be able to exploit it.



 I have posted the report on my site:



 http://www.cisware.co.uk/xmlproblem 
 http://www.cisware.co.uk/xmlproblem
 it's only 20 K



 Anybody could give me a tool to just convert this thing? I am fluent 
 in English/French..



 Best wishes,

 Jimmy



-- 

Re: Help to convert an XML document to another format

[Carlos M. S. Bento Nogueira]

Hi!
I'm using apache cocoon to pass xml documents from xml to html and from 
xml to pdf.

Check cocoon features on
http://cocoon.apache.org/2.1/features.html
and see if it fits your problem. It is not an 
easy framework for non-programmers though.


CarlosN.




On Sun, 31 Jul 2005, Jimmy Pierre wrote:


Greetings,



I am not a programmer, so when I encounter the type of problem that I will
expose, I am ever so grateful :-)



I have a report per machine and the report can only be saved in XML.



I would like to now convert the report in whatever, HTML, DOC, PDF,
spreadsheet etc. The issue is that I need to be able to exploit it.



I have posted the report on my site:



http://www.cisware.co.uk/xmlproblem http://www.cisware.co.uk/xmlproblem
it's only 20 K



Anybody could give me a tool to just convert this thing? I am fluent in
English/French..



Best wishes,

Jimmy




--