From acadf9d6b407f9948b6c3e4937e7ba6b3b997a76 Mon Sep 17 00:00:00 2001 From: Midgard Date: Sun, 20 Jun 2021 23:08:07 +0200 Subject: [PATCH] Tabs don't work at all for alignment I had forgotten this fact when I wrote the old version of this paragraph. --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 13ff970..9389d6e 100644 --- a/README.md +++ b/README.md @@ -8,10 +8,10 @@ repository](https://git.zeus.gent/haldis/haldis/-/tree/master/etc). For VSCode t in the standard repository. ## Indentation -Indentation at the beginning of the line requires hard **tabs**. Spaces will not work. +Indentation at the beginning of the line requires hard **tabs** (spaces will not work). -For alignment (putting things in the same column between lines) spaces are allowed. Example (`↦` -for tab and `·` for space): +For alignment (putting things in the same column between lines) **spaces** are required (tabs will +not work). Example (`↦` for tab and `·` for space): ``` dish·fries:·Frietjes ↦ single_choice size:·Formaat @@ -101,14 +101,14 @@ dish dishid: Name -- This is a description € 3 **Note:** Only the `{no_text}` tag is supported at this moment. You can ignore other tags for now. -You can add tags after ` :: `. Tags are `{identifier}`. You can use tags to attach more information +You can add tags after ` `. Tags are `{identifier}`. You can use tags to attach more information about a dish or option in a structured way. For example: `{has_meat}` signals to vegetarians that they should avoid this. The order is always id, name, description, tags, price (not all have to be present of course). ```hlds -dish dishid: Name -- This is a description :: {has_meat} € 3 +dish dishid: Name -- This is a description {has_meat} € 3 ``` The `{no_text}` tag signals that an option is not to be shown in a dish's description. This is