Inline blocks of code (snippets) no longer formattable via keyboard (Markdown backticks) with certain keyboard layouts

[vancromy]

According to MS teams documentation, inline code snippets can be written by enclosing the code with single backticks as is usually done in markdown. This is an example of that implementation.

Multiline code snippets do however still work as can be seen in the attached video below.

The keystrokes I pressed in the following video to try and write an inline code snippet was [backtick]my code[backtick][space]

In my current version of Teams this does not work (see: https://github.com/MicrosoftDocs/msteams-docs/assets/59556820/8b90f413-9adf-466d-9df6-b596bc2d7d4c).

Teams version: You have Microsoft Teams Version 1.6.00.17554. It was last updated on 31/07/2023. OS Info: macOS 13.4.1 (c) (22F770820d)

EDIT: It seems someone opened a FR for this around the same time I opened this issue. Feel free to upvote that one too: https://feedbackportal.microsoft.com/feedback/idea/965f520a-e40c-ee11-a81c-000d3a7a48db

[ObliviousMonkey]

Hello, for anyone finding this and using an international keyboard (US Intl in my case) with the dead-keys effect (used for accent and stuff)...

I just found that using Option+Shift+[backtick] (or ALT+Shift+[backtick]) will produce a [backtick] directly without the dead-key effect, and thus works with the inline code formatting functionality. No need to remap to a different layout or install any additional software.

Note that this still does not work for AZERTY French keyboard.

It has been literal months since you broke it, why is it still not fixed, forcing international (understand: "non-English") users to resort to third-parties keyboard modifiers as workarounds??

@Meghana-MSFT @Nivedipa-MSFT

[manuelseromenho]

I have the same issue in Ubuntu 22.04 with Chrome Version 120.0.6099.216 (Official Build) (64-bit) I'm using a PT-PT keyboard, with PT Layout:

Like a month ago it was working, not sure if this is related to Chrome version, or MS Teams Web App version.

Since MS Teams it's used a lot in my team, this it's frustrating for a lot of people.

@Meghana-MSFT @Nivedipa-MSFT

[MCHalbi]

Workaround for people using the Neo 2 keyboard layout: On layer 3 there is the 'direct backtick' (on the 'z' key).

Writing two backticks and then jumping back between them and writing inline code does not work for me this way though.

[mateusfccp]

Hello, for anyone finding this and using an international keyboard (US Intl in my case) with the dead-keys effect (used for accent and stuff)...

I just found that using Option+Shift+[backtick] (or ALT+Shift+[backtick]) will produce a [backtick] directly without the dead-key effect, and thus works with the inline code formatting functionality. No need to remap to a different layout or install any additional software.

Adding to this, I just found that you only need to do it in the closing end.

For instance, you can type "`" normally at the start (Backtick+Space, for me), type whatever you want and then the workaround (Option+Shift+Backtick) to end.

P.s. This exact bug with the exact same workaround also happens in Microsoft Loop 🤡

[black-snow]

As funny as it sounds - this is a major issue for me. I use inline code blocks a lot.

Fresh macOS setup w/ Teams for work, German qwertz layout. Triple backticks seem to work just fine (even though I need to hit space twice afterwards - I think it was just once on my Windows machine), so what's so different about single backticks? :/

[straurob]

I can confirm that this behavior is reproducible on my system running:

• MacOS Sonoma 14.2.1
• MS Teams 1.6.00.35956
• German QWERTZ layout

[TobiasVonEssenQED]

@straurob Yep, same for me.

• MacOS Sonoma 14.2.1
• MS Teams (work or school) version 24004.1302.2612.7086
• German QWERTZ layout

[cromagnoli]

The modifier key + back tick hack doesn't work on a Spanish QWERTY keyboard, while it does on a Latin-american layout.

MacOS Ventura 13.4 MS Teams (work or school) version 24004.1302.2612.7086 Spanish QWERTY layout

[Pierre-HenriLemp]

I can confirm that inline code feature seem to not work properly. The easy way to reproduce one issue is to put firstly the two back tick and then inside put any text/code. This will never work.

I would not expect that Teams is not able to handle the first case scenario.

This is currently impossible.

---

Tested on Microsoft Teams version 23335.232.2637.4844 Windows 10 : 19045.3930

[NicoAdrian]

Can confirm it still doesn't work on Teams Version 24004.1304.2655.7488 on macOS Ventura 13.6.3. I'm using the Microsoft Teams "New"

[makulatur]

Doesn't work here on a German keyboard with:

You have Microsoft Teams version 23285.3809.2525.961. You've got the latest version. It was last updated on 20/11/2023. The client version is 50/24010419119.

MacOS 14.0 (23A344)

[feilchenfeldt]

Same here on MacOS Ventura 13.6.4 (22G513) with Microsoft Teams (work or school) 24004.1304 and US International keyboard. Inline single backticks `Code` do not display as Code

[dominikfeininger]

Same here on MacOS 14.3.1 with Microsoft Teams (24004.1304.2655.7488) and German keyboard. Inline single backticks Code do not display as Code

[cyberw]

Hi @Meghana-MSFT and @Nivedipa-MSFT , any chance someone can take a look at this?

[kolbasa]

Same problem here. Would be nice if someone looked at this.

[tayalnishu]

Same issue with MacOS 14.3.1 and MS Teams(24004.1304), never got it to work. Would be nice to get it fixed.

[maehne]

I observe the same issue when using the Teams PWA in Chromium on Linux with a Swiss keyboard layout. Interestingly, it is working correctly in Firefox.

[cyberw]

It is broken pretty much everywhere except with US keyboard layout and microsoft is ignoring it entirely. Maybe they will listen if more people use the escalation form: https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR7iCOpS5_b9Nqmwx43u5rtZUN0dNSTA4WVo2S05JQ1M4TVlYMjROSjhURS4u

[antonio-rodrigues]

MacOS, Microsoft Team (New), Portuguese keyboard layout. Not working for a very long time. Filled the escalation form, thanks for sharing 👌

[ChetanSharma-msft]

It is broken pretty much everywhere except with US keyboard layout and microsoft is ignoring it entirely. Maybe they will listen if more people use the escalation form: https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR7iCOpS5_b9Nqmwx43u5rtZUN0dNSTA4WVo2S05JQ1M4TVlYMjROSjhURS4u

Hello @Everyone, Engineering team has suggested the below: In Windows, on a German keyboard, this works fine using the [SHIFT] + [+] followed by [SPACE] key.

This seems localized specifically to the Mac behavior. A workaround for Mac can be to just use the UI toolbar:

Also, rather than escalating it multiple times, I would suggest you raise your request here: Teams Feedback Portal.

We will also inform engineering team on this.

[vancromy]

It is broken pretty much everywhere except with US keyboard layout and microsoft is ignoring it entirely. Maybe they will listen if more people use the escalation form: https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR7iCOpS5_b9Nqmwx43u5rtZUN0dNSTA4WVo2S05JQ1M4TVlYMjROSjhURS4u

Hello @everyone, Engineering team has suggested the below: In Windows, on a German keyboard, this works fine using the [SHIFT] + [+] followed by [SPACE] key.

This seems localized specifically to the Mac behavior. A workaround for Mac can be to just use the UI toolbar:

Also, rather than escalating it multiple times, I would suggest you raise your request here: Teams Feedback Portal.

We will also inform engineering team on this.

Hi @ChetanSharma-msft,

I don't believe you have properly read through this thread. This was a feature that used to work and no longer works. As such it is a bug. I'm happy to fill out a feature request if that is what it takes to fix it though.

It is also NOT a Mac specific behaviour as has been commented multiple times. Its related to the diacritical marks created by international keyboard structures and as such is impacted on all versions of Teams (mobile, web, and all OS).

The workaround provided by the engineering team does not fix this issue which is to use inline typing/shortcuts to write code in a message. If I wanted to click myself around Teams all day I would not have opened this issue...

Providing specific keyboard structure solutions is also not a very sustainable and long term solution. Should the whole world migrate to either a US or German keyboard just because the engineering team does not fix this issue?

I hope this is something the MSTeams team will start prioritising. It has many upvotes, is the most commented issue on this repo and has been open for more than 7 months now and with the problem well documented by @danielsitnik within the first week of it being open...

EDIT: It seems someone opened a FR for this around the same time I opened this issue. Feel free to upvote that one too: https://feedbackportal.microsoft.com/feedback/idea/965f520a-e40c-ee11-a81c-000d3a7a48db

[black-snow]

Hitting Shift and + will produce * ... how does this address the issue?

[ChetanSharma-msft]

Hello @vancromy & All - I have escalated this issue with Engineering team and let you know the updates if any.

[Chealer]

Hello @vancromy & All - I have escalated this issue with Engineering team and let you know the updates if any.

How high did you "escalate" this issue? You wrote the same on 2023-10-06, yet here we are 5 months later.

[Chealer]

[...]

Hi @ChetanSharma-msft,

[...]

The workaround provided by the engineering team does not fix this issue which is to use inline typing/shortcuts to write code in a message. If I wanted to click myself around Teams all day I would not have opened this issue...

I recommend retitling this ticket more accurately, with something like "Inline block of code (snippets) no longer formattable via keyboard (Markdown `backticks`)".

[...] I hope this is something the MSTeams team will start prioritising. It has many upvotes, is the most commented issue on this repo and has been open for more than 7 months now and with the problem well documented by @danielsitnik within the first week of it being open...

@danielsitnik confirmed the issue, but I would not say he documented the problem well. To my knowledge, this issue's reproduction conditions remain largely undetermined, which must be the main reason why Microsoft is struggling so much with it.

[vancromy]

@Chealer I beg to differ. It has been documented several times and I have also provided clear reproduction conditions for both Mac and Windows. There should be no reason why Microsoft cannot reproduce this. It is simply a matter of changing keyboard layout to a keyboard with diacritical marks and you will notice that inline code snippets no longer work.

[maehne]

I observe the same issue when using the Teams PWA in Chromium on Linux with a Swiss keyboard layout. Interestingly, it is working correctly in Firefox.

[danielsitnik]

@Chealer I beg to differ too. I was the one who spotted the problem being keyboards with diacritical marks and I provided enough evidence (video + text) on my Aug/11 comment for anyone to be able to reproduce it. Therefore I do not agree that "reproduction conditions remain largely undetermined".

This is further confirmed by the numerous comments that came after that from people all over the world describing the same problem with their specific language/keyboard configurations.

This is a feature that "just worked" in the past, therefore this is a bug and there's no excuse for MSFT to leave it like this for 7 months.

[Chealer]

@Chealer I beg to differ. It has been documented several times and I have also provided clear reproduction conditions for both Mac and Windows. There should be no reason why Microsoft cannot reproduce this.

Please re-read the ticket. You were still claiming in October that this is specific to "UNIX based systems".

It is simply a matter of changing keyboard layout to a keyboard with diacritical marks and you will notice that inline code snippets no longer work.

If you think you know the reproduction conditions, thanks for indicating them in the description. But as previously mentioned at least as far as October, using a layout with diacritics does not suffice to reproduce.

[Chealer]

@Chealer I beg to differ too. I was the one who spotted the problem being keyboards with diacritical marks and I provided enough evidence (video + text) on my Aug/11 comment for anyone to be able to reproduce it. Therefore I do not agree that "reproduction conditions remain largely undetermined".

This is further confirmed by the numerous comments that came after that from people all over the world describing the same problem with their specific language/keyboard configurations.

...and refuted by comments from people indicating they do not necessarily experience the problem with a layout having diacritics, such as that one.

Both of the last 2 PCs on which I used Teams are unaffected using CAN/CSA Z243.200, even though they're on different Windows versions.

[vancromy]

@Chealer I beg to differ too. I was the one who spotted the problem being keyboards with diacritical marks and I provided enough evidence (video + text) on my Aug/11 comment for anyone to be able to reproduce it. Therefore I do not agree that "reproduction conditions remain largely undetermined".

This is further confirmed by the numerous comments that came after that from people all over the world describing the same problem with their specific language/keyboard configurations.

...and refuted by comments from people indicating they do not necessarily experience the problem with a layout having diacritics, such as that one.

Both of the last 2 PCs on which I used Teams are unaffected using CAN/CSA Z243.200, even though they're on different Windows versions.

As far as I can tell, you are the only one claiming that and referring to yourself is not evidence enough of "several". There are over 100 comments of people claiming the same thing as was identified early on and all have the common theme of international keyboards.

I also promptly changed my standpoint after your report and confirmed on a windows VM that it wasn't working as well. Something which I directly responded to when you initially posted. Note also that I mentioned Windows in my earlier post today.

I just tested again today simply changing my keyboard layout back to GB and it was working again proving both that it can easily be reproduced and that it is most likely due to diacritical marks.

I don't think it's helping that you are claiming this cannot be reproduced when that is simply not the case. Let's work together to get MSFT to fix this!

[Chealer]

@Chealer I beg to differ too. I was the one who spotted the problem being keyboards with diacritical marks and I provided enough evidence (video + text) on my Aug/11 comment for anyone to be able to reproduce it. Therefore I do not agree that "reproduction conditions remain largely undetermined".

This is further confirmed by the numerous comments that came after that from people all over the world describing the same problem with their specific language/keyboard configurations.

...and refuted by comments from people indicating they do not necessarily experience the problem with a layout having diacritics, such as that one. Both of the last 2 PCs on which I used Teams are unaffected using CAN/CSA Z243.200, even though they're on different Windows versions.

As far as I can tell, you are the only one claiming that and referring to yourself is not evidence enough of "several".

Sorry but I don't understand (Who talked about "several"? Several what?)

I also promptly changed my standpoint after your report and confirmed on a windows VM that it wasn't working as well. Something which I directly responded to when you initially posted. Note also that I mentioned Windows in my earlier post today.

Nobody claimed you hadn't. What I wrote is that the conditions you described are incorrect; typing using a layout with diacritics does not suffice to reproduce (unless the given environment already satisfies still undetermined conditions).

I just tested again today simply changing my keyboard layout back to GB and it was working again proving both that it can easily be reproduced and that it is most likely due to diacritical marks.

Finding a workaround for a bug unfortunately does not mean it can easily be reproduced :-(

I don't think it's helping that you are claiming this cannot be reproduced when that is simply not the case.

Again, please re-read. If someone claimed this cannot be reproduced, that's certainly not me. Spreading misinformation is certainly not helping.

Let's work together to get MSFT to fix this!

If you want "MSFT" to fix this, you could start by providing accurate (and ideally complete) information. If you expect something from others, please specify.

[sidbena]

Instead of turning this thread in to a ”he said, she said”, perhaps we can focus on identifying the underlying issue.

Perhaps I've misunderstood the way to reproduce this, but this is my situation: I'm running on Windows 11, with English (US) as display language but a Swedish keyboard layout (which uses diacritics, such as å, ä and ö), and also does not directly type the character `. I.e. I need to press space to show the character. This combination works ”straight out of the box”, i.e. I can simply type the ` character (with space if I type a ”diacriticable” letter after, or without space for a ”non-diacriticable”) and then my code, and finish with a ` and it is correctly turned in to an in-line code block – as expected.

I also have a Mac, this time with English (UK) language, and Swedish keyboard (again, with diacritics). The keyboard acts the same in general as for my Windows machine. Here the in-line code blocks never work, regardless of keyboard layout. I've tried Swedish (default), English (ABC), English (ABC – Extended), British – PC and a few others. The only way I get it to work on my Mac, is using U+0060 from Character Viewer. Writing one of these, some other text, and another of these turns the block in to an in-line code block – as expected. Using the button shift+´ (next to backspace with a Swedish keyboard layout) seems to write a ”modifier letter grave accent” (U+02CB).

I'm not sure this will help with troubleshooting this in any way, but there might be several issues seemingly posing as similar issues.

Versions: Windows 11 (23H2, build 22635.3286) with Microsoft Teams version 24033.811.2738.2546 (client version is 49/24020205515) macOS 14.3.1 (23D60) with Microsoft Teams version 23335.208.2601.834(preview) (client version is 50/24020205511)

[tirolerstefan]

Hi there, sorry if I'm confusing this discussion with another related issue.

On Linux (Ubuntu 22.04), German keyboard (set up with no dead keys - so, backticks are working without space) and using the Edge progressive web app (or also the web app in Firefox), the inline code works for one line, but not for multiline snippets :-(.

When I select multiple lines and click on "Monospaced" from the menu, this happens:

[oliverw]

Still broken in Windows 11 Teams App using German Keyboard.

[Chealer]

Occurring on Windows as well using a uk layout keyboard.

Please detail your configuration @eglavin . @bit2shift reported that switching to the UK keyboard layout allowed to work around. Are you using the United Kingdom Extended layout or the standard one?

[Chealer]

Here is a list of keyboard layouts with dead keys.

[Chealer]

Hi @ChetanSharma-msft,

[...]

The workaround provided by the engineering team does not fix this issue which is to use inline typing/shortcuts to write code in a message. If I wanted to click myself around Teams all day I would not have opened this issue...

The toolbar workaround doesn't actually require clicking. It is keyboard-accessible... but it is way longer than what it used to take. 😒

Providing specific keyboard structure solutions is also not a very sustainable and long term solution. Should the whole world migrate to either a US or German keyboard just because the engineering team does not fix this issue?

You're misunderstanding. @ChetanSharma-msft was providing a workaround for German layouts. In other words, the German layout is affected.

[...]

[Chealer]

This seems localized specifically to the Mac behavior. A workaround for Mac can be to just use the UI toolbar:

@ChetanSharma-msft You're suggesting "Monospaced" ("À espacement fixe" in French, or "à chasse fixe" or "à largeur fixe") as a substitute for what your documentation calls "Inline block of code". Are these really the same? Their effect does look the same to me, but "Monospace" is just a font property and doesn't imply any highlighting (different background color). I recommend rectifying the UI and/or the documentation if these are really equivalent.

[Chealer]

I cannot reproduce this (with a Microsoft Natural Ergonomics 4000 French Canadian keyboard) using the CAN/CSA Z243.200 layout, either on:

1. Windows 10, Teams desktop 1.7.00 (Dell Latitude)
2. Windows 10, Teams classic web app in Firefox 123.0.1 (Dell Latitude)
3. Windows 10, Teams classic web app in Microsoft Edge 122.0 (Dell Latitude)
4. Windows 11 (23H2), Teams classic web app in Firefox 123.0.1 (Lenovo ThinkPad)

However, in the very same environment as #4 (same computer, same Windows profile, same Firefox profile, even same browser launch), I can reproduce using the German layout.

[Chealer]

Hi there, sorry if I'm confusing this discussion with another related issue.

On Linux (Ubuntu 22.04), German keyboard (set up with no dead keys - so, backticks are working without space) and using the Edge progressive web app (or also the web app in Firefox), the inline code works for one line, but not for multiline snippets :-(.

The documentation for multiline snippets doesn't make much sense to me, but for sure it's not easy to use with CAN/CSA Z243.200. I don't know if these are related issues, but thanks for mentioning. I assume you're referring to xkeyboard-config's nodeadkeys German variant ("German (no dead keys)")?

[Chealer]

Is anyone affected able to reproduce this with the CAN/CSA Z243.200 keyboard layout (Canadian Multilingual Standard in Windows, Canadian multilingual in Debian)?

[tirolerstefan]

Hi there, sorry if I'm confusing this discussion with another related issue. On Linux (Ubuntu 22.04), German keyboard (set up with no dead keys - so, backticks are working without space) and using the Edge progressive web app (or also the web app in Firefox), the inline code works for one line, but not for multiline snippets :-(.

The documentation for multiline snippets doesn't make much sense to me, but for sure it's not easy to use with CAN/CSA Z243.200. I don't know if these are related issues, but thanks for mentioning. I assume you're referring to xkeyboard-config's nodeadkeys German variant ("German (no dead keys)")?

$ setxkbmap -print
xkb_keymap {
    xkb_keycodes  { include "evdev+aliases(qwerty)" };
    xkb_types     { include "complete"  };
    xkb_compat    { include "complete"  };
    xkb_symbols   { include "pc+at(nodeadkeys)+us:2+inet(evdev)+level3(ralt_switch)"    };
    xkb_geometry  { include "pc(pc105)" };
};

To be precise, it's Austrian, but yes - with "nodeadkeys" configured.

[tirolerstefan]

Is anyone affected able to reproduce this with the CAN/CSA Z243.200 keyboard layout (Canadian Multilingual Standard in Windows, Canadian multilingual in Debian)?

This took a while until I found the backticks in this layout ;-).

[Chealer]

Thank you @tirolerstefan but are you saying you can reproduce the issue with inline code snippets with CAN/CSA Z243.200? Your screenshot seems to show the closing character is a typewriter apostrophe.

I am posting again the exact procedure I use to try reproducing on CAN/CSA Z243.200. In a new (empty) message:

1. Hold AltGr
2. Press the caret (dead) key (immediately right of P)
3. Release AltGr
4. Press x
5. Hold AltGr
6. Press the caret key
7. Release AltGr
8. Press Space (for example)

[tirolerstefan]

This was really weird, the backtick was transformed to this apostrophe as I typed it.

[tirolerstefan]

Thank you @tirolerstefan but are you saying you can reproduce the issue with inline code snippets with CAN/CSA Z243.200? Your screenshot seems to show the closing character is a typographic apostrophe.

I am posting again the exact procedure I use to try reproducing on CAN/CSA Z243.200. In a new (empty) message:

1. Hold `AltGr`

2. Press the caret (dead) key (immediately right of P)

3. Release `AltGr`

4. Press `x`

5. Hold `AltGr`

6. Press the caret key

7. Release `AltGr`

8. Press `Space` (for example)

Sorry, my fault. I took the forward ticks!

Here a screenshot with the backticks (after setxkbmap ca multix).

[tirolerstefan]

Additionally, I switched back to Austrian layout with "nodeadkeys":

And now I recognized what I did wrong - I have to press Space after the three backticks. I always pressed Shift+Enter...

[victor-marino]

Hi, I found a workaround on MacOS :

1. In the Keyboard settings, bind the **Show Emoji & Symbols** action on the `Fn` key
   ![image](https://private-user-images.githubusercontent.com/50028809/268295457-cab7712a-6a8a-4447-993b-965826a4adb8.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTExMDE2NTUsIm5iZiI6MTcxMTEwMTM1NSwicGF0aCI6Ii81MDAyODgwOS8yNjgyOTU0NTctY2FiNzcxMmEtNmE4YS00NDQ3LTk5M2ItOTY1ODI2YTRhZGI4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDAzMjIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwMzIyVDA5NTU1NVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBmZDdkMzQ3MWY3MTQ2ZTgyNmRlMjFjNTM2YzdjZjliOGYzYjczZGU4ZmU2NGJmNGJkNzkyYWIzZTMwYmJhY2ImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.Z1RjBpFiNu7ijRkejvsdnnZ83TNYznsrFeAlyyWGRjU)

2. In Teams, when writing, hit the `Fn` key to show the emoji window, and click the little toggle on the top right to expand the window :
   ![image](https://private-user-images.githubusercontent.com/50028809/268295736-3503d4ba-1075-4f6d-85e7-43a4ce62f4e6.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTExMDE2NTUsIm5iZiI6MTcxMTEwMTM1NSwicGF0aCI6Ii81MDAyODgwOS8yNjgyOTU3MzYtMzUwM2Q0YmEtMTA3NS00ZjZkLTg1ZTctNDNhNGNlNjJmNGU2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDAzMjIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwMzIyVDA5NTU1NVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBkZjMwNjI3N2M1MWFhYmVlYzM3MjFkZjdkOTIxZjQ2NzFkMWFhYThhNTRlN2VmNmVkZDliMDE2OTg1NTA1YWYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.hIAeHVGewoVLjpgYJeks83IzSnsRuZ7NdPc9ZmvQGxE)

3. Look for the backtick in **Punctuation** category, and double-click on it to insert it
   ![image](https://private-user-images.githubusercontent.com/50028809/268295945-7b1d51a4-6a7e-4ad8-acd9-5dc91d97df8d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTExMDE2NTUsIm5iZiI6MTcxMTEwMTM1NSwicGF0aCI6Ii81MDAyODgwOS8yNjgyOTU5NDUtN2IxZDUxYTQtNmE3ZS00YWQ4LWFjZDktNWRjOTFkOTdkZjhkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDAzMjIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwMzIyVDA5NTU1NVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTczODAxNGM3NjE5MDRjMTQ3MWQ4OTMwNDBmZWY0MzAzYzk0NGI2NWEyMzJiNzQzMGJkZWU3YTc5YjEzZDY2YzQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.1AOywWehVtRlOoPIqVp9p3G-TA6jb95KvpqACLLy4lo)

Those backticks should be processed correctly by Teams Later, hit Fn key to toggle the symbols window on/off again (it will stay expanded), then you'll find the backtick directly in the Favourites section.

Hope it will help some of you until this is fixed :-)

Hey @arnauddohogne.

I've been facing this issue with a keyboard with Spanish layout for a long time now, and I just came across your excellent workaround. Thanks for this!

Now this got me curious, and I was trying to find a way to improve on the workaround. I found you can use MacOS built-in text substitution system to make this a little less painful. For instance, you can add a substitution from ` to (or from any other string that you think won't interfere with your regular typing).

Now, whenever you type `, you'll see a pop-up offering you the option to insert instead. All you have to do is press space and the substitution will be done:

I think this is a bit faster/less cumbersome than the emoji method!

[Chealer]

Sorry, my fault. I took the forward ticks!

Here a screenshot with the backticks (after setxkbmap ca multix).

[...]

I assume you're saying you reproduced with CAN/CSA Z243.200 then, thanks @tirolerstefan .

Can someone affected using Windows (ideally version 10) indicate the result of trying to reproduce with CAN/CSA Z243.200?