0.95beta out of the wilderness?
Hi, I know it is bad form to ask this question, but I was wondering when 0.95beta would cease to be a beta and become a full fledged version? I would like to use it in our production environment but I cannot make the case for it while it is in beta. Actually, I would really like what is in trunk to be released (working of course) as it has a feature I really need. Thanks. -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 0.95beta out of the wilderness?
Jeremias Maerki wrote: Hehe. We've been working on the during the last few days. I'm just waiting for the mirrors to catch up until I post the announcement. Please note that 0.95 final will be a bugfix release to 0.95 beta. Most of the features in trunk won't be in 0.95 final. What feature are you referring to? The feature I wanted was min-height. We spent most of today trying to work out a good hack to replicate it. Setting a height on a row is the closest we could get :( (FOP just spits out a warning if there is "overflow", but lets it go through). Just as long as 0.95 doesn't change this, we will probably upgrade. How long does it take for the mirrors catch up? On 05.08.2008 10:07:27 Kamal Bhatt wrote: Hi, I know it is bad form to ask this question, but I was wondering when 0.95beta would cease to be a beta and become a full fledged version? I would like to use it in our production environment but I cannot make the case for it while it is in beta. Actually, I would really like what is in trunk to be released (working of course) as it has a feature I really need. Thanks. -- Kamal Bhatt Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 0.95beta out of the wilderness?
I had a closer look at the compliance table, there are some seriously good features in trunk (integer support for keep-with-*, min/max heights). 0.96 is looking like a great version as well. Thanks. Jeremias Maerki wrote: Hehe. We've been working on the during the last few days. I'm just waiting for the mirrors to catch up until I post the announcement. Please note that 0.95 final will be a bugfix release to 0.95 beta. Most of the features in trunk won't be in 0.95 final. What feature are you referring to? The feature I wanted was min-height. We spent most of today trying to work out a good hack to replicate it. Setting a height on a row is the closest we could get :( (FOP just spits out a warning if there is overflow, but lets it go through). Just as long as 0.95 doesn't change this, we will probably upgrade. How long does it take for the mirrors catch up? On 05.08.2008 10:07:27 Kamal Bhatt wrote: Hi, I know it is bad form to ask this question, but I was wondering when 0.95beta would cease to be a beta and become a full fledged version? I would like to use it in our production environment but I cannot make the case for it while it is in beta. Actually, I would really like what is in trunk to be released (working of course) as it has a feature I really need. Thanks. -- Kamal Bhatt Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 0.95beta out of the wilderness?
Jeremias Maerki wrote: min-height is the (more or less) same as block-progression-dimension.minimum which already works with 0.95. min-height and max-height are so-called "corresponding properties" and are only in FO for CSS compatibility. See: http://www.w3.org/TR/xsl11/#min-height OK, in which case, I have another reason to upgrade :) On 05.08.2008 10:53:34 Kamal Bhatt wrote: snip/ The feature I wanted was min-height. We spent most of today trying to work out a good hack to replicate it. Setting a height on a row is the closest we could get :( (FOP just spits out a warning if there is "overflow", but lets it go through). Just as long as 0.95 doesn't change this, we will probably upgrade. snip/ Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 0.95beta out of the wilderness?
Kamal Bhatt wrote: Jeremias Maerki wrote: min-height is the (more or less) same as block-progression-dimension.minimum which already works with 0.95. min-height and max-height are so-called "corresponding properties" and are only in FO for CSS compatibility. See: http://www.w3.org/TR/xsl11/#min-height OK, in which case, I have another reason to upgrade :) Well, that was a waste of half a day. block-progression-dimension.minimum works in 0.93. Question about this. I have this code: fo:table-body fo:table-row fo:table-cell font-size="7.5pt" font-weight="bold" background-color="#DCE3E9" display-align="center" border-color="white" border-style="solid" border-bottom-style="none" fo:block fo:block margin-bottom="1mm" margin-top="1.5mm" margin-left="1mm" IBadfasfd /fo:block /fo:block /fo:table-cell fo:table-cell number-rows-spanned="2" font-size="7.5pt" line-height="1.4" background-color="#DCE3E9" display-align="center" border-color="white" border-style="solid" border-left-style="none" block-progression-dimension.minimum="45mm" fo:block fo:block margin-bottom="1mm" margin-left="3mm" margin-top="3mm" fo:blockblah/fo:block fo:blockblah/fo:block fo:blockTb;ah/fo:block fo:blockblah/fo:block fo:block font-size="7.5pt" font-weight="bold" margin-top="3mm"asdft/fo:block fo:block font-size="7.5pt" font-weight="bold" margin-top="3mm"asdf/fo:block fo:block font-size="7.5pt" font-weight="bold" margin-top="3mm"asdf/fo:block fo:block font-size="7.5pt" font-weight="bold" margin-top="3mm"asdf/fo:block fo:block font-size="7.5pt" font-weight="bold" margin-top="3mm"asdf/fo:block fo:block font-size="7.5pt" font-weight="bold" margin-top="3mm"asdf/fo:block fo:block font-size="7.5pt" font-weight="bold" margin-top="3mm"asdf/fo:block /fo:block /fo:block /fo:table-cell /fo:table-row fo:table-row fo:table-cell font-size="7.5pt" line-height="1.4" background-color="#EBF1F6" display-align="center" border-color="white" border-style="solid" fo:block margin-bottom="1mm" margin-top="0mm" margin-left="3mm" TTESTESTETSTEET /fo:block fo:block margin-bottom="1mm" margin-top="0mm" margin-left="3mm" asdfasdf /fo:block /fo:table-cell /fo:table-row /fo:table-body Now, when I run this, it works, but if I put the block-progression-dimension.minimum="45mm" on the block (instead of the table) it doesn't work. My reading of the standard is that it should be. What am I missing? Also, I want subsequent pages to have the same height, how can I achieve this? On 05.08.2008 10:53:34 Kamal Bhatt wrote: snip/ The feature I wanted was min-height. We spent most of today trying to work out a good hack to replicate it. Setting a height on a row is the closest we could get :( (FOP just spits out a warning if there is "overflow", but lets it go through). Just as long as 0.95 doesn't change this, we will probably upgrade. snip/ Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Progress of FOP development
Olakara wrote: Hi all, I would like to know the status of FOP library development. Some say development has stopped and not to use it. Regards, Abdel Development on 0.20.x stopped a long time ago. If that is what you are talking about, then yes, but 0.9x is (as far as I know) very much an active project. -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Getting hyphenation to work
Andreas Delmelle wrote: On May 29, 2008, at 04:28, Kamal Bhatt wrote: J.Pietschmann wrote: paul womack wrote: Kamal Bhatt wrote: Thanks. Works a treat. One more question, where can I get these hyphenation files for asian languages (such as japanese). I'm far from sure hyphenation is even a valid concept in Japanese. Well, digging around: http://marc.info/?l=fop-devm=102992807207069w=2 While this is mostly about line breaking, hyphenation may happen under certain, apparently very rare circumstances. Some more info is in the wikipedia: http://en.wikipedia.org/wiki/Kinsoku_shori I wonder whether the rules there are reflected in the Unicode line breaking properties, which would mean that FOP 0.95ff would handle this properly. snip / Only partially, if I'm correct. As a fall-back, the UAX#14 implementation in FOP allows breaks between /any/ pair of CJK ideographs. (see: http://markmail.org/search/?q=CJK+linebreaking#query:CJK%20linebreaking+page:1+mid:uykln4qu3gz6r45d+state:results) OK, I didn't understand that post, but by the looks of it FOP does not support Asian languages. Seeing as most Asian languages (I would think) are monospaced, am I correct in saying that it would be something that would be best done at the XSLT level (ie, build your own hyphenation rules into an XSLT and put them in blocks)? As mentioned in the post, this is simplistic, and may very well lead to a layout that is undesirable/suboptimal from the POV of someone who is versed well enough in either one of the related languages. (see the Korean example attached to the OP in that thread) Someone once started more detailed work on this, and an initial patch is available in Bugzilla #36977, but this hasn't been incorporated in the codebase yet, since there were concerns about the approach operating 'on top of' UAX#14 (unnecessarily increasing iterations over the same character sequences). Also, how does one convert a Tex file into a valid hyphenation XML file? I don't think there's a tool available to do so directly, although, from the last time I researched this topic, I do seem to remember that there are tools that convert TeX hyphenation files into a generic XML format. Subsequently, with a minimum of effort, such an XML file could then be transformed via XSLT to match the format used by FOP. HTH! -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Getting hyphenation to work
Thanks. Works a treat. One more question, where can I get these hyphenation files for asian languages (such as japanese). On May 28, 2008, at 03:05, Kamal Bhatt wrote: Hi I have downloaded they hyphenation files from: http://offo.sourceforge.net/hyphenation/index.html I have copied these files into c:/fop-0.93/hyph I have updated my config file to point to this directory for hyphenation base: hyphenation-baseC:/fop-0.93/hyph//hyphenation-base I have updated my FO to include language=en. There is an C:/fop-0.93/hyph/en.xml file (both attached) However, my line does not hyphenate. Instead, it remains a mess (attached) What am I doing wrong? The only thing you seem to be forgetting is: fo:blockALLWORKANDNOPLAYMAKESKAMALADULLBOYALLWORKANDNOPLAYMAKESKAMALADULLBOYALLWORKANDNOPLAYMAKESKAMALADULLBOYALLWORKANDNOPLAYMAKESKAMALADULLBOYALLWORKANDNOPLAYMAKESKAMALADULLBOYALLWORKANDNOPLAYMAKESKAMALADULLBOYALLWORKANDNOPLAYMAKESKAMALADULLBOYALLWORKANDNOPLAYMAKESKAMALADULLBOYALLWORKANDNOPLAYMAKESKAMALADULLBOYALLWORKANDNOPLAYMAKESKAMALADULLBOYALLWORKANDNOPLAYMAKESKAMALADULLBOY fo:block You need: fo:block hyphenate=true... Or alternatively, specify the property on the fo:root, if you want it to apply to all fo:blocks in the document. HTH! Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fox:continued-label
bonekrusher wrote: Hi, I am hoping if someone can provide some guidance on fox:continued-label in FOP 0.94. Is this supported? If not what is the possible work arounds? Thanks for the guidance. Bones Answer, according to this page: http://xmlgraphics.apache.org/fop/0.94/extensions.html, is no. And based on the release notes, ditto 0.95a. The general (pretty poor) work around is to use markers. See here: http://www.dpawson.co.uk/xsl/sect3/markers.html#d14055e100 -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Japanese postscript fonts
Hi, I was wondering if anyone knew of any postscript Japanese fonts (or if such a thing exists). I am talking about a font that doesn't simply support Japanese at the expense of english, but support for Latin text, Kana and Kanji. I want postscript so I can support printing. Thanks. -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] New release of PDF image support for Apache FOP
Jeremias Maerki wrote: Thanks. I've added a redirect. It actually should have been http://www.jeremias-maerki.ch/development/fop/ This would be useful to my company if you supported the addition of PDFs to postscript files or the addition of postscript files to PDFs. Do you have any plans to do so? Thanks. On 14.03.2008 22:38:54 Kamal Bhatt wrote: In your readme, you specify the following website: http://www.jeremias-maerki.ch/dev/fop/ This website doesn't seem to work any more. Jeremias Maerki wrote: I've just published a new release (Version 1.1) of the PDF image support plug-in for Apache FOP. Note: this release is only interesting for people using FOP Trunk revision 611768 or later. Version 1.1 doesn't work with FOP 0.94 or any earlier version. If you use FOP 0.94, you can use Version 1.0 of the plug-in which is still available for download. For details on the plug-in, please read the README file in the distribution. Downloads: http://www.jeremias-maerki.ch/download/fop/pdf-images/ Jeremias Maerki Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] New release of PDF image support for Apache FOP
In your readme, you specify the following website: http://www.jeremias-maerki.ch/dev/fop/ This website doesn't seem to work any more. Jeremias Maerki wrote: I've just published a new release (Version 1.1) of the PDF image support plug-in for Apache FOP. Note: this release is only interesting for people using FOP Trunk revision 611768 or later. Version 1.1 doesn't work with FOP 0.94 or any earlier version. If you use FOP 0.94, you can use Version 1.0 of the plug-in which is still available for download. For details on the plug-in, please read the README file in the distribution. Downloads: http://www.jeremias-maerki.ch/download/fop/pdf-images/ Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Unexplained space
/ fo:table-body fo:table-row font-size=9pt fo:table-cell fo:blockABC 123/fo:block /fo:table-cell fo:table-cell fo:block Page fo:page-number / /fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table /fo:static-content fo:flow flow-name=itin-body fo:block margin-bottom=6.5mm fo:table border-bottom-width=1.7mm border-bottom-color=#d6d3cf border-bottom-style=solid border-top-width=1.7mm border-top-color=#d6d3cf border-top-style=solid padding-bottom=3.5mm padding-top=3.5mm table-layout=fixed width=100% fo:table-column column-width=27mm / fo:table-column column-width=90mm / fo:table-column column-width=75mm / fo:table-body font-family=sans-serif font-size=10pt color=#333 margin-bottom=3mm fo:table-row fo:table-cell fo:block margin-left=3mmItinerary for/fo:block /fo:table-cell fo:table-cell fo:blockMR A TEST/fo:block fo:blockAND PARTY/fo:block /fo:table-cell fo:table-cell fo:table table-layout=fixed width=100% fo:table-column column-width=50mm / fo:table-column column-width=25mm / fo:table-body fo:table-row fo:table-cell padding-after=2.2mm fo:block border-bottom-color=#333 border-bottom-width=thin border-bottom-style=solid Booking /fo:block /fo:table-cell fo:table-cell padding-after=2.2mm fo:block border-bottom-color=#333 border-bottom-width=thin border-bottom-style=solid text-align=right GG/219306 /fo:block /fo:table-cell /fo:table-row fo:table-row fo:table-cell padding-after=2.2mm fo:blockIssued/fo:block /fo:table-cell fo:table-cell padding-after=2.2mm fo:block text-align=right13 Nov 2007/fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table /fo:table-cell /fo:table-row /fo:table-body /fo:table /fo:block fo:block font-size=9pt font-family=HelveticaMonospace color=#333 white-space-treatment=preserve linefeed-treatment=preserve fo:table table-layout=fixed width=100% fo:table-column column-width=11mm / fo:table-column column-width=16mm / fo:table-column column-width=169mm / fo:table-body fo:table-row fo:table-cell number-columns-spanned=3 fo:block color=#005F97 font-size=12pt font-family=sans-serif font-weight=bold margin-bottom=3mm border-bottom-width=0.1mm border-bottom-style=solid border-bottom-color=#005F97 PREPARED ON BEHALF OF ABC 123 /fo:block /fo:table-cell /fo:table-row fo:table-row fo:table-cell fo:block / /fo:table-cell fo:table-cell number-columns-spanned=2 fo:block linefeed-treatment=preserve margin-bottom=5mm margin-top=0 fo:block padding=0 margin-bottom=0 white-space-collapse=false white-space-treatment=preserve flight enquiries to check that your aircraft will be /fo:block departing at the time shown on your ticket and itinerary. * Baggage weight should not exceed 20 kilograms. For every kilogram over the allowance, excess baggage fees may be charged. * The standard Australian hotel check-in time is 2:00pm. If you are arriving on an early flight, you may not be able to access your room until this time. * Upon check-in at your hotel or collection of your rental car, you will be asked for either a credit card imprint or a cash deposit. This is standard procedure and is used as a deposit against incidentals, excess car insurance, etc. /fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table /fo:block /fo:flow /fo:page-sequence /fo:root -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Lines become unnecessarily thick - IGNORE ME
Kamal Bhatt wrote: Hi, I am producing the FO below from an XSLT and I noticed that certain lines would be needlessly thick. I was wondering if anyone had any clues. Ignore this email. It was a trick of my monitor/adobe acrobat. ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; xmlns:str=http://exslt.org/strings; xmlns:datetime=http://exslt.org/dates-and-times; fo:layout-master-set fo:simple-page-master margin-right=11mm margin-left=19mm margin-bottom=13mm margin-top=8mm page-height=297mm page-width=210mm master-name=A4 fo:region-body region-name=itin-body margin-right=10mm margin-bottom=16mm margin-top=7mm / fo:region-after extent=16mm region-name=itin-after / /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=A4 fo:flow flow-name=itin-body fo:block font-size=9pt font-family=sans-serif margin-bottom=6mm font-weight=bold text-align-last=justify Itinerary for Asbjorn Widvey and party fo:leader leader-pattern=space / Issued 05 October 2007 /fo:block fo:block font-size=9pt font-family=sans-serif margin-bottom=6mm font-weight=bold Booking Reference: GG/211531 /fo:block fo:block font-size=9pt font-family=sans-serif margin-bottom=6mm fo:block linefeed-treatment=preserve We wish you an enjoyable and memorable holiday. Please note the following information: * The standard Australian hotel check-in time is 2:00pm. If you are arriving on an early flight, you may not be able to access your room until this time. * Upon check-in at your hotel or collection of your rental car, you will be asked for either a credit card imprint or a cash deposit. This is standard procedure and is used as a deposit against incidentals. /fo:block /fo:block fo:block border-color=black border-width=0.75pt border-style=solid fo:block border-bottom-color=black border-bottom-width=0.75pt border-bottom-style=solid background-color=#C1 fo:block font-size=9pt font-family=sans-serif font-weight=bold margin-top=3mm margin-bottom=3mm margin-left=1mm color=whiteSunday 23 September 2007 /fo:block /fo:block fo:block fo:block border-bottom-color=black border-bottom-width=0.75pt border-bottom-style=solid background-color=#E6E6E6 keep-with-previous=always fo:block font-size=9pt font-family=sans-serif font-weight=bold margin-top=3mm margin-bottom=3mm margin-left=1mm color=black keep-with-previous=always Flight/fo:block /fo:block fo:block border-bottom-color=black border-bottom-width=0.75pt border-bottom-style=solid background-color=white keep-with-previous=always orphans=2 fo:block margin-top=2mm margin-left=1mm margin-bottom=2mm fo:table table-layout=fixed width=100% fo:table-column column-width=19% / fo:table-column column-width=2% / fo:table-column column-width=36% / fo:table-column column-width=32% / fo:table-column column-width=11% / fo:table-body fo:table-row margin-right=0 margin-left=0 fo:table-cell font-size=9pt font-family=sans-serif color=#333 fo:block margin-bottom=2mm7am/fo:block /fo:table-cell fo:table-cell font-size=9pt font-family=sans-serif color=#333 number-columns-spanned=3 fo:block margin-bottom=2mmDepart AUCKLAND on Virgin Blue flight DJ187/fo:block /fo:table-cell /fo:table-row fo:table-row margin-right=0 margin-left=0 fo:table-cell font-size=9pt font-family=sans-serif color=#333 fo:block margin-bottom=2mm/fo:block /fo:table-cell fo:table-cell font-size=9pt font-family=sans-serif color=#333 number-columns-spanned=3 fo:block margin-bottom=2mmOperated by Pacific Blue (NZ)/fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table /fo:block /fo:block /fo:block fo:block fo:block border-bottom-color=black border-bottom-width=0.75pt border-bottom-style=solid background-color=#E6E6E6 keep-with-previous=always fo:block font-size=9pt font-family=sans-serif font-weight=bold margin-top=3mm margin-bottom=3mm margin-left=1mm color=black keep-with-previous=always Flight/fo:block /fo:block fo:block border-bottom-color=black border-bottom-width=0.75pt border-bottom-style=solid background-color=white keep-with-previous=always
Re: Capitalize not working?
Pascal Sancho wrote: Hi, Capitalize value indicates that the first character of each word is put in uppercase. No tranformation is invoked for other characters. With a full uppercase word, this value has no effect. I see your point. I just wonder if that was the intent when it was written. Seem counter intuitive for it work that way. Anyway, thanks. Pascal -Message d'origine- De : Kamal Bhatt [mailto:[EMAIL PROTECTED] Envoyé : jeudi 25 octobre 2007 01:50 Hi, I have the following: fo:inline text-transform=capitalizeJOHN SMITH/fo:inline I expect this to render as John Smith based on this explanation: http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#text-transform However, this does not happen. Is this a bug or am I misreading this functionality? Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple pages on one page
Philipp Wagner wrote: On Monday 27 August 2007 09:20, Kamal Bhatt wrote: Hi, Is there any way of configuring FOP to put multiple pages on the one page? For example, I want to generate a document where two FO pages sit on the one physical page. Would it be difficult to modify the Renderer to do this, if we cannot do it already? Why don't you let FOP generate two seperate PDF pages and merge them afterwards? pdftk is only one example, the multivalent tools is another (http://multivalent.sourceforge.net/Tools/pdf/Impose.html). If you output PS you have an even broader toolset you may use. There is nothing wrong with that approach, this is how it's done in commercial printing (called imposition; although used usually on a much larger Your right, that is what I need. They can do themselves a favour and put some download links on their page (instead of telling us to go to sourceforge) -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: keep-together always
After all this makes sense: we can imagine situations where the user prefers the content to be clipped rather than broken over two, e.g., pages. always allows for that. If the user simply wants the content to be broken only if it doesn't fit, they would choose an integer value. An unfortunate side effect of this interpretation is that keep-together is next to useless for most people as I suspect most people do not want clipping and FOP doesn't support integers for keep-together (though I admit that is nothing more than opinion). Is it likely that FOP will support integer values for keeps and breaks in the next couple of versions? If not, would it be possible to make keep-together work the way most people seem to think it will work if you specify an integer? (ie an integer would cause it to work in the way most people think always should) -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: keep-together always
Michiel Roos wrote: Dear Karmal, I read your mail as first this morning and it kind of struck me. Usually my fop mail gets filtered out into the fop box, but your mail came through the filter. The subject struck me first, then I read the mail. The syntax of the mail hints that it is about fop, but the words / concepts used kind of struck a chord in me. Imposes a keep-together condition with strength always in the appropriate context. Wow! I was hoping to see an email from a woman I met recently. I have known her for only a week but the experience has been a profound and powerful one. So I kind of read your mail with that mindset. . . . got me thinking again . . . Cheers, kindest of regards, Glad I inspired you (or at least the FO standard :) I don't know why my email didn't get filtered, if it is any consolation, emails from fop-user don't get automatically filtered on my Thunderbird. I can't help by feel that this is a round about way of asking me to be more specific in my posting on the mailing list. I will endeavour to do so in the future. FYI, my name is not spelt with a 'r'. -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: keep-together always
Vincent Hennebert wrote: An unfortunate side effect of this interpretation is that keep-together is next to useless for most people as I suspect most people do not want clipping and FOP doesn't support integers for keep-together (though I I don't agree. The content will be clipped only if the whole block doesn't fit on a page alone, which is not that usual I think. If the content can fit by, e.g., starting a page then the paging algorithm will do so. Speaking personally, I cannot see any circumstance I would use keep-together in FOP (at least in its current form). I am using FOP to generate travel documentation (itineraries) and I don't know the size of most of the data before hand (I cannot do multiple passes). Question is, when will those versions be released ;-) If I were to ask this question would I get a helpful answer? :) -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
keep-together always
Hi I noticed a feature of keep-together=always. Basically it does exactly that, even when it doesn't make sense. That is, it will overflow a block instead of breaking across a page. Now, I have looked at the standard, and it is fairly airy fairy about what keep-together=always actually does: *always* Imposes a keep-together condition with strength always in the appropriate context. What appropriate context means is anyone's guess. From what I have read, some have interpreted this to mean that always is the highest possible strength. Seems to me that makes sense. So is this bit of functionality a bug? Cheers. -- Kamal Bhatt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: basic-link and external-graphic
Pascal Sancho wrote:
Hi Kamal,
What you describe occurs with FOP 0.93 and latest TRUNK.
This seems to be a bug.
==
The active area is limited to font-size.
The fo:basic-link return one or more inline areas, and one of these areas
should be defined by the fo:external-graphic.
And the XSL-FO REC 1.1 [1] says: ...typically by clicking on any of the containing
areas.
Can you please fill in a bug in bugzilla [2]?
Workaround:
===
Adding the property font-size={$banner_height}mm elsewhere does the trick..
Note that thought FOP accepts this property in the fo:basic-link, it is not in
the list of appliable properties for this FO in the spec [1].
Inserting a fo:wrapper in the fo:basic-link and giving it the property
font-size is a good thing
Thanks for that. I put the font-size in and the link still doesn't span
the full image (it misses the top). I am using sans-serif. That said,
this is acceptable to me as it covers the middle of the image. I noticed
that if I put the font-size on the enclosing block, my static content
(which my link is in) overflows. Is this a bug (symptomatic of the same
problem) or a feature of FO?
Cheers.
PS. I have that bug report:
42501
--
Kamal Bhatt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
