~luxferre/Bopher-NG

f9a9be171c97c0b1386949602c9ebf83b735b6b7 — Luxferre 1 year, 2 months ago 7dfc0c4
Added gmi2txt.sh tool
1 files changed, 4 insertions(+), 4 deletions(-)

M tools/README-tools.md
M tools/README-tools.md => tools/README-tools.md +4 -4
@@ 1,9 1,9 @@
# Bopher Tools: a set of simple Bash scripts to not just browse Gopher but also create content for it

Bopher Tools is a small collection of simple shell scripts that are:
Bopher Tools is a small collection of simple shell scripts that:

- written in pure Bash with no external dependencies;
- totally independent from each other (but can be combined in the true spirit of Unix philosophy);
- are written in pure Bash with no external dependencies;
- are totally independent from each other (but can be combined in the true spirit of Unix philosophy);
- only accept input from stdin and only output their results into stdout;
- aim to ease your life when it comes to creating and publishing your own content in Gopherspace.



@@ 107,7 107,7 @@ Note that this tool hasn't been tested for all possible edge cases yet, so I rec

## `gmi2txt.sh`

This tool converts Gemtexts into CRLF-terminated and preformatted plaintext files ready to be served on Gopher. It has the same parameters as `gmi2map.sh` sans the placeholder character. Link lines are converted to the "[description]: [url]" format and, unlike `gmi2map.sh`, also are subject to reflows like everything else.
This tool converts Gemtexts into CRLF-terminated and preformatted plaintext files ready to be served on Gopher. It has the same parameters as `gmi2map.sh` sans the placeholder character. Link lines are converted to the `[description]: [url]` format and, unlike `gmi2map.sh`, also are subject to reflows like everything else.

Example - imagine we have this rudimentary Gemtext document in the `example.gmi` file:
```