# Markdown compatibility (with concrete example) **URL:** \ **Category:** Closed\ **Tags:** Desktop, Markdown\ **Created:** [May 23, 2025, 3:02pm UTC](https://community.anytype.io/t/markdown-compatibility-with-concrete-example/27924 "2025-05-23T15:02:57Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![flypenguin](https://community.anytype.io/user_avatar/community.anytype.io/flypenguin/32/5868_2.png) [@flypenguin](https://community.anytype.io/u/flypenguin)\ **Post date:** [May 23, 2025, 3:02pm UTC](https://community.anytype.io/t/markdown-compatibility-with-concrete-example/27924/1 "2025-05-23T15:02:58Z")
### What’s The Bug? Please improve markdown compatibility of the editor. The concrete example I have in mind is this: `Test for something (_really!!_) imporant`. Feel free to not stop there if you find other issues 😉 My reference is GitHub markdown, see screenshots. ### How To Reproduce It 1. open a page 2. write `test (_really!!_)` 3. see the wrong result See video. ### Image or Video ![github1](https://community-static.anytype.io/original/3X/f/3/f3fa227e41b9267b3b4d5374c8303e3d97af7267.png) ![github2](https://community-static.anytype.io/original/3X/e/0/e0a4e0898063ada1823ae9a18e9ae898baf036ec.png) ### The Expected Behavior See video and images. ### Device Mac Mini 2024 ### OS Sequoia 15.5 (24F74) ### Anytype Version 0.46.5 ### Network Mode AnySync ### Technical Information OS version: darwin arm64 15.5.0 App version: 0.46.5 Build number: build on 2025-05-09 13:56:27 +0000 UTC at #d0dff8b9a774bb25e57dc6aaf3e8cf0903351d69 Library version: v0.40.21 Anytype Identity: ABRAoHEP1impMW3DyMRAbELnYjV5M27h5JRecNB3KPGi6vLr Analytics ID: A8MkhLywF2qZjmjdF7NF8GwFa2shiGNZAynUfxNWv6uH5J78 Device ID: 12D3KooWQ333dNmGYeFXPeSw6NrMFLb11fnTCphnWmh5R9xfaNCR Ethereum Address: 0xFC3226BD51F6D415e9Dff876006459861E4c5fD9 ---
**Author:** ![Shampra](https://community.anytype.io/user_avatar/community.anytype.io/shampra/32/8056_2.png) [@Shampra](https://community.anytype.io/u/Shampra)\ **Post date:** [May 23, 2025, 3:24pm UTC](https://community.anytype.io/t/markdown-compatibility-with-concrete-example/27924/2 "2025-05-23T15:24:17Z")
> [@flypenguin](#): > > test (_really!!_) I don’t think it’s a bug (and modifying could cause other unwanted markdown problems). Markdown doesn’t accept bold or italic caracter inside a word. It sometimes works, but in many applications it’s also refused. With a space to mark the beginning of the word, it works very well. > #### Italic Best Practices > > Markdown applications don’t agree on how to handle underscores in the middle of a word. For compatibility, use asterisks to italicize the middle of a word for emphasis. > [Basic Syntax | Markdown Guide](https://www.markdownguide.org/basic-syntax/) > Many implementations have also restricted intraword emphasis to the `*` forms, to avoid unwanted emphasis in words containing internal underscores. (It is best practice to put these in code spans, but users often do not.) > [CommonMark Spec](https://spec.commonmark.org/0.31.2/) ---
**Author:** ![flypenguin](https://community.anytype.io/user_avatar/community.anytype.io/flypenguin/32/5868_2.png) [@flypenguin](https://community.anytype.io/u/flypenguin)\ **Post date:** [May 24, 2025, 3:14pm UTC](https://community.anytype.io/t/markdown-compatibility-with-concrete-example/27924/3 "2025-05-24T15:14:51Z")
Well, define “inside a word” … in no definition I am aware of either one of `[!()]` are part of “word characters”. Also while GitHub might have more resources than Any, it’s a pretty straightforward implementation of Markdown. Also the spec you just linked has a similar example to mine: “`Italicized text is the _cat's meow_.`” The only difference to mine is the opening parenthesis, which should behave similar on first impulse. So I would say I’m very well within the confounds of the _defined_ 😉 areas of the spec. ---
**Author:** ![Shampra](https://community.anytype.io/user_avatar/community.anytype.io/shampra/32/8056_2.png) [@Shampra](https://community.anytype.io/u/Shampra)\ **Post date:** [May 24, 2025, 3:47pm UTC](https://community.anytype.io/t/markdown-compatibility-with-concrete-example/27924/4 "2025-05-24T15:47:45Z")
For information, the regex as defined in the Anytype code considers the beginning of a markdown string as having to start with a space (or be at the beginning of a line) 😉. Not complicated to modify, I can always propose a correction (but I’m always afraid of working for nothing if it affects an internal decision). ---
**Author:** ![Razor](https://community.anytype.io/user_avatar/community.anytype.io/razor/32/28735_2.png) [@Razor](https://community.anytype.io/u/Razor)\ **Post date:** [May 24, 2025, 4:29pm UTC](https://community.anytype.io/t/markdown-compatibility-with-concrete-example/27924/5 "2025-05-24T16:29:29Z")
Merged, thanks ---
**Author:** ![flypenguin](https://community.anytype.io/user_avatar/community.anytype.io/flypenguin/32/5868_2.png) [@flypenguin](https://community.anytype.io/u/flypenguin)\ **Post date:** [May 30, 2025, 7:28am UTC](https://community.anytype.io/t/markdown-compatibility-with-concrete-example/27924/6 "2025-05-30T07:28:11Z")
> [@Shampra](#): > > I can always propose a correction I start wondering what “Bug Detectives” actually are, if you apparently can make corrections in the source … or did I get this wrong? 🤔 > [@Razor](#): > > Merged, thanks so … does that mean that correction was made and it’s fixed now? wohoo! (thanks @Shampra, i guess 🙂) so while we’re on the subject of markdown, i’d like to redirect attention again to “[whitespace behavior](https://community.anytype.io/t/markdown-replacement-whitespace-behavior/27193)” … 😬 ---
**Author:** ![Shampra](https://community.anytype.io/user_avatar/community.anytype.io/shampra/32/8056_2.png) [@Shampra](https://community.anytype.io/u/Shampra)\ **Post date:** [May 30, 2025, 8:18am UTC](https://community.anytype.io/t/markdown-compatibility-with-concrete-example/27924/7 "2025-05-30T08:18:03Z")
> [@flypenguin](#): > > I start wondering what “Bug Detectives” actually are, if you apparently can make corrections in the source … or did I get this wrong? We’re just here to help out on the forum (basic: tag bug tickets or FRs, and more if affinity ^^). But the source code is open and anyone can participate (with quite a few limitations, unfortunately). So if I can help with debugging AND fixing, that’s one problem less :). > [@flypenguin](#): > > thanks @Shampra 😊 > [@flypenguin](#): > > so while we’re on the subject of markdown, i’d like to redirect attention again to “[whitespace behavior](https://community.anytype.io/t/markdown-replacement-whitespace-behavior/27193)” 😅 Helping out requires a lot of free time (and inevitably, I’m less efficient than the team on their code). And of course it’s very dependent on my motivation, which, as I’ve already mentioned, is currently in serious decline. I’ll save the post for later 😉 ---
**Author:** ![flypenguin](https://community.anytype.io/user_avatar/community.anytype.io/flypenguin/32/5868_2.png) [@flypenguin](https://community.anytype.io/u/flypenguin)\ **Post date:** [May 30, 2025, 8:49am UTC](https://community.anytype.io/t/markdown-compatibility-with-concrete-example/27924/8 "2025-05-30T08:49:03Z")
> [@Shampra](#): > > But the source code is open and anyone can participate aaaaah let’s not go there please 😆 – [been there](https://community.anytype.io/t/thoughts-on-a-development-specific-engagement/25406/23), won’t change my mind 😉 > [@Shampra](#): > > Helping out requires a lot of free time (and inevitably, I’m less efficient than the team on their code). … and this should not be your responsibility. that was, in fact, directed rather more at @Razor … . sorry if that was unclear 🙂