Stance upon markdown

[JeffreyArts]

Hi,

I was wondering what the the stance is upon the inclusion of markdown. Let's take the following desired outcome as example;

<p>
    This project is made with <a href="https://vuejs.org/" target="_blank">VueJS</a>, <a href="https://vue-i18n.intlify.dev/">Vue-i18n</a> and various <strong>other packages<strong>
</p>

According to the documentation, this is the desired workflow:

const messages = {
  en: {
    paragraphPart1: 'This project is made with ',
    paragraphPart2: 'VueJS ',
    paragraphPart3: 'Vue-i18n ',
    paragraphPart4: 'and various ',
    paragraphPart5: 'other packages '
  }
}

<p>
    $t('paragraphPart1') <a href="https://vuejs.org/" target="_blank">$t('paragraphPart2) </a>, <a href="https://vue-i18n.intlify.dev/" >$t('paragraphPart3') </a> $t('paragraphPart4') <strong>$t('paragraphPart5')<strong>
</p>

This workflow is frictional for both the translator (for missing the context/structure of translating these texts) as well as the developer (hard to read, cluttered codebase)

Mardown interpretation

const messages = {
  en: {
    paragraph: 'This project is made with [VueJS](https://vuejs.org/){:target="_blank"}, [Vue-i18n](https://vuejs.org/)  and various **other projects**',
  }
}

<p>
$t('paragraphPart')
</p>

Markdown seems like a wonderful solution to this, yet this Vue component (which exists for multiple years) does not support this. I was wondering why this is.