Apologies for a vague specification. Desired features:
- Several (10+) different types of reports
- Common graphic design
- Reports are static -- not interactive CGI apps.
- Reports contain both text and tables and figures. Some text is stock, others are templated.
- Reports are rendered for different media: html for intranet (one page with internal links), for paper (pdf with sensible page breaks), et.
Here's an example of a templated section, written in psuedo TT2 code ...
## PSUEDO CODE
"Parsing [% num_major_files %] files generated a total
of [% num_major_incidents %] incidents, falling into
[% num_classes %] classes. Table [% an autogenerated
table number would go here %] presents the top 10
incident categories. Note that [% top_incident_class %]
comprises [% top_fract %] of the cases ....
A good DTD would get me much of the way there. I'm seeking an decent XML spec for sections, tables, figures, captions, etc.
rkg
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.