Update tools.md

[felixhaeberle]

Hey @kazupon,
hope you are doing good☀️

We recently renamed our VS Code extension to "Sherlock" and made the ecosystem experience even better.
Let me know what needs to be changed in order to merge this.

Have a nice day!:)
Greetings from 🇩🇪

[kazupon]

And, I noticed that there was no mention of vue-i18n in inlang vue docs.
https://inlang.com/c/vue

In the react docs, there are plugins for i18next and next-intl.
https://inlang.com/c/react

3rd Party Tooling is the section for use vue-i18n or put tools that work with vue-i18n.
Why is there no vue-i18n in your docs or not use vue-i18n ?

[felixhaeberle]

@kazupon Sorry, I think the vue-i18n entry got lost with an update – we will fix it.

@NilsJacobsen Can we please re-add vue-i18n to the the inlang marketplace?

[felixhaeberle]

Issue to readd vue-i18n opral/inlang.com#84 to inlang marketplace.

[kazupon]

sorry, I also missed about having this page. There it mentions vue-i18n.
https://inlang.com/m/r7kp499g/app-inlang-ideExtension/supported-i18n-libraries

However, I would like to see a small mention of vue-i18n on the Vue page.
I also think inlang is a great tool. I would like to be part of the ecosystem, working on the same i18n issues.

[kazupon]

And, If possible, we would also like hopely to put about nuxt i18n, which integrates vue-i18n.

[felixhaeberle]

@kazupon I talked to the team and we removed the entry in order to achieve first-class support through a dedicated plugin we are building both for vue-i18n & nuxt-i18n. So this was probably a bit too early for us to remove the listing but will have a comeback with dedicated first-class plugin.

Progress can be tracked here:

• plugin support | vue-i18n | https://github.com/intlify/vue-i18n opral/inlang-sherlock#70
• plugin support | nuxt-i18n | https://github.com/nuxt-modules/i18n opral/inlang-sherlock#71

Btw, this is not only Sherlock (VS Code extension) related. With a plugin the library/content gets enabled to be part of every inlang app in the inlang ecosystem.

[kazupon]

@felixhaeberle
Thank you for considering putting vue-i18n and nuxt-i18n in inlang.
We hope the issue will be realized.

With a plugin the library/content gets enabled to be part of every inlang app in the inlang ecosystem.

I wonder what that means. Does it mean that vue-i18n and other i18n libraries will be imported as inlang apps and disappear like this issue situation? 🤔

[felixhaeberle]

I wonder what that means.

An inlang plugin is a connector to the ressource files & markup used in a vue-i18n / nuxt-i18n project. vue-i18n & nuxt-i18n users can then profit from all inlang apps because inlang apps "understand" the code & ressource files used + can then also modify them through apps (like Sherlock).

[kazupon]

Thank you for your explanation!
Okay, I belive that your efforts will return for those involved in i18n libraries and toolings :)