Title | MPS RefMan is not valid XHTML |
Status | closed |
Priority | optional |
Assigned user | Richard Kistruck |
Organization | Ravenbrook |
Description | MPS RefMan is not valid XHTML. RHSK 2006-04-14 The MPS RefMan (manual/reference/index.html) is not valid XHTML, at least according to the current [W3C checker]. |
Analysis | RHSK 2006-04-14 Fix until w3 accepts it. |
How found | inspection |
Evidence | [W3C checker]: http://validator.w3.org/ |
Observed in | 1.106.2 |
Created by | Richard Kistruck |
Created on | 2006-04-14 12:01:15 |
Last modified by | Gareth Rees |
Last modified on | 2013-05-22 12:06:39 |
History | 2006-04-14 RHSK Created. 2006-04-14 RHSK Correct W3C checker link. |
Change | Effect | Date | User | Description |
---|---|---|---|---|
180943 | closed | 2013-02-08 16:17:34 | Richard Brooksby | Integrating branch/2012-10-09/user-guide back to master. |
158165 | closed | 2006-04-14 11:57:20 | Richard Kistruck | MPS master RefMan: make it valid XHTML (according to http://validator.w3.org/check ):A. fix head: add xml encoding; specify DTD correctly. B. close tags properly. C. escape ampersands properly. D. resolve duplicate anchors for mps_res_t constants (MPS_RES_*): D.1. The mps_res_t entry is a useful overview: it enumerates and gives a pithy description of each constant. I make this the primary anchor for each of MPS_RES_*, because that seems the most helpful. D.2. Some constants (MPS_RES_MEMORY, MPS_RES_LIMIT, MPS_RES_PARAM) have a more detailed entry of their own. I name the anchors for these entries MPS_RES_*_detailed, and add links to them from the mps_res_t entry. |