Skip to content

FAQ/TODO/KNOWN_BUGS: convert to markdown #19875

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
bagder wants to merge 5 commits into from
Closed

FAQ/TODO/KNOWN_BUGS: convert to markdown #19875

bagder wants to merge 5 commits into from

Conversation

@bagder
Copy link
Member

@bagder bagder commented Dec 8, 2025 •
edited
Loading

  • convert the FAQ, KNOWN_BUGS and TODO to markdown
  • auto-generate the TOCs on the website, remove them from the docs
  • cleanups
  • spellchecked
  • updated links

@github-actions github-actions bot added the CI Continuous Integration label Dec 8, 2025
@bagder bagder marked this pull request as ready for review December 8, 2025 13:40
@bagder bagder force-pushed the bagder/more-markdown branch from 32f1a7c to 59a38c3 Compare December 8, 2025 21:20
@bagder bagder changed the title docs: more markdown FAQ/TODO/KNOWN_BUGS: convert to markdown Dec 8, 2025
@bagder bagder mentioned this pull request Dec 8, 2025
Closed
@bagder
Copy link
Member Author

bagder commented Dec 8, 2025

The known bugs TOC currently rendered with my WIP script for the site.

Screenshot 2025-12-09 at 00-12-25 curl - Known Bugs

jhauga
jhauga reviewed Dec 9, 2025
View reviewed changes
jhauga
jhauga reviewed Dec 9, 2025
View reviewed changes
jhauga
jhauga reviewed Dec 9, 2025
View reviewed changes
jhauga
jhauga reviewed Dec 9, 2025
View reviewed changes
jhauga
jhauga reviewed Dec 9, 2025
View reviewed changes
jhauga
jhauga reviewed Dec 9, 2025
View reviewed changes
docs/TODO.md
The existing support for the `--ciphers` option could be extended by mapping
the OpenSSL/GnuTLS cipher suites to the Schannel APIs, see [Specifying
Schannel Ciphers and Cipher
Strengths](https://learn.microsoft.com/windows/win32/secauthn/specifying-schannel-ciphers-and-cipher-strengths).
Copy link
Contributor

@jhauga jhauga Dec 9, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was changed.
Edit: the redirect works now, but below is redirect to link.

Suggested change
Strengths](https://learn.microsoft.com/windows/win32/secauthn/specifying-schannel-ciphers-and-cipher-strengths).
Strengths](https://learn.microsoft.com/en-us/windows/win32/secauthn/specifying-schannel-ciphers-and-cipher-strengths).

Copy link
Member Author

@bagder bagder Dec 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

isn't that a decision for the site + browser? en-us in the link might suggest other users could get other choices?

jhauga
jhauga reviewed Dec 9, 2025
View reviewed changes
@bagder
FAQ/TODO/KNOWN_BUGS: convert to markdown
8db7f54 
Also somewhat cleaned up and spellchecked.

No TOC in the files. It is generated and prepended on the web version.
@bagder bagder force-pushed the bagder/more-markdown branch from d02d4a6 to 8db7f54 Compare December 9, 2025 07:15
@bagder bagder closed this in 3dd1ffd Dec 9, 2025
@bagder bagder deleted the bagder/more-markdown branch December 9, 2025 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@jhauga jhauga jhauga left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

CI Continuous Integration documentation

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@bagder @jhauga