The Project Publisher does a good job of exporting an entire project to an html structure.
The elements which contain sub diagrams let me link to them as I would expect.
The Glossary Items show up LOOKING LIKE links as they do inside VPP but clicking on the links in the html structure does not behave the same way as within VPP.
Inside VPP, clicking on a glossary item takes you straight to the glossary explanation.
That’s exactly what I want in the html version. Instead it takes me to a page summarising the Element containing the glossary term, rather than the glossary itself.
I’ve looked at some of the html pages and what appears to be happening is that the html generates an image of the relevant diagram, then places dynamic links corresponding to the positions of the elements on the image, which is clever stuff, but it doesn’t drill down to the content of the element (to find such things as the glossary items within. And of course, this leads potential readers to see what looks like links but aren’t really.
Is there a solution to this or are we required to rejig the pages in an html editor to insert the missing links?
and - if we are forced to insert our own links - where can we retrieve the link ids for individual glossary items and how would be export the glossary itself to a location in the html tree where we could access the individual items?