Once again I need a little more help please.
I followed Jay Bryant's advice and structured my xsl file according to his example. I got it to work well, but in saving things I overwrote what I had done. I recreated it -- almost. I now have a few questions; 1 - In the attached files, why are no business units showing up? I have looked and looked but can't figure out why they don't. 2 - How do I get the background color to fill the entire cell and not just the text background. (When I had the business units data showing up, the header cell backgrounds filled the entire space). 3 - When the business data did appear earlier, and I viewed at 100%, the borders did not run into each other and left a small space between them. How do I force the borders to join? Thanks for any help. ?xml version=1.0? xsl:stylesheet version=2.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:fo=http://www.w3.org/1999/XSL/Format; xsl:template match=print-compliance xsl:processing-instruction name=cocoon-formattype=text/xslfo /xsl:processing-instruction fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=compliance-form margin-top=50pt margin-bottom=50pt margin-left=15pt margin-right=20pt page-height=8.5in page-width=11in fo:region-body margin-bottom=1pt/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=compliance-form fo:flow flow-name=xsl-region-body xsl:apply-templates select=header / xsl:apply-templates select=business_units / /fo:flow /fo:page-sequence /fo:root /xsl:template xsl:template match=header fo:table table-layout=fixed border-collapse=collapse space-before=0pt border-style=none xsl:variable name=product_list select=product_list / fo:table-column column-width={fullwidth}/ fo:table-body fo:table-row fo:table-cell background-color={title_bg_color} fo:block text-align=center wrap-option=no-wrap font-size={fontsize} line-height={linespace} font-weight={fontweight} color={color} border={border} xsl:value-of select=report_name/ /fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table xsl:apply-templates select=headerline/ /xsl:template xsl:template match=headerline fo:table table-layout=fixed border-collapse=collapse space-before=0pt xsl:for-each select=colsize fo:table-column column-width={value}/ /xsl:for-each fo:table-body fo:table-row line-height={linespace} display-align={vertical} xsl:apply-templates select=hdr_itm/ /fo:table-row /fo:table-body /fo:table /xsl:template xsl:template match=hdr_itm fo:table-cell wrap-option={../wrap} fo:block text-align={align} font-size={fontsize} border={border} font-weight={../fontweight} color={color} background-color='{bg_color}' xsl:value-of select=value/ /fo:block /fo:table-cell /xsl:template xsl:template match=business_units xsl:for-each select=bu xsl:apply-templates select=bus_header/ xsl:apply-templates select=bus_data/ xsl:apply-templates select=bus_summary/ /xsl:for-each /xsl:template xsl:template match=bus_header fo:table table-layout=fixed border-collapse=collapse space-before=0pt space-after=0pt border={border} fo:table-column column-width='{fullwidth}'/ fo:table-body fo:table-row xsl:variable name=bu_bg_color select=bu_bg_color / xsl:variable name=bu_color select=bu_color / fo:table-cell background-color='{bu_bg_color}' fo:block text-align=start wrap-option={wrap} font-size={fontsize} line-height={linespace} font-weight=bold color='{bu_color}' border={border} xsl:value-of select=bu_title/ /fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table /xsl:template xsl:template match=bus_data fo:table table-layout=fixed border-collapse=collapse space-before=0pt space-after=0pt background-color={data_bg_color} line-height={data_linespace} xsl:for-each select=bu_col_width fo:table-column column-width={value}/ /xsl:for-each fo:table-body xsl:for-each select=bu_line fo:table-row xsl:for-each select=bu_item fo:table-cell fo:block text-align={align} wrap-option=no-wrap font-size={fontsize} font-weight={fontweight} color={color} border={borderline} xsl:value-of select=value/ /fo:block /fo:table-cell /xsl:for-each /fo:table-row /xsl:for-each /fo:table-body /fo:table /xsl:template xsl:template match=bus_summary fo:table table-layout=fixed
Re: Once again I need a little more help please.
Sheldon Glickler wrote: I followed Jay Bryant's advice and structured my xsl file according to his example. I got it to work well, but in saving things I overwrote what I had done. I recreated it -- almost. I now have a few questions; 1 - In the attached files, why are no business units showing up? I have looked and looked but can't figure out why they don't. 2 - How do I get the background color to fill the entire cell and not just the text background. (When I had the business units data showing up, the header cell backgrounds filled the entire space). 3 - When the business data did appear earlier, and I viewed at 100%, the borders did not run into each other and left a small space between them. How do I force the borders to join? Thanks for any help. I figured out what the answer to (1) is. I needed to bracket the data in the xml with tags to match the select in the xsl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Once again I need a little more help please.
Sheldon Glickler wrote: Sheldon Glickler wrote: I followed Jay Bryant's advice and structured my xsl file according to his example. I got it to work well, but in saving things I overwrote what I had done. I recreated it -- almost. I now have a few questions; 1 - In the attached files, why are no business units showing up? I have looked and looked but can't figure out why they don't. 2 - How do I get the background color to fill the entire cell and not just the text background. (When I had the business units data showing up, the header cell backgrounds filled the entire space). 3 - When the business data did appear earlier, and I viewed at 100%, the borders did not run into each other and left a small space between them. How do I force the borders to join? Thanks for any help. I figured out what the answer to (1) is. I needed to bracket the data in the xml with tags to match the select in the xsl. I have attached the xsl and xml tags. They generate what I am now asking about. Viewing the output at 100%: 1 - How do I fill the backgrounds of the cells of the third line (the last header line). 2 - How can I get the borders top join? Look at the line between the last header line and the first business unit header line. Also, between the other lines. the intent here is for the borders to be with 1pt of .5pt. 3 - Why doesn't the border show when cells are empty in the data area? 4 - Why does it look like the vertical borders on the last line extend beyond the bottom of the line? ?xml version=1.0? xsl:stylesheet version=2.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:fo=http://www.w3.org/1999/XSL/Format; xsl:template match=print-compliance xsl:processing-instruction name=cocoon-formattype=text/xslfo /xsl:processing-instruction fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=compliance-form margin-top=50pt margin-bottom=50pt margin-left=15pt margin-right=20pt page-height=8.5in page-width=11in fo:region-body margin-bottom=1pt/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=compliance-form fo:flow flow-name=xsl-region-body xsl:apply-templates select=header / xsl:apply-templates select=business_units / /fo:flow /fo:page-sequence /fo:root /xsl:template xsl:template match=header fo:table table-layout=fixed border-collapse=collapse space-before=0pt border-style=none xsl:variable name=product_list select=product_list / fo:table-column column-width={fullwidth}/ fo:table-body fo:table-row fo:table-cell background-color={title_bg_color} fo:block text-align=center wrap-option=no-wrap font-size={fontsize} line-height={linespace} font-weight={fontweight} color={color} border={border} xsl:value-of select=report_name/ /fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table xsl:apply-templates select=headerline/ /xsl:template xsl:template match=headerline fo:table table-layout=fixed border-collapse=collapse space-before=0pt xsl:for-each select=colsize fo:table-column column-width={value}/ /xsl:for-each fo:table-body fo:table-row line-height={linespace} display-align={vertical} xsl:apply-templates select=hdr_itm/ /fo:table-row /fo:table-body /fo:table /xsl:template xsl:template match=hdr_itm fo:table-cell wrap-option={../wrap} fo:block text-align={align} font-size={fontsize} border={border} font-weight={../fontweight} color={color} background-color='{bg_color}' xsl:value-of select=value/ /fo:block /fo:table-cell /xsl:template xsl:template match=business_units xsl:for-each select=bu xsl:apply-templates select=bus_header/ xsl:apply-templates select=bus_data/ xsl:apply-templates select=bus_summary/ /xsl:for-each /xsl:template xsl:template match=bus_header fo:table table-layout=fixed border-collapse=collapse space-before=0pt space-after=0pt border={border} fo:table-column column-width='{fullwidth}'/ fo:table-body fo:table-row xsl:variable name=bu_bg_color select=bu_bg_color / xsl:variable name=bu_color select=bu_color / fo:table-cell background-color='{bu_bg_color}' fo:block text-align=start wrap-option={wrap} font-size={fontsize} line-height={linespace} font-weight=bold color='{bu_color}' border={border} xsl:value-of select=bu_title/ /fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table /xsl:template xsl:template match=bus_data fo:table table-layout=fixed border-collapse=collapse space-before=0pt
Re: Once again I need a little more help please.
I followed Jay Bryant's advice and structured my xsl file according to his example. I got it to work well, but in saving things I overwrote what I had done. I recreated it -- almost. I now have a few questions; Glad it worked for you as far as it did. I have attached the xsl and xml tags. They generate what I am now asking about. Viewing the output at 100%: 1 - How do I fill the backgrounds of the cells of the third line (the last header line). Put the background-color attribute on the table-cell element rather than on the block element. 2 - How can I get the borders top join? Look at the line between the last header line and the first business unit header line. Also, between the other lines. the intent here is for the borders to be with 1pt of .5pt. Borders are amazingly tricksy beasts. First off, to really get them to render correctly, you need to throw out the idea of border-collapse. Then you have two choices: Control each border (left, right, top, bottom) for each cell individually or set them all to the same values (width, color, and style). Thus, a simple way to get all the borders in a table to be 1pt wide is to set both the table's border and each cell's border to be .5pt wide. They'll all be adjacent when rendered, and you'll get 1pt borders. If you want something more complicated (some cells have borders while others don't or all the outside borders are double while the inners are solid), you should set each border (left, right, etc.) individually. To that end, I've moved all your border attributes to table-cells, so that table and block no longer have border attributes. 3 - Why doesn't the border show when cells are empty in the data area? Actually, it did (I zoomed in to 400% to be sure. However, because the block in the cell had no content, the height of the block was 0, so you had a top border and a bottom border and nothing in between them. Consequently, the block rendered such that it looked like a thick line. To fix this (and other issues), I removed the borders from blocks and put them on the cells. As a rule of thumb, define borders at the cell level and not at the block level. You should generally only put a border on a block if it's a stand-alone block (not in a table). There are exceptions, but, until you've strengthened your XSL-FO muscle some more, I suggest keeping things simple. 4 - Why does it look like the vertical borders on the last line extend beyond the bottom of the line? I'm not seeing that, but I've seen it in other documents. If it's what I think it is, it's a rendering error in Acrobat Reader. Try zooming to different levels and seeing if the problem persists. If it does, you've got work to do. If not, it's a well-known (and much-loathed) quirk of Acrobat Reader. It just occurred to me that you may mean Why does the border stick out to the left and right relative to the cells that don't have borders. That's the nature of borders. The cell has its space, and the border has a space around the cell's space. So, if one cell has no border and the next cell down does have a border, the bordered cell appears to stick out. Take a peek at http://www.w3.org/TR/2001/REC-xsl-20011015/slice4.html#area-intro to see what's happening. To fix those issues, either be consistent about your borders (everything has a border or everything doesn't), use just top and bottom borders, or set the border color of borderless cells to the cell's background color. Also, fo:table doesn't have a line-height attribute, so I put that on the blocks. I have attached the modified XSLT file. I am off to a movie, so I can't show you exactly how to control the borders individually right now. I hope these changes help you, though. Jay Bryant ?xml version=1.0? xsl:stylesheet version=2.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:fo=http://www.w3.org/1999/XSL/Format; xsl:template match=print-compliance xsl:processing-instruction name=cocoon-formattype=text/xslfo /xsl:processing-instruction fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=compliance-form margin-top=50pt margin-bottom=50pt margin-left=15pt margin-right=20pt page-height=8.5in page-width=11in fo:region-body margin-bottom=1pt/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=compliance-form fo:flow flow-name=xsl-region-body xsl:apply-templates select=header / xsl:apply-templates select=business_units / /fo:flow /fo:page-sequence /fo:root /xsl:template xsl:template match=header fo:table table-layout=fixed space-before=0pt border-style=none xsl:variable name=product_list select=product_list / fo:table-column column-width={fullwidth}/ fo:table-body fo:table-row
Re: Once again I need a little more help please.
Jay Bryant wrote: I followed Jay Bryant's advice and structured my xsl file according to his example. I got it to work well, but in saving things I overwrote what I had done. I recreated it -- almost. I now have a few questions; Glad it worked for you as far as it did. Great. You have been a tremendous help. I have attached the xsl and xml tags. They generate what I am now asking about. Viewing the output at 100%: 1 - How do I fill the backgrounds of the cells of the third line (the last header line). Put the background-color attribute on the table-cell element rather than on the block element. Did that. It worked. Thanks. 2 - How can I get the borders top join? Look at the line between the last header line and the first business unit header line. Also, between the other lines. the intent here is for the borders to be with 1pt of .5pt. Borders are amazingly tricksy beasts. First off, to really get them to render correctly, you need to throw out the idea of border-collapse. Then you have two choices: Control each border (left, right, top, bottom) for each cell individually or set them all to the same values (width, color, and style). Thus, a simple way to get all the borders in a table to be 1pt wide is to set both the table's border and each cell's border to be .5pt wide. They'll all be adjacent when rendered, and you'll get 1pt borders. If you want something more complicated (some cells have borders while others don't or all the outside borders are double while the inners are solid), you should set each border (left, right, etc.) individually. To that end, I've moved all your border attributes to table-cells, so that table and block no longer have border attributes. When I moved them to the the table-cells, it looked great. 3 - Why doesn't the border show when cells are empty in the data area? Actually, it did (I zoomed in to 400% to be sure. However, because the block in the cell had no content, the height of the block was 0, so you had a top border and a bottom border and nothing in between them. Consequently, the block rendered such that it looked like a thick line. To fix this (and other issues), I removed the borders from blocks and put them on the cells. As a rule of thumb, define borders at the cell level and not at the block level. You should generally only put a border on a block if it's a stand-alone block (not in a table). There are exceptions, but, until you've strengthened your XSL-FO muscle some more, I suggest keeping things simple. They show now when they are at the cell level. 4 - Why does it look like the vertical borders on the last line extend beyond the bottom of the line? I'm not seeing that, but I've seen it in other documents. If it's what I think it is, it's a rendering error in Acrobat Reader. Try zooming to different levels and seeing if the problem persists. If it does, you've got work to do. If not, it's a well-known (and much-loathed) quirk of Acrobat Reader. It just occurred to me that you may mean Why does the border stick out to the left and right relative to the cells that don't have borders. That's the nature of borders. The cell has its space, and the border has a space around the cell's space. So, if one cell has no border and the next cell down does have a border, the bordered cell appears to stick out. Take a peek at http://www.w3.org/TR/2001/REC-xsl-20011015/slice4.html#area-intro to see what's happening. To fix those issues, either be consistent about your borders (everything has a border or everything doesn't), use just top and bottom borders, or set the border color of borderless cells to the cell's background color. Also, fo:table doesn't have a line-height attribute, so I put that on the blocks. It looks great now. I have attached the modified XSLT file. I am off to a movie, so I can't show you exactly how to control the borders individually right now. I hope these changes help you, though. I hope you enjoyed the movie. I still have a few minor questions. 1 - I am using number-columns-spanned in order to use the same template with sub-section headings and totals. I use the parameter merge. For the sub-titles, I give it a value of 13 (all the columns). For the sub-section totals, I give the first one a value of 5, followed by eight cells with a value of 1. It all worked, but I get one blank for the number of columns spanned and one blank for the background color. I isolated it to the following in the xml file: bu_line bu_item valueTRACKING SALES/value alignstart/align borderlinesolid .5pt/borderline fontweightnormal/fontweight fontsize6pt/fontsize colorblack/color merge13/merge bg_color#99/bg_color /bu_item /bu_line If I remove that block, then there are no errors. In the xsl, it uses those keys for every line in the business bu_tiem section, with no additional errors. I'm stumped. It works, but it
Re: Once again I need a little more help please.
Hi, Sheldon, 1 - I am using number-columns-spanned in order to use the same template with sub-section headings and totals. I use the parameter merge. For the sub-titles, I give it a value of 13 (all the columns). For the sub-section totals, I give the first one a value of 5, followed by eight cells with a value of 1. It all worked, but I get one blank for the number of columns spanned and one blank for the background color. I isolated it to the following in the xml file: bu_line bu_item valueTRACKING SALES/value alignstart/align borderlinesolid .5pt/borderline fontweightnormal/fontweight fontsize6pt/fontsize colorblack/color merge13/merge bg_color#99/bg_color /bu_item /bu_line If I remove that block, then there are no errors. In the xsl, it uses those keys for every line in the business bu_tiem section, with no additional errors. I'm stumped. It works, but it isn't clean. Without seeing your XSL for this bit, it's hard to provide a for-sure answer. My initial thought is that you're not checking for the existence of the merge element. If you have fo:table-cell number-columns-spanned={merge} but there's no merge element, you get fo:table-cell number-columns-spanned= in the FO output. At best, it'll be ignored. Instead, use something like this: fo:table-cell xsl:if test=merge gt; 0 !-- test for the presence of the element, that its value is numeric, and that its value is 1 or more -- xsl:attribute name=number-columns-spannedxsl:value-of select=merge//xsl:attribute /xsl:if Again, though, I'm just guessing. If you want a spot-on answer, post your XSLT with the spanning code. 2 - How do I put spaces in place. For example, if I wanted Admin, rather than Admin, how do I make that happen? It seems to ignore initial whitespace. First, you should understand that leading and trailing white space is, by default, stripped when the transform loads the XML input stream. Think of it as having a trim() function run on everything. However, you can dictate which elements should have their spaces preserved and which shouldn't by using the xsl:strip-space and xsl:preserve-space elements at the top of your transform. In looking at your XML, it looks like you want to preserve space on the value element, so you'd add xsl:preserve-space elements=value/ at the top of your transform. Note that both instructions take a space-separated list (rather ironic for instructions that manage spaces, no?). So, if you had a second element (call it widget) on which you needed to preserve spaces, you'd have xsl:preserve-space elements=value widget/. Both instructions take wildcards, so you can do xsl:preserve-space elements=*/ and xsl:strip-space elements=value widget/ to get exactly the reverse of xsl:preserve-space elements=value widget/. Also (and this ties to your next question), you can always force a space by using the trusty old entity for a non-breaking space. Note that you have to use the decimal value for it, though (or you have to define an nbsp entity somewhere). So you can do things like fo:blockForce a space here:#160;/fo:block (160 is the decimal code for an nbsp). 3 - How do put in special characters like the ampersand? XML (and remember that XSL is also XML) defines 5 special entities: amp; - the ampersand quot; - the double quotation mark apos; - the single quotation mark lt; - the less than sign () gt; - the greater than sign () You can always use those 5 entities to get those characters from an XSL transform. Assuming your using the UTF-8 character set, you can also use just about any character in the set by specifying its decimal value in an entity (as I did above for the non-breaking space). In addition to #160;, I use #8226; (that's a bullet a charater) when I need bullets. I'm sure you can find umpteen examples with a quick search. One heavy caveat: entities are guaranteed to bite you hard if you again transform the output of a transform. Consider the trusty ampersand character. In your first transform, you insert one with amp;. Then your second transform throws an error complaining that it can't resolve an entity because it hit that character. This leads to weirdness such as: amp;amp; It's far better to make sure all your processing doesn't involve entities until the last step in your processing chain. As a side note, I use Ant to control build processes that sometimes have transform after transform (because the process needs to merge data sets and such). I make sure that I get all the content in place before I add any entities in the formatting step (which has to be the last step for just this reason). As I progress through this, I pick up more and more ideas. For example, in the shouda dun it that way category is to use just the template for the data line. I could have run all the lines through that template without the need for specialized xsl stuff. Next time! Thanks
Re: Once again I need a little more help please.
Jay Bryant wrote: Hi, Sheldon, 1 - I am using number-columns-spanned in order to use the same template with sub-section headings and totals. I use the parameter merge. For the sub-titles, I give it a value of 13 (all the columns). For the sub-section totals, I give the first one a value of 5, followed by eight cells with a value of 1. It all worked, but I get one blank for the number of columns spanned and one blank for the background color. I isolated it to the following in the xml file: bu_line bu_item valueTRACKING SALES/value alignstart/align borderlinesolid .5pt/borderline fontweightnormal/fontweight fontsize6pt/fontsize colorblack/color merge13/merge bg_color#99/bg_color /bu_item /bu_line If I remove that block, then there are no errors. In the xsl, it uses those keys for every line in the business bu_tiem section, with no additional errors. I'm stumped. It works, but it isn't clean. Without seeing your XSL for this bit, it's hard to provide a for-sure answer. My initial thought is that you're not checking for the existence I am posting the files. No, I don't do the checking, but this is the only bu_line that gives a problem and they all go through the same code. Thank you for being so exceedingly helpful. Now my REAL effort begins. I have to do a log of php coding in order to gather the data and generate the xml files that use this xsl file. ?xml version=1.0? xsl:stylesheet version=2.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:fo=http://www.w3.org/1999/XSL/Format; xsl:template match=print-compliance xsl:processing-instruction name=cocoon-formattype=text/xslfo /xsl:processing-instruction fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=compliance-form margin-top=50pt margin-bottom=50pt margin-left=5pt margin-right=5pt page-height=8.5in page-width=11in fo:region-body margin-bottom=1pt/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=compliance-form fo:flow flow-name=xsl-region-body xsl:apply-templates select=header / xsl:apply-templates select=business_units / /fo:flow /fo:page-sequence /fo:root /xsl:template xsl:template match=header fo:table table-layout=fixed border-collapse=collapse space-before=0pt border-style=none xsl:variable name=product_list select=product_list / fo:table-column column-width={fullwidth}/ fo:table-body fo:table-row line-height={linespace} fo:table-cell background-color={title_bg_color} fo:block text-align=center wrap-option=no-wrap font-size={fontsize} font-weight={fontweight} color={color} border={border} xsl:value-of select=report_name/ /fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table xsl:apply-templates select=headerline/ /xsl:template xsl:template match=headerline fo:table table-layout=fixed space-before=0pt xsl:for-each select=colsize fo:table-column column-width={value}/ /xsl:for-each fo:table-body fo:table-row line-height={linespace} display-align={vertical} xsl:apply-templates select=hdr_itm/ /fo:table-row /fo:table-body /fo:table /xsl:template xsl:template match=hdr_itm fo:table-cell background-color='{bg_color}' border={border} fo:block text-align={align} font-size={fontsize} wrap-option={../wrap} font-weight={../fontweight} color={color} xsl:value-of select=value/ /fo:block /fo:table-cell /xsl:template xsl:template match=business_units xsl:for-each select=bu xsl:apply-templates select=bus_header/ xsl:apply-templates select=bus_data/ xsl:apply-templates select=bus_summary/ /xsl:for-each /xsl:template xsl:template match=bus_header fo:table table-layout=fixed space-before=0pt space-after=0pt fo:table-column column-width='{fullwidth}'/ fo:table-body fo:table-row line-height={linespace} fo:table-cell background-color='{bu_bg_color}' border={border} fo:block text-align=start wrap-option={wrap} font-size={fontsize} font-weight=bold color='{bu_color}' xsl:value-of select=bu_title/ /fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table /xsl:template xsl:template match=bus_data fo:table table-layout=fixed space-before=0pt space-after=0pt xsl:for-each select=bu_col_width fo:table-column column-width={value}/ /xsl:for-each fo:table-body xsl:for-each select=bu_line fo:table-row line-height={../linespace} xsl:for-each select=bu_item fo:table-cell background-color={bg_color} number-columns-spanned={merge}
Re: Once again I need a little more help please.
1 - I am using number-columns-spanned in order to use the same template with sub-section headings and totals. I use the parameter merge. For the sub-titles, I give it a value of 13 (all the columns). For the sub-section totals, I give the first one a value of 5, followed by eight cells with a value of 1. It all worked, but I get one blank for the number of columns spanned and one blank for the background color. I isolated it to the following in the xml file: bu_line bu_item valueTRACKING SALES/value alignstart/align borderlinesolid .5pt/borderline fontweightnormal/fontweight fontsize6pt/fontsize colorblack/color merge13/merge bg_color#99/bg_color /bu_item /bu_line If I remove that block, then there are no errors. In the xsl, it uses those keys for every line in the business bu_tiem section, with no additional errors. I'm stumped. It works, but it isn't clean. Without seeing your XSL for this bit, it's hard to provide a for-sure answer. My initial thought is that you're not checking for the existence I am posting the files. No, I don't do the checking, but this is the only bu_line that gives a problem and they all go through the same code. I ran the files through Saxon 9 and FOP .95 and didn't see the issue you mention. The Trackwork Sales line came out fine. I added the bu_line element mentioned earlier in your message (the Tracking Sales one) and still didn't get a problem. It's possible that the issue arises because of whichever XSLT processor you're using or the version of FOP you have. It's also possible that you fixed the issue while fixing some other issue. Let me know if it keeps biting you and I'll try to look more deeply. Thank you for being so exceedingly helpful. Now my REAL effort begins. I have to do a log of php coding in order to gather the data and generate the xml files that use this xsl file. You're welcome. I'm that lucky fellow who actually enjoys his job, so doing a little weekend programming to help someone out is no problem. I know what you mean about the real work. For me, it's Java and SQL (with XML- and CSV-based metadata defining things) that do all the heavy lifting. Much as I love XSL, it's just the tail end of a much larger and much more complex process. Jay Bryant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]