Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've had a look at #1883 and fixed a bunch of formatting issues in the generated llms.txt
As expected, overlapping regex leads to multiple issues:
This should be a mode reasonable
In addition, we are not handling the double html encoding in prop tables, which is an unrelated issue:
This should be
(
\<is added by remark to avoid opening a tag)Unrelated issue - the `code` was not rendered properly from the frontmatter descrition:

Fixed, which also fixes it for llms.txt:

This PR fixes all the issue. I had a good look at the generated llms.txt, and among a large amount of improvements I don't see any new issues.
Here's a commit I made in a separate branch to compare the before and after: xl0@2f17d25
Instead of relying on regex, I worked on the remark AST for the few instances that actually required work.
I also took the liberty to get rid of the unicode replacement stuff. LLMs have no problems with unicode tokenization, and we were missing a bunch of uncode characters mainly in examples:
