If you come across something that doesn’t work pop it here

  • tb_@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    7 months ago

    Code blocks in quotes appear a little funky.

    Some line of code

    
    > Extended quote
    > ```
    More code
    

    Further extended quote

  • Voxtopass@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    6 months ago

    Furigana (a feature of Japanese text) is supported by Lemmy on the web but doesn’t work in Sync. It’s not a part of core markdown but Lemmy uses a plugin.

    Here’s an example post showing how to use it. https://programming.dev/post/530608

    Here’s what it should look like:

    And here’s Sync:

  • Risk@feddit.uk
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 months ago

    Posts are not being marked as read, unless the comments are opened.

  • cyberic@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 months ago

    Footnotes are weird? Maybe this post is weird?

    https://lemmy.world/comment/8880898

    Sync view:

    Mobile web view:

    Device information

    Sync version: v24.03.26-14:56    
    Sync flavor: googlePlay    
    
    Ultra user: true    
    View type: Slides    
    Push enabled: false    
    
    Device: d2q    
    Model: samsung SM-N975U    
    Android: 12
    
  • Stovetop@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    7 months ago

    !spoiler spoiler Test Comment

    with line breaks!<

    
    with line breaks!<```
    
    Saw this comment in the wild which does not appear correct in Sync.
    
    https://discuss.tchncs.de/comment/8334366
    
    In Sync it looks like this:
    
    ![](https://lemmy.world/pictrs/image/a660f68f-f78b-41a8-ae15-17a8cd896c3e.jpeg)
    
    On Lemmy via browser, it looks like this:
    
    ![](https://lemmy.world/pictrs/image/ed917b91-cdf6-401a-92e0-01462790b8ce.jpeg)
  • Aido@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 months ago

    Funny stuff is happening with the spoilers in this comment, they aren’t rendering as spoilers on the first two but tapping the actual spoilers removes the broken spoiler characters around the first two lines? Really strange: https://lemmy.world/comment/10822445

  • pivot_root@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 months ago

    While this isn’t strictly a markdown issue, it is slightly related. Link domain indicators are handled specially for Reddit, and they probably shouldn’t be.

    This is a link to a Lemmy post. Sync appends (lemmy.world) after it.

    This is a link to a Reddit post. Sync appends (/comments/) after it.

    This is a link to an old.reddit post. Sync appends (/comments/) after it.

    This is a link to a Lemmy profile. Sync appends (lemmy.world) after it.

    This is a link to a Reddit profile. Sync appends (u/ljdawson) after it.


    I acknowledge that there would be technical difficulties in trying to make Sync identify ActivityPub users and posts, and the current implementation of showing the domain name is good, in my opinion.

    Reddit links should probably display the Reddit domain name, however. These links are external to Sync and would open a new browser page, and it’s more informative for the user to know the domain of the link they are opening.

      • Zagorath@aussie.zone
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 months ago

        sharing it to someone without sync

        The bang syntax will work much better for anyone on Lemmy itself, regardless of which instance they’re on or which client they use, while the URL syntax is better when users want to share a link to a community off-platform.

    • Zagorath@aussie.zone
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 months ago

      I installed Sync just to test this. To me, that’s displaying with “not” superscript but not “working”. On web, it just doesn’t work at all (this is due to the markdown library lemmy-ui uses not allowing spaces).

      Suspect ~subscript will~ also not work. Curious about struck-out text.

      • Zagorath@aussie.zone
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        7 months ago

        Okay subscript didn’t work on lemmy-ui or Sync. Struck out is fine.

        How about single-word subscript? edit: yup, works in lemmy-ui, not in Sync.

    • SanguinePar@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      7 months ago

      I think a way to make them work is to add two spaces after each line. Here’s a test…

      • Line one
      • Line two
      • Line three

      Hopefully that works.

      It did :-)

      • CrayonRosary@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        7 months ago

        That’s a placebo and it’s not doing anything. Bulleted lists never need two spaces at the end of each line. You only use two spaces at the end of line that are not in bulleted or numbered lists.

        The bug is that Sync requires a blank line before you start the bulleted list. The Lemmy website doesn’t require that.

        Here is your comment with no spaces at the end of each line:

        spaces after each line. Here’s a test…

        • Line one
        • Line two
        • Line three

        See? It still works fine.

        Now here’s an example of what two spaces do.

        The first sentence below has a new line after each word but no spaces. The second sentence has two spaces and a new line after each word. The spaces force a line break to be rendered.

        This Is Not A List

        This
        Is
        Not
        A
        List

        Source of the above:

        This 
        Is 
        Not 
        A 
        List
        
        This  
        Is  
        Not  
        A  
        List
        

        This feature of markdown was implemented to prevent text from emails and such from wrapping in funny ways when pasted into a comment (or whatever). Old emails often force line breaks after 80 columns of text and it looks goofy when viewed in a modern web browser if those line breaks are kept, so they are ignored. To preserve the line breaks, you add two spaces at the end of each line. That or you might prefer to write paragraphs with a hard wrap at some column, but other people shouldn’t have to suffer that.

        Adding the two spaces to lines in a bulleted list does nothing useful, but it also doesn’t break it, so of course it works.

  • DoomBot5@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    7 months ago

    No text image links in post bodies. Usually see them in the format [](link here) don’t show up at all.