softwaresaved / software-deposit-guidance Goto Github PK

Currently, this is a manual process, done within an SVG editor. This should be automated, the Makefile (and if applicable README.md) updated, then the PNGs removed from the repository.

I'm not keen on Times New Roman as a web, or guide, font. I experimented with Arial/Helvetica in css/style.css:

@font-face
{
    font-family: Arial, Helvetica, sans-serif;
}

The changes were visible in HTML but not PDF. Googling proved no help in providing a straightforward solution. Defining the following did work for PDFs too:

body
{
    font-family: Arial, Helvetica, sans-serif;
}

However, line spacing within paragraphs can look inconsistent depending on the presence/absence of footnotes. Experiment with CSS to get a footnote style that does not lead to inconsistent spacing between lines within the same paragraph.

Image width/heights, defined in CSS, and page breaks, defined in Markdown via CSS markup, are used to ensure a heading does not appear at the very bottom of a page or that half a page is empty because an image is too high for the space remaining.

Implement more elegant handling of page breaks to remove the need for using CSS markup in MarkDown.

This may require separate CSS depending on whether the HTML is to be deployed online or is being created as an intermediate step when creating PDFs.

pandoc Markdown supports inline footnotes e.g.

^[Example inline footnote with links to [Google](http://www.google.co.uk) and [EPCC](http://www.epcc.ed.ac.uk)]

One advantage of these is that footnote numbering is handled automatically.

Update Markdown documents to move all footnotes to be inline footnotes.