From: Paul Hänsch
Date: Thu, 18 Dec 2025 06:30:34 +0000 (+0100)
Subject: correct tests for aria-label anchors
X-Git-Url: http://git.plutz.net/?a=commitdiff_plain;h=686647c3f1bb23a894d5a333a86376bb9b8cae40;p=cgilite
correct tests for aria-label anchors
---
diff --git a/tests-markdown.sh b/tests-markdown.sh
index 3e033dd..bee2e37 100755
--- a/tests-markdown.sh
+++ b/tests-markdown.sh
@@ -219,45 +219,45 @@ assert '{tv ard function-check}' \
# Headings
assert 'Heading first Order
============' \
-'Heading first Order
+'' \
'Heading h1'
assert 'Heading first Order {.foo #bar}
============' \
-'Heading first Order
+'' \
'Heading h1 + attributes'
assert 'Heading second Order
------------' \
-'Heading second Order
+'' \
'Heading h2'
assert 'Heading second Order {.foo #bar}
------------' \
-'Heading second Order
+'' \
'Heading h2 + attributes'
assert '#### Heading four' \
-'Heading four
+'' \
'Heading arbitrary'
assert '###Heading three ######' \
-'Heading three
+'' \
'Heading arbitrary'
assert '### Heading three ## {foo bar}' \
-'Heading three
+'' \
'Heading arbitrary + attributes'
assert '# Heading \# # {foo bar}' \
-'Heading #
+'' \
'Heading arbitrary + attributes'
@@ -395,11 +395,11 @@ sub bar
##sub2 bar {x}
' \
-'bar
-sub2 bar
+'' \
'Headline Nesting'
@@ -532,8 +532,8 @@ Markdown.awk can run in GNU awk (`gawk`) and in Busybox awk. It is _not_ fully P
Tests
-----
[Link with Title](https://en.wikipedia.org/wiki/Markdown "Markdown in Wikipedia"), *emphasis*, **strong**, **strong containing *emphasis***, `inline code`, `` code with `backticks` ``. See more tests [here](./tests/).' \
-'Markdown.awk
-Supported Features / TODO:
+'Markdown.awk
+Supported Features / TODO:
-Basic Markdown - Block elements:
+Basic Markdown - Block elements:
Basic Markdown - Inline elements:
+Basic Markdown - Inline elements:
NOTE: Set the environment variable MD_HTML=true to enable verbatim HTML
-Extensions - Block elements:
+Extensions - Block elements:
-Extensions - Inline elements:
+Extensions - Inline elements:
-Compatibility
Markdown.awk can run in GNU awk (gawk) and in Busybox awk. It is not fully POSIX compliant and does not run in mawk or nawk. In particular it makes heavy use of the gensub() function and its ability to use paranthesized subexpressions in the replacement text. This feature is not available in the POSIX specified sub() and gsub() functions. Hence it cannot be replaced without effort.
-Tests
Link with Title, emphasis, strong, strong containing emphasis, inline code, code with `backticks`. See more tests here.
' \
'Full Page (cgilite markdown)'
@@ -718,15 +718,15 @@ Term 2
1. first list item
2. second list item' \
-'Headline First Order
-Headline Second Order
+'Headline First Order
+Headline Second Order
Code Block
with indentation
-Blockquote
+Blockquote
like in an email
-Headline 3rd order
+Headline 3rd order
@@ -1017,7 +1017,7 @@ How to write:
- [Macros](dev-macros/)
- [Handlers](dev-handlers/)
- [Parsers](dev-parsers/)' \
-'Shellwiki
+'Shellwiki
Shellwiki is a Wiki and Content Management System with minimal dependencies. It can run on embedded devices, as well as full size web servers. Its goals are:
easy deployment
@@ -1054,7 +1054,7 @@ interface. It aims to be secure and predictable. Extensions can
be written and modified by system administrators.
-toc 2 2Features
+toc 2 2Features
Markdown Wiki Syntax
@@ -1149,7 +1149,7 @@ visitors into handling GDPR "consent" forms.
-Dependencies
Shellwiki is based on cgilite, which is included in the installation. It is written in posix compliant shell script, and the markdown renderer is written in posix compliant AWK. The entire wiki system can run with nothing more than a busybox. In fact it can be served from the rescue shell in a Debian initrd, or from an OpenWRT router.
Its precise requirements are:
@@ -1172,7 +1172,7 @@ visitors into handling GDPR "consent" forms.
Optional: Sendmail for sending password reminders, etc.
-Installation
Also see → installation/
You can try out shellwiki right now using busybox:
@@ -1181,10 +1181,10 @@ visitors into handling GDPR "consent" forms.
~$ _DATA=~/wikidata busybox nc -llp 1080 -e ~/shellwiki/index.cgi
For additional examples, regarding permanent installation and configuration in webservers see installation/.
-Syntax
The wiki syntax is based on John Grubers Markdown with extensions borrowed from Pandoc and PHP Markdown Extra. The Markdown parser is provided by Cgilite and its full documentation can be looked at here.
-include --nolink /[wiki]/editorhelp/Macros
+include --nolink /[wiki]/editorhelp/Macros
Also see → macros/
In addition to the Markdown syntax, wiki pages can include Macros, which perform additional functions on a page, like generating an image gallery, including parts of other pages, etc. Macros make Shellwiki truly dynamic and flexible.
@@ -1196,14 +1196,14 @@ visitors into handling GDPR "consent" forms.
Macros are the most easy to write type of extension. See Macros for a full list of available macros.
-Themes
Also see → theming/
While Shellwiki supports plugins for theming, it's apearance can mostly be configured by the user. Pages can be configured to use custom CSS files. In addition page headers and footers are themselves wiki pages which can be modified to add menus, custom logos, links, etc. The same goes for error pages.
For an example, see the technical pages for this wiki.
-Multiple Languages
To enable a multilingual setup you must set a default language in your configuration environment:
export LANGUAGE_DEFAULT=en
@@ -1215,12 +1215,12 @@ visitors into handling GDPR "consent" forms.
Header, footer, and error pages will be included from their respective language version, as will all macro includes, etc. Should a page not exist in a given language, the default page will be displayed instead. However, included elements will still be taken from the respective language version, possibly mixing languages between the selected user language and the default.
-Constraints of the current implementation
+Constraints of the current implementation
- There can be only one default language, with no priority of different fallback languages
- Page URLs can currently not be translated. Doing so would require a model for manually assigning translated page names and would not be trivial to use.
-Developer Documentation
+Developer Documentation
How to write: