Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Storage and presentation format for specification #6

Open
mo-marqh opened this issue Sep 27, 2023 · 6 comments
Open

Storage and presentation format for specification #6

mo-marqh opened this issue Sep 27, 2023 · 6 comments
Assignees

Comments

@mo-marqh
Copy link
Member

mo-marqh commented Sep 27, 2023

Decide on a storage format and presentation formats for the #5 specification

requirements:

  1. storage format is plain text
    • to support source control
  2. identified releases of source and publish content are provided
  3. html presentation format required
    • may this be in the public domain?
  4. pdf presentation format required

Options Analysis

  • markdown
  • asciidoc
  • sphinx
  • latex
  • m$Word
    • discounted - not plain text or source controllable
@mo-marqh
Copy link
Member Author

on AsciiDoc (https://asciidoctor.org/)

  • +ve
    • meets core requirements
    • widely used by standards bodies (e.g. CF-netCDF, OGC)
    • flexible and well featured
    • simple markup syntax
  • -ve
    • asciidoctor not installed on linux desktop
    • not widely used within Met Office

@mo-marqh
Copy link
Member Author

on MarkDown

  • +ve
    • flexible and usefully featured
    • simple markup syntax
  • -ve
    • processors not installed on linux desktop (e.g. pandoc)
    • lacking rich features

@mo-marqh
Copy link
Member Author

on sphinx

  • +ve
    • meets core requirements
    • flexible and well featured
    • simple markup syntax
  • -ve
    • lots of tools targeting code documentation, rather than specification

@mo-marqh
Copy link
Member Author

on LaTeX

  • +ve
    • widely used in UM documentation
    • flexible and well featured
    • widely used within Met Office
  • -ve
    • not so good at producing html content
    • less than simple markup syntax

@mo-marqh
Copy link
Member Author

there's a TeX example in PR #11 and an asciidoc example in PR #12

@mo-marqh
Copy link
Member Author

after in-person discussions, the consensus appears to be to run with asciidoc for now

there's a good set of reasons to consider sphinx and we may come back to this in the future
(indeed, converting from asciidoc markup to sphinx should not be too onerous, if needed)

But the simple setup, the clear markup, and the PDF and HTML document style output of asciidoctor have gained significant support.
Also recognising that communities including the CF-netCDF community use this for their own publishing.

So, we'll close this Issue, merge #12 and close #11

This was referenced Oct 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant