You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get we need to be careful about how we write Github markdown and respect the standard.
We can't expect to dump a bunch of crufty crap in a file and expect it to render properly but this is a bit much.
Code blocks don't work (especially when combined with bullets and/or tasks) unless everything is perfectly vertically aligned AND there are no trailing spaces.
I've read the other issues on this topic which is how I know about the alignment peculiarity but I found the trailing spaces thing on my own.
I've been over this text ten times at least (see image below) re-aligning this and remove all the stray space characters and have been able to make some progress but the rendering engine loses its way towards bottom of the file and kind of gives up.
I too work for a software company and have written ~150 help articles and am the editor for what others write (in Gitbook BTW). I'm not some lost lost markdown newbie.
Can we please get some attention on what (according to the issues in this repo) is a long-standing issue?
Just really looking for some consistency so we can at least find our own way through it.
The text was updated successfully, but these errors were encountered:
I get we need to be careful about how we write Github markdown and respect the standard.
We can't expect to dump a bunch of crufty crap in a file and expect it to render properly but this is a bit much.
Code blocks don't work (especially when combined with bullets and/or tasks) unless everything is perfectly vertically aligned AND there are no trailing spaces.
I've read the other issues on this topic which is how I know about the alignment peculiarity but I found the trailing spaces thing on my own.
This is beyond finicky. The [*Writing Code Blocks* reference](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks) makes no mention of either alignment or trailing spaces.
I've been over this text ten times at least (see image below) re-aligning this and remove all the stray space characters and have been able to make some progress but the rendering engine loses its way towards bottom of the file and kind of gives up.
URL: NetScr1be/XRPLLabs.Bluesky#1
I'd be happy to attach a copy of the file for review if the [documentation on attachments[(https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/attaching-files) agreed with what we are seeing here.
I too work for a software company and have written ~150 help articles and am the editor for what others write (in Gitbook BTW). I'm not some lost lost markdown newbie.
Can we please get some attention on what (according to the issues in this repo) is a long-standing issue?
Just really looking for some consistency so we can at least find our own way through it.
The text was updated successfully, but these errors were encountered: