summaryrefslogtreecommitdiff
path: root/legacy/README.gd
diff options
context:
space:
mode:
authorBenjamin Chausse <benjamin@chausse.xyz>2021-01-03 02:07:50 -0500
committerBenjamin Chausse <benjamin@chausse.xyz>2021-01-03 02:07:50 -0500
commit3bc7d8d894fc6c50636dfb9f3c04e72cce02cb28 (patch)
tree0c6bfcfe405123ebd688cf49533ed3063c904f27 /legacy/README.gd
parente686830c06560f69489c6a9edae909da9e42f4df (diff)
Moving developpement to a C implementation
Diffstat (limited to 'legacy/README.gd')
-rw-r--r--legacy/README.gd65
1 files changed, 65 insertions, 0 deletions
diff --git a/legacy/README.gd b/legacy/README.gd
new file mode 100644
index 0000000..df3d0d0
--- /dev/null
+++ b/legacy/README.gd
@@ -0,0 +1,65 @@
+---
+title: Groffdown
+author: Benjamin Chausse
+date: 2019-09-19
+Markdown syntax with GNU/Troff-like compilation speeds.
+---
+
+
+# What is Groffdown?
+Groffdown aims to take the already existing (and well-known)
+markdown syntax and make it compile at speed similar to the
+ones of groff. The main compiler for markdown to pdf usually
+being `pandoc`, it can be quite long to compile a document (up
+to four seconds for one page documents
+in some cases) unlike Groff which is known
+to usually compile very quickly (0.1 second on average for
+one page documents). As a proof of concept, this *README*
+pages can be fully compiled using groffdown to then be used by groff.
+
+# Example piping workflow
+Groffdown is a script which when run on a markdown document,
+will convert the most typical markdown syntax into groff
+(using the `ms` macros) to then send it to standard output.
+Therefore, it can be piped directly into groff (or
+it's related software). Here is an example of a complete piping
+command:
+
+- groffdown <filename>.gd | refer -PS -e "-p$REFERBIB" | groff -me -ms -kejpt -T pdf > <filename>.pdf
+
+# Syntax goals
+- Speed
+- Markdown Syntax (with yaml preamble)
+- LaTeX where markdown lacks
+
+
+## Existing Syntax
+
+### Commands similar to markdown
+- Headers (1-5)
+- *Italic*
+- **Bold**
+- ***Bold & Italic***
+- Bullet points
+- `Code blocks (in a monospaced font)`
+
+### Commands similar to LaTeX
+- Abstract
+- Inline equations
+- Centered equations
+- Citations
+
+### Commands similar to YAML
+- Titles
+- Authors
+- Dates
+- Author's Institution
+
+# Current issues
+- All text formatings need to be on the same line (you can't start bold
+ on one line and finish on the other) Doing otherwise seems to trigger
+ an unescapable recursive loop on the groff side of things.
+
+# Needed implementations
+- Numbered lists
+- multi-macro compatibility (mom macros for urls)