Xsl

[Cowboy Bob]

ok, tell me how to do the following using fking XSL: I have got report that I want to be modular (thus easily customisable without much work), to do that I keep header, body and footer of the report in separate files. This means that header needs to output TABLE tag - only starting one, there is no closure in THAT template. The fking thing does not like the fact that unclosed (in that template) tag is generated ffs!

The parser is not designed to work with invalid XML which it is if you are not closing a tag. You need to find a different solution. Surely the TABLE tag should be in the body anyway, not the header? It sounds like the technology is not the problem, but how you're attempting to use it.

[bogeyman]

ok, tell me how to do the following using fking XSL: I have got report that I want to be modular (thus easily customisable without much work), to do that I keep header, body and footer of the report in separate files. This means that header needs to output TABLE tag - only starting one, there is no closure in THAT template. The fking thing does not like the fact that unclosed (in that template) tag is generated ffs!

Ah - I think I see your XSL problem...

It's a tulipE DESIGN

[AtW]

It sounds like the technology is not the problem, but how you're attempting to use it.

Look, I want to generate HTML that also doubles up as valid XML - table tag is necessary at the START of the table, and it should be closed at the END of the table, where as fking XSL expects me to have all tags closed within template, which means I can't have PrintHeader template (with open TABLE tag in it), then PrintBody (with my stuff) and finally PrintFooter - which would contain closed TABLE tag. The only solution appears to put the whole lot into one template, ffs, but I fking want to call templates for reason of them being separate ffs!

[CaribbeanPirate]

I used Apache FOP to convert XML data into PDFs for council planning applications. Boring subject, but not too hard... What problems have you had? Apache FOP has a generator to output XSL stylesheets from a PDF, so first create your desired PDF report format, pipe it through the generator, and then tweak it to the data that you're receiving.

Nothing major, just the fiddly bits such as sizing of blocks and finding things that the Apache FOP doesn’t support.

In our case we are generating some charts using Dundas at the same time as generating the XML report. Different types of financial instruments have different things to report.

We had to support US Letter and Euro A4 paper sizes too.

It was frustrating going round the iterative loop.

[DaveB]

Look, I want to generate HTML that also doubles up as valid XML - table tag is necessary at the START of the table, and it should be closed at the END of the table, where as fking XSL expects me to have all tags closed within template, which means I can't have PrintHeader template (with open TABLE tag in it), then PrintBody (with my stuff) and finally PrintFooter - which would contain closed TABLE tag. The only solution appears to put the whole lot into one template, ffs, but I fking want to call templates for reason of them being separate ffs!

Then change the template and have the tags in the main body and not in the header and footer. Or have seperate tables in each and stitch them together.

[bogeyman]

Then change the template and have the tags in the main body and not in the header and footer. Or have seperate tables in each and stitch them together.

Thank you Dave B.

[AtW]

Then change the template and have the tags in the main body and not in the header and footer.

Yes of course I can (and just did) do that, but WTF should I have to? <TABLE> tag belogs to header and footer of the table (you can't have header rows before table starts), its nonsense that partial tags can't be part of templates - its the final XML that should validate, not necesserily its parts.

Thank Chico's boss that I've got interpretation layer on top to take care of some other issues, otherwise it would have suck real bad - no wonder nobody uses it.

[bogeyman]

Thank Chico's boss that I've got interpretation layer on top to take care of some other issues, otherwise it would have suck real bad - no wonder nobody uses it.

Ah! But have you micro-optimised it?

p.s. what's up with the posting form here today? In FF 1.5 it spills over into the right-side navigation.

[DimPrawn]

Anyone here thinking the same as me?

The more "technical" posts AtW makes, the more you think,

"Oh Dear"

[Numptycorner]

I usually like to hoist the main brace and put a recall out to FSO polensk owners. If that is of no use I tripple fringer the database with a 3 bull side kick photocheck, this usually confuses the widget and resets the counter to zero.

Makes us laugh every time!