add support for custom language mapping to hard-coded string extraction

Describe the solution you’d like: Would like to have an config option to map .svelte files to the html parser of hard-coded string extraction, it should work with no issue since they are just html files with <script> & <style> tags, which can be excluded already

[alexanderniebuhr]

I will open any findings in a new issue. Nevermind about the extracted strings, can’t reproduce it anymore.

[alexanderniebuhr]

Not having a public one for now (working on one in private repo), can attach it later this week, since it is going public by then. However, a Svelte file with internationalization would look similar like

<script>
  import { _ as t } from 'svelte-i18n'
</script>

<div>
  <f-button class="bg-light-300" on:click={(e) => handle365Login(e)}>
    {$t('page.login.ms365')}
  </f-button>
  <f-button class="bg-light-300" on:click={(e) => handle365Logout(e)}>
    {$t('page.logout.ms365')}
  </f-button>
  <f-button class="bg-light-300" on:click={(e) => handle365Logout(e)}>
    Text to extract
  </f-button>
</div>

<style>

</style>

this is an example by svelte-i18n

<script>
  import { _ } from 'svelte-i18n'
</script>

<h1>{$_('page.home.title')}</h1>

<nav>
  <a>{$_('page.home.nav', { default: 'Home' })}</a>
  <a>{$_('page.about.nav', { default: 'About' })}</a>
  <a>{$_('page.contact.nav', { default: 'Contact' })}</a>
</nav>