diff --git a/Makefile b/Makefile index 7bfb628..f3ab6d4 100644 --- a/Makefile +++ b/Makefile @@ -10,10 +10,10 @@ gmi.css.5: gmi.css.5.scd scdoc < $< > $@ format: + ./node_modules/prettier/bin-prettier.js --write README.md ./node_modules/prettier/bin-prettier.js --write gmi.css ./node_modules/prettier/bin-prettier.js --write *.js !*.min.js - clean: rm -rf gmi.min.* gmi-web.1 diff --git a/README.md b/README.md index ba50069..a765aff 100644 --- a/README.md +++ b/README.md @@ -10,9 +10,10 @@ The generated HTML document must have a `` tag with _at minimum_ the follo ```html - - - + + + + ``` @@ -20,22 +21,22 @@ You might want to also include these (or whatever else): ```html - - + + ``` ## `` The converted Gemini document should be placed inside the ``. Due to the ambiguity of HTML several translations from Gemini exist in the wild. I propose the following standard: -``` +````

↔ => 

          ↔ ```
        ↔ #[##]
 
  •            ↔ *
 
       ↔ >
-```
+````
 
 The `` for a link should be presented un-wrapped without any parent elements. Many implementations use `
    ` or `
    ` to enforce "block" styling as opposed to the default "inline" which renders the link next to the previous block instead of below it. But the nested markup adds an unnecessary layer of indirection in semantics. The best way to handle this is to include `` in the ``.
 
@@ -55,94 +56,66 @@ If a link is consumable by ``, `