Opened 17 years ago
Last modified 11 years ago
#43 assigned enhancement
Improve output markup (pgml.xsl)
Reported by: | Owned by: | Graham Dutton | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | 1:pg-eclipse | Keywords: | |
Cc: |
Description (last modified by )
Output markup can and should be improved a lot by extending the XSL file for PGML.
- More x-symbol compatibility to support Isabelle symbol usage may be possible (e.g., superscripts/subscripts).
- Can we make some parameters which can be configured in the interface to set fonts/colours, etc?
Longer term it is frustrating to have the input/output disparity so great. The HTML view may be better replaced with a StyledText once that is flexible enough and a semi-wysiwyg approach is possible.
Change History (7)
comment:1 Changed 17 years ago by
comment:2 Changed 17 years ago by
Status: | new → assigned |
---|
Output markup now needs to be updated for PGML 2.0.
comment:3 Changed 17 years ago by
Milestone: | → PG-Eclipse-1.0.6 |
---|---|
Type: | defect → enhancement |
comment:4 Changed 16 years ago by
Owner: | changed from David Aspinall to Graham Dutton |
---|
comment:5 Changed 16 years ago by
Description: | modified (diff) |
---|---|
Priority: | major → minor |
comment:6 Changed 16 years ago by
Milestone: | PG-Eclipse-1.0.6 → PG-Eclipse-1.0.7 |
---|
Note: See
TracTickets for help on using
tickets.
Note on PGML symbols in style sheet:
These are emitted by Isabelle as
<sym name="foo">\<foo></sym>
.We can add unicode options to stylesheet (or generate some parameters from the Symbols table in Eclipse?). This is beginning to look a bit old fashioned, though, maybe we could just use Unicode directly now in PGML.