running FOP .95 version report with 0.20 version of jar

2011-08-01 Thread vjintegrates

Hi, We have a large set of reports written with 0.20 version of FOP. We are
planning to upgrade then to .095 version. However at customer installation
there are custom reports files which we do not have access to so we did not
want to upgrade to jar file to .95 version. Will .95 version of reports fail
in .20 version of JAR ?
-- 
View this message in context: 
http://old.nabble.com/running-FOP-.95-version-report-with-0.20-version-of-jar-tp32168565p32168565.html
Sent from the FOP - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Tool or schema to validate report xsl files

2011-08-01 Thread vjintegrates

Is there tool or schema to validate report xsl files for a specific version
of FOP at development time. ?
-- 
View this message in context: 
http://old.nabble.com/Tool-or-schema-to-validate-report-xsl-files-tp32168625p32168625.html
Sent from the FOP - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



RE: Tool or schema to validate report xsl files

2011-08-01 Thread Eric Douglas
I've used a free version of a tool from editix.com just to validate some
xsl syntax.
Eclipse Java editor can also edit xsl files.
FOP's web page lists which xslfo commands it supports.
FOP's input is the xslfo.  It accepts xslt along with xml as a
convenience only.  With embedded code this part can be broken out to a
second step which references no FOP classes.
 

-Original Message-
From: vjintegrates [mailto:vijaypawnar...@gmail.com] 
Sent: Monday, August 01, 2011 6:46 AM
To: fop-users@xmlgraphics.apache.org
Subject: Tool or schema to validate report xsl files


Is there tool or schema to validate report xsl files for a specific
version of FOP at development time. ?
--
View this message in context:
http://old.nabble.com/Tool-or-schema-to-validate-report-xsl-files-tp3216
8625p32168625.html
Sent from the FOP - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Re: Content spanning multiple pages issue

2011-08-01 Thread Fernando Israel
Hi Andreas and Rob,

Thank you very much both for your suggestions.

The idea of using space-before and start-indent attributes instead of top
and left respectively, and dropping the absolute position looks promising,
I'll try that. In fact there are 2 tables in the document, the main one
which we have discussed so far, and another one I did not mentioned so far
to keep things simple, that always follows the main one and it is
conceptually a summary of it. In the summary table I have actually used
space-before and start-indent and that works fine. So now I think I should
try to translate the top and left values to space-before and start-indent
and thereby relax the whole structure and let it flow more naturally.

Let me perhaps give you a more detailed picture of what I am trying to
acomplish with FOP. This work is part of an application that deals with
billing out of a system. Part of the application let users design their own
invoice template that we then use, along with the actual data for each
invoice, to produce an invoice PDF document. So the WSIWYG editor let users
drop text, pictures and a table with the items sold which are part of the
invoice. Some of the text and the invoice items table are generated from
live data. So for instance, a typical invoice would include the company logo
(a pic) static text with the company address, dynamic text with the invoice
number, invoice date, client name and address, etc. Generally an invoice is
arranged with all these bits on the top of the page followed by a table with
the items invoiced; the table includes the name of the product, quantity,
price, etc.

This is why we need to the PDF to reproduce what the users have designed. In
the template editor since we don't know upfront the height of the table (we
know the width and the columns headers) we drop a table with 3 rows as a
sample, but in practice the table's height varied depending on the number of
invoiced items. Underneath the table there is the other table with the
summary with things such as subtotal, VAT, total, etc. We made that summary
table follow the main one using space-before and start-indent.

This design has the limitation that anything underneath the main table and
the following summary table might get hidden by the content of the tables if
they are too long. Having said that, in most of the cases that will not be
so. We just need to tell users to take this into account during design. Put
it in a different way, the tool does the job and covers most needs but it
does not cover 100% of the cases.

We did use absolute positioning because it was the easiest thing to do.
However I now see that perhaps that wasn't the best choice and doing all the
positioning with space-before and start-indent will provide a more flexible
tool. For once, it will remove the limitation that anything under the tables
might get hidden by the tables content. It will also span multiple pages if
needed.

Going forward we also plan to support header/footer, which will allow users
to have a finer control on what should appear in each page when it spans
over a single page.

One last question. I think that the main issue we are having with the
current design is the constarins along the block propagation direction. So
the first thin we need to do is to relax the structure and replace the top
attribute by the space-before one. We don't have an issue in the inline
direction, so, can I keep using the left attribute there ?. So it will be a
mix of start-before and left attributes.

Thanks again for you input. It is very much appreciated.

Regards,
Fernando


On Sun, Jul 31, 2011 at 12:11 AM, Rob Sargent rsarg...@xmission.com wrote:

 OP might also be interested in calculating the required offset on the
 second page (end of the table) at which to place (absolutely??) the
 follow-on text. If so follow the (ill-named) thread breakpoint suggestions
 please.

 One is tempted to ask why the WYSIWYG editor doesn't open a second page...




 Andreas L. Delmelle wrote:

 On 30 Jul 2011, at 21:13, Fernando Israel wrote:

 Hi Fernando,



 snip /
 So I now have to rephrase the question. Can I have a table within an
 absolute postioned block container go over to a second page it its length
 requires so ?. I guess that the answer is no, but I better ask.



 You guess correct.

 BTW, it just occurred to me, while re-examining the FO you sent, that the
 'position' property does not apply to fo:block, so it actually serves no
 purpose there.
 Specifying the property can almost be seen as wasteful, because it
 'overburdens' the property parser. Big word, because it does not matter
 _that_ much, but less is more. :-)



 If the answer is no, given my description of the objective, can you think
 of a different way of trying to achieve the objective ?.



 Let's see...

 The block-container will only be broken if its top/left positioning is
 relative, which FOP does not support. Never mind, because that is not what
 you want anyway. You would get a 

Re: Tool or schema to validate report xsl files

2011-08-01 Thread Giuseppe Briotti
2011/8/1 Eric Douglas edoug...@blockhouse.com:
 I've used a free version of a tool from editix.com just to validate some
 xsl syntax.
 Eclipse Java editor can also edit xsl files.
 FOP's web page lists which xslfo commands it supports.
 FOP's input is the xslfo.  It accepts xslt along with xml as a
 convenience only.  With embedded code this part can be broken out to a
 second step which references no FOP classes.

I agree with Eric: xml will be transformed to fo via xslt using an
appropriate xslt engine (saxon, xalan, etc.). The input format for FOP
is fo.

You can appropriate validate your xml (if a xsd is provided) and xslt.
There are several unofficial xsd for fo file too. Some tool provide
such fo schema...

G.




-- 

Giuseppe Briotti
g.brio...@gmail.com

Alme Sol, curru nitido diem qui
promis et celas aliusque et idem
nasceris, possis nihil urbe Roma
visere maius.
(Orazio)

-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



RE: Tool or schema to validate report xsl files

2011-08-01 Thread Theresa Jayne Forster
I use the open source Kernow program to test my files, it is really good for
both Schema and actually testing the transform as well.

Kindest regards


Theresa Forster
Senior Software Developer


-Original Message-
From: Eric Douglas [mailto:edoug...@blockhouse.com] 
Sent: 01 August 2011 13:48
To: fop-users@xmlgraphics.apache.org
Subject: RE: Tool or schema to validate report xsl files

I've used a free version of a tool from editix.com just to validate some
xsl syntax.
Eclipse Java editor can also edit xsl files.
FOP's web page lists which xslfo commands it supports.
FOP's input is the xslfo.  It accepts xslt along with xml as a
convenience only.  With embedded code this part can be broken out to a
second step which references no FOP classes.
 

-Original Message-
From: vjintegrates [mailto:vijaypawnar...@gmail.com] 
Sent: Monday, August 01, 2011 6:46 AM
To: fop-users@xmlgraphics.apache.org
Subject: Tool or schema to validate report xsl files


