I am a total noob with XSL and XSL-FO and I'm looking for some advice on possibilities and boundaries with DotNet 2.0 3.5 When using XSL to format XML data for reporting purposes
This is what I was doing.
1) Get data from SQL 2005 DB based on some business rules
2) Create XML files from output directly from XML or some other custom medium level components and Save files to disk.
3) Use a 3rd party libraries to create PDFs from transformed files. & Lt; - I also need tips on tools.
My worries are around the page break and when the break is done, keep the relevant material together. I can say to these two commandments: stay with the past and stay with the next. But I believe that there are XSL-FO commands, please correct me if I am wrong. Is there anything that appears in the base XSL commands? Have I read and did not support DotNet XSL-FO, is it still true? I also read some posts about adding XSL schema to the Visual Studio schema for accessibility, is anyone aware of the current XSL-FO schema for this purpose? So what I have achieved and what concerns me should I know about the boundaries of XSL-FO in Dotnet and IE.
I have used XSL-FO in a very professional, both Java and .NET environments. It actually gives you total control over the printed document / PDF. I have prepared myself very complex PDF for mass-printing (brochures and papers). They included complex structures such as text in the columns, graphs (using embedded SVG) and tables.
XSL-FO is for printing which is HTML for the screen, Given that you learn to know it well, you will be able to produce anything with it, no matter how complex designs are.
Java is probably one of the best XSL-FO processors and it's also free, open-source.
Good 2.
XSL-FO is definitely the way to go on generating pdf or printed documents.
EDIT: I only answered your question, I think XSL-FO is not fundamentally supported in any of today's normal browsers, I do not think that implementing native support in IE There is no plan, I would wonder if it was. XSL-FO is just XML, so you will not need any further XSL-FO support as per today's NAT Framework. Typically, XSL-FO is generated using XSLT, and then the conversion result goes to a formatting object processor, such as FOP. In some cases, XSLT (at least not 1.0) is not enough, if your XSL-FO document is very complex, then you might consider using the XSLT extension, which is written in languages such as C #. In some cases, maybe XSLT is not good for the job, then you can use the code to generate XSL-FO.
Comments
Post a Comment