Skip to main content
5 events
when toggle format what by license comment
Sep 13, 2020 at 21:25 comment added Sonic the Anonymous Hedgehog @BenKelly I just read further into that post, and it seems like the plan wasn't to remove language entirely, but to remove its support only for four-space indent code blocks and retain it for HTML <pre><code> blocks. I think that may be too technically difficult to implement, so I think the best solution would be to retain it as is. (It seems to me that Ham intended to remove it entirely at that time, but ran into issues with it, so he simply marked it as "deprecated, subject to removal" instead.)
Sep 11, 2020 at 17:33 comment added Ben Kelly StaffMod I should have specified: There is at this time no plan to completely remove either language or language-all. One or both could possibly be removed in the future (with language potentially going first since there's a real, widely accepted alternative). If we do decide to do this in the future, then we'll broadcast the change ahead of time in order to gather feedback from the community.
Sep 11, 2020 at 17:17 comment added Sonic the Anonymous Hedgehog @BenKelly To be clear, language-all would continue to be supported; only language had been deprecated. As you say, there isn't a good replacement for language-all, but code fence hints exist as the preferred alternative to language today.
Sep 11, 2020 at 14:10 comment added Ben Kelly StaffMod At this moment, there is no plan to completely remove support for the language comment syntax. If this were to change, we'd make an announcement on meta first. As much as I am not a fan of the syntax, we don't have a good replacement for language-all in commonmark or our supported extended syntax. I've not changed anything in the implementation for the highlightjs switch, so any issues are to be considered bugs. (I see the one you reported above, thanks for reporting!)
Sep 11, 2020 at 6:03 history answered Sonic the Anonymous Hedgehog CC BY-SA 4.0