Is there tool or schema to validate report xsl files for a specific
version of FOP at development time. ?
--
View this message in context:
http://old.nabble.com/Tool-or-schema-to-validate-report-xsl-files-tp3216
8625p32168625.html
Sent from the FOP - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



-
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1390 / Virus Database: 1518/3790 - Release Date: 07/26/11




-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Re: Tool or schema to validate report xsl files

2011-08-01 Thread vjintegrates

Could you please point me to these - unofficial xsd  schema.

- There are several unofficial xsd for fo file too. Some tool provide
such fo schema... 





Giuseppe Briotti-2 wrote:
 
 2011/8/1 Eric Douglas edoug...@blockhouse.com:
 I've used a free version of a tool from editix.com just to validate some
 xsl syntax.
 Eclipse Java editor can also edit xsl files.
 FOP's web page lists which xslfo commands it supports.
 FOP's input is the xslfo.  It accepts xslt along with xml as a
 convenience only.  With embedded code this part can be broken out to a
 second step which references no FOP classes.
 
 I agree with Eric: xml will be transformed to fo via xslt using an
 appropriate xslt engine (saxon, xalan, etc.). The input format for FOP
 is fo.
 
 You can appropriate validate your xml (if a xsd is provided) and xslt.
 There are several unofficial xsd for fo file too. Some tool provide
 such fo schema...
 
 G.
 
 
 
 
 -- 
 
 Giuseppe Briotti
 g.brio...@gmail.com
 
 Alme Sol, curru nitido diem qui
 promis et celas aliusque et idem
 nasceris, possis nihil urbe Roma
 visere maius.
 (Orazio)
 
 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
 
 
 

-- 
View this message in context: 
http://old.nabble.com/Tool-or-schema-to-validate-report-xsl-files-tp32168625p32169695.html
Sent from the FOP - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



RE: Tool or schema to validate report xsl files

2011-08-01 Thread Eric Douglas
Official xslfo keywords are on the official website: http://www.w3.org/TR/xsl/
FOP supported xslfo keywords are on the FOP page: 
http://xmlgraphics.apache.org/fop/compliance.html
You can read about xsd stuff on the official site also: 
http://www.w3.org/TR/xmlschema-0/
Xsd is optional.  I don't use it..
 

-Original Message-
From: vjintegrates [mailto:vijaypawnar...@gmail.com] 
Sent: Monday, August 01, 2011 9:35 AM
To: fop-users@xmlgraphics.apache.org
Subject: Re: Tool or schema to validate report xsl files


Could you please point me to these - unofficial xsd  schema.

- There are several unofficial xsd for fo file too. Some tool provide such fo 
schema... 





Giuseppe Briotti-2 wrote:
 
 2011/8/1 Eric Douglas edoug...@blockhouse.com:
 I've used a free version of a tool from editix.com just to validate 
 some xsl syntax.
 Eclipse Java editor can also edit xsl files.
 FOP's web page lists which xslfo commands it supports.
 FOP's input is the xslfo.  It accepts xslt along with xml as a 
 convenience only.  With embedded code this part can be broken out to 
 a second step which references no FOP classes.
 
 I agree with Eric: xml will be transformed to fo via xslt using an 
 appropriate xslt engine (saxon, xalan, etc.). The input format for FOP 
 is fo.
 
 You can appropriate validate your xml (if a xsd is provided) and xslt.
 There are several unofficial xsd for fo file too. Some tool provide 
 such fo schema...
 
 G.
 
 
 
 
 --
 
 Giuseppe Briotti
 g.brio...@gmail.com
 
 Alme Sol, curru nitido diem qui
 promis et celas aliusque et idem
 nasceris, possis nihil urbe Roma
 visere maius.
 (Orazio)
 
 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
 
 
 

--
View this message in context: 
http://old.nabble.com/Tool-or-schema-to-validate-report-xsl-files-tp32168625p32169695.html
Sent from the FOP - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Re: Tool or schema to validate report xsl files

2011-08-01 Thread Giuseppe Briotti
Some of them are provided by the tool author (Oxygen, FOP, Renderx
provide a XML Schema or DTD for FO files).

Take a look at fo page at FOP: http://xmlgraphics.apache.org/fop/fo.html

section Validating XSL-FO

2011/8/1 vjintegrates vijaypawnar...@gmail.com:

 Could you please point me to these - unofficial xsd  schema.

 - There are several unofficial xsd for fo file too. Some tool provide
 such fo schema... 





 Giuseppe Briotti-2 wrote:

 2011/8/1 Eric Douglas edoug...@blockhouse.com:
 I've used a free version of a tool from editix.com just to validate some
 xsl syntax.
 Eclipse Java editor can also edit xsl files.
 FOP's web page lists which xslfo commands it supports.
 FOP's input is the xslfo.  It accepts xslt along with xml as a
 convenience only.  With embedded code this part can be broken out to a
 second step which references no FOP classes.

 I agree with Eric: xml will be transformed to fo via xslt using an
 appropriate xslt engine (saxon, xalan, etc.). The input format for FOP
 is fo.

 You can appropriate validate your xml (if a xsd is provided) and xslt.
 There are several unofficial xsd for fo file too. Some tool provide
 such fo schema...

 G.




 --

 Giuseppe Briotti
 g.brio...@gmail.com

 Alme Sol, curru nitido diem qui
 promis et celas aliusque et idem
 nasceris, possis nihil urbe Roma
 visere maius.
 (Orazio)

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org




 --
 View this message in context: 
 http://old.nabble.com/Tool-or-schema-to-validate-report-xsl-files-tp32168625p32169695.html
 Sent from the FOP - Users mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org





-- 

Giuseppe Briotti
g.brio...@gmail.com

Alme Sol, curru nitido diem qui
promis et celas aliusque et idem
nasceris, possis nihil urbe Roma
visere maius.
(Orazio)

-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Re: running FOP .95 version report with 0.20 version of jar

2011-08-01 Thread Rob Sargent
If you can deduce at run-time which users/reports need 0.20 v. 0.95 then
you can invoke the correct library as necessary with classpath
manipulation, but I doubt you'll have much luck running in mixed mode.


On 08/01/2011 04:34 AM, vjintegrates wrote:
 Hi, We have a large set of reports written with 0.20 version of FOP. We are
 planning to upgrade then to .095 version. However at customer installation
 there are custom reports files which we do not have access to so we did not
 want to upgrade to jar file to .95 version. Will .95 version of reports fail
 in .20 version of JAR ?

-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Re: FOP-ComplexScript (connectivity, direction and fonts of Arabic)

2011-08-01 Thread Glenn Adams
Thanks for the further update. In general, you should not be using font
metric files with FOP 1.0 or later.

Regarding Arial, Times New Roman, and Courier New fonts, I have not
explicitly tested these for Arabic support, but I will look into it. Keep in
mind that the Complex Script support requires OpenType fonts to support
GDEF, GSUB, and GPOS to perform contextual substitution and mark (e.g.,
vowel sign) placement. So if the fonts you used do not have these tables,
then FOP CS will not produce the desired results.

The fonts for which I have tested FOP CS are listed at
http://skynav.trac.cvsdude.com/fop/wiki/SupportedFonts.

Regarding the problem you report with Scheherazade and Lateef, I'm aware of
this, and a ticket is already filed for it at
http://skynav.trac.cvsdude.com/fop/ticket/38.

Regards,
Glenn

