Adding an indent (+) after a Autonumbered Headings (#) should not be require to keep the text properly formatted in the wiki syntax

• Usability
• Dogfood on a *.tiki.org site

In the wiki syntax the following code

# Status on ((TikiFest Virtual 2021 Summer Workshops)) - May shift to longer second hour topic
#   [https://tiki.org/forumthread77173-Translation-for-tiki-site-close-page-tiki-error_simple-php|Tiki simple-error (site closed)] translation dilemma
When closing a Tiki website we gave the option for the admin to edit the message. It sound like a good thing BUT on the other hand translation of the rest of the page may be impossible and if the admin of a french Tiki insert a french message the final screen for the end-user will look badly done. (half english and half french)
* Is it important to solve this
* Is it possible to avoid english/hardcoded strings (so the Admin wrote everything he want)
* ...
# Is there a delay between what we see at Gitlab and the reality see: https://tiki.org/forumthread77159-How-reliable-is-gitlab-informations

Will produce this (the not expected result):

1. Status on TikiFest Virtual 2021 Summer Workshops - May shift to longer second hour topic
2. Tiki simple-error (site closed) translation dilemma

When closing a Tiki website we gave the option for the admin to edit the message. It sound like a good thing BUT on the other hand translation of the rest of the page may be impossible and if the admin of a french Tiki insert a french message the final screen for the end-user will look badly done. (half english and half french)

• Is it important to solve this
• Is it possible to avoid english/hardcoded strings (so the Admin wrote everything he want)
• ...

1. Is there a delay between what we see at Gitlab and the reality see: https://tiki.org/forumthread77159-How-reliable-is-gitlab-informations

This is bad as it is breaking the page format and the heading numbering system.
To prevent this I have to add indent for each block between a line feed (+) and so this code:

# Status on ((TikiFest Virtual 2021 Summer Workshops)) - May shift to longer second hour topic
#   [https://tiki.org/forumthread77173-Translation-for-tiki-site-close-page-tiki-error_simple-php|Tiki simple-error (site closed)] translation dilemma
+When closing a Tiki website we gave the option for the admin to edit the message. It sound like a good thing BUT on the other hand translation of the rest of the page may be impossible and if the admin of a french Tiki insert a french message the final screen for the end-user will look badly done. (half english and half french)
+* Is it important to solve this
+* Is it possible to avoid english/hardcoded strings (so the Admin wrote everything he want)
+* ...
# Is there a delay between what we see at Gitlab and the reality see: https://tiki.org/forumthread77159-How-reliable-is-gitlab-informations

Will produce this (the wanted result):

1. Status on TikiFest Virtual 2021 Summer Workshops - May shift to longer second hour topic
2. Tiki simple-error (site closed) translation dilemma
   When closing a Tiki website we gave the option for the admin to edit the message. It sound like a good thing BUT on the other hand translation of the rest of the page may be impossible and if the admin of a french Tiki insert a french message the final screen for the end-user will look badly done. (half english and half french)
   * Is it important to solve this
   * Is it possible to avoid english/hardcoded strings (so the Admin wrote everything he want)
   * ...
3. Is there a delay between what we see at Gitlab and the reality see: https://tiki.org/forumthread77159-How-reliable-is-gitlab-informations

That is pretty dumb in 2021 and as long as I’m between 2 heading Tiki should understand it has to indent the text accordingly.

This bug has been demonstrated on show2.tiki.org

Please demonstrate your bug on show2.tiki.org

This bug has been demonstrated on show.tikiwiki.org

Please demonstrate your bug on show.tikiwiki.org