Something went wrong. Try again.
my forest
Something went wrong. Try again.
12345678910111213\title{Porting to Forester 6.0}\author{liamoc}\p{This forest has now been ported to Forester 6.0. You may need to clear your cache to get rid of stale stylesheets or redirects. Despite the fact that the HTML backend of Forester 6.0 doesn't support any customisation, I was able to inject mycustomisations including [Gregorian chants](loc-0015), [syntax highlighting](loc-0029), [TSV tables](loc-002F) and most of mystyle tweaks simply by making a custom Forester 6.0 theme that replaces the existing \code{style.css} with a file that \code{@import}s my additional style sheets, and similarly the \code{min.js} with a file that imports all of my custom scripts.}\p{There were a few bugs or minor things that I had to fix, that I'll document here:}\ul{ \li{The new search dialog looks for \code{forest.js} in the wrong place, so I hardcoded a fix for my forest in my custom theme.} \li{The generated pages preload \code{katex.min.css} but don't actually load it. I put a \code{@import(katex.min.css)} line into my stylesheet to fix this.} \li{The generated \code{index.html} redirects to the wrong place, so I put a custom \code{index.html} in the custom theme that overrides Forester's generated one.} \li{The top-level \code{.block} elements in a page didn't have the \code{data-taxon} attribute which my custom stylesheet depends on. I guess this is also a bug, as it's a regression from the previous Forester 5.0 pages. I added this to the Forester source code in my private fork.} \li{The download link meta-data that I added custom to my XSLT sheet in Forester 5.0 is now hardcoded in my private fork of Forester 6.0. Perhaps when more customisation options are added (and the above bug fixed), I will not need a private fork anymore, as this is really the only customisation I had that cannot already be accommodated by my custom theme.}}