diff options
author | EuAndreh <eu@euandre.org> | 2021-10-02 19:59:16 -0300 |
---|---|---|
committer | EuAndreh <eu@euandre.org> | 2021-10-02 19:59:16 -0300 |
commit | f7b842748f94629f15ed318924f36d0166a44e0e (patch) | |
tree | 3e2e7ede1cf3a4d04877b8ab5b8d079a0259fe57 /TODOs.md | |
parent | TODOs.md: Start DOING #td-0c4937c5-fbbd-9ec9-4a23-e71eebf18fee (diff) | |
download | git-permalink-f7b842748f94629f15ed318924f36d0166a44e0e.tar.gz git-permalink-f7b842748f94629f15ed318924f36d0166a44e0e.tar.xz |
TODOs.md: Mark #question-e7faf3ec-a40e-f35c-7380-6965942d957f as DONE
Diffstat (limited to '')
-rw-r--r-- | TODOs.md | 13 |
1 files changed, 12 insertions, 1 deletions
@@ -1106,7 +1106,18 @@ name of less requirements. # Questions -## TODO How to make the generated HTML files be more semantic? Only by writing it manually? {#question-e7faf3ec-a40e-f35c-7380-6965942d957f} +## DONE How to make the generated HTML files be more semantic? Only by writing it manually? {#question-e7faf3ec-a40e-f35c-7380-6965942d957f} +- DONE in 2021-10-02 + + Either by writing them manually, or by using tools that better translate the + markup (troff with the `man` macro package) into semantic HTML. + + Since the first class target format are manpages to be viewed after being + installed, and the HTML is derived from that, I choose not to write HTML and + generate manpages, and instead keep the current solution. + The semantic can be improved by having better tools, and in fact we would all + benefit from having alternatives to groff and pandoc. + Until then, the current HTML is all we have. - TODO in 2021-08-20 ## DONE Should I switch from pandoc to groff for generating HTML? {#question-539a1902-ed41-fc93-806a-088b6caf8134} |