2011/7/31 Maher Qais m.q...@gmx.de

  Hallo Adams,

 Thanks for the feedback. I have inbetween repeat the test and found
 that the most troubles were occured because of using the font metrics
 files and referencing the same fonts in a specified directory at the
 same time.

 Now i can use the supported fonts, the Base-14 Fonts and the  Arabeyes
 Fonts without need to use “Free Ressam”.
 [FOP-ComplexScript_Test-20110731.fo]
 [FOP-ComplexScript_Test-20110731.pdf]

 Only the Base-14 Fonts seem not to support the vowel signs.
 [FOP-ComplexScript_Test-20110731_vowel-sings.fo]
 [FOP-ComplexScript_Test-20110731_vowel-sings.pdf]

 Another problem I've found (only applies to Scheherazade and Lateef):
 When I open the created PDF file using Adobe Acrobat Reader, copy the
 text to the clipboard and then insert it, for example, into a Word
 document, I do not get the original text.
 [FOP-ComplexScript_Test-20110731_reimport-text.fo]
 [FOP-ComplexScript_Test-20110731_reimport-text.pdf]
 [FOP-ComplexScript_Test-20110731_reimport-text-result.pdf]

 I use the fop-ComplexScripts-20110615. My OS is a Microsoft Windows
 XP Home Edition, 5.1.2600 Service Pack 3, Build 2600 (DE).

 Regards,
 Maher Qais



  Original-Nachricht   Betreff: Re: FOP-ComplexScript
 (connectivity, direction and fonts of Arabic)  Datum: Fri, 29 Jul 2011
 04:11:26 GMT  Von: Glenn Adams gl...@skynav.com gl...@skynav.com


  Hello Qais,

 Thanks for taking some time to test out the complex script features being
 developed for FOP.

 To help address these issues, could you:

 (1) provide input FO test files showing the specific problems you have
 found? it is best if each test file contains the minimum needed to
 demonstrate the problem;

 (2) indicate which complex script build you are using? fyi, the latest work
 is available at http://github.com/skynavga/fop;

 Regarding connectivity, shape selection, kerning, point placement, etc.,
 keep in mind that FOP doesn't do anything special other than implement the
 substitutions and positioning operations defined in the OpenType GSUB/GPOS
 tables. I'm not certain if the Arabeyes or other fonts you have tried
 support these tables. If they do, then there may be a bug in the new TTF/OTF
 parsing of this table data.

 In any case, if you provide some additional input as requested above, I'm
 sure we can resolve this matter soon. Also, if you haven't already seen it,
 please take a look at the documentation and active tickets found 
 athttp://skynav.trac.cvsdude.com/fop.

 Regards,
 Glenn Adams


 On Wed, Jul 27, 2011 at 1:57 PM, Qais m.q...@gmx.de m.q...@gmx.de wrote:

  Hi,
 
  Since a week I am working closely with FOP, Cocoon and Co, especially with
  the Complex Script (connectivity, direction and fonts of Arabic). Below is
  the result.
 
  Testing the Complex Script of FOP (27.07.2011)
 
  1) Supported Fonts by the Complex Script:
 
  1.1) Automatically registered:
  Arial Unicode MS, Lateef and Scheherazade in a fo:block: connectivity: ok,
  direction: ok.
  Arial Unicode MS, Lateef and Scheherazade in a fo:block-container, fo:table
  or fo:list-block: connectivity: none, direction: ok.
 
  1.2) Using font metrics:
  Arial Unicode MS and Traditional Arabic in a fo:block, fo:block-container,
  fo:table or fo:list-block: connectivity: none, direction: ok.
  Simplified Arabic in a fo:block, fo:block-container, fo:table or
  fo:list-block: connectivity: none, direction: ok, glyphs: partially.
  Lateef and Scheherazade in a fo:block, fo:block-container, fo:table or
  fo:list-block: glyphs: none.
 
  2) Base-14 Fonts:
 
  2.1) Automatically registered:
  Arial, Times New Roman, Courier New and Tahoma in a fo:block: connectivity:
  ok, direction: ok.
  Arial, Times New Roman, Courier New and Tahoma in a fo:block-container,
  fo:table or fo:list-block: connectivity: none, direction: ok.
 
  3) Arabeyes Fonts:
  www.arabeyes.org
 
  3.1) Automatically registered:
  KacstArt, KacstBook, KacstDecorative, KacstDigital, KacstFarsi,
  KacstLetter, KacstNaskh, KacstOffice, KacstOne, KacstPoster,
  KacstScreen, KacstTitle, KacstTitleL and Thabit in a fo:block,
  fo:block-container, fo:table or