Re: apache and eclipse
On Tue, Jan 02, 2007 at 10:15:38AM +0100, Jef Vrijhoeven (RY/ETM) wrote: > Hi, > > I wonder if there exist any eclipse plugins that implement apache > projects, like resolver, xerces etc? Can you maybe give me a hint how or > where I can find these? There is one for FOP: http://www.ahmadsoft.org/fopbridge.html Simon -- Simon Pepping home page: http://www.leverkruid.eu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: help needed for generating PDF using FOP.
Hi,
Thanks for your kind response. Yes, previously, I used Courier new font in
the xml file but as courier new font can not be used for multilingual PDF
generation support (japanese, chinese) , therefore I am using Arial
Unicode font. I tried with Arial Unicode font in the xml as well as in the
xsl file. The problem now is that I am not getting the proper layout in the
generated PDF document. Please let me know what changes I might have to do
in the xsl file so that I get the proper layout in PDF.
Thanks
Chandan Ray
4th floor, Lok Bharti Complex, AFL Bldg,
Marol Maroshi, Andheri(E) , Mumbai-59
Office Direct # 6-649-4760
"Pascal Sancho"
<[EMAIL PROTECTED] To:
akoma.fr>cc: <[EMAIL PROTECTED]>
Subject: RE: help needed for
generating PDF using FOP.
28/12/2006 06:44
PM
Re-Hi,
After reading your xml file, I see a regular html file, not a generic xml
file.
In this file, you use a fixed width font (Courier).
In you XSL-FO, you want to use the 'Arial Unicode', witch is a proportional
width font, that is why you get a different layout.
If you want a similar result, you should use a fixed width font ('Courier'
or the generic family 'monospace').
If you want unicode + monospace fonts, you should visit: [1], [2], [3], or
[4]
[1] http://www.wazu.jp/index.html
[2] http://savannah.nongnu.org/projects/freefont/
[3] http://www.math.utah.edu/~beebe/fonts/postscript-type-1-fonts.html
[4] http://www.alanwood.net/unicode/fonts.html
HTH,
Sorry for the noise with my previous message
Pascal
> -Message d'origine-
> De : Murali Paladugu [mailto:[EMAIL PROTECTED]
> Envoyé : jeudi 28 décembre 2006 10:05
> À : fop-users@xmlgraphics.apache.org
> Cc : [EMAIL PROTECTED]
> Objet : help needed for generating PDF using FOP.
>
> Hi,
> I am using fop-0.91 beta version for generating of reports
> in PDF format where i should also support multiple
> languages(Chinese , Japanese etc). The font I am using is
> Arial Unicode truetype font. I have to create the PDF in
> Simple A4 size from an XML file and I have specified the page
> layout attributes and font in the xsl file as under -
(...)
> The problem is if I try to create PDF documents which
> contains multiple pages then I am not getting the proper page
> layouts.I am sending the xml, xsl and the generated PDF files
> in the attachment.
>
>
> Please reply me on this mail id : [EMAIL PROTECTED]
>
> Thanks in advance
> Chandan
This e-Mail may contain proprietary and confidential information and is sent
for the intended recipient(s) only. If by an addressing or transmission error
this mail has been misdirected to you, you are requested to delete this mail
immediately. You are also hereby notified that any use, any form of
reproduction, dissemination, copying, disclosure, modification, distribution
and/or publication of this e-mail message, contents or its attachment other
than by its intended recipient/s is strictly prohibited.
Visit us at http://www.polaris.co.in
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: fo:table-row is missing child elements
The other FO compilers don't validate by default. Unfortunately, strict validation, because it contains the word "strict", has connotations of meanness that companies want to avoid. But again, there are scenarios where strict validation is actually the "nicer" route for a user[1]--it can save a lot of inadvertent errors from going out. Glen [1] http://marc.theaimsgroup.com/?l=fop-dev&m=111365780207108&w=2 [EMAIL PROTECTED] wrote: Yes, it is the Docbook-XSL-Stylesheet 1.71.1 which causes this error. But strange to say using -r-mode a xml-file is created by FOP with the Docbook-XSL very well another one using the same Docbook-XSL and -r-mode causes the "fo:table-row is missing child elements"-error. It's all very confusing me. Regards, Leeloo */Glen Mazza <[EMAIL PROTECTED]>/* schrieb: Hmmm...judging from your email address, I hope it is not a docbook stylesheet that is requiring you to run in "-r" mode. I would send a bug report to the OASIS docbook team if it is. Glen [EMAIL PROTECTED] wrote: > Hi Glen, > > running FOP 0.92beta with the option > > -r relaxed/less strict validation (where available) > > now generates a PDF without the error described below :-))) > > Thanks and happy new year. > > Best Regards, > Leeloo > > */Glen Mazza /* schrieb: > > [EMAIL PROTECTED] escribió: > > > Trying to convert an FO-File which was generated by FOP 0.92beta > to an > > PDF just stopped with following Error Message: > > javax.xml.transform.TransformerException: > > org.apache.fop.fo.ValidationException: file:///test/test.fo:1:43655: > > Error(1/43655): fo:table-row is missing child elements. > > Required Content Model: (table-cell+) > > > > Process of elimination is probably best here: keep minimizing your FO > file until you identify the element causing the error to occur. > > There is also an option I believe in FOP 0.93 to run in non-strict > validation mode, which would I believe would accept the situation that > is occurring for you. > > > I can't find any fo:table-row in FO-File which missed a > fo:table-cell. I > > think everything is alright. Using FOP 0.20.5 converting the XML > to PDF > > -> it works fine. > > > > The new FOP raises an error by default, as protection in case you > goofed > up your XSLT template calls and ended up creating no cells where you > actually wanted some. This way erroneously created invoices with no > rows, for example, won't end up going out to the customer, or if you > create a 250 page document you don't have to manually read each page > just to make sure every table has the rows you intended. > > Glen > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > __ > Do You Yahoo!? > Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz > gegen Massenmails. > http://mail.yahoo.com > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fo:table-row is missing child elements
Yes, it is the Docbook-XSL-Stylesheet 1.71.1 which causes this error. But strange to say using -r-mode a xml-file is created by FOP with the Docbook-XSL very well another one using the same Docbook-XSL and -r-mode causes the "fo:table-row is missing child elements"-error. It's all very confusing me. Regards, Leeloo Glen Mazza <[EMAIL PROTECTED]> schrieb: Hmmm...judging from your email address, I hope it is not a docbook stylesheet that is requiring you to run in "-r" mode. I would send a bug report to the OASIS docbook team if it is. Glen [EMAIL PROTECTED] wrote: > Hi Glen, > > running FOP 0.92beta with the option > > -r relaxed/less strict validation (where available) > > now generates a PDF without the error described below :-))) > > Thanks and happy new year. > > Best Regards, > Leeloo > > */Glen Mazza /* schrieb: > > [EMAIL PROTECTED] escribió: > > > Trying to convert an FO-File which was generated by FOP 0.92beta > to an > > PDF just stopped with following Error Message: > > javax.xml.transform.TransformerException: > > org.apache.fop.fo.ValidationException: file:///test/test.fo:1:43655: > > Error(1/43655): fo:table-row is missing child elements. > > Required Content Model: (table-cell+) > > > > Process of elimination is probably best here: keep minimizing your FO > file until you identify the element causing the error to occur. > > There is also an option I believe in FOP 0.93 to run in non-strict > validation mode, which would I believe would accept the situation that > is occurring for you. > > > I can't find any fo:table-row in FO-File which missed a > fo:table-cell. I > > think everything is alright. Using FOP 0.20.5 converting the XML > to PDF > > -> it works fine. > > > > The new FOP raises an error by default, as protection in case you > goofed > up your XSLT template calls and ended up creating no cells where you > actually wanted some. This way erroneously created invoices with no > rows, for example, won't end up going out to the customer, or if you > create a 250 page document you don't have to manually read each page > just to make sure every table has the rows you intended. > > Glen > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > __ > Do You Yahoo!? > Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz > gegen Massenmails. > http://mail.yahoo.com > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com
Re: fo:table-row is missing child elements
Hmmm...judging from your email address, I hope it is not a docbook stylesheet that is requiring you to run in "-r" mode. I would send a bug report to the OASIS docbook team if it is. Glen [EMAIL PROTECTED] wrote: Hi Glen, running FOP 0.92beta with the option -r relaxed/less strict validation (where available) now generates a PDF without the error described below :-))) Thanks and happy new year. Best Regards, Leeloo */Glen Mazza <[EMAIL PROTECTED]>/* schrieb: [EMAIL PROTECTED] escribió: > Trying to convert an FO-File which was generated by FOP 0.92beta to an > PDF just stopped with following Error Message: > javax.xml.transform.TransformerException: > org.apache.fop.fo.ValidationException: file:///test/test.fo:1:43655: > Error(1/43655): fo:table-row is missing child elements. > Required Content Model: (table-cell+) > Process of elimination is probably best here: keep minimizing your FO file until you identify the element causing the error to occur. There is also an option I believe in FOP 0.93 to run in non-strict validation mode, which would I believe would accept the situation that is occurring for you. > I can't find any fo:table-row in FO-File which missed a fo:table-cell. I > think everything is alright. Using FOP 0.20.5 converting the XML to PDF > -> it works fine. > The new FOP raises an error by default, as protection in case you goofed up your XSLT template calls and ended up creating no cells where you actually wanted some. This way erroneously created invoices with no rows, for example, won't end up going out to the customer, or if you create a 250 page document you don't have to manually read each page just to make sure every table has the rows you intended. Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fo:table-row is missing child elements
Hi Glen, running FOP 0.92beta with the option -r relaxed/less strict validation (where available) now generates a PDF without the error described below :-))) Thanks and happy new year. Best Regards, Leeloo Glen Mazza <[EMAIL PROTECTED]> schrieb: [EMAIL PROTECTED] escribió: > Trying to convert an FO-File which was generated by FOP 0.92beta to an > PDF just stopped with following Error Message: > javax.xml.transform.TransformerException: > org.apache.fop.fo.ValidationException: file:///test/test.fo:1:43655: > Error(1/43655): fo:table-row is missing child elements. > Required Content Model: (table-cell+) > Process of elimination is probably best here: keep minimizing your FO file until you identify the element causing the error to occur. There is also an option I believe in FOP 0.93 to run in non-strict validation mode, which would I believe would accept the situation that is occurring for you. > I can't find any fo:table-row in FO-File which missed a fo:table-cell. I > think everything is alright. Using FOP 0.20.5 converting the XML to PDF > -> it works fine. > The new FOP raises an error by default, as protection in case you goofed up your XSLT template calls and ended up creating no cells where you actually wanted some. This way erroneously created invoices with no rows, for example, won't end up going out to the customer, or if you create a 250 page document you don't have to manually read each page just to make sure every table has the rows you intended. Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com
Re: PNG transparency renders as black - urgent
...just to keep the track - I applied your patch as you posted it, worked nice for all my PNGs (but I didn't explicitly tested various png types); Thanks for the help! Martin Jeremias Maerki wrote: Actually, this is so simple, I've created a patch. I'm hesitant to apply it without much testing with various PNGs for which I have no time right now. But maybe one of you can take a look. If it's good JAIImage and JimiImage could be similarly patched. On 19.12.2006 23:01:36 Jeremias Maerki wrote: It turns out the following revision is responsible for the regression: http://svn.apache.org/viewvc?rev=424349&view=rev Putting the Commons codec before the ImageIO variant in ImageFactory is a quick fix for this. I originally switched because of speed reasons but obviously I didn't test PNGs with alpha channel. The reason why Martin's PNG doesn't work with the ImageIOImage class is the lack of support for java.awt.Transparency.TRANSLUCENT. If it were a BITMASK it would work. The same problem exists for JAIImage and JimiImage, BTW. Again, this is something a complete redesign of the image package would have addressed. It's on my higher priority list but I still haven't got to it, yet. If someone wants to try to implement that little code that is missing as a temporary fix, please do. It shouldn't be difficult. You can maybe use XmlGraphicsCommonsImage for hints. On 19.12.2006 20:30:35 Andreas L Delmelle wrote: On Dec 19, 2006, at 19:56, Peter wrote: When working on the patch I certainly can not remember coming anywhere close to code that could have an influence on how png's get into the pdf. I was also a bit puzzled, since in the patch there are no explicit references to anything png-related (IIC, png-related stuff is already put in Commons for that matter, so it couldn't have been touched directly by the patch) OTOH, this was the only significant change to the codebase between 13.11 and now, so one can reasonably assume that the cause is in there somewhere... I'd expect something which has an impact on the interaction with the commons-lib? Cheers, Andreas Jeremias Maerki Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: help needed for generating PDF using FOP.
Hi,
If you just want to convert html to PDF, this is a FAQ entry in FOP site (see
[1]).
If you want to have a specific layout for PDF output, you'll probably need to
write a XSLT to convert your xml (or xhtml) source in XSL-FO.
[1] http://xmlgraphics.apache.org/fop/faq.html#xhtml-to-pdf2
Happy new year!
Pascal
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Envoyé : vendredi 29 décembre 2006 06:25
>
> Hi,
> Thanks for your kind response. Yes, previously, I used
> Courier new font in the xml file but as courier new font can
> not be used for multilingual PDF generation support
> (japanese, chinese) , therefore I am using Arial Unicode
> font. I tried with Arial Unicode font in the xml as well as
> in the xsl file. The problem now is that I am not getting the
> proper layout in the generated PDF document. Please let me
> know what changes I might have to do in the xsl file so that
> I get the proper layout in PDF.
>
> Thanks
> "Pascal Sancho"
> 28/12/2006 06:44 PM
>
>
> Re-Hi,
> After reading your xml file, I see a regular html file, not a
> generic xml file.
> In this file, you use a fixed width font (Courier).
> In you XSL-FO, you want to use the 'Arial Unicode', witch is
> a proportional width font, that is why you get a different layout.
>
> If you want a similar result, you should use a fixed width
> font ('Courier'
> or the generic family 'monospace').
> If you want unicode + monospace fonts, you should visit: [1],
> [2], [3], or [4] [1] http://www.wazu.jp/index.html [2]
> http://savannah.nongnu.org/projects/freefont/
> [3] http://www.math.utah.edu/~beebe/fonts/postscript-type-1-fonts.html
> [4] http://www.alanwood.net/unicode/fonts.html
>
> HTH,
>
> Sorry for the noise with my previous message Pascal
>
>
> > -Message d'origine-
> > De : Murali Paladugu [mailto:[EMAIL PROTECTED]
> > Envoyé : jeudi 28 décembre 2006 10:05
> >
> > Hi,
> > I am using fop-0.91 beta version for generating of reports in PDF
> > format where i should also support multiple languages(Chinese ,
> > Japanese etc). The font I am using is Arial Unicode
> truetype font. I
> > have to create the PDF in Simple A4 size from an XML file
> and I have
> > specified the page layout attributes and font in the xsl
> file as under
> > -
>
> (...)
>
> > The problem is if I try to create PDF documents which contains
> > multiple pages then I am not getting the proper page layouts.I am
> > sending the xml, xsl and the generated PDF files in the attachment.
> >
> >
> > Please reply me on this mail id : [EMAIL PROTECTED]
> >
> > Thanks in advance
> > Chandan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
