| Name | Modified | Size |
|---|---|---|
| .. | ||
| css | ||
| images | ||
| htmlhelp.xsl | 10 years ago | 11 KB |
| Change | User | Description | Committed |
|---|---|---|---|
| 12828 | eedwards | #review-1028126 Update the logo for both PDF, HTML, and CHM output. Includes updated favi...con.ico for the HTML output. Includes some additional tweaks: - In the HTML presentation, the "book" icon (to access the PDF, if available) and the magnifying glass icon for searching both look more clickable, using colors from the latest perforce.com design. - Also, both icons stick to the right edge of the doc content, rather than the right edge of the browser. - The background color in the HTML presentation is now plain white; the gradient image is removed. - The Google Analytics code is now included in the HTML presentation by default. Individual guides can disable this by setting the DocBook parameter perforce.analytics=0. Once this change is in place, subsequent generation of guides will incorporate these changes. « |
10 years ago |
| 12823 | eedwards | Add a new 'htmlhelp' doc build target that generates the HTML, index, TOC files that can... be compiled into a CHM file on a Windows machine using HTML Help Workshop. The build target can be used wherever the doc infrastructure runs, but the final CHM compilation currently needs to be performed on a Windows box. This means full CHM production automation is currently unavailable. Further investigation into non-Microsoft CHM compilers will be required for full automation. Note that any guide that requires CHM production will need to add its own 'htmlhelp' asset tree. The P4VS guide will (shortly) become a decent reference, if required. For any XSLT tinkerers, note that only a few of the 'htmlhelp' DocBook parameters are currently passed through to the transformation phase. If you need to pass any additional parameters through, add them to build.xml as appropriate. « |
10 years ago |