Given that Jebora has markdown support, just throwing a few bits in here…

bold and italic

  • li item 1
  • li item 2

Quote

heading

link

inline code

Code block

// Not trying xss just doing examples
alert("example")

strike

sub

up

  • Farid@lemmy.worldEnglish
    32·
    1 year ago

    On Connect, sub and up (which, I assume, was supposed to say sup) don’t get formatted.

  • tal@kbin.social
    20·
    1 year ago

    One thing I’ve never been enthusiastic about has been Markdown’s auto-renumbering support. I have never seen someone really being happy with the implementation and lots of people frustrated as they try to embed numbered items and get them renumbered.

    1. First

1. Second

    Yields:

    1. First

    2. Second

    Usually came up on Reddit when someone wants to quote a single item in a numbered list from some external text, quotes only that, and it gets renumbered…and they don’t know how to backslash-escape the period to avoid the thing:

    1\. First

1\. Second

    Yields:

    1. First

    2. Second

    It looks like kbin also does the auto-renumbering. Dunno about lemmy. Kind of the one element of Markdown that I’d be happy to see die. I don’t mind having a syntax for auto-numbered lists – I just don’t think that using an actual number as prefix to indicate that that should happen is a reasonable way to go about it.

    • shroomato@lemmy.worldEnglish
      6·
      1 year ago

      Markdown is pretty ‘dumb’ in that it simply uses regular expressions to detect markdown tags/structures and then translates them into corresponding html elements. So when it sees subsequent lines each starting with a ‘{number}{dot}{space}’ it determines that it’s supposed to be a numbered list, so it translates that to an html ordered list. The numbers in an ordered list are not there if you look at a page source, they’re only being rendered by your browser starting with ‘1’ by default.

      With all that being said, HTML5 supports overriding default values in an ordered list, so with additional logic in the markdown parser having numbers out of order could be done.

  • chaorace@lemmy.sdf.orgEnglish
    14·
    1 year ago

    For anyone interested, here’s the Lemmy markdown configuration. As you can see, Lemmy’s website UI supports the full commonmark spec (tutorial / official spec), plus a bunch of extensions. I don’t think anyone’s fully documented these yet, so I’ll try doing so below. Apologies in advance to mobile users, this is probably gonna get ugly (see included image links for how it should look):

    • URL autolinking (plaintext URLs automatically turn into links)
    • Lemmy autolinking:
      • NOTE: No link will be inserted if the viewer is browsing an instance where the resource is not yet known/blocked
      • Communities: !fediverse@lemmy.ml→!fediverse@lemmy.ml (link ref: /c/fediverse@lemmy.ml)
      • Users: /u/chaorace@lemmy.sdf.org→ /u/chaorace@lemmy.sdf.org (link ref: /u/chaorace@lemmy.sdf.org)
    • Typography substitutions:
      • (c)→©
      • (tm)→™
      • (r)→®
      • +-→±
      • ...→…
      • ---→—
      • --→–
      • ???? (>= 4x)→???
      • !!!! (>= 4x)→!!!
    • Github-flavor Markdown extensions:
    • Subscript/Superscript:
      • Sub: example~sub~→examplesub (image)
      • Super: example^super^→examplesuper (image)
    • Footnotes:
      • Inline part: example[^notename]→example[1] (image)
      • Bottom part: [^notename]: Note text→(see bottom of post) (image)
        • Important: the bottom part must be at the very end of the post, otherwise both halves of the footnote will break!
    • Ruby Text: {example base text|example ruby text}→example base textexample ruby text (image)
      • “Ruby” is an html-ism for special pronunciation aids which frequently appear within young person’s media where the language includes non-phonetic characters (e.g.: Chinese characters)
      • Japanese Furigana example: {凄|すご}い！→凄すごい！(image)
    • Spoilers:
      ::: spoiler visible part example
hidden part example
:::
    • Image/Video embedding: ![accessibility alt-text example](https://i.imgur.com/9nVMRqa.jpeg) => accessibility alt-text example (image)

    1. Note text ↩︎

    • oohgodyeah@lemmy.worldEnglish
      2·
      1 year ago

      Your hyperlink to the Official Spec doesn’t work for me on Vger. It launches my web browser without a URL and hiding down on the link doesn’t reveal its destination.

    • Orphie Baby@lemmy.worldEnglish
      2·
      1 year ago

      I think this should be put on a page someone on Lemmy. Somewhere that’s easy to find. The tables and stuff too.

  • Mythril@lemm.eeEnglish
    10·
    1 year ago

    That reminds me of the threads/comments about the spoiler tagging in Lemmy being broken in many apps, hopefully that’ll be worked out sooner than later.

    This is a spoiler

    Magneto kills Dumbledore in Mordor

    Just tested and it doesn’t seem to work in neither Connect, Voyager/wefwef, Liftoff nor even in Jerboa… Only worked in the Lemmy PWA.

    • Xylight (Photon dev)@lemmy.xylight.devEnglish
      5·
      1 year ago

      I don’t believe spoilers are part of the official markdown specification. Even if markdown parsers supported it, I’d assume it would be ||this is a message||

      • Mythril@lemm.eeEnglish
        3·
        1 year ago

        Yeah I guess the apps are just using regular markdown libraries so they haven’t added any “Lemmy extras” to the parsing.

  • breadsmasher@lemmy.worldEnglish
    4·
    1 year ago

    sub should have two ~

    sub

    I guess up should have two ^ as well?

    ^up^

    ^^ doesnt seem to do anything

    Memmy seems to have slightly different markdown rendering

    • Scaldart@lemmy.worldEnglish
      3·
      1 year ago

      The only two things formatting makdown consistently, for now, are Jerboa and the web interfaces.

      I’ve been posting a lot of poetry using some markdown witchery to format, only to realize that some interfaces show all of the markdown even inside the post itself. Jerboa will show it in the summary tile before you click in, but it does format.

  • tal@kbin.social
    4·
    1 year ago

    Kbin’s implementation differs from Reddit’s in at least one way that I’ve run into: Reddit permitted a link to be italicized using asterisks inside the link. Like:

    I read a [book called *Arabian Nights*](https://en.wikipedia.org/wiki/One_Thousand_and_One_Nights).

    Valid in Reddit Markdown, but in kbin’s Markdown – dunno what lemmy does – that’s not permitted, and gives this:

    I read a book called .

    You can do:

    I read a book called *[Arabian Nights](https://en.wikipedia.org/wiki/One_Thousand_and_One_Nights)*.

    Which yields this:

    I read a book called Arabian Nights.