Closed jakebeal closed 3 years ago
I think it would be cleaner to have a separate CSV or JSON file that lists (filename, caption, sbol-version) triples, and a script that uses this to automatically generate both the .tex
file for the spec and a .html
file for the webpage.
Parsing the LaTeX seems like a kludge, and whilst something like Pandoc could convert it to HTML the change bar macros could be a hassle to deal with.
(Unless you meant just building this appendix as a separate PDF, rather than converting to HTML - which should be easy but be slightly less well integrated into the website)
I think hugo already has a latex parser for websites.
On Wed, Dec 2, 2020 at 1:25 PM James Scott-Brown notifications@github.com wrote:
I think it would be cleaner to have a separate CSV or JSON file that lists (filename, caption, sbol-version) triples, and a script that uses this to automatically generate both the .tex file for the spec and a .html file for the webpage.
Parsing the LaTeX seems like a kludge, and whilst something like Pandoc could convert it to HTML the change bar macros could be a hassle to deal with.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/SynBioDex/SBOL-visual/issues/121#issuecomment-737340228, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC5LO7ADB4LIAHJWFKD63YDSSZS6XANCNFSM4S7IRUFQ .
This is now implemented, with the caveat that the LaTeX figure references (e.g, \ref{f:apdx:exa1}
) in captions are not being converted.
The appendix of examples in the back of the specification would be good to share on the website as well as examples. One way to do this and maintain it would be to automate generation of webpage materials from the LaTeX source of https://github.com/SynBioDex/SBOL-visual/blob/master/specification/apdx-examples.tex