09 Dec, 2011
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@593 d98387aa-ee2c-4292-a9e6-504d2a719fd3
06 Dec, 2011
2 commits
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@573 d98387aa-ee2c-4292-a9e6-504d2a719fd3
-
I'd recommend <section> instead of <sect1> <sect2> <sect3> etc. as the stylesheets know how to handled nested <section> elements, and docs are easier to restructure when sections are not numbered. git-svn-id: https://svn.forgerock.org/openidm/trunk@572 d98387aa-ee2c-4292-a9e6-504d2a719fd3
02 Dec, 2011
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@557 d98387aa-ee2c-4292-a9e6-504d2a719fd3
30 Nov, 2011
1 commit
-
Notice that you get syntax highlighting by adding a language attribute, such as language="javascript", to block elements that preserve whitespace like <programlisting> or <screen>. I'm not particularly proud of the colors defined in src/main/docbkx-stylesheets/html/coredoc.xsl. Perhaps someone less aesthetically challenged could fix that. git-svn-id: https://svn.forgerock.org/openidm/trunk@547 d98387aa-ee2c-4292-a9e6-504d2a719fd3
29 Nov, 2011
1 commit
-
This works around http://code.google.com/p/docbkx-tools/issues/detail?id=36 allowing links that work in the HTML, and look like this in the source: refer to the chapter on <link xlink:href="admin-guide#chap-troubleshooting" xlink:role="http://docbook.org/xlink/role/olink"><citetitle >Troubleshooting</citetitle></link> in the <citetitle>Administration Guide</citetitle>. As the olinkdb files are not currently built for other formats, the xlink:role="http://docbook.org/xlink/role/olink" links are ignored during output generation. git-svn-id: https://svn.forgerock.org/openidm/trunk@542 d98387aa-ee2c-4292-a9e6-504d2a719fd3
09 Jun, 2011
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@228 d98387aa-ee2c-4292-a9e6-504d2a719fd3
25 May, 2011
1 commit
-
git-svn-id: https://svn.forgerock.org/openidm/trunk@211 d98387aa-ee2c-4292-a9e6-504d2a719fd3