which graphic file formats are supported ?
hi ! anybody know where to get a list of which graphic file formats are supported in fop ( in fo:external graphic tag ) ? beside, i can't load the xml.apache.org site or www.apache.org at the moment seems to be the server is down ? greetings Nick Winger (Software-Developer) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Triggering XALAN/XERXES from a start routine
Is it possible to program a start routine, let's say: in some programming language (preferably Visual Basic) to trigger an XSL transformation from the outside? Have XALAN/XERXES the necessary interface(s)? I would need to hand over the source and target paths of the XML instances and the path of the XSLT. Has anyone done this already? Matthias Fischer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Triggering XALAN/XERXES from a start routine
wrong group??? -Original Message- From: Matthias Fischer [mailto:[EMAIL PROTECTED]] Sent: Friday, February 01, 2002 10:41 AM To: Liste, FOP Cc: Zelkanovic, Adnan; Thaler, Gregor Subject: Triggering XALAN/XERXES from a start routine Is it possible to program a start routine, let's say: in some programming language (preferably Visual Basic) to trigger an XSL transformation from the outside? Have XALAN/XERXES the necessary interface(s)? I would need to hand over the source and target paths of the XML instances and the path of the XSLT. Has anyone done this already? Matthias Fischer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] sitewaerts GmbH Hebelstraße 15 D-76133 Karlsruhe Tel: +49 (721) 920 918 0 Fax: +49 (721) 920 918 29 http://www.sitewaerts.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: transforming fo to pdf
After looking closer at your mail, when Jörg replied, I realized what's wrong. Bhawana, you're using the CVS version (main branch) of FOP which is currently in a redesign phase. That version is not intended to be used, yet. FOP 0.20.x does not have any LayoutManagers. I suggest you download a release or get FOP using CVS tag fop-0_20_2-maintain. I wish to transform FO document (docFo) into PDF. I am using fop.20 I have the following code : -- java.lang.NullPointerException at org.apache.fop.layoutmgr.PageLayoutManager.makeNewPage(PageLayoutManager.java:141) at org.apache.fop.layoutmgr.PageLayoutManager.getParentArea(PageLayoutManager.java:176) at org.apache.fop.layoutmgr.FlowLayoutManager.getParentArea(FlowLayoutManager.java:49) at org.apache.fop.layoutmgr.BlockLayoutManager.getParentArea(BlockLayoutManager.java:81) at org.apache.fop.layoutmgr.LineLayoutManager.createLine(LineLayoutManager.java:95) at org.apache.fop.layoutmgr.LineLayoutManager.addChild(LineLayoutManager.java:118) at org.apache.fop.layoutmgr.TextLayoutManager.parseChars(TextLayoutManager.java:164) at org.apache.fop.layoutmgr.TextLayoutManager.generateAreas(TextLayoutManager.java:55) Can someone suggest where I am going wrong. Cheers, Jeremias Märki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern Fon +41 (41) 317 2020 - Fax +41 (41) 317 2029 Internet http://www.outline.ch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: white-space
Title: RE: white-space u can put #160; ( # 1 6 0 ;) this will work. rgds, Rabi. -Original Message- From: Joerg Pietschmann [SMTP:[EMAIL PROTECTED]] Sent: Friday, February 01, 2002 5:37 PM To: FOP Dev Subject: Re: white-space I need white space between fields, how do I do that? ... xsl:value-of select=city /, !--I NEED A WHITE SPACE HERE-- xsl:value-of select=state / !--I NEED WHITE SPACE The canonical solution is to use xsl:text xsl:value-of select=city / xsl:text, /xsl:text xsl:value-of select=state / xsl:text /xsl:text xsl:value-of select=zipcode / This is actually a XSLT questio, not directly related to FOP. Read the XSLT spec http://www.w3.org/TR/xslt or any of the good books for more about whitespace handling during an XSL transformation. XSLFO has some specialities as well. HTH J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: making classes off your fonts...
thanks... it worked but not the way i thought (lol) i think each space is used as a linebreak (nicxe view though :-]) and some characters aren't correct (like a ° in stead off an ë). do you know where i can find a tutorial for that (making metrix-files...)... and implementing correctly (must be doing something wrong ... thanks guys Jochen Maes EDP departement Programmeur KBC-Securities Havenlaan 16 1080 Brussel Tel : 02/429.96.81 Fax : 02/429.17.48 E-mail : [EMAIL PROTECTED] ** This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. KBC Securities reserves the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. ** Jeremias Maerki jeremias.maerki@oTo: [EMAIL PROTECTED] utline.chcc: Subject: Re: making classes off your fonts... 01-02-02 08:42 AM Please respond to fop-dev got a question. when i use FOP i use it with different fonts then allready specified... and loading those fonts into the java takes some time now i want to make that FOP more performant... Is there a way to make classes (like some allready exist) off them fonts so that the rendering takes less time if there isn't a way supplied, can i adapt them classes (or java's) to whatever font i want? That was actually the way it was done about a year ago. Personally, I don't think it will help performance a lot. There are more performance-critical parts in FOP. Or did you do any measurements that lead you to this conclusion. Anyway, if you really want to create classes for your fonts, have a look at build.xml and the codegen folder which contains XSLTs that convert XML font metric files to Java classes. Then you need to add these classes in org.apache.fop.render.pdf.FontSetup.java. Cheers, Jeremias Märki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern Fon +41 (41) 317 2020 - Fax +41 (41) 317 2029 Internet http://www.outline.ch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: making classes off your fonts...
Everything on fonts is on the following page: http://xml.apache.org/fop/fonts.html Sometimes the metric files need some tweaking, especially for Type 1 fonts, but that requires reading into the font specs. I'm still quite sure you're making yourself a hard time with little profit. Good luck. it worked but not the way i thought (lol) i think each space is used as a linebreak (nicxe view though :-]) and some characters aren't correct (like a ° in stead off an ë). do you know where i can find a tutorial for that (making metrix-files...)... and implementing correctly (must be doing something wrong ... Cheers, Jeremias Märki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern Fon +41 (41) 317 2020 - Fax +41 (41) 317 2029 Internet http://www.outline.ch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 6178] New: - Color palette of .bmp files with 1 bit/pixel not used
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=6178.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6178
Color palette of .bmp files with 1 bit/pixel not used
Summary: Color palette of .bmp files with 1 bit/pixel not used
Product: Fop
Version: all
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: images
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
The color palette of .bmp files with 1 bit/pixel is not used when loading image.
Example of a bmp header I've received from Alchemy on Unix:
424DAE8E0100 3E002800
0010 1603FC03 01000100
0020 708E0100C21E C21E
0030 FF00
0040
The palette is inverted (why, I don't know). So a 0 bit means a white pixel and
a 1 bit means a black pixel.
In class org.apache.fop.image.BmpImage, method loadImage ignores the palette in
that case (it's not even constructed). For FOP, a 0 bit means always black
pixel and a 1 bit means always white pixel.
So my image appears in Acrobat Reader as inverted video.
I have fixed the bug with the following statements :
if (headermap[28] == 4 || headermap[28] == 8 || headermap[28] == 1) {
to always build the palette and
for (int countr = 0; countr 8 x this.m_width;
countr++) {
if ((p 0x80) != 0) {
this.m_bitmaps[3 * (i * this.m_width + x)] =
// (byte)0xFF;
palette[3];
this.m_bitmaps[3 * (i * this.m_width + x) + 1] =
// (byte)0xFF;
palette[4];
this.m_bitmaps[3 * (i * this.m_width + x) + 2] =
// (byte)0xFF;
palette[5];
} else {
this.m_bitmaps[3 * (i * this.m_width + x)] =
// (byte)0;
palette[0];
this.m_bitmaps[3 * (i * this.m_width + x) + 1] =
// (byte)0;
palette[1];
this.m_bitmaps[3 * (i * this.m_width + x) + 2] =
// (byte)0;
palette[2];
}
to use it.
I think it could help.
Frédéric.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
RE: Why do you use FOP instead of ...
Our application is a servlet based web application. We have adopted the MVC approach. We found Cacoon over kill, so we implmented our own frame work. Our frame work requires all business components produce XML. We then use XSL:HTML to format HTML output for the browser. It was only a natural next step to use XSL:FO to generate PDF since we already had XML being generated. One of the real blessings of this approach is our clients can customize the look and feel of the application by changing the XSL files without our ever opening a Java source file. It was a BIG investment and learning curve up front to take this approach, but now that we are past that phase, the return on the investment has enabled us to justify the up front expense. Looking back, I think it was a vary sound decission. We are in a position where adding WAP (WML) and a B2b SOAP interface are a natural extension of our framework, not a rewrite. Thank yous go to not only FOP, but Xalan and Xerces for all the XML and XSL support! Jim Urban Product Manager Netsteps Inc. Suite 505E 1 Pierce Pl. Itasca, IL 60143 Voice: (630) 250-3045 x2164 Fax: (630) 250-3046 At 08:58 PM 1/29/02 -0500, you wrote: I would like to know why FOP enthousiast (I am one) are using FO rather than products such as Crystal Reports or other such software (anyone Jetfoms ?). Just for the fun of playing with new technology ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Why do you use FOP instead of ...
At 10:32 AM 2/1/02 -0600, you wrote: step to use XSL:FO to generate PDF since we already had XML being generated. One of the real blessings of this approach is our clients can customize the look and feel of the application by changing the XSL files without our ever opening a Java source file. We also have a web based service here, and currently are using the same approach as you are, but the problems we encouter are the following: If you generate XSL:FO from XML, the XSLT(stylesheet) can become very complicated, at least for us because: We generate a lot of tables, and they are quite different what concerns the formatting/color. That means, there has to be a section in the XSLT for each type of table and complicated if-then-else decisions to decide which formatting to apply and how. Take into account also, that up to now you have to manually code in the column width of each column in every table for FOP, this is a nightmare! In other words, changing the XSLT is much, much, much more painfull than changing a java source file(supposing the use of iText). An alternative for having a simpler XSLT, would be to encode most of the formatting in the XML, but then you would have XML with formatting information, and if you want to change the look and feel you have to change the java source that is generating the XML. I think the use of XSLT is only usefull if you have a standardized look and feel, like every table looks the same way, etc... But even then, if you decide that you need a new table it is very difficult to define a new formatting using XSLT to generate XSL:FO. XSL:FO is a complicated language, and the complexity transfers to the generating XSLT(which is cumbersome enough on its own), which looks like a big messy thing here at the company. Our XSLT files are currently VERY long and MESSY. It would be much simpler to code the same thing in Java, take a look at the iText page and their examples(http://www.lowagie.com/iText/). And if you still need your XML, you can take this approach: 1. Generate XML from Java for whatever you need. 2. Generate the PDF from Java using iText. I think this is probably the approach we are gonna take here... And if you code smartly you can arrange is to also not have to change the java source for a change of look and feel. Just store the formatting information in a '.properties' file like: tableBackGroundColor=red tableFont=Roman8 etc... Then you can change the look and fell by just editing that properties file... I will nail down the weaknesses of the XML-PDF approach: 1. XSL:FO is a very complicated and messy language 2. XSLT is also kinda complicated to use, at least if you have to do complicated formatting... Best regards...Roland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Why do you use FOP instead of ...
I will nail down the weaknesses of the XML-PDF approach: 1. XSL:FO is a very complicated and messy language 2. XSLT is also kinda complicated to use, at least if you have to do complicated formatting... I'm replying to my own email adding that of course I would be glad if someone can show me how to make a simpler XSLT. Maybe we just didn't figure out how to make the XSLT simple. But please take a look at the iText http://www.lowagie.com/iText/ examples first. That is what I call simplicity!!! Also keep in mind that we generate many different tables, with different formatting each on a single pdf document. Best regards, Roland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Why do you use FOP instead of ...
At 04:06 PM 2/1/02 -0200, you wrote: I will nail down the weaknesses of the XML-PDF approach: 1. XSL:FO is a very complicated and messy language 2. XSLT is also kinda complicated to use, at least if you have to do complicated formatting... Sometimes it seems folks assume that FO is synomous with pdf, but for some of us, the point of using FO is not to create pdf output but to format and send xml data directly to a printer. ;-) ' Best, -Ralph LaChance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Why do you use FOP instead of ...
Hi Roland, We had the very same prob cause the xsl that translate from our XML content to FO went quite messy as we made all modifications needed to paper export (we're usually building 50-200 pages in our pdfs, with many pictures, tables cause it's made of courses contents). So we made some kind of pre-formatting in a xmlsublanguage of our own then we actually turn everything to fo). That's not a big prob in our context since pdf building is almost an offline task, made by teachers. Cheers, Fred. ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.fr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Why do you use FOP instead of ...
Ralph LaChance wrote: At 04:06 PM 2/1/02 -0200, you wrote: I will nail down the weaknesses of the XML-PDF approach: 1. XSL:FO is a very complicated and messy language 2. XSLT is also kinda complicated to use, at least if you have to do complicated formatting... Sometimes it seems folks assume that FO is synomous with pdf, but for some of us, the point of using FO is not to create pdf output but to format and send xml data directly to a printer. ;-) Well, what does it take to develop an XSL-FO interpreter on a printer ? No need to transform to PDF or PS then. I thought of doing it for some time, but got discouraged when an old Xerox guy told me that Adobe actually supplies (for free ?) their PS interpreter and that developing an interpeter and fine-tuning it takes a LOT of time. Patrick Andries - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Why do you use FOP instead of ...
Forgot to say that our fo formatting would be ready in 10 years when we'll have those *good* voice synthetizer that are supposed to *print* our fo code according to the XSL-FO specs. ;) Fred. --- Ralph LaChance [EMAIL PROTECTED] a écrit : At 04:06 PM 2/1/02 -0200, you wrote: I will nail down the weaknesses of the XML-PDF approach: 1. XSL:FO is a very complicated and messy language 2. XSLT is also kinda complicated to use, at least if you have to do complicated formatting... Sometimes it seems folks assume that FO is synomous with pdf, but for some of us, the point of using FO is not to create pdf output but to format and send xml data directly to a printer. ;-) ' Best, -Ralph LaChance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.fr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Why do you use FOP instead of ...
At 12:59 PM 2/1/02 -0600, you wrote: 2. XSLT is also kinda complicated to use, at least if you have to do complicated formatting... So is any other kind of programming language. The more complex the task, the more lines of coded need to achieve the desired results. Wrong! Look at iText http://www.lowagie.com/iText/ to see how simple their examples are. They build a complex table with just a few lines of java codes. Try doing the same with the XML/XSLT/XSL:FO approach and I guarantee you that the total outcome will be much more both in lines and complexity. I think to generate PDF with iText is as easy as generating XML from Java. XSLT is just a complicated language. But I will take a closer look at our xsl files and see how and if things could be simplified... Roland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
fop dtd attached
A couple of people have written in recently asking for an FOP dtd. I'm guessing so they can use it with PSGML. So, I made one using the standard document as well as I could read it. I tried to include lists of valid values for things like integer so, if you want to use it as a real validating document, those lists are going to invalidate valid integers. (Replace the list with CDATA and you should be fine) Also, the DTD omits the FO: prefix for the elements. Feel free to fix the problems and repost the DTD. FOP DTD attached Chuck __ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com ?xml version=1.0 encoding=iso-8859-1? !-- This DTD has been developed in order to validate XSL FO documents It has not been well tested. For instance, the length attribute is able to be negative for some elements like margins. I have not represented that here. I have not added values for the Aural properties There are several instances where I've entered %integer; and it should be positive-integer or number The DTD trys to handle the text based rules re: markers, float, footer and initial-property-set But, allows you to do illegal things if you want because I couldn't figure out how to constrain against the illegal actions. Please e-mail your comments to [EMAIL PROTECTED] -- !-- *** -- !-- Entity definitions for groups of formatting objects -- !-- *** -- !-- The following definitions are supplied for the creation of drop down boxes of sample valid values If you intend to validate free-form, these should be CDATA -- !ENTITY % px_length 0px|1px|2px|3px|4px|5px|6px|7px|8px|9px|10px|11px|12px|13px|14px|15px|16px|17px|18px|19px|20px|21px|22px|23px|24px|25px|26px|27px|28px|29px !ENTITY % in_length 1in|2in|3in|4in|5in|6in|7in|8in|9in|10in !ENTITY % pt_length 1pt|2pt|3pt|4pt|5pt|6pt|7pt|8pt|9pt|10pt !ENTITY % mm_length 1mm|2mm|3mm|4mm|5mm|6mm|7mm|8mm|9mm|10mm !ENTITY % pc_length 1pc|2pc|3pc|4pc|5pc|6pc|7pc|8pc|9pc|10pc !ENTITY % length %px_length; | %in_length; | %pt_length; | %mm_length; | %pc_length; !ENTITY % absolute-size xx-small | x-small | small | medium | large | x-large | xx-large !ENTITY % relative-size larger | smaller !-- The percent sign blows up the dtd so I don't know how to represent that -- !ENTITY % percentage .01|.02|.03|.04|.05|.06|.07|.08|.09|.10|.20|.30|.40|.50|.60|.70|.80|.90|1 !ENTITY % color aqua|black|blue|fuscia|gray|green|lime|maroon|navy|olive|purple|red|silver|teal|white|yellow !ENTITY % margin-width auto | %length; | %percentage; !ENTITY % angle 0deg|90deg|180deg|270deg !ENTITY % keep auto | always | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 !ENTITY % breaks auto | column | page | even-page | odd-page !ENTITY % displace auto | none | line | indent | block !ENTITY % floatType before | start | end | left | right | none !ENTITY % clear start | end | left | right | both | none !ENTITY % integer 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 !-- The following language definitions are taken from http://www.oasis-open.org/cover/iso639a.html -- !-- I have supplied Language Family, Language Name and Language code in parallel arrays so you can build pick lists and tabbed boxes for their selection in a UI -- !ENTITY % language_name AYMARA | GUARANI | QUECHUA | BHUTANI | BURMESE | CAMBODIAN | CHINESE | JAPANESE | KOREAN | LAOTHIAN | THAI | TIBETAN | VIETNAMESE | LATVIAN;LETTISH | LITHUANIAN | BASQUE | BRETON | IRISH | SCOTS-GAELIC | WELSH | KANNADA | MALAYALAM | TAMIL | TELUGU | GREENLANDIC | INUPIAK | ESTONIAN | FINNISH | HUNGARIAN | AFRIKAANS | DANISH | DUTCH | ENGLISH | FAROESE | FRISIAN | GERMAN | ICELANDIC | NORWEGIAN | SWEDISH | YIDDISH | AFAN-(OROMO) | AFAR | SOMALI | ABKHAZIAN | GEORGIAN | ASSAMESE | BENGALI;BANGLA | BIHARI | GUJARATI | HINDI | KASHMIRI | MARATHI | NEPALI | ORIYA | PUNJABI | SANSKRIT | SINDHI | SINGHALESE | URDU | ALBANIAN | ARMENIAN | ESPERANTO | INTERLINGUA | INTERLINGUE | VOLAPUK | KURDISH | PASHTO;PUSHTO | PERSIAN-(farsi) | TAJIK | GREEK | LATIN | HAUSA | KINYARWANDA | KURUNDI | LINGALA | SANGHO | SESOTHO | SETSWANA | SHONA | SISWATI | SWAHILI | TSONGA | TWI | WOLOF | XHOSA | YORUBA | ZULU | FIJI | INDONESIAN | JAVANESE | MALAGASY | MALAY | MAORI | SAMOAN | SUNDANESE | TAGALOG | TONGA | CATALAN | CORSICAN |
