You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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>
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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I was wondering what the the stance is upon the inclusion of markdown. Let's take the following desired outcome as example;
According to the documentation, this is the desired workflow:
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
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.
Beta Was this translation helpful? Give feedback.
All reactions