4 ms·
>There are many flavors of markdown. We'd need a standards body, compatibility suites, etc., and for all the browser vendors to adopt it. Well, if it were to b
by coldtea 4y ago
>There are many flavors of markdown. We'd need a standards body, compatibility suites, etc., and for all the browser vendors to adopt it.
Well, if it were to be adopted by vendors, the many flavors would be a non-problem. They can just agree on a flavor and be down with it. There's CommonMark anyway, they can just use that.
- seized 4y agoExcept that CommonMark has its own very annoying things. Like loose lists. Multiple lists of bullet points ends up an ugly mess with CommonMark.
- v3ss0n 4y agoCan you give me an example?
- seized 4y agoThis is in ObsidianMD, which uses CommonMark. If you have two lists separated by only new lines: https://imgur.com/IFejJvX https://imgur.com/IFejJvX They render as loose lists (note the ugly spacing that appears) regardless of the number of new lines between them: https://imgur.com/VEiAZKV https://imgur.com/VEiAZKV The workaround is adding a tab (or other character, like a braille space) between the lists, which really makes them one list: https://imgur.com/Z5WLy6w https://imgur.com/Z5WLy6w Which makes it render in a less worse way: https://imgur.com/F5lc0ek https://imgur.com/F5lc0ek This is expected behavior per CommonMark.
- Beltalowda 4y ago"I don't like this standard" is not the same as "there is no standard".
- seized 4y agoI didn't say there wasn't a standard. Just because there is a standard doesn't mean it works well. Hence the whole "more than one standard" situation...
- evolve2k 4y agoGood thing about a standard is you just bring those issues up there.
- seized 4y agoMany have. Bringing an issue up doesn't mean something gets changed....