-
Notifications
You must be signed in to change notification settings - Fork 129
Processing of <attRef> pointing at a class produces ugly output #384
Copy link
Copy link
Open
Labels
conversion: htmlpriority: lowNot urgent; can be dealt with when someone has free time or is looking for a project.Not urgent; can be dealt with when someone has free time or is looking for a project.resp: StylesheetsGroupIssue is suitable for the group-learning approach taken in the Stylesheets Coop Working Group.Issue is suitable for the group-learning approach taken in the Stylesheets Coop Working Group.type: bugA bug report.A bug report.
Milestone
Metadata
Metadata
Assignees
Labels
conversion: htmlpriority: lowNot urgent; can be dealt with when someone has free time or is looking for a project.Not urgent; can be dealt with when someone has free time or is looking for a project.resp: StylesheetsGroupIssue is suitable for the group-learning approach taken in the Stylesheets Coop Working Group.Issue is suitable for the group-learning approach taken in the Stylesheets Coop Working Group.type: bugA bug report.A bug report.
Type
Fields
Give feedbackNo fields configured for issues without a type.
@sydb and @martindholmes found that the output shown on this page:
https://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/lastSuccessfulBuild/artifact/P5/release/doc/tei-p5-doc/en/html/ref-att.entryLike.html
is the result of the processing of a workaround for the bug in #370. However, it includes an unnecessary introductory word "Attributes". Although in this case it's a workaround, legitimate cases for using attRef then overriding it obviously exist, so this should work and should produce cleaner output.