Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IDEA] Vue i18n integration #62

Open
raulghm opened this issue Apr 4, 2017 · 1 comment
Open

[IDEA] Vue i18n integration #62

raulghm opened this issue Apr 4, 2017 · 1 comment

Comments

@raulghm
Copy link

raulghm commented Apr 4, 2017

Could be a useful idea an integration with this package https://github.com/kazupon/vue-i18n

I'am using and generate a JS object with https://github.com/martinlindhe/laravel-vue-i18n-generator, but the call of key for translate is some like this $t('message.hello') and the the workflow for include the key is manual, not like the easy command php artisan langman:sync.

Example in Vue template file:

<div class="message">
    <p>{{ $t('message.hello', {name: 'visitor'}) }}</p>
</div>

It's just an idea, if you need more details let me know ;)

@lsmith77
Copy link

I think what would help is if \Themsaid\Langman\Manager::getAllViewFilesWithTranslations() would move the $functions and $patterns to a config variable.

I am using this syntax proposed here https://github.com/kg-bot/laravel-localization-to-vue#some-examples-why-would-you-use-this-package-and-messages-over-laravel-standard-localization which again is slightly different.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants