Overriding component translations

[paul-blundell]

As #56 has been closed and ignored now for over 2 years I wanted to create a new feature request in the hopes of getting the authors attention for this.

Being able to override component defined locales would be incredibly useful, and others seem to agree. The main use case being that you have built a reusable component and that component defines a number of strings, however it is very likely that users of that component might want to change one of those. We have several clients using the same components and a few of them have already asked for certain strings to be worded differently.

[exoego]

I started using a vue-i18n recently and opening Pull Requests for new features, optimizations and bug fixes. Kazupon, the creator of this awesome OSS, reviewed and merged the recent PRs promptly.

He is one of Japan's Vue.js community organizer and an author of the recently-published Vue book in Japan. So I think he just lacked his time to implement new feature this past year.

He is very welcoming to contribution. If someone really needs this feature, it is a good opportunity to try implement. Vue-i18n is well-designed and have a fast and robust test suite, so a new contributor may not need a long time to start contribution.

I agree this feature has use-cases, but I am unlikely to open PR for this, since I am not a heavy user of Vue component.

[lucpotage]

Hi @paul-blundell. The plugin vee-validate relies on vue-i18n for the localization and allows to add a custom dictionary that overrides the default one. I think it's what you are looking for. I just browsed the code base and the function merge (dictionary) should raise your interest:

https://github.com/baianat/vee-validate/blob/master/src/localization/i18n.js#L98

I hope you will find this workaround useful even though it's not the default feature you expect in vue-i18n.

[akszydelko]

Hi guys, we have faced the same issue, where we have a core project used as a base for other projects and we needed to override some core components translations. As there is no easy way to do it with vue-i18n, after some research we decided to go for a custom translation loader for Webpack. We have open sourced the solution, so feel free to check it out and propose modification, if that will not fit your use case.

https://github.com/infermedica/object-override-loader

It turned out to be more general purpose loader to override JSON/YAML resources during the compilation. It does not interfere with other loaders like @kazupon/vue-i18n-loader or yaml-loader.

[NullObjectDev]

Hello,

I was hoping to bump this issue up on the agenda since it is also a feature for our use-case. We are currently rewriting a big enterprise application written in GWT in Vue3 by progressively replacing the components from the inside out. We already have the feature that clients can upload their own custom labels that override our labels in the internationalization in the GWT App and need the same feature in the Vue3 App, preferably natively as part of vue-i18n.

Greetings

[johnantoni]

any news on this? it would be extremely useful to override component based translations, especially for white-labelling