| | 1 | = Using XSLT for C code generation and testing = |
| | 2 | |
| | 3 | == Abstract == |
| | 4 | |
| | 5 | [http://xmlroff.org xmlroff] is a fast, free, high-quality, multi-platform XSL formatter that aims to excel at !DocBook formatting and that integrates easily with other programs and with scripting languages. |
| | 6 | |
| | 7 | xmlroff is written in C, but much of the C code is generated from the XML source for the XSL recommendation. What started out as a simple stylesheet to extract FO and property names from the XSL spec to avoid transcription errors has grown (and shrunk) over time to generate: |
| | 8 | |
| | 9 | * C code for GObjects representing FOs and properties |
| | 10 | * C code to verify allowed property values |
| | 11 | * A single enumeration of all the 'enumerated token' values defined by XSL |
| | 12 | * Structured comments in the C code that are used by gtk-doc to generate documentation |
| | 13 | * XML entity declarations and references for assembling the generated documentation into one !DocBook document |
| | 14 | |
| | 15 | The code generation has been toned down in places over time. The initial object hierarchy was very flat because it was very easy to generate a unique class for each FO and each property, but just because you can doesn't mean you should, and there is now more use of common superclasses and that single, common enumuration of all of XSL's 'enumeration token' values. |
| | 16 | |
| | 17 | Other uses of XSLT and XPath in the xmlroff project include: |
| | 18 | |
| | 19 | * Pruning unsupported FOs and properties from the input FO document |
| | 20 | * Generating test scripts for any XSL formatter from a W3C-format XSL testsuite's XML description |
| | 21 | * Generating HTML reports from test results XML |
| | 22 | * Generating a W3C-format XSL testsuite from FOP "layoutengine" |
| | 23 | |
| | 24 | == Download == |
| | 25 | |
| | 26 | Poster (A0 size): [attachment:xmlroff-xslt.pdf] |
