On 2020-01-19 21:56, Mark Rotteveel wrote:
On 2020-01-19 19:32, Alex Peshkoff via Firebird-devel wrote:
On 2020-01-19 18:58, Adriano dos Santos Fernandes wrote:
- A technical documentation does not need anything more than
markdown offers. Markdown sources are good directly and with tools
help may be used to produce docs in others formats (pdf, html).
Adriano, do you know (I've failed to find something working in
standard at https://www.markdownguide.org/) how to have links inside a
document? I use them in html docs.
[link-text](uri), where uri can be just a local reference
(#section-id). However, there doesn't seem to be a standarized way of
generating a section id. But pandoc and GitHub-flavoured markdown both
apply (almost) the same rules: lowercase the section name, replace
space with `-`, and non-alphanumeric characters are removed (though
pandoc preserves `.` as well, while GitHub does not).
Great - that works! After using described by you conversion rules.
However, if you are in a bind, you could always add an anchor yourself
(eg using <a name="section-id"></a>), but that is a workaround at best.
What are you using, that what works on GitHub is not good enough?
I've tried to write section names 'as is'. That was a reason.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
