RE: feature overview
Clay Leeds wrote: > Here's a link which has a list of graphics formats: > > http://www.dcs.ed.ac.uk/home/mxr/gfx/ Thanks, I had just gotten them from my handy O'Reilly "Encyclopedia of Graphics File Formats" book. The good news is that all agree! > BTW, perhaps these messages should be going to/from fop-dev? Dunno... I agree. I think this started with a user question about graphics, and kind of got out of hand from there :-). Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: feature overview
Clay Leeds wrote: > - To help with searching the FOP site, put the "title" of the image > format in parentheses for all image formats (if known) like you've done > with ICO, PICT & PSD--i.e., GIF (Graphics Interchange Format); PNG > (Portable Network Graphics); etc. OK. Done in CVS. > - at the bottom of the JPG and/or Graphics Resolution section(s), add a > hint (FAQ?) about increasing the resolution of the JPG image to improve > rendering. My JPG images looked pixelated until I changed it from 72dpi > to 300dpi in Photoshop. OK, I have added (in CVS) a paragraph at the bottom of the Graphics Resolution section that addresses this in general terms. > - I don't know if you can automate this, but it would be nice to have > the Batik version indicated. OK, added (in CVS) in the Batik section (as opposed to the SVG section). > - You might also indicate "FOP uses the SVG library from the href="http://www.apache.org/";>Apache Foundation's href="http://xml.apache.org/batik/";>Batik OK, I reworked this a bit (in CVS), adding the Apache name in the Batik section, and adding a link to Batik from the SVG section. > - it also might be nice to include why someone might want to use SVG > instead of JPG, PNG or one of the other graphics formats (resolution > independent, standard, vector-based, small size? dunno...) I'm not going to do that one. The page needs to be informative, not persuasive. I don't care what format they use, and there are much better forums (fora?) for getting that information. Thanks for all of the good input. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: feature overview
Clay Leeds wrote: > - To help with searching the FOP site, put the "title" of the image > format in parentheses for all image formats (if known) like you've done > with ICO, PICT & PSD--i.e., GIF (Graphics Interchange Format); PNG > (Portable Network Graphics); etc. Here's a link which has a list of graphics formats: http://www.dcs.ed.ac.uk/home/mxr/gfx/ BMP (MS-Windows bitmap format) PCX (PC Paintbrush format) PNM (portable anymap file format) TGA (Targa File format) TIFF (Tag Image File Format) XBM (X-Bitmap Format) XPM (X-Pixmap Format) (for more info on any of these, see the above link) BTW, perhaps these messages should be going to/from fop-dev? Dunno... -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: feature overview
Victor, Victor Mote wrote: > Sorry to be so slow responding. First, it took me a while to write the > content, then there is a time lag before it is published, then ... I forgot > I had flagged the message for followup. Anyway, please review the revised > graphics doc: > http://xml.apache.org/fop/graphics.html > and let me know if we missed anything. The only thing that I think is > missing is for all of the formats to be in the faq, which we have already > discussed. This looks great (!) I only have a couple of ideas/suggestions: - To help with searching the FOP site, put the "title" of the image format in parentheses for all image formats (if known) like you've done with ICO, PICT & PSD--i.e., GIF (Graphics Interchange Format); PNG (Portable Network Graphics); etc. - at the bottom of the JPG and/or Graphics Resolution section(s), add a hint (FAQ?) about increasing the resolution of the JPG image to improve rendering. My JPG images looked pixelated until I changed it from 72dpi to 300dpi in Photoshop. - I don't know if you can automate this, but it would be nice to have the Batik version indicated. - You might also indicate "FOP uses the SVG library from the http://www.apache.org/";>Apache Foundation's http://xml.apache.org/batik/";>Batik - it also might be nice to include why someone might want to use SVG instead of JPG, PNG or one of the other graphics formats (resolution independent, standard, vector-based, small size? dunno...) Did I mention this looks grreat!? -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: feature overview
Clay Leeds wrote (Friday, April 11, 2003 4:58 PM): > This is "sort of" a FAQ (although the FAQ only mentions PNG images). The > answer appears to be JIMI which is used by FOP for all image formats > except most forms of JPG & GIF files: > > http://java.sun.com/products/jimi/ > > (if FOP handles other image formats, I couldn't find them quickly). > According to Sun's JIMI download page: > > Jimi's range of supported formats includes GIF, > JPEG, TIFF, PNG, PICT, Photoshop, BMP, Targa, > ICO, CUR, Sunraster, XBM, XPM, and PCX, although > some of these formats do not have complete > support for all features. > > Since "Photoshop" is listed, I assume the "PSD" graphic you're referring > to is supported. Good luck! > > p.s. Note to Victor: Might we update FAQ 3.2 to: > > My PNG|JPEG|TIFF|GIF|PICT|PSD|BMP|ICO|CUR|SUNRASTER(?)|XBM|XPM|PCX > images don't work. > > or better yet (borrowing from one of Joerg's replies): > > Q: > My image(s) don't work. > > A: > If you're using a JPG, JPG images can contain all kind of weird > color lookup tables and color profiles, not all variants are > supported (not to mention the *illegal* subformats seen here > and there in the wild). Try a JPG produced by a different > graphic program. Specifying 24-bit color output may also help. > > Alternatively, if you're not using a JPG or GIF image, > Sun's Jimi image library, is by default used for > processing images in the following formats: GIF, JPEG > (JPG), TIFF, PNG, PICT, Photoshop (PSD), BMP, Targa, ICO, > CUR, Sunraster, XBM, XPM, and PCX, although some of these > formats do not have complete support for all features. > > The JIMI class library was removed from the FOP > distribution for licensing reasons. You'll have to > download (linked to http://java.sun.com/products/jimi) > and install it by yourself. > > Extract the file "JimiProClasses.zip" from the archive > you've downloaded, rename it to "jimi-1.0.jar" and move > it to FOP's lib directory. > > An alternative to Jimi is to use Sun's JAI. It is much > faster, but not available for all platforms. > > Double-check all my content, as it was copy/pasted (and some of it may > not be true!). This would help with Joerg & my handy dandy "ultimate > assistant" idea (Ctrl-F--ROTFL!) come to fruition... ;-p Sorry to be so slow responding. First, it took me a while to write the content, then there is a time lag before it is published, then ... I forgot I had flagged the message for followup. Anyway, please review the revised graphics doc: http://xml.apache.org/fop/graphics.html and let me know if we missed anything. The only thing that I think is missing is for all of the formats to be in the faq, which we have already discussed. Thanks for the good input. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: feature overview
Clay Leeds wrote: > p.s. Note to Victor: Might we update FAQ 3.2 to: > > My PNG|JPEG|TIFF|GIF|PICT|PSD|BMP|ICO|CUR|SUNRASTER(?)|XBM|XPM|PCX > images don't work. > ... That is a good idea. Look for that within the next few days. The content will probably be in a different location, with the FAQ referenced to it. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: feature overview
This is "sort of" a FAQ (although the FAQ only mentions PNG images). The answer appears to be JIMI which is used by FOP for all image formats except most forms of JPG & GIF files: http://java.sun.com/products/jimi/ (if FOP handles other image formats, I couldn't find them quickly). According to Sun's JIMI download page: Jimi's range of supported formats includes GIF, JPEG, TIFF, PNG, PICT, Photoshop, BMP, Targa, ICO, CUR, Sunraster, XBM, XPM, and PCX, although some of these formats do not have complete support for all features. Since "Photoshop" is listed, I assume the "PSD" graphic you're referring to is supported. Good luck! p.s. Note to Victor: Might we update FAQ 3.2 to: My PNG|JPEG|TIFF|GIF|PICT|PSD|BMP|ICO|CUR|SUNRASTER(?)|XBM|XPM|PCX images don't work. or better yet (borrowing from one of Joerg's replies): Q: My image(s) don't work. A: If you're using a JPG, JPG images can contain all kind of weird color lookup tables and color profiles, not all variants are supported (not to mention the *illegal* subformats seen here and there in the wild). Try a JPG produced by a different graphic program. Specifying 24-bit color output may also help. Alternatively, if you're not using a JPG or GIF image, Sun's Jimi image library, is by default used for processing images in the following formats: GIF, JPEG (JPG), TIFF, PNG, PICT, Photoshop (PSD), BMP, Targa, ICO, CUR, Sunraster, XBM, XPM, and PCX, although some of these formats do not have complete support for all features. The JIMI class library was removed from the FOP distribution for licensing reasons. You'll have to download (linked to http://java.sun.com/products/jimi) and install it by yourself. Extract the file "JimiProClasses.zip" from the archive you've downloaded, rename it to "jimi-1.0.jar" and move it to FOP's lib directory. An alternative to Jimi is to use Sun's JAI. It is much faster, but not available for all platforms. Double-check all my content, as it was copy/pasted (and some of it may not be true!). This would help with Joerg & my handy dandy "ultimate assistant" idea (Ctrl-F--ROTFL!) come to fruition... ;-p [EMAIL PROTECTED] wrote: > Is there a way to include a psd graphic > > Thanks > vikram -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: feature overview
Is there a way to include a psd graphic Thanks vikram - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: feature overview
Clay Leeds wrote: > Seriously, though, perhaps someone (like me? ;-p) could start generating > a few test cases like those that are sitting up on renderx.com. Anyone > have a set of test cases lying around? See http://xml.apache.org/fop/dev/testing.html. This document just got moved from the user (Home) tab to the Developer tab. One of the things on my agenda is to go through this document and make sure it is accurate & complete. Also, somewhat related, there are at least two examples pages: http://xml.apache.org/fop/examples.html http://xml.apache.org/fop/dev/examples.html I would root around in the related directories in the source distribution as there might be some that are not documented on these pages. One of the problems with the examples is that they are generated using the trunk version of FOP, not the maintenance branch that all of the users are using, so they are not very helpful on the web site, but they are probably helpful for testing. > Also, where would one submit these? See http://xml.apache.org/fop/dev/index.html#Contributing+code%2C+tests+and+docu mentation That URL will change as soon as I can clean it up. Also, the content is not up-to-date. The correct way is to submit a new issue in Bugzilla: http://xml.apache.org/fop/bugs.html#issues_new and include "[PATCH]" at the beginning of the issue description. If done correctly, the item should then appear in the "Patch queue" (see the FOP Development tab for the URL). I would be very, very glad to have someone pounding on this testing so that we can get compliance.html up-to-date. That is an extremely valuable tool for user self-help. Thanks for your efforts here. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: feature overview
Woohoo! There's a party in compliance.html, and everyone's invited! BYOB-S (Bring Your Own Border-Style! ;-p) Seriously, though, perhaps someone (like me? ;-p) could start generating a few test cases like those that are sitting up on renderx.com. Anyone have a set of test cases lying around? Also, where would one submit these? Web Maestro Clay Jeremias Maerki wrote: > You know, that's an awful lot of work to document each and every > attribute of the XSL-FO standard. We're working on completing that page. > We've had a lot less before Victor put so much work into the compliance > page. An hour ago I've added comments on the border-style and > font-family attributes in CVS. It'll take a while but that information > will make it on the website soon. All users of FOP are invited to > participate in making the compliance page better. > > On 08.04.2003 13:06:23 Todtenhaupt, Susann wrote: > >>This side I already found... but what I search is an overview where also the >>supported values for the attributes are listed. For example: for >>border-style the value solid only works. >> >>-Ursprüngliche Nachricht- >>Von: Oleg Tkachenko [mailto:[EMAIL PROTECTED] >>Gesendet: Dienstag, 8. April 2003 12:47 >>An: [EMAIL PROTECTED] >>Betreff: Re: feature overview >> >>Todtenhaupt, Susann wrote: >> >> >>>Where can I find an overview of features that are supported by fop and >>>things that don't work? >> >>http://xml.apache.org/fop/compliance.html > > > > Jeremias Maerki -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: feature overview
Hello jeremias! I know that's a huge effort... I've joined that group not long ago and I've not so much experience with fop. And so I thought somebody can help me in this case. Where did you add this comment on cvs? Thanx! suse -Ursprüngliche Nachricht- Von: Jeremias Maerki [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 8. April 2003 13:32 An: [EMAIL PROTECTED] Betreff: Re: AW: feature overview You know, that's an awful lot of work to document each and every attribute of the XSL-FO standard. We're working on completing that page. We've had a lot less before Victor put so much work into the compliance page. An hour ago I've added comments on the border-style and font-family attributes in CVS. It'll take a while but that information will make it on the website soon. All users of FOP are invited to participate in making the compliance page better. On 08.04.2003 13:06:23 Todtenhaupt, Susann wrote: > This side I already found... but what I search is an overview where also the > supported values for the attributes are listed. For example: for > border-style the value solid only works. > > -Ursprüngliche Nachricht- > Von: Oleg Tkachenko [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 8. April 2003 12:47 > An: [EMAIL PROTECTED] > Betreff: Re: feature overview > > Todtenhaupt, Susann wrote: > > > Where can I find an overview of features that are supported by fop and > > things that don't work? > > http://xml.apache.org/fop/compliance.html 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: AW: feature overview
You know, that's an awful lot of work to document each and every attribute of the XSL-FO standard. We're working on completing that page. We've had a lot less before Victor put so much work into the compliance page. An hour ago I've added comments on the border-style and font-family attributes in CVS. It'll take a while but that information will make it on the website soon. All users of FOP are invited to participate in making the compliance page better. On 08.04.2003 13:06:23 Todtenhaupt, Susann wrote: > This side I already found... but what I search is an overview where also the > supported values for the attributes are listed. For example: for > border-style the value solid only works. > > -Ursprüngliche Nachricht- > Von: Oleg Tkachenko [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 8. April 2003 12:47 > An: [EMAIL PROTECTED] > Betreff: Re: feature overview > > Todtenhaupt, Susann wrote: > > > Where can I find an overview of features that are supported by fop and > > things that don't work? > > http://xml.apache.org/fop/compliance.html Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: feature overview
This side I already found... but what I search is an overview where also the supported values for the attributes are listed. For example: for border-style the value solid only works. -Ursprüngliche Nachricht- Von: Oleg Tkachenko [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 8. April 2003 12:47 An: [EMAIL PROTECTED] Betreff: Re: feature overview Todtenhaupt, Susann wrote: > Where can I find an overview of features that are supported by fop and > things that don't work? http://xml.apache.org/fop/compliance.html -- Oleg Tkachenko http://www.tkachenko.com/blog Multiconn Technologies, Israel - 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]
AW: feature overview
There is a nice table on the FOP-Site: http://xml.apache.org/fop/compliance.html Greetings Carsten -Ursprüngliche Nachricht- Von: Todtenhaupt, Susann [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 8. April 2003 11:41 An: '[EMAIL PROTECTED]' Betreff: feature overview Hello! Where can I find an overview of features that are supported by fop and things that don't work? greetz suse - 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: feature overview
Todtenhaupt, Susann wrote: Where can I find an overview of features that are supported by fop and things that don't work? http://xml.apache.org/fop/compliance.html -- Oleg Tkachenko http://www.tkachenko.com/blog Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
feature overview
Hello! Where can I find an overview of features that are supported by fop and things that don't work? greetz suse - